docs(.claude/board): complete triple-ledger board pattern (LATEST_STATE + TECH_DEBT) - #273
Conversation
…TE + TECH_DEBT) lance-graph's board-hygiene rule names LATEST_STATE.md (current inventory/queue snapshot), an append-only PR ledger, and TECH_DEBT.md as the standing board triple; OGAR carried only EPIPHANIES.md + ISSUES.md. Add LATEST_STATE.md: the 32-crate workspace inventory, the classid domain occupancy table (sourced from ogar-vocab::ConceptDomain, the authoritative enum), and a queued/gated snapshot (RBAC authorize probe, the ogar-obo numeric-0 pad gate, V3-TRANSPILER-ADR promotion, PLAN.md staleness). It explicitly defers to docs/DISCOVERY-MAP.md and docs/INTEGRATION-MAP.md for depth — this is the five-second index, not a third copy of either. Add TECH_DEBT.md, seeded with TD-0X03-CROSS-REPO-OCCUPANCY: the documented 0x03 Ontology-domain collision history in crates/ogar-obo/src/registry.rs (three mint attempts, landing at 0x0340 with the module doc's own admission that "there is no vantage point in this crate from which the block is verifiably clean") — real, already-written debt that had no ledger home until now. Deliberately NOT adding a PR-by-PR ledger (lance-graph's PR_ARC_INVENTORY.md): docs/DISCOVERY-MAP.md's dated, graded D-* entries plus EPIPHANIES.md's dated findings already cover "what shipped and why" in more depth than a flat PR table would add; a third ledger would cut against the anti-fragmentation thesis DISCOVERY-MAP.md states at its own top. Co-Authored-By: Claude <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 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. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_4cb37d07-944d-472b-9ba4-f3ef35ff4f30) |
What was missing
lance-graph's
.claude/CLAUDE.md(§ Mandatory Board-Hygiene Rule) names astanding board triple:
LATEST_STATE.md(mutable current-inventory/queuesnapshot), an append-only per-PR ledger (
PR_ARC_INVENTORY.md), andTECH_DEBT.md, alongsideEPIPHANIES.mdandISSUES.md. OGAR's.claude/board/had only the latter two —EPIPHANIES.mdandISSUES.mdexisted and are in good shape;
LATEST_STATE.mdandTECH_DEBT.mddid notexist anywhere in the repo.
What was added
.claude/board/LATEST_STATE.md— the 32-crate workspace inventory(one line per crate, from each
Cargo.toml's owndescription), theclassid domain occupancy table (sourced from
ogar-vocab::ConceptDomain,the authoritative enum — includes the
0x04–0x06/0x10–0x16/0x18+unassigned ranges and the mint-on-emit reservations), and a short
"actively queued/gated" snapshot (the RBAC-authorize probe from
ISSUES.md, theogar-obonumeric-0 pad gate's actual current wiringstate,
V3-TRANSPILER-ADR.md's pending RFC→adopted promotion, and a notethat
.claude/PLAN.md's sprint roadmap is v0-era and stale)..claude/board/TECH_DEBT.md— seeded with one real entry,TD-0X03-CROSS-REPO-OCCUPANCY: the0x03Ontology-domain collisionhistory already documented in
crates/ogar-obo/src/registry.rs's ownmodule doc (three mint attempts — colliding first with
ogar-ro's liveRELATION_BODY_CONCEPT_ID, then with four allocations held by a privatedownstream consumer on an odd-stride run this repo cannot see, finally
landing at
0x0340as a mitigation, not a guard — the module doc's ownwords: "there is no vantage point in this crate from which the block is
verifiably clean"). That sentence is real, standing debt with no ledger
home before this PR.
What was deliberately NOT added, and why
No
PR_ARC_INVENTORY.md(a flat per-PR ledger).docs/DISCOVERY-MAP.mdalready carries dated, graded (
[G]/[H]/[S]), status-tracked (IDEA→EPIPHANY→ADR→CODED) entries for every discovery, andEPIPHANIES.mdcarries dated findings/rulings — together these cover "whatshipped and why" with more structure than a flat table would add. Adding a
third ledger duplicating that would cut directly against the
anti-dilution thesis
DISCOVERY-MAP.mdstates at its own top ("shapedilutes... from fragmentation... a future reader sees N disconnected
[artifacts] instead of one doctrine").
docs/INTEGRATION-MAP.mdplays thecomposition-mapping half lance-graph's board doesn't have a dedicated
file for at all.
LATEST_STATE.mdis explicit in its own header that it defers toDISCOVERY-MAP.md/INTEGRATION-MAP.mdfor depth and exists only as thefive-second index (crate list + classid map + queue snapshot) — not a
third copy of either.
Judgment calls
TECH_DEBT.mdanonymized as "aprivate downstream consumer" (matching how
registry.rsitself alreadyphrases it — "a product lane") rather than naming it, per that repo's
own stated commitment against naming private-consumer specifics in a
public repo.
.claude/PLAN.mditself (tempting to mark itSUPERSEDED given its staleness) — flagged it as queued/noted in
LATEST_STATE.mdinstead, since retiring an existing append-onlydocument is a bigger call than this PR's scope.
ogar-obonumeric-0 pad gate text inregistry.rsis stale relative to theedges.rsA1 fix (2026-08-08) —verified it isn't (the fix is in
edges.rs;META_STUDY_SPINEitself isstill example-only, not wired into production
bake()), and left aprecise, checkable note about it in
LATEST_STATE.mdrather thanasserting a conclusion.
Co-Authored-By: Claude noreply@anthropic.com
Generated by Claude Code