KCAE.ENCOUNTER:5 - Archetypal Grounding
CedarBench already has an authorized weekly support handover. Its ordinary notes include compensating work after nominally successful exports. A designated engineer follows one entry to the receiving use and asks why a senior analyst removes duplicates. The original note and the customer’s faster-worker proposal remain distinct. Retrieval exposes the protocol condition; the useful first encounter is a small configuration question at that handover.
For an installation without a permitted event feed, this human occasion is the complete initial profile. Adding a retrieval skill to the helpdesk does not change that fact. Later, an authorized ticket hook can automate projection and inquiry, but its subscription, privacy boundary, receiver and quiet behavior must be constructed and tested.
For a constructed software case, CedarBench receives event E42 and operation version Q3. A database supports conditional claims and an atomic commit of the inquiry result plus an outbox intent. The inquiry only reads permitted, identified inputs; it does not directly send notices or modify the customer’s system. The dispatcher and recipient use E42/Q3 as the stable notice identity. These are stipulated capabilities to obtain from a real installation, not effects supplied by the record format.
| Arrival/failure case | Available state and next operation | Result and remaining boundary |
|---|---|---|
| Worker A claims E42/Q3, then crashes before storing a result. | The record is in progress and has no result. A real recovery invocation confirms A’s termination, conditionally acquires a new token, repeats the permitted read-only inquiry, then commits its result and one outgoing intent. | The inquiry is completed rather than silently abandoned. A late commit with A’s old token is rejected. If A might already have performed an uncontrolled effect, recover its status first or return unresolved instead. |
| A repeated delivery arrives while A’s claim is valid. | Return pending or defer according to the queue contract; do not acquire another live claim. The original invocation or the established recovery mechanism remains responsible. | No second inquiry is launched by this duplicate. A later expired claim follows the recovery case; pending is not reported as completion. |
| A repeated delivery arrives after result and completed state were committed. | Retrieve the stored result under the same event/input identity and current access rules. Reuse any existing outgoing intent. | No new inquiry or notice intent is created. A lost display acknowledgement still leaves receipt unknown; the result record does not prove display or use. |
Now remove one stipulated capability: the first worker sends a non-idempotent external notice before saving its result, and the receiver cannot reveal whether it displayed it. A crash then leaves possible delivery with no reliable receipt. Automatic replay is not licensed by the absent local result. Preserve that uncertainty and use the agreed reconciliation or human decision. Restoring automatic recovery requires moving publication behind the guarded outbox construction or obtaining a receiver operation whose repeated effect is controlled.