Skip to content

contractiles: state the Mathesis contracts (re-anchoring WO 3.3) - #76

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/mathesis-stage-3-reanchoring-s2qr20
Nov 11, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
claude/mathesis-stage-3-reanchoring-s2qr20

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Summary

Work order 3.3 of docs/proposals/mathesis-re-anchoring.adoc. The contractiles are a sensitive area, so WO 3.3 needed a ruling. On 2026-11-11 the owner ruled through the selector: follow the plan, show the text first, run WO 3.5 before WO 3.3, use probes and accept "probe-deferred", severity critical, accept an amber band. The owner reviewed and approved every clause below before this commit.

Changes

  • intend: the purpose, anti-purpose and doubt texts describe Mathesis. The template intents and wishes (repo-initialization and six more) give way to the six stages of the plan. Stages 0 to 2 are done, each with a probe. Stage 3 is in progress. Stages 4 and 5 are declared.
  • must: six critical invariants, in a section "Mathesis Invariants": views-current, no-private-name, no-hand-typed-grade, receipts-stay-home, home-theorem-has-receipt, rows-have-provenance. Each probe works offline and prints no private name. The abstract now says that no runner executes must probes yet; the CI gate named in each note enforces the same rule. No template clause is removed: each one can apply to a minted repo.
  • trust: a new section "Writers" says who writes which record.
  • Witness map: the entry for the removed intent repo-initialization goes. No deed fact attests a stage, so no witness is added.
  • Coaptation receipt: regenerated. It reads amber: three committed stages are open (3, 4, 5) and the tolerance is 2. The owner accepted that reading. It turns green as stage 3 completes.

RSR Quality Checklist

As Applicable

  • No licence edited, no .a2ml file, no private name

Testing

Run in this session on main bd5259a plus this change:

  • the six must probes and the three intend probes: pass
  • negative controls, one per must probe, each caught: stale catalogue, private frame record, PWG in a claim pin, a second receipt deed, the THY-1 pin removed, a row without its commit
  • k9 validator (standards 8e48b1c, the CI pin): 14 files, 0 failing
  • canon deed lint, just validate-coapt, validate-claude-md, validate-state, validate-rsr, validate-repo-map: pass

Not run here: just check-proofs (no Guix and no provers in this container; CI runs it).

Finding: the generated coaptation receipt holds one U+2014 character. It comes from the advice text in .machine_readable/coaptation/coapt.ncl, not from this change, and a hand edit would break validate-coapt.


Generated by Claude Code

Summary by CodeRabbit

  • Status
    • The latest project assessment now reports an advisory posture drift, with more deferred obligations and staged intents.
  • Documentation
    • Clarified project scope, trust and writing responsibilities, and expectations for records, claims, receipts, and generated views.
  • Validation
    • Added checks for catalogue consistency, public repository records, claim and receipt alignment, and census record formatting.

The owner reviewed and approved every clause through the selector on
2026-11-11 (WO 3.3 needs a ruling: the contractiles are a sensitive area).

- intend: the purpose, anti-purpose and doubt texts describe Mathesis.
  The template intents and wishes give way to the six stages of the
  re-anchoring plan: stages 0 to 2 done, each with a probe; stage 3 in
  progress; stages 4 and 5 declared.
- must: six critical invariants in a section "Mathesis Invariants":
  views-current, no-private-name, no-hand-typed-grade,
  receipts-stay-home, home-theorem-has-receipt, rows-have-provenance.
  Each probe is offline and prints no private name. The abstract says
  that no runner executes must probes yet; the CI gate in each note
  enforces the rule. No template clause is removed: each can apply.
- trust: a section "Writers" says who writes which record.
- witness map: the entry for the removed intent repo-initialization
  goes. No deed fact attests a stage, so no new witness is added (owner
  ruling 2026-11-11: probe-deferred is the expected reading).
- coaptation receipt regenerated. It reads amber: three committed stages
  are open and the tolerance is two. The owner accepted that reading.

Observed in this session on main bd5259a plus this change: the six must
probes and the three intend probes pass; each must probe fails on a
planted fault (stale catalogue, private frame record, PWG in a pin, a
second receipt deed, the THY-1 pin removed, a row without its commit);
the k9 validator (standards 8e48b1c), the canon deed lint,
just validate-coapt, validate-claude-md, validate-state, validate-rsr and
validate-repo-map pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zo9dheFQzYYWV49hAk
@coderabbitai

coderabbitai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Explain Change →

Caution

Review failed

The pull request is closed.

Walkthrough

The contractiles now describe Mathesis as an atlas and define six re-anchoring stages. The must declaration adds six Mathesis-specific invariants. The witness map, trust writer guidance, and coaptation receipt are updated to match these declarations.

Changes: Mathesis contractile re-anchoring

Layer / File(s) Summary
Mathesis intent stages
.machine_readable/contractiles/intend/intend.k9.ncl, .machine_readable/coaptation/witness-map.ncl, .machine_readable/coaptation/receipts/latest.toml
The intent declaration describes Mathesis’s atlas purpose and defines six re-anchoring stages. Stages 0–2 are done, stage 3 is in progress, and stages 4–5 are declared. The witness map removes the repository-template intent witness. The receipt reflects the updated intent entries.
Mathesis-specific invariants
.machine_readable/contractiles/must/must.k9.ncl, .machine_readable/coaptation/receipts/latest.toml
The must declaration adds six invariants for generated views, repository visibility, grade text, receipt location, theorem and receipt correspondence, and census-row provenance. The receipt records the increased clause and probe-deferred counts and its amber advisory status.
Writer guidance and receipt provenance
.machine_readable/contractiles/trust/trust.k9.ncl, .machine_readable/coaptation/receipts/latest.toml
The trust declaration assigns writers for listed records and artifacts. The receipt updates the intend, must, and trust provenance hashes.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Feature

Possibly related PRs

Suggested reviewers: claude

Merge Risk: Low · up to 9965b

The new Mathesis invariants can report a pass without checking what they claim, for example when an input file is missing or a pin points at the wrong receipt. Nothing runs these probes yet, so there is no current breakage. Tighten the probes and add CI gates for receipt ownership and claim-pin consistency before relying on them.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 11, 2026 17:16
@hyperpolymath
hyperpolymath merged commit f778a19 into main Nov 11, 2026
44 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-11T17:16:15.203839Z
We couldn’t complete this review. Comment @codex review to try again.
9965bd1 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants