Skip to content

ci(estate-rescan): pin panic-attack at cbf2b93 (deed-first classification reader) - #1154

Merged
hyperpolymath merged 13 commits into
mainfrom
pins-1118
Nov 15, 2026
Merged

hyperpolymath merged 13 commits into
mainfrom
pins-1118

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

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.ai/code/session_0136P7ZmSuTPtG4zjRCN2UaY

claude and others added 12 commits November 14, 2026 18:29
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
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.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
…fication reader

Part of the lane-wide scanner pin move for #1118: standards b2aaeb0 (#1585)
already defaults panic-ref to this commit.

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

coderabbitai Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You'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 21 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 9aaa81ef-1669-47af-a7ae-8915bd9db81d
Commits

Reviewing files that changed from the base of the PR and between b75e313 and c117f6d.

Files selected for processing: 7

  • .claude/CLAUDE.md
  • .github/workflows/dogfood-gate.yml
  • .github/workflows/estate-rescan.yml
  • audits/assail-classifications.a2ml
  • audits/assail-classifications_praxis.deed
  • docs/history/A2ML-REMOVED.adoc
  • test/dogfood_manifest_detection_test.rb
  • 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

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@hyperpolymath
hyperpolymath marked this pull request as ready for review November 15, 2026 08:31
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 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-15T08:32:29.215424Z 919f531 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-15T08:33:44.720196Z 919f531 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.

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit f48e9fc into main Nov 15, 2026
88 checks passed
@hyperpolymath
hyperpolymath deleted the pins-1118 branch November 15, 2026 08:32
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