E.9.DA:4.6 - Compact result form

An ordinary bounded result is deliberately short:

E.9.DA bounded review:
  Exact DRR:
  Required authoring use and its source:
  Effective floor and source: <E.9.DA default 3 | predeclared higher floor and exact raising source>
  Actual-host evidence: <required only when a broad authoring rule is selected>
  Substantive result: <findings, including any answer-changing omitted question | repaired text | unchanged checked DRR when clean>
  Status:
  First drafting action or first repair: <include the applicable stop or return condition>
  Most expansive non-admissible overread?: <only when one is locally warranted>
  Reopen if:

This is sufficient when no named later use needs a reusable coordinate result. A clean focused review may point directly to the unchanged DRR and needs no separate clean ledger for the bounded omitted-question search. An inspect-repair-verify pass points to the repaired text and focused verification.

When a complete reusable coordinate evaluation is explicitly required, or a named later reliance needs exact result identity, extend rather than replace the bounded result:

E.9.DA reliance-bearing result:
  Exact DRR and effective ReferenceScheme:
  Required authoring use, its source, and qualification window:
  Effective coordinate floor map and source:
  CharacteristicSpace and evaluation-spec refs:
  Semantic evaluation Method ref, only when used by the receiving claim:
  A.6.1 assessment application and actual binding refs, only when used:
  A.13 performer-core and A.15.1 Work refs, only when dated U.Work is asserted:
  F.6 attribution refs, only when precise assignment-bound attribution is asserted:
  Evidence basis checked, including the bounded omitted-question search:
  Coordinate table: <Coordinate | Value | ShortRationale | EvidenceLocus>
  Precision-restoration reading and triggered exact checks:
  Witness and evidence-use refs actually used by the reliance:
  Status, first action or repair, bounded overread, and reopen condition: <include stop or return; overread only when independently grounded>

Only this reliance-bearing branch requires every coordinate and the exact identities its receiving use consumes. Method, application, and Work refs remain independently conditional; asserting dated U.Work requires the Method, application, every precise performer’s A.13 core, and independent A.15.1 admission from the branch in 4.2. F.6 is additionally required only when the result asserts precise assignment-bound attribution. A downstream status use, assurance, E.19 admission, authority, or drafting permission remains a separate claim with its own defining or constraining pattern.