Skip to content

Reader-facing premise audit of root_soundness: classify InputsAgree/SailTrace fields, document the irreducible-trust core #184

Description

@codygunton

Goal

The legibility deliverable for root_soundness, distinct from the derivation
work (#141 / #115 / #119 / #151). Make the theorem's premise list readable as a
clean trust boundary: every binder is visibly one of

Scope

  1. Audit every field of InputsAgree / SailTrace / RowOutsideDefectRegion
    consumed by root_soundness; tag each (a)/(b)/(c).
  2. Document the irreducible core (the (a) set) in the root_soundness
    docstring as the trust boundary a reader must accept, with a one-line
    justification each (why it cannot come from the circuit alone).
  3. For each (c) field still carried as a premise, link the issue deriving it so a
    reader sees it is dischargeable, not load-bearing trust.
  4. Cross-check against the trust gate: the documented (a) set should match what
    actually appears in the audited axiom/binder closure.

This produces the reader-facing artifact that makes "a human reads the statement
and is convinced" true, even where #141/#115/#119 derivations are still in flight.

Acceptance

  • root_soundness docstring enumerates the irreducible-trust premise core with
    justifications, and labels every other premise as derived-or-tracked.
  • A short trust/ note (or section) cross-referencing binders ↔ trust classes.
  • No code/proof change required (documentation + optional binder reordering for
    readability).

Blocks #61. Relates to #141, #115, #119, #151.

Metadata

Metadata

Assignees

No one assigned

    Labels

    mvpRequired for the two legible root theorems (non-vacuous + every premise derived or named trust)soundnessCircuit faithfully implements the Sail spec (equivalence, trust, defects, extraction fidelity)

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions