Make local page admission resistant to duplicate retries — what should the operator record?
A received page may be processed twice after an interruption even when the remote request was not repeated. Keep local admission state separate from receipt storage. The goal is to admit the same eligible evidence once under a declared identity rule while preserving repeated observations and conflicts when they matter operationally.
Use receipt and key ledgers so repeated processing cannot silently double the working membership.
Use chain_ref, receipt_ref and qualified_source_key to distinguish processing state from evidence identity. A receipt is an observation container, while a source key identifies the object under your declared grain; one should not be silently substituted for the other.
Record the resulting table revision and actual admitted keys after validation. If the local write is interrupted, reconcile ledger and artifact state before retrying instead of assuming either that nothing happened or that every received row was already committed.Define admission identity
Use chain_ref, receipt_ref and qualified_source_key to distinguish processing state from evidence identity. A receipt is an observation container, while a source key identifies the object under your declared grain; one should not be silently substituted for the other.
Record the admission decision
For each row, retain admitted, duplicate-observation, conflict or invalid-key with the permitted source reference. Do not merely mark the entire page processed when some rows failed validation and still need a specific review or retry decision.
Test repeated processing
Run a labeled page fixture through the local append twice and compare accepted membership. The second pass should not double admitted objects, while the processing ledger can still show that the receipt was inspected again after an interruption.
Review changed observations
If a repeated key carries different fields, route that difference according to the observation contract rather than dropping it as a duplicate automatically. A source object can remain the same while its returned descriptive or metric values change between receipts.
Commit with evidence
Record the resulting table revision and actual admitted keys after validation. If the local write is interrupted, reconcile ledger and artifact state before retrying instead of assuming either that nothing happened or that every received row was already committed.
Keep the boundaries clear.
- Use receipt and key ledgers so repeated processing cannot silently double the working membership.
- Operational record: Define admission identity. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.