Skip to content

chore(audits): translate assail-classifications.a2ml into a deed - #1118

Merged
hyperpolymath merged 11 commits into
mainfrom
chore/assail-classifications-deed
Nov 14, 2026
Merged

hyperpolymath merged 11 commits into
mainfrom
chore/assail-classifications-deed

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

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

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
The last A2ML registry this repo kept for an outside reader. panic-attack
now reads audits/assail-classifications_praxis.deed before the A2ML
names (panic-attack branch feat/deed-classifications), so the file moves
to deed form and the .a2ml goes.

- audits/assail-classifications_praxis.deed: all 14 entries, entry for
  entry. (file "…"), (audit "…") and (rationale "…") are the :file,
  :audit and :rationale fields; (category "…") is the symbol :category.
  praxis-deed with :profile assail-classifications; :beholding-chora is
  the estate chora id hypatia_chora.deed already carries.
- audits/assail-classifications.a2ml: deleted.
- docs/history/A2ML-REMOVED.adoc: the file moves from Retained to Removed.
- dogfood-gate.yml: the carve-outs for the A2ML registry go; the deed is
  an ordinary deed and is counted and validated (detection test updated).
- .claude/CLAUDE.md: lists the deed; one .a2ml file remains.

Lands only after panic-attack with the deed reader is the pinned scanner:
until then the pinned panic-attack reads no registry here and the 14
audited findings come back unsuppressed.

Checked: deed_lint.js (standards 490b952) OK; panic-attack
feat/deed-classifications suppresses exactly the same findings on this
tree as on the A2ML tree (123 suppressed of 306; 14 from the registry).

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
@hyperpolymath
hyperpolymath marked this pull request as ready for review November 14, 2026 19:18
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T19:43:48.544844Z 9e1371a Draft marked ready
🔒 Security Review ✅ Completed 2026-11-14T19:46:54.561850Z 9e1371a 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.

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1f4e22fbe0

ℹ️ 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".

Comment on lines +10 to +12
;; Read by panic-attack's deed-first registry reader (load_user_classifications,
;; src/assail/classifications.rs): findings matching (:file, :category) are
;; flipped to suppressed = true AFTER the structural kanren suppression pass.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update scanner pins before replacing the classification registry

Keep the legacy registry until every checked-in scanner lane uses the deed-aware panic-attack revision. In this commit, .github/workflows/estate-rescan.yml still pins 410a8f821ea8297833162565b50a298f787815da, and .github/workflows/hypatia-scan.yml still delegates to the unchanged standards workflow at 7641c7fdb01420696b5420ab85d88f599f32f609; those revisions predate the deed reader described here. Consequently, scans through either lane ignore this new file after the .a2ml registry is deleted, causing all 14 audited findings to reappear unsuppressed.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. This is the ordering the PR body called for.


Generated by Claude Code

Base automatically changed from chore/a2ml-to-deed to main November 14, 2026 19:21
@hyperpolymath hyperpolymath assigned Copilot and unassigned Copilot Nov 14, 2026
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
@hyperpolymath
hyperpolymath marked this pull request as draft November 14, 2026 19:38
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 14, 2026 19:42
Repository owner deleted a comment from coderabbitai Bot Nov 14, 2026
@hyperpolymath
hyperpolymath merged commit 79bf51a into main Nov 14, 2026
50 of 52 checks passed
@hyperpolymath
hyperpolymath deleted the chore/assail-classifications-deed branch November 14, 2026 19:42
hyperpolymath added a commit that referenced this pull request Nov 14, 2026
…#1124)

## Summary

#1118 merged before this commit reached it. That PR replaced
`audits/assail-classifications.a2ml` with
`audits/assail-classifications_praxis.deed`. The scanner in
`estate-rescan.yml` is still pinned at `410a8f82`, which predates
panic-attack's deed reader. Until the pin moves, that lane reads no
registry, and the 14 audited findings come back unsuppressed. This was
Codex's P1 on #1118.

