Repository navigation
feat(deed): restore the seven (related …) edges in the (ecosystem) clause - #1116
Conversation
Owner ruling 2026-11-14, "Full migration now". Each retired descriptile is translated under the mapping spec for its family, then deleted: - META.a2ml -> (meta): last-updated, scoping-first and the five ADRs (id, title, status, date), per meta-ecosystem-to-repo-deed.adoc. - ECOSYSTEM.a2ml -> (ecosystem): project, ecosystem, position-type, purpose. The seven related-projects entries are not translated: their relationships are outside the closed set the (related) row allows. - AGENTIC.a2ml -> (agentic): version, last-updated, permissions and the five integrity axioms (allow-silent-skip stays #f). - NEUROSYM.a2ml -> (neurosym): version, last-updated and the hypatia scan config (scan-depth deep). - PLAYBOOK.a2ml -> (playbook): version, last-updated and the five operational positions. - STATE.a2ml -> (maturity :level alpha), state-v1-decision option B; the lifecycle claim is the existing (status) clause and the journal is archived by reference, not translated. - CLADE.a2ml was already translated (identity, clade, forges, lineage, status); the legacy file is deleted. Fields no table lists are dropped, not re-homed; the deed comments name each one. The deed lints clean (deed_lint.js, plain and --egress). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
…FEST.deed The machine front door is now 0-AI-MANIFEST.deed, pointer-only (A7 ruling Q15): it names hypatia_chora.deed and README.adoc and carries no facts. The A2ML manifest's sections (identity, context tiers, canonical locations, architecture, invariants, lifecycle) do not match the field table of ai-manifest-decision.adoc, so nothing was translated from it; its architecture summary duplicated .claude/CLAUDE.md. Readers moved with it: - MUST.contractile: the structure invariant now preserves the .deed. - www/.well-known/ai.txt and .github/CONTRIBUTING.md point agents at the deed front door and the chora deed. - hypatia-cli-bash.sh and poc-scanner.sh accept 0-AI-MANIFEST.deed first (the legacy names still count for unmigrated repos) and recommend the deed, not an .a2ml file. The deed lints clean (deed_lint.js). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
Owner ruling 2026-11-14, "Full migration now"; A7 section 11, ruling Q7:
a file is translated where a mapping spec exists and deleted where none
does. None of these has a spec in standards 1-formats/deed/mappings/:
- .machine_readable/anchors/ANCHOR.a2ml (it also has no `authority`, which
the (anchor) clause requires and a translator never invents)
- .machine_readable/bot_directives/{coverage,debt,methodology}.a2ml and
their README (template methodology boilerplate, not per-bot directives)
- .machine_readable/contractiles/{bust,dust,intend,must,trust}/*file.a2ml
- .machine_readable/integrations/*.a2ml (four integration notes)
- .machine_readable/dogfooding.a2ml, testing/blitz.a2ml,
merge-orchestration/LEDGER.a2ml (a journal; archived by reference)
- rules.a2ml
docs/history/A2ML-REMOVED.adoc records every removed file with its size,
sha256 and git blob id, what it held and where its content went, plus the
two .a2ml files that stay and why.
References moved with the files: bust.ncl names Bustfile.deed (A7 8.1);
contractile.just says its sources are retired and must not be regenerated
from; GOVERNANCE.adoc points bot configuration at the (bot-directives)
clause; comments in verdict.ex, findings.ncl, schema/README.adoc,
Verdict.idr and ObservedIsNotSound.idr state the rule-lifecycle threshold
without citing the deleted file; design and audit docs point at the ledger;
docs/integration/a2ml.adoc is marked historical.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
…a2ml RuleLoader is a shared reader of standards' hypatia-rules/*.a2ml, which is still the only form those definitions take (A7 section 10 moves them to A5 rule registry entries in both repositories together), so its .a2ml reading stays. Its fixtures need not be checked-in .a2ml files: the three definitions are now ~S heredocs in the test, written to a temporary directory in setup_all. They are byte-identical to the deleted fixtures (verified by diff), and the ten tests pass unchanged. docs/history/A2ML-REMOVED.adoc gains the three removed fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
… ANCHOR A7 M5: shared readers read the new input first and keep the A2ML only as a fallback. Hypatia's own descriptiles now live in hypatia_chora.deed, and the oracle scored them as missing. RsrConformance (the RSR oracle): - 3.1.2 STATE accepts a top-level (status) clause (state-v1-decision, option B: the one lifecycle claim is that clause); - 3.1.3 META and 3.1.4 ECOSYSTEM accept (meta) and (ecosystem) (meta-ecosystem-to-repo-deed), as 3.1.5-3.1.7 and 3.1.9 already did for their clauses; - 3.1.8 accepts the (anchor) clause (A7 ruling S1: there is no ANCHOR.deed); - 3.2.1 with no record-dialect .a2ml left passes when the repo deed parses, and still fails when there is neither. The legacy .a2ml carriers still count. Nested clauses never do. HonestCompletion: a repo has state when its chora deed carries a top-level (status) clause or it has a STATE.deed; STATE.a2ml and STATE.scm still count. The finding no longer tells a repo to add an .a2ml file. Hypatia's self-score against the bundled criteria: 3.1.2-3.1.4 and 3.2.1 pass from the deed. 3.1.1 (a descriptiles/ directory) now fails: the criterion names the directory, and hypatia has none left. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
- .claude/CLAUDE.md: the "Machine-Readable Artefacts" section told agents to read six descriptiles/*.a2ml files that no longer exist. It now names 0-AI-MANIFEST.deed, hypatia_chora.deed and its clauses, the rules praxis deed and the removal ledger, says A2ML must not be created, and lists the two .a2ml files that remain and why. - README.adoc "Project status" points at hypatia_chora.deed instead of STATE.a2ml and PLAYBOOK.a2ml. - docs/quickstart/llm-warmup-dev.adoc no longer lists .machine_readable/6a2/ *.a2ml as the metadata home. scripts/check-readme-claims.sh and tests/readme-claims-test.sh pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
The script converted STATE/META/ECOSYSTEM .scm checkpoints into new .a2ml files. A2ML is retired and nothing may create one (standards rulings D99, D269c, D312, D313; A7 Part 1 stops the producers). Nothing in the tree called it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
…ause The A2ML migration dropped ECOSYSTEM.a2ml's seven [related-projects] entries because their relationships (sibling-standard, data-dependency, dispatch-target, scanner-source, mcp-host) were outside the closed set. The owner ruled on 2026-11-14 to extend the set (standards deed/ecosystem-relationships: clauses/ecosystem.abnf v1.1.0), so the edges come back, from the source at origin/main: - one (related :name :relationship :notes) per entry, the source's description as :notes, verbatim; - the [[related-projects.sibling]] / [[...infrastructure]] group names are not carried (the mapping's grouped-entry row); - no :uuid: the source names repos by path, and inventing a chora id is not translation (J12 strict mode would require one). docs/history/A2ML-REMOVED.adoc records that the entries are now carried. Depends on the standards change: until it lands, the closed set the ecosystem profile enforces has 11 terms and refuses all seven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
…tia lacks Hypatia's structural_drift rule SD022 reads a backticked path as a path in this tree. src/assail/ is panic-attack's, so the ledger now names the module and the repository instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 35 minutes. View limit details
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. |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
5cba98e to
527a642
Compare
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eea64f8b79
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| :position-type "component" | ||
| :purpose "Neurosymbolic CI/CD intelligence layer — scans repos via panic-attack, classifies findings through the Safety Triangle, dispatches fixes to gitbot-fleet, learns from outcomes via 5 neural networks.") | ||
| :purpose "Neurosymbolic CI/CD intelligence layer — scans repos via panic-attack, classifies findings through the Safety Triangle, dispatches fixes to gitbot-fleet, learns from outcomes via 5 neural networks." | ||
| (related :name "verification-ecosystem/echidnabot" :relationship sibling-standard :notes "Receives ProofObligation dispatches from Hypatia FleetDispatcher at confidence >= 0.85. Retrain loop feeds back via LearningScheduler N5.") |
There was a problem hiding this comment.
Update the migration ledger when restoring these edges
When these (related …) clauses are restored, docs/history/A2ML-REMOVED.adoc:49 still records that all seven entries were dropped because their relationships were outside the closed set. That document is the repository's migration provenance record, so readers and audits now receive the opposite answer from the deed; update its ECOSYSTEM row to record that the entries were restored under ecosystem v1.1.0.
Useful? React with 👍 / 👎.



Summary
This PR is stacked on #1113. On 2026-11-14 the owner ruled to extend the ecosystem closed set (metadatastician/standards#1582) rather than drop hypatia's operational edges, so they can be carried over.
Changes
hypatia_chora.deed: the 7(related …)edges go back inside(ecosystem …), copied verbatim fromECOSYSTEM.a2mlat main. The header comment is updated.:uuid. The source names repos by path, and inventing chora ids would not be translation.docs/history/A2ML-REMOVED.adoc: the ledger line now says the edges are carried, not dropped.Ordering
Plain
deed_lintdoes not check the(ecosystem)clause of a chora deed against the closed set, so this PR passes either way. A scratch check against the closed set shows why the order still matters: all 7 edges pass against standards#1582 and all 7 are refused against standards main. Merge standards#1582 first.Verification
Hypatia.Deedparses the deed. The deed, rsr, root_hygiene, egress-mirror and honest_completion tests pass: 130 tests, 0 failures.Generated by Claude Code