The Container That Arrived in Only One System

The story

05:31–05:42 — the container arrives in only one system

At 05:42, Blue Current Lines reports invented container DEMO-BOX-017 discharged. Elena Park is responsible for deciding whether the consignee may authorize dispatch for its 07:30–07:45 pickup appointment, but Alder Gate Terminal's latest record has neither a grounded state nor a stack location. Sending the truck on partial evidence risks a dry run; waiting could surrender a still-recoverable appointment.

Earlier that morning, Quaystone Brokerage supplied its received regulatory-release assertion and Blue Current supplied its freight-release assertion. Those two gates pass, but neither source establishes physical availability. The container has arrived in the carrier system only. Dispatch remains blocked on terminal-owned evidence, and Grid cannot turn either participant's partial truth into universal permission to move cargo.

05:48 — an appointment cannot repair a missing location

Lantern Motor Freight publishes appointment APT-731: a confirmed pickup slot from 07:30 through 07:45. That slot answers when a pickup might be presented. It does not answer whether Alder Gate Terminal has grounded the box or where it sits.

Grid refuses the tempting shortcut from “discharged, released, and appointed” to “send the truck.” Appointment validity and physical availability are different dimensions.

05:52 — three bounded alternatives expose the stopping point

The model compares exactly three authored responses:

Alternative	Result	Why
Dispatch now from the partial packet	Rejected	Terminal grounding and location are absent.
Hold the driver assignment while retaining the appointment	Conditional	It preserves the slot but still requires current terminal evidence before dispatch authorization.
Cancel and request a later appointment immediately	Feasible proposal	It reduces dry-run exposure but gives up a recoverable window and requires Elena's external authority.

The conditional hold is the authored preference because the evidence may still arrive in time. Preferred does not mean authorized.

06:18 — the terminal supplies the missing fact

Alder Gate publishes TER-516: grounded at 06:07, stack location B14-07, zero active holds, observed at 06:18, and valid through 06:28.

The release, physical, and appointment predicates all pass. The authority state remains not-requested. A complete readiness packet can now be reviewed; the result does not dispatch a driver or guarantee interchange.

06:20–06:23 — old delivery cannot move time backward

The adapter receives CAR-8841 again and then receives older terminal revision TER-514 after TER-516. The duplicate discharge does not create a second event. The older terminal record remains inspectable but cannot replace the accepted newer revision, and a late receipt cannot make an old observation current.

At 06:23, terminal correction TER-517 reports grounded state, zero holds, an observation time of 06:23, and validity through 06:33 while changing the location from B14-07 to B14-09. Only the location-dependent driver instruction and map callout become stale. Release state, appointment identity, and the immutable TER-516 history remain intact. Accepting a correction creates no authority.

06:34–06:38 — evidence expires, refreshes, and stops at authority

The terminal feed degrades. By 06:34, its last observation is eleven minutes old—one minute beyond the authored ten-minute validity rule. Grid retains B14-09 as the last known location while setting pickup_eligible = false and explaining HOLD / REFRESH REQUIRED. A reconnect or cache timestamp cannot become a terminal observation.

Revision TER-518 arrives at 06:37 with grounded state, B14-09, zero holds, and validity through 06:47. Elena then signs authorization DISPATCH-AUTH-204 for exact packet PICKUP-204, binding the current broker, carrier, terminal, and appointment revisions to that expiry. Lantern's dispatch system acknowledges request DSP-611 at 06:38. That acknowledgement is not driver departure, gate interchange, or receipt.

07:38–09:12 — external reports close different loops

Alder Gate's GATE-992 reports pickup at 07:38, inside the appointment window. North Orchard Appliances' RCV-404 reports receipt at 09:12.

The evidence line remains explicit:

proposal → human authorization → dispatch request acknowledged → terminal pickup reported → consignee receipt reported

Current terminal evidence and Elena's exact authorization made the dispatch request permissible; pickup and receipt became facts only when their owning systems reported them. No earlier state is relabeled as a later one. These authored reports do not prove the model was correct, establish a real logistics outcome, or authorize one participant to speak for another.

Why this setting is recognizable

The U.S. Department of Transportation's Freight Logistics Optimization Works program describes a public-private effort using aggregated information from cargo owners, carriers, ports, terminals, and railways to improve a broader view of supply-chain conditions. U.S. Customs and Border Protection's ACE materials publish distinct technical and reference material for manifest, Cargo Release, post-release, status, cancellation, recordkeeping, and downtime processes. The Federal Maritime Commission's detention and demurrage billing rule summary describes billing roles, timing, disputes, and required invoice information in a context where container availability can matter.

Those official sources ground only the multi-party freight context and the need to keep institutional meanings distinct. They do not establish this container, its statuses, the ten-minute rule, the preferred alternative, a Grid integration, a charge, permission to move cargo, or any outcome.

Where the model stops

Grid can represent selected source revisions, order, freshness, contradiction, correction, declared alternatives, an exact decision packet, and later external evidence. It cannot originate customs or freight release, invent a terminal location, book or alter an appointment, dispatch a driver, grant gate access, transfer custody, waive a fee, or declare delivery.

The page contains no real container number, bill, vessel, voyage, commodity, customer, driver, facility coordinate, terminal layout, credential, interface secret, or live movement instruction. The identifier DEMO-BOX-017 is deliberately not a valid ISO container number.

What remains to prove

Source revision 2026-08-27.1 has reviewed domain context, product boundaries, and a public-suitability finding, so this authored page can be published at R2. The fixture itself remains authored.

The next proof is an exact deterministic implementation of the five narrow contracts, the conjunctive gates, ten-minute freshness rule, duplicate and out-of-order delivery, B14-07 to B14-09 correction, eight source and decision revisions, three alternatives, authority stop, and separate dispatch, gate, and receiving reports. It needs a separately identified independent oracle reviewer, negative cases, and retained execution and verification evidence. Intended-environment work would additionally require participant-owned semantics, identity, delegation, security, records, contractual controls, reconciliation, and qualified integrations. None of that can turn this editorial fixture into customs advice, a terminal instruction, or authority to move cargo.