Repository navigation
docs(deed): draft the ecosystem text for the owner to review - #40
Conversation
Fill purpose, IS-NOT, pipeline position and chain in the repo deed, from the README and the merged plan. Regenerate CLAUDE.md and the coaptation receipt with the repo tools. No identity id and no clade placement: those stay with the registry and the owner. 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, 10 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 39 (39 reporter observations; 20 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): 179 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. |



Summary
Draft text for the UNASSIGNED
(ecosystem)fields ofbactrian_chora.deed. The owner asked for a draft to review (selector answer, 2026-11-19). The text comes from the README and the merged plan (docs/plan/ULTRAPLAN.adoc). It is a proposal: edit the words before merge if they are not right.Changes
bactrian_chora.deed::position-type,:purpose,:not(IS-NOT),:pipeline-position,:chain.:kind "tool", the same value asatomaandquintessence.CLAUDE.md: regenerated withjust claude-md..machine_readable/coaptation/receipts/latest.toml: regenerated withjust coapt(band green).Not changed, on purpose: the identity id, the clade placement,
:domain, and the unique-strength text. Those stay with the registry and the owner.RSR Quality Checklist
Required
just validate-claude-mdOK;just coaptgreen;scripts/check-no-placeholders.shPASS;scripts/check-internal-links.shPASS.envfiles includedAs Applicable
(ecosystem)updatedTesting
Ran locally with Nickel 1.17.0:
just claude-md,just validate-claude-md,just coapt,scripts/check-no-placeholders.sh,scripts/check-internal-links.sh. Known baseline failure, not from this change:tests/bactrian/arrival_pack_anchor_override_test.shfails onmaintoo.Generated by Claude Code