Repository navigation
docs: bring PROOF-STATUS.adoc and witness-map.ncl to the template form - #17
hyperpolymath wants to merge 1 commit into
Conversation
The template upgrade did not apply the template's changes to these two files. Both were identical to the template at the base commit, apart from the project name filled in, so the change is the template update applied with no project content lost. Co-Authored-By: Claude <noreply@anthropic.com>
|
|
🟢 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: 20 (20 reporter observations; 19 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 4 finding(s)
panic-attack assail: 18 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): 88 finding(s)
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 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. |
This comment was marked as low quality.
This comment was marked as low quality.
|
Closing: replaced by bactrian#23. Reason (owner ruling relayed by the sweep session): this branch cannot take an update push (its rules include Generated by Claude Code |
…m, with the seven obligations as open rows Replaces #17. The template-form PROOF-STATUS.adoc, with the {{PROJECT}} title token filled (bactrian), and the seven mandatory obligations from PROOF-NEEDS.adoc (ABI-1..5, TP-1, TP-2) restated as rows with status token open, PWG ungraded and no receipt, so the census sees open obligations. No row claims a proof. Row text is copied from PROOF-NEEDS.adoc. witness-map.ncl is unchanged from #17. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
…UMED bridge (replaces #23) (#27) * docs: bring PROOF-STATUS.adoc and witness-map.ncl to the template form, with the seven obligations as open rows Replaces #17. The template-form PROOF-STATUS.adoc, with the {{PROJECT}} title token filled (bactrian), and the seven mandatory obligations from PROOF-NEEDS.adoc (ABI-1..5, TP-1, TP-2) restated as rows with status token open, PWG ungraded and no receipt, so the census sees open obligations. No row claims a proof. Row text is copied from PROOF-NEEDS.adoc. witness-map.ncl is unchanged from #17. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ * docs: record the ASSUMED coaptation bridge in the proof-status trust boundary The trust boundary said none, but the coaptation README and Coaptation.idr declare the Idris2-model-to-coapt.ncl correspondence ASSUMED (argued, not kernel-checked). List it, and say that no Claims row rests on it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ --------- Co-authored-by: Claude <noreply@anthropic.com>



Summary
Brings two files to the template form that my template upgrade missed. The cause is the same as in the
main.zigPR: my upgrade script compared raw hashes against unfilled template tokens, so it never saw these files as unchanged. The owner asked to find the causes and resolve them.Changes
docs/status/PROOF-STATUS.adoc: identical to the template at the base commit (0 differing lines), now the current template file..machine_readable/coaptation/witness-map.ncl: identical to the template at the base commit once{{PROJECT_NAME}}is filled with the project name (0 differing lines), now the current template file with the name filled in.For both files, a three-way merge applies with no conflicts and equals the template file. No project content is lost.
Explicitly left out
.machine_readable/ai/PLACEHOLDERS.adoc(mint filled its examples) and.machine_readable/mint-verbatim.txt(changed by follow-up chore: finish the template upgrade, fill mint tokens and drop retired files #11, one template line missing).RSR Quality Checklist
witness-map.nclcomment now namescore/Coaptation.idr, which this repository does not carry (it is a template file). It is a comment only. I have not run thewitness-mapconsumers.Testing
Diff checks only, as above. Other reds on
mainare not from this PR.Owner decisions
Generated by Claude Code