FIELD NOTE / LINKEDIN
The recovery journal needs an owner.
The short film, the complete written thought, and the evidence behind it.
The LinkedIn conversation link will follow its public release.
The recovery journal needs an owner.
Video caption
The recovery journal needs an owner.
Identity and authorization stay outside editable summaries.
The agent gets enough to reconcile, not raw secrets.
My rule: The next run begins from an append-only event trail.
#EricFieldNotes
Full written post / accessibility read
When a model session ends after dispatch, the host needs an action history it controls. A new worker should consume that history, not reconstruct it from the previous worker's prose.
Before dispatch, persist the case ID, operation ID, principal, customer, target, precondition version and allowed outcome. Append attempt, service receipt, readback and owner handoff as separate events.
The workflow owns retention and access control. It gives the model the relevant action envelope and current observation. Credentials and unrelated customer data do not need to live in prompt replay.
Keep the journal immutable enough to audit, then make each resumer query current state before changing it. Do that because a session summary records belief; an owned event trail records what was attempted and observed.
#EricFieldNotes
Four-beat scene transcript
1. The recovery journal needs an owner.
When a model session ends after dispatch, the host needs an action history it controls. A new worker should consume that history, not reconstruct it from the previous worker's prose.
Visual: A replacement agent must not invent the prior action.
2. Protect the critical fields.
Before dispatch, persist the case ID, operation ID, principal, customer, target, precondition version and allowed outcome. Append attempt, service receipt, readback and owner handoff as separate events.
Visual: Identity and authorization stay outside editable summaries.
3. Expose a bounded view.
The workflow owns retention and access control. It gives the model the relevant action envelope and current observation. Credentials and unrelated customer data do not need to live in prompt replay.
Visual: The agent gets enough to reconcile, not raw secrets.
4. Make continuity a host property.
Keep the journal immutable enough to audit, then make each resumer query current state before changing it. Do that because a session summary records belief; an owned event trail records what was attempted and observed.
Visual: The next run begins from an append-only event trail.
Research and claim limits
- AWS Step Functions redrive (S214)
- Temporal Child Workflows (S216)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.