Last updated September 18, 2026
4 min read
A fictional agent pauses on Friday because a refund rule needs product approval. On Monday, another provider resumes from chat history, misses the rejected option, and edits the wrong service. The pause worked. The resume contract did not. This is an explicitly fictional composite, used to expose a repeatable engineering decision without inventing a customer result.
In this article
A pause is a state transition, not a conversation break
Store the workflow ID, feature ID, current stage, specification digest, repository revision, changed file set, completed checks, and known failures. Without these fields, the next session reconstructs state from prose and can silently reinterpret what already happened.
Lee and See on trust in automation helps bound this point. The paper supplies general human-factors guidance, not coding-specific prevalence.
| Lens | What to inspect |
|---|---|
| 1 | Chat memory: conversational |
| 2 | Workflow state: structured |
| 3 | Pause: no guessing |
| 4 | Resume: preconditions satisfied |
The numbers and labels above are a diagnostic, not benchmark data. Replace them with repository evidence before using the model in a staffing or investment decision.
The decision packet must be bounded
A decision packet should contain the question, why it blocks progress, available options, affected modules, risk of each option, recommended choice, decision owner, allowed edits while paused, and expiry. General trust-in-automation research supports calibrated authority rather than maximizing automatic acceptance.
The sequence matters because later evidence depends on earlier intent. Skipping one step transfers uncertainty to a reviewer who has less time and often less context.
Resume requires freshness and integrity checks
Before resuming, compare the stored repository revision and specification fingerprint with current state. Check whether the decision expired, an affected module changed, a newer decision superseded it, or someone edited files that were meant to stay frozen. A mismatch should create a new review point, not a best guess.
NIST AI Risk Management Framework adds a second boundary. This is voluntary risk guidance, not certification or proof of a product outcome.
The correction is deliberately procedural. A workflow can be inspected, rehearsed, and improved. A warning without an owner or artifact rarely survives the next busy sprint.
Test the contract across providers
Provider portability becomes testable here. Pause a sandbox feature under one host, transfer only the repository-owned state, and resume under another. The second host should identify the same stage, decision, allowed scope, and evidence gaps before editing. Record which guarantees each host can enforce.
paqad-ai v1.67.0 was the current public release when this article was verified on July 21, 2026. Its public repository describes local workflows, risk routing, specialist roles, deterministic checks, documentation sync, and audit records. Those are product mechanisms, not independent proof that a team will achieve a specific outcome.
Use the broader AI workflow audit guide to map the operating system, compare the evidence bar with production-ready AI code, and use the consultant selection guide when outside ownership is being considered.
The decision rule for this article is: Resume only when the approved decision is current and every stored fingerprint still matches the state it authorized.
Frequently Asked Questions
What if the repository changes during a pause?
Compare the stored revision and affected files with current state. If the change intersects the paused feature or invalidates evidence, reopen planning or review. Do not resume against stale assumptions.
Should every decision have an expiry?
Use expiry when context can change, such as temporary risk acceptance, model permission, or dependency choice. Stable architecture decisions may use an explicit invalidation event instead of a calendar date.
Can chat history remain part of the handoff?
Yes, as supporting context. It should not be the authority for stage, scope, decision, or evidence state. Those fields belong in structured repository-owned artifacts.
What next?
If this failure pattern exists in your repository, install paqad-ai and test the decision tool above on one real feature. Keep the evidence local, inspect provider permissions, and retain human authority for the final risk decision.