Skip to content

TYPE-CONNECTIONS.adoc: re-cite the residual receipt (run 35773288367 @ 8f3b46f) and give the Echo→Residual / Epistemic→Residual obligations acceptance criteria #115

Description

@hyperpolymath

Measured (2026-09-22, main = 1fa506c)

  • docs/TYPE-CONNECTIONS.adoc:174 links residual-evidence-types/blob/4325198c…/PROOF-STATUS.adoc; :176 links run 34400282291 (2026-09-09).
  • residual-evidence-types main is 8f3b46f0 (2026-09-22T19:21Z); its Agda proofs run 35773288367 is green on the container recipe (Agda 2.6.4.3, stdlib 2.1, --double-check, zero third-party actions). The proof core is byte-identical to 4325198c, so the cited claims hold; the citation is stale, not wrong.
  • :114 "Echo → Residual Evidence" and :118–119 "Epistemic → Residual Evidence: make the meaning and evidence obligations of candidate-wide claims explicit" are listed as obligations with no acceptance criteria.

Acceptance criteria

  1. :174–176 re-cite the current receipt (commit and run) once the residual Phase 2 pin refresh lands (echo-types 7a569b7 → 9c4b72b5, epistemic-types 3f4250f → dd948fbd), so the hub cites a receipt whose sibling pins are current. Until then, the 8f3b46f run is added as "re-verified" beside the original.
  2. Echo → Residual: accepted when the residual composition module (ResidualEvidence.Composition, Phase 3 item 2 of the family plan) states and proves compose-claims over the Echo comparison, with its reject module rejected in CI.
  3. Epistemic → Residual: accepted when the residual revision module (ResidualEvidence.Revision, Phase 3 item 3) makes retraction constructive and EpistemicComparison proves more than typing (whether SoundWarrant sits on a vacuous path is the open measurement).
  4. Watched-failing → green: grep -c 34400282291 docs/TYPE-CONNECTIONS.adoc is 1 today; after, the current run id appears and the old one is kept as history or removed.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions