1 · Package
NO PACKAGE
Discovers declared endpoints, moves A25-compatible envelopes, carries destination intake responses back, queues unavailable deliveries, supports operator-controlled retry/reroute, custody tracking, replay detection, and integrity-chained transport evidence without interpreting project payloads.
NO PACKAGE
NO ROUTE DISCOVERED
Courier stages the envelope unchanged. A destination may accept, reject, or preserve it. Operator approval is required before direct HTTP delivery.
NOT STAGED
NO DESTINATION RESPONSE
NO RECEIPT GENERATED
Local operator registry only. It stores URLs and discovered declarations; it is not network authority.
EMPTY REGISTRY
Packages stay preserved when a node is unavailable. Retry or reroute only happens when the operator chooses it.
EMPTY QUEUE
Append-only local chain of outbound, retry, reroute, destination-response, and return legs.
NO CHAIN
Tracks package custody, detects previously staged package hashes, fingerprints declared endpoint identities, and verifies chained transport legs.
NO ENDPOINT IDENTITY EVIDENCE
NO REPLAY CHECK
NO CUSTODY RECORD
Local transport mailboxes track outbound custody, imported destination acknowledgements, completion state, and recovery checkpoints without interpreting payloads.
INBOX: 0 · OUTBOX: 0 · COMPLETED: 0
NO ACKNOWLEDGEMENT SELECTED
Local courier safeguards only: endpoint observations, package age, operator-set delivery constraints, and explicit stale-package decisions.
NO HEALTH OBSERVATION
NO DELIVERY POLICY
NO STALE SCAN
Purpose: neutral A25-0.1 envelope transport. Payload interpretation: NONE. Network authority: NONE.
Flow: load → verify → discover → stage/queue → operator approve → deliver/handoff → acknowledgement → return/result → receipt chain.
Recovery: unavailable, stale, held, rejected, preserved, or unresolved packages remain operator-visible until explicitly removed.
Checkpoint: export a checkpoint before deployment changes or destructive local returns.