Repository navigation
chore(a2ml): move hypatia off A2ML: translate per the mapping specs, move the readers, delete 28 of 30 files - #1113
Conversation
…uthority (#1119) ## Summary This PR is stacked on #1113. The owner directed that hypatia's ANCHOR authority be boj-server's chora id. ## Changes - `hypatia_chora.deed` gains `(anchor :schema "hyperpolymath.anchor/2" :authority "6c7f9305-2a47-8f96-a1ed-bd0940e4d4e6" (metadata :version "1.0.0"))`. A comment gives the source of each value. - The id comes from boj-server's chora deed (`#u8"gv-clade-index:github.com/hyperpolymath/boj-server"`), and the chora registry (`worker/data/repos.json`) holds the same id. - It is a pre-V9 id, so it keeps its `gv-clade-index` domain. - Nothing was minted or reminted. - The ledger's ANCHOR row and `.claude/CLAUDE.md` are updated. ## Verification - `deed_lint` at standards `490b952` passes in plain, `--anchor` and `--egress` modes. - `Hypatia.Deed` parses the deed. - RSR criterion 3.1.8 now passes for hypatia. ## Draft: owner question open In `anchor.abnf` v2.0.0 (A7 J7, J26), `:authority` is a free non-empty string, not an id. The template writes `"upstream-canonical"`, and J7 plans to close that vocabulary after a census. A parent link would normally be `(related :uuid … :relationship parent)` in the ecosystem clause. This stays a draft until the owner confirms the uuid string as the authority, or names a vocabulary term instead. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ Co-authored-by: Claude <noreply@anthropic.com>
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
…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
…uthority (#1119) ## Summary This PR is stacked on #1113. The owner directed that hypatia's ANCHOR authority be boj-server's chora id. ## Changes - `hypatia_chora.deed` gains `(anchor :schema "hyperpolymath.anchor/2" :authority "6c7f9305-2a47-8f96-a1ed-bd0940e4d4e6" (metadata :version "1.0.0"))`. A comment gives the source of each value. - The id comes from boj-server's chora deed (`#u8"gv-clade-index:github.com/hyperpolymath/boj-server"`), and the chora registry (`worker/data/repos.json`) holds the same id. - It is a pre-V9 id, so it keeps its `gv-clade-index` domain. - Nothing was minted or reminted. - The ledger's ANCHOR row and `.claude/CLAUDE.md` are updated. ## Verification - `deed_lint` at standards `490b952` passes in plain, `--anchor` and `--egress` modes. - `Hypatia.Deed` parses the deed. - RSR criterion 3.1.8 now passes for hypatia. ## Draft: owner question open In `anchor.abnf` v2.0.0 (A7 J7, J26), `:authority` is a free non-empty string, not an id. The template writes `"upstream-canonical"`, and J7 plans to close that vocabulary after a census. A parent link would normally be `(related :uuid … :relationship parent)` in the ecosystem clause. This stays a draft until the owner confirms the uuid string as the authority, or names a vocabulary term instead. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ Co-authored-by: Claude <noreply@anthropic.com>
5cba98e to
527a642
Compare
|
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 45 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. |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 527a642900
ℹ️ 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".
| cond do | ||
| record_files == [] -> | ||
| :fail | ||
| if deed_parses?(repo), do: :pass, else: :fail |
There was a problem hiding this comment.
Validate mixed-carrier deeds before passing 3.2.1
When a repository has both a chora deed and any legacy record-dialect file—most notably rsr-profile.a2ml—this branch skips deed_parses?/1 entirely and returns :pass if the A2ML parses. A malformed deed in a partially migrated repository therefore passes criterion 3.2.1, even though the new deed-only path fails the same malformed deed; require every carrier that is present to parse rather than consulting the deed only when record_files is empty.
Useful? React with 👍 / 👎.
| * Bot actions are subject to the same quality and review standards as human | ||
| contributions. | ||
| * Configure bots in `.machine_readable/bot_directives/`. | ||
| * Configure bots in the `(bot-directives …)` clause of `hypatia_chora.deed`. |
There was a problem hiding this comment.
Point bot configuration at a location the gate reads
The referenced (bot-directives …) clause does not exist in hypatia_chora.deed, and the enforcement path in Hypatia.Kin.Gate.check_bot_directives/2 reads only .bot_directives/<bot>.json, .machine_readable/bot_directives.json, or .bot_directives/default.json. An operator following this new governance instruction would therefore create configuration that has no effect, after which the gate's no-file fallback permits all bots; document one of the actual JSON inputs or add a deed reader before directing users to this clause.
Useful? React with 👍 / 👎.
| ;; CLADE.a2ml -> (identity) (clade) (forges) (lineage) (status) | ||
| ;; clade-to-repo-deed.adoc. CLADE's [identity] name and | ||
| ;; project repeat canonical-name and are not emitted. | ||
| ;; :repo-uuid is the ADR-008 profile C UUIDv8 re-derived | ||
| ;; from the name (spec section 5, P-1), not the v5 that | ||
| ;; CLADE.a2ml held. |
There was a problem hiding this comment.
Move the CLADE identity scanner to the deed carrier
After this migration deletes .machine_readable/CLADE.a2ml, scan_clade_identity in hypatia-cli-bash.sh still immediately returns unless .machine_readable/descriptiles/CLADE.a2ml exists and never reads these translated deed clauses. Consequently HYP-S010 stops checking template residue, UUIDv8 recomputability, and owner/name preimage mismatches for Hypatia and every fully migrated repository; update that scanner to extract identity data from the chora deed before removing its only readable carrier.
Useful? React with 👍 / 👎.
| (ecosystem | ||
| :project "hypatia" | ||
| :ecosystem "hyperpolymath" | ||
| :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.") |
There was a problem hiding this comment.
Correct the neural-network count in canonical metadata
The newly canonical repo deed says Hypatia learns through five neural networks, but lib/neural/coordinator.ex orchestrates eight and .machine_readable/MUST.contractile explicitly protects all eight; .claude/CLAUDE.md also marks this count as load-bearing. Keeping the stale value from the retired ECOSYSTEM file makes the new machine-readable source contradict the implemented architecture and can cause agents or inventory consumers to omit GNN, VAE, and SequenceModel.
Useful? React with 👍 / 👎.
| Full mapping in `+.machine_readable/testing/blitz.a2ml+`, retired 2026-11-14 and | ||
| kept in git history (`+docs/history/A2ML-REMOVED.adoc+`). |
There was a problem hiding this comment.
Remove the instruction to recreate dogfooding A2ML
Although this edit now labels the testing A2ML inventory as retired, the same operational audit still identifies missing .machine_readable/dogfooding.a2ml as DOG-09 at lines 128–130 and explicitly tells contributors to create it at lines 265–266. Following that remediation would violate the new repository-wide rule that .a2ml files must never be created or restored, so the audit needs a deed-era replacement or must mark DOG-09 retired too.
Useful? React with 👍 / 👎.
| # AI manifest: the deed is the front door; the legacy A2ML names still count | ||
| if [[ ! -f "$dir/0-AI-MANIFEST.deed" && ! -f "$dir/0-AI-MANIFEST.a2ml" && ! -f "$dir/AI.a2ml" ]]; then | ||
| emit_finding "high" "repo_structure" "missing_ai_manifest" \ | ||
| "$dir" 0 "No AI gateway manifest found" "CWE-1021" \ | ||
| "Add 0-AI-MANIFEST.a2ml or AI.a2ml" | ||
| "Add 0-AI-MANIFEST.deed (A2ML is retired)" |
There was a problem hiding this comment.
Accept the canonical chora deed in shell manifest checks
For a fully migrated estate repository that has the canonical <repo>_chora.deed but no optional 0-AI-MANIFEST.deed, this condition still emits a high-severity missing_ai_manifest finding. Hypatia.Rules.RootHygiene explicitly accepts any root *_chora.deed and notes that the estate template ships no 0-AI-MANIFEST, so both this scanner and the identical check in poc-scanner.sh now disagree with the deed-era repository contract; include the repo deed carrier in these checks.
Useful? React with 👍 / 👎.
| version = "1.0.0", | ||
| description = "Exercises declared failure modes and verifies recovery paths. Hard-gates on any failure mode without working recovery.", | ||
| paired_xfile = "Bustfile.a2ml", | ||
| paired_xfile = "Bustfile.deed", |
There was a problem hiding this comment.
Do not point the bust runner at a missing deed
The migration changes paired_xfile to Bustfile.deed while explicitly acknowledging that this file has not been written and deleting the previous Bustfile.a2ml. Any contractile bust check or contractile bust drill that resolves this metadata now has no failure-mode declaration to load, so the recovery hard gate is unusable; retain the old carrier until a valid deed exists or add the deed in the same change.
Useful? React with 👍 / 👎.
| defp state_file_exists?(repo_path) do | ||
| chora_status_clause?(repo_path) or state_named_file_exists?(repo_path) | ||
| end | ||
|
|
||
| @state_names ~w(STATE.deed STATE.a2ml STATE.scm) |
There was a problem hiding this comment.
Read the new state carriers during the audit
This change makes a chora (status) clause or STATE.deed set has_state_file: true, but audit/1 still obtains claims through find_state_file/1, which only checks the two direct legacy paths .machine_readable/STATE.a2ml and .machine_readable/STATE.scm; parse_state_file/1 also only understands A2ML-style assignments. On a deed-era repository the audit therefore suppresses the missing-state finding while silently discarding every state claim and falling back to an adjusted score of 50 with :no_claim, so the new carriers need to be located and parsed consistently by audit/1.
Useful? React with 👍 / 👎.
## Summary This PR is stacked on #1113. On 2026-11-14 the owner ruled that RSR criteria 3.1.x accept the chora deed, with `.a2ml` only as the A7 fallback. ## Changes - **3.1.1** passes, reading the deed first, when the chora deed parses and carries any top-level descriptile clause: status, meta, ecosystem, agentic, neurosym, playbook, anchor or clade. Otherwise the `descriptiles/` directory still counts. - **3.2.1** requires every carrier to parse, the deed first. **This is stricter than before:** a broken chora deed now fails 3.2.1 even when the remaining `.a2ml` files parse. - **3.1.2–3.1.9** read the deed first and fall back to `.a2ml`. Their verdicts don't change. - `RsrProfile.idr` models only 3.2.2, so it needs no change. - `rsr_conformance_test.exs`: the `#u5` test ids become `#u8`/`#uuid` (owner ruling Q2). DEBT-REGISTER M-1 is marked superseded. ## Verification - `rsr_conformance` tests: 30/30. - Full `mix test`: 3225 tests, 10 failures, all of them the `HttpcRedirectCredentialsTest` failures that main also has. - Self-score: | Criteria file | Before | After | |---|---|---| | Bundled fixture | 84.08%, bronze | 86.91%, bronze | | Standards canon 2.1.0-draft | 82.71% | 85.78% | ## Not done here (owner decision) The canon `0-canon/rsr/rsr-criteria-v2.a2ml` still names only `.a2ml` carriers in 3.1.1–3.2.2. Changing that text would add a fact to a retired A2ML file, and `canon.lock` pins the file by hash. A7 §10 instead routes the canon to a criteria praxis deed generated by kyX. This PR therefore changes the oracle and leaves the canon alone. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ --------- Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
…ause (#1116) ## 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 from `ECOSYSTEM.a2ml` at main. The header comment is updated. - No edge gets a `: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_lint` does 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.Deed` parses the deed. The deed, rsr, root_hygiene, egress-mirror and honest_completion tests pass: 130 tests, 0 failures. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ --------- Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
Resolves the conflicts left by the squash-merge of #1113: the tree is main plus only this PR's own change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZmSuTPtG4zjRCN2UaY
## Summary This PR is stacked on #1113 and removes hypatia's last live `.a2ml` registry. ## Changes - Adds `audits/assail-classifications_praxis.deed`, with all 14 entries translated mechanically. It passes `deed_lint`, and `Hypatia.Deed` reads it. - Deletes `audits/assail-classifications.a2ml`. - `docs/history/A2ML-REMOVED.adoc`: the file moves from Retained to Removed, with its size, sha256 and blob id. - `.github/workflows/dogfood-gate.yml` and `test/dogfood_manifest_detection_test.rb`: the `.a2ml` exclusions are removed, so the new deed is counted and validated. The Ruby test passes. ## Blocked until **Do not merge this before the panic-attack deed reader (hyperpolymath/panic-attack#295) lands and the scanner pins move to its merge commit.** Until then, the pinned scanner reads no registry and the 14 audited findings come back unsuppressed. The pins to move: 1. `estate-rescan.yml` `PA_SHA`, here in hypatia. 2. In standards `hypatia-scan-reusable.yml`, the `panic-ref` default. 3. Then this repo's `hypatia-scan.yml` `uses:` SHA. All lanes move together (2026-11-13 ruling; `mix hypatia.ci_triage pins`). --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ --------- Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
…osystem parent (#1123) ## Summary This finishes #1119 according to the owner's anchor ruling of 2026-11-14. #1119 merged into #1113 with boj-server's chora id as `:authority`, before the ruling's change was pushed. This PR applies the ruling on top of main. ## Changes - `hypatia_chora.deed`, `(anchor)`: `:authority "upstream-canonical"`. - In `anchor.abnf` v2.0.0, `:authority` is a vocabulary term (J7), not an id, and this is the template's term. - `hypatia_chora.deed`, `(ecosystem)`: adds `(related :name "boj-server" :relationship parent :notes … :uuid #uuid"6c7f9305-2a47-8f96-a1ed-bd0940e4d4e6")`. This is the parent that ANCHOR.a2ml named (J26). - The uuid is boj-server_chora.deed's `:repo-uuid #u8"gv-clade-index:github.com/hyperpolymath/boj-server"`, and the chora registry records the same `uuid_v8`. - It is a pre-V9 id and keeps its domain. Nothing was minted. - The pair (boj-server, parent) is distinct from the existing (boj-server, mcp-host) edge. - `docs/history/A2ML-REMOVED.adoc`: the ANCHOR row says the same. ## Verification `deed_lint` from standards main passes in plain, `--anchor` (authority `"upstream-canonical"`) and `--egress` (12 jobs) modes. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ Co-authored-by: Claude <noreply@anthropic.com>
…#115) ## Summary The owner approved this on 2026-11-14, and A1, who owns this repo, agreed. It follows hyperpolymath/hypatia#1113 and deletes 114 of the 117 `.a2ml` files. `docs/history/A2ML-REMOVED.adoc` records each one (path, size, sha256, blob id and disposition), plus the files kept and the questions still open. ## Changes - **New `gv-clade-index_chora.deed`.** The registry had no repo deed, so this is a judgement call for A1 to confirm. - It is built from `CLADE.a2ml` (identity, clade gv with secondary db, forges, lineage) and from AGENTIC, NEUROSYM and PLAYBOOK, following their mapping specs. - `:repo-uuid #uuid"a65b74d8-351a-89d9-a38d-aea470863b03"` is the id the seed already holds (`:minted-in gv-clade-index`). Nothing was minted. - The file name follows the canonical name. Rename it to `chora-registry_chora.deed` when GitHub renames the repo; the id stays the same. - **`.machine_readable/descriptiles/STATE.deed`:** the CLADE status and STATE maturity `alpha`. It passes `--state --strict`. - **`0-AI-MANIFEST.deed`:** pointer-only. - **Deleted, with no spec or no translatable content:** - META and ECOSYSTEM, whose shapes fall outside the table; - ANCHOR, which held template defaults; - `ENSAID_CONFIG`, `ai/AI.a2ml`, and the agent_instructions, contractiles, integrations and policies files; - `clade-hygiene.a2ml`; - the docs/governance copies, whose `.adoc` versions stay; - blank templates; - 81 boilerplate directory manifests, listed as one class. - **Kept, under A1's guardrails:** - `verisim/seed/clades.a2ml`, which builds the served `clades.json`; - `verisim/seed/forges.a2ml`, covered by the seed lint and still waiting for its own conversion; - `verisim/config.a2ml`, cited by `wrangler.toml` and the release runbook. - **Not touched**, under A1's guardrail 2: the seed praxis deed, the sync scripts, `check-registry.sh` and its test. - **Readers moved:** - Justfile recipes; `rhodibot.yml` checks for `0-AI-MANIFEST.deed`; - `MUST.contractile`, `bust.ncl`, `contractile.just` and CODEOWNERS; - a comment in `worker/src/validate.js`; - agent and doc pointers. ## Verification - `scripts/check-registry.sh`: PASS. With `GV_BASE_REPOS_JSON` set to main's `repos.json` it also passes: all 327 repos are present and no id changed. - `tests/check-registry-test.sh`: PASS. - `check-uuid-v8.sh --strict`: no new findings (the same 702 as main). - `validate-a2ml.sh`, `just fmt-check`, `just lint` and the yq workflow parse all pass. ## Open questions These are in the ledger: - the ECOSYSTEM edge terms (`depends-on`, `feeds-into`, `sibling`); - a mapping-table row for META's keyed ADR tables; - the anchor values once A7 §6.4 is in `mappings/`; - the deed file name. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ Co-authored-by: Claude <noreply@anthropic.com>
…runtime ruling (#383) ## Summary The owner approved this on 2026-11-14. It follows hyperpolymath/hypatia#1113 and deletes 48 of the 52 `.a2ml` files. `docs/history/A2ML-REMOVED.adoc` records each one with size, sha256 and blob id, plus the files kept and the questions still open. ## Changes **Translated into `boj-server_chora.deed`**, following the mapping specs. Fields a spec doesn't list are dropped, and a deed comment names each one. - META → `(meta)`, including 14 `(adr)` clauses. `license` is left out because meta open question 2 is unruled. - PLAYBOOK → `(playbook)`. - ANCHOR → `(anchor :schema "hyperpolymath.anchor/2" :authority "upstream-canonical" …)`, under A7 §6.4. - CLADE, AGENTIC and NEUROSYM were already translated. Three `(status)` fields outside the clade spec are removed. - `0-AI-MANIFEST.a2ml` → a pointer-only `0-AI-MANIFEST.deed` (Q15) with the same `:repo-uuid`. The id is unchanged. **Deleted, with no spec and no reader** (grepped across the repo and the org): - 19 directory manifests; - `ENSAID_CONFIG` and `dev-toolchain`; - the agent_instructions, contractile, integrations and policies files; - `servers/menu.a2ml` and `servers/order-ticket.a2ml` (the live menu is `GET /menu`, built from `cartridge.json`); - `docs/examples/extension.a2ml`. **Kept, with the reasons in the ledger:** - `6a2/ECOSYSTEM.a2ml`, cut by deletion only to its `[publishing.readme]` block, which `readme-derive.yml` reads; - `audits/assail-classifications.a2ml`, because no released panic-attack reads the deed yet; - `.boj/project-memories.a2ml`; - `panll/src/Boj.a2ml`. **Readers moved off the deleted files:** - Justfile recipes (`validate-rsr`, which was failing on main and now passes; `validate-state` and others); - the contractile runners; - agent files and docs. **`.claude/CLAUDE.md`:** - The runtime is Bun > Deno > pnpm > npm, with `package.json` plus `bun.lock` required. - The garbled line now says *ReScript* is no longer the destination. - The Machine-Readable section points to the deeds and the ledger. No licence or SPDX line was changed. ## Verification - `deed_lint` passes on both deeds, and `--anchor` passes. - `check-uuid-v8.sh --strict`: exit 0. - `validate-a2ml.sh` and `validate-k9.sh` pass. - `scripts/pre-merge-gate.sh --offline` passes. - `just validate-rsr` and `just validate-state` pass. These were already failing on main and still fail: `just validate` (AI_INSTALLATION_GUIDE missing), `just --fmt --check`, and nickel on `bust.ncl`. ## For the owner The ledger lists the open points: - the source of `(clade :rationale)`; - META `license`; - an out-of-date anchor implementation-policy; - Trustfile runbook steps that now have no file; - departures not touched here: `report_format = "a2ml"`, the pre-commit hook, the k9 example, the `<name>.a2ml.json` cartridge manifests, the dep5 lines (flagged only), and `bun.lock` missing. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_ Co-authored-by: Claude <noreply@anthropic.com>
) ## Summary Main does not compile since #1117. `descriptiles_parse/1` calls `deed_state/1`, which nothing defines. A duplicate `record_files == []` branch could never run, and `descriptile_carrier/0` was never called. ## Changes - 3.1.1 now uses `descriptile_carrier/0` (deed first, then the directory), as #1117 describes. - `deed_state/1` replaces `deed_parses?/1` and returns `:ok`, `:none` or `:broken`. - 3.2.1: a broken chora deed fails even when the `.a2ml` files parse, as #1117 says. The dead duplicate branch is removed. ## Verification - `mix compile --warnings-as-errors`: clean (it failed before with the undefined function and the unused function). - `mix format --check-formatted` on the file: clean. - `mix test`: 3514 tests, 0 failures, 246 excluded (LANG=C.UTF-8). Not run: Rust, Zig and Idris2 checks. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZmUcth17dd8P9G2L1G)_ Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
Governance's "Validate Hypatia Baseline" step is red on main since #1135 (85cc775), and on #1136: unfiltered medium finding structural_drift/SD022 in docs/history/A2ML-REMOVED.adoc -- doc references `src/assail/` but no such directory exists in the tree #1135 re-added the literal `src/assail/mod.rs` path in the assail-classifications row. That path is in panic-attack, not here, and #1113 had reworded it for the same reason. This rewords it again ("its assail module"). The row's meaning is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC



Why
On 2026-11-14 the owner ruled "full migration now" for Hypatia's A2ML departure. Estate rule: no
.a2mlfile should exist. Translate first whatever a reader still needs, and drop whatever the mapping specs don't list.What
28 of the 30
.a2mlfiles are gone.docs/history/A2ML-REMOVED.adocrecords each removed file (size, sha256, git blob id, what it held, where the content went) and the two that stay.Translated into
hypatia_chora.deedunder the mapping specs in standards1-formats/deed/mappings/. Every field a spec doesn't list is dropped, and a deed comment names it.(meta)with 5(adr)clauses(ecosystem)(agentic), including the 5 integrity axioms(neurosym … (hypatia …))(playbook)(maturity :level alpha)(state-v1-decision option B)0-AI-MANIFEST.a2ml0-AI-MANIFEST.deedDropped because no mapping spec covers them:
.a2mlfiles;rules.a2ml.Inlined: the 3 rule-loader fixtures are now byte-identical heredocs in
test/rules/rule_loader_test.exs.Kept, each with its reason in the ledger:
audits/assail-classifications.a2ml: panic-attack's classifications loader reads only that name, and deleting the file would unsuppress audited findings.test/fixtures/a2ml/rsr-criteria-v2.a2ml: a copy of the standards RSR canon, which is still A2ML. This is the A7 shared-reader exception.Readers moved:
(status),(meta),(ecosystem)and(anchor). Its.a2mlfallback stays, as A7 M5–M7 require.(status)orSTATE.deed.0-AI-MANIFEST.deedfirst..claude/CLAUDE.md, README, CONTRIBUTING,GOVERNANCE.adoc,ai.txtand the design docs point at the deeds.tools/scm-to-a2ml.sh(an A2ML producer) is deleted.No LICENSE or SPDX header is touched. The only SPDX lines in the diff belong to deleted files and to the inlined, byte-identical fixtures.
Checks (run locally on Elixir 1.19.4 / OTP 27.3.4)
mix test: 3222 tests, 10 failures, 246 excluded.HttpcRedirectCredentialsTest(sandbox network). No new failures.deed_lint:hypatia_chora.deedOK, and OK with--egress(12 jobs);0-AI-MANIFEST.deedOK;hypatia_rules_praxis.deedOK.gen-rules-praxis.sh --check,tests/rules-praxis-test.sh(22/22) andreadme-claims-test.sh(7/7) pass.rsr_scoreself-score drops from 86.91% to 84.08% and stays bronze. The one new failure is 3.1.1: the canon criterion still requires adescriptiles/directory. That is an open question below.scripts/check-verdicts.sh, because idris2 was absent in that environment. The.idredits are comment-only.Open questions for the owner (raised separately; nothing here guesses them)
.a2mlfiles anddescriptiles/.:authorityvalue.rsr_score --writeandrsr-oracle.ymlstill write an.a2mlscorecard into scored repos, which makes them an estate-wide A2ML producer.Departures seen, not fixed here (out of scope)
.a2ml(SD007, SD023, root_hygiene).bust.nclreport_format = "a2ml".a2mlpre-commit hook.#u5ids in thedeed_egressfixtures and the conformance test helper, which are errors under Q2.Generated by Claude Code