Repository navigation
docs(plan): define replay in the family plan - #23
Conversation
The family plan and the six repository plans use the word replay for the W2 exit evidence and name echidna prove as the interface. A review on bactrian#37 pointed out that echidna prove checks one backend and verifies no certificate, so a prove result alone is not replay. The plan now defines replay one time: an echidna prove result on a pinned revision, then an independent kernel check of the same artifact, as scripts/atoma-replay.sh does. Package F7 names the kernel check as part of the client contract. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zmp1i8PGVHkq3u2iNz
|
|
🟢 clean · commit Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 23 (23 reporter observations; 21 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 4 finding(s)
panic-attack assail: 20 finding(s)
pons asinorum: 9 finding(s)
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 94 finding(s)
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 185 finding(s)
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run. |
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. |



Summary
One definition in
docs/plan/FAMILY-ULTRAPLAN.adoc. A review on bactrian#37 found that the plans made "ECHIDNA replay" the W2 exit evidence and namedechidna proveas the interface. The ECHIDNA prove contract says thatechidna provechecks one backend and verifies no certificate. So a prove result alone is not replay. The finding is correct and applies to the family plan, which the six repository plans use for their definitions.Changes
echidna proveresult on a pinned ECHIDNA revision, then an independent kernel check of the same artifact.scripts/atoma-replay.shis the reference (Coq backend,coqchk, assumptions audit). A receipt from replay stays INCOMPLETE until the full kernel chain of wave W4 exists.Not from this work
estate-rulesis red onmain:tests/workflows/proof_claims_rows_test.shreports no rows in the== Claimstable ofdocs/status/PROOF-STATUS.adoc. This PR does not change that file.Testing
asciidoctor --failure-level=WARNon the file: clean.scripts/check-internal-links.sh: pass. The file has nosrc/juliapath (the SD022 trigger that atoma#21 removed).Generated by Claude Code