## Changes

- `estate-rescan.yml`: `PA_SHA` moves from `410a8f82…` to
`cbf2b935ef4260cc3ae66010f4ffc91385ff8f8c`, the
hyperpolymath/panic-attack#295 merge commit that holds the deed-first
reader.

## Remaining lane

The standards lane moves in metadatastician/standards#1585. After that,
this repo's `hypatia-scan.yml` `uses:` moves to the new standards
commit. That step is a reusable-workflow pin, so it goes through the
standards pin applier rather than a hand edit.

---
_Generated by [Claude
Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_

Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath added a commit to metadatastician/standards that referenced this pull request Nov 14, 2026
…#1585)

## Summary

hyperpolymath/panic-attack#295 (merged at `cbf2b93`) makes `assail` read
the user-classification registry from
`audits/assail-classifications_praxis.deed` before it reads the retired
`.a2ml`. The owner approved moving the scanner pins together so that
hypatia can drop its last `.a2ml` registry (hyperpolymath/hypatia#1118).

## Changes

All lanes move together, under the 2026-11-13 ruling, from `410a8f82…`
to `cbf2b935ef4260cc3ae66010f4ffc91385ff8f8c`:

- `hypatia-scan-reusable.yml`: the `panic-ref` default.
- `fork-governance.yml`: `PANIC_ATTACK_SHA`.
- `deep-recon-reusable.yml`: the panic-attack default.
- `scripts/tests/hypatia-scanner-refs-test.sh`: the agreed default it
locks.

`hypatia-blocking-gate-test.sh` uses the old SHA only as fixture data
and is unchanged. `docs/GOVERNANCE-SOURCE-HANDOFF.adoc` is a dated
measurement and is also unchanged.

## Verification

- `scripts/tests/hypatia-scanner-refs-test.sh`: PASS.
- `scripts/tests/hypatia-blocking-gate-test.sh`: PASS.
- `tests/test_workflow_unique_keys.sh` and
`tests/test_governance_reusable_shape.sh`: PASS.

## Follow-on

In hypatia, `estate-rescan.yml` `PA_SHA` moves to the same SHA, and
`hypatia-scan.yml` `uses:` moves to this PR's merge commit. Then #1118
lands.

---
_Generated by [Claude
Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_

Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request Nov 15, 2026
…tion reader) (#1154)

## Warning: this PR is branched from #1118, not from main

The branch `pins-1118` was created from #1118's branch by mistake.
Besides the pin edit it contains all of #1118's changes (7 files, 12
commits), and it conflicts with current `main`. **Do not merge this
PR.** The owner will close it or replace it with a clean branch.

## The intended change

Move `PA_SHA` in `.github/workflows/estate-rescan.yml` from `410a8f8…`
to `cbf2b935ef4260cc3ae66010f4ffc91385ff8f8c`, the merge commit of
panic-attack#295 (the deed-first classification reader). One line:
commit `c117f6d`.

## Why it must move with the other lanes

All scanner lanes move together (2026-11-13 ruling; `mix
hypatia.ci_triage pins`). Not done here:

- standards `hypatia-scan-reusable.yml` already defaults `panic-ref` to
`cbf2b93` (standards#1585, `b2aaeb0c142de45ca1ed6e7b29f548c979737f54`).
- hypatia's `uses:` pin on that workflow is still `7641c7f…`, shared by
`hypatia-scan.yml`, `governance.yml`, `mirror.yml`, `ci.yml`,
`secret-scanner.yml`, `scorecard.yml`, `security-policy.yml` and the
generated `actions.lock`. It needs a lane-wide bump to `b2aaeb0` with
`actions.lock` regenerated by `gh actions-lock`.

## Evidence

Not run: tests and the pin-drift check, because the toolchain is missing
in the session that made this.

---
🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_0136P7ZmSuTPtG4zjRCN2UaY

---------

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
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