Reframe an AI Engagement

Turn a consequential field contradiction into a bounded decision that keeps delivery moving. Do not silently rewrite the brief, infer authority, or treat this engagement disposition as production approval.

Read first

1. Read Field Engagement and Accountable Reframing and the engagement-reframe schema.
2. Use the engagement-reframe record, field-observation log, and discovery pack.
3. Read the worked invoice engagement only as a teaching case, never as customer evidence.
4. Apply FDE-001, FDE-002, FDE-005, CTX-001, CTX-004, and DEL-002 from the control catalog.
5. If the reframe may affect a recurring solution, resolve the solution portfolio and read only the selected context after the disposition; it is not target evidence or authority.

Workflow

1. Preserve the inherited claim, exact source, revision, commercial status, and limitations without improving its wording.
2. Separately verify the sponsor, process knower, operator, disposition authority, and verifier. A person may hold several roles only with separate evidence or authority bases.
3. Bind the work to one engagement, customer or tenant, workflow, environment, evidence store, and retention policy. Stop on a missing or ambiguous boundary; never blend engagements.
4. Inspect one actual or sanitized recent representative case and a material exception. After each interaction, stage its source record, propose cited additions, preview them for named human confirmation, then append a dated receipt that preserves rejected or deferred items.
5. Classify consequential claims as sold, stated, observed, system_enforced, or policy_authorized. No class universally outranks another or grants authority.
6. Bound the conflict: affected workflow, outcome, human authority, data, acceptance evidence, economics, downstream work, and safe behavior while unresolved.
7. Prepare one cited reframe with inclusions, exclusions, retained authority, safe fallback, affected work, required decision, and next field move under each outcome.
8. Obtain a scoped continue_discovery, bounded_kickoff, defer, or stop disposition from the verified disposition authority. Bind the authority basis, exact passage, scope, rationale, and time.
9. Preserve chronology and propagate only dependency-linked changes. Leave unrelated revisions and digests unchanged; route stale work for review. Derive any sponsor readout from current receipts and governed records rather than maintaining a second narrative.

Output contract

Return:

• a current field brief with roles, representative evidence, limitations, and next move;
• the competing claims, cited conflict, safe fallback, and decision brief;
• a schema-valid engagement-reframe record with scoped human disposition or explicit missing authority;
• the affected downstream list with no_change, review_required, or supersede and preserved chronology;
• the current boundary and evidence required to reconsider it.
• the latest interaction receipt and a source-linked current readout when the request follows a field interaction.

Stop if the relevant evidence, process knower, or disposition authority cannot be established. Do not invent observations, approvals, acceptance, or target-system authority.