# Engagement Reframe Record

Use when field evidence materially contradicts an inherited brief. Never overwrite the inherited commitment.

For self-directed practice, use the [fictional claims-denial case](claims-denial-practice-case.md)
and the [field conversation kit](field-conversation-kit.md). Complete a first pass
before consulting the [annotated strong answer](claims-denial-annotated-answer.md).

## Inherited engagement

- Evidence mode: live field evidence / sanitized retrospective / synthetic practice:
- Evidence-mode limitation; synthetic work cannot prove customer disposition or
  authority:
- Engagement and workflow:
- Original commitment, quoted exactly:
- Source, revision, date, and passage:
- Commercial or delivery context:
- Current downstream outputs that depend on the commitment:

## Material contradiction

- Contested claim:
- Contesting evidence, exact passage, and digest or revision:
- Evidence basis: observed case / exact-build test / policy / assertion:
- Applicability and limitations:
- Why the contradiction changes scope, authority, evaluation, economics, or acceptance:

## Typed proposal

- Proposed reframe:
- Proposal status: open / accepted / rejected / stale:
- Included boundary:
- Explicit exclusions:
- Safe fallback while open:
- Affected outputs:
- Unaffected outputs:
- Evidence or event that would stale this proposal:

## Scoped disposition

For synthetic practice, complete this section as a proposed disposition exercise.
Do not claim that the fictional actor recorded a real customer decision.

- Decision: continue discovery / bounded kickoff / defer / stop:
- Named actor:
- Direct or explicitly delegated authority basis:
- Exact source passage supporting the decision:
- Scope of authority:
- Date and revision:
- Limitations and next review condition:

## Selective propagation

| Dependent object | Before revision | Required change | Currentness after decision | Why |
| --- | --- | --- | --- | --- |
|  |  |  | current / review required / superseded |  |

## Chronology

Record inherited commitment, evidence arrival, proposal, review, disposition, propagation, and any later invalidation as immutable events.

## Review gate

- The inherited claim remains visible.
- Both sides of the conflict are cited and bounded.
- The fallback does not require disputed authority.
- Rejection or deferral causes no downstream mutation.
- Acceptance updates only dependency-linked objects and preserves prior revisions.