Repository navigation
fix(clade): adopt real registry values — fv/nl per gv-clade-index#58 - #75
Conversation
The registry has ruled: haec is fv (Formal Verification & Proofs) with secondary nl — rm was a scaffold-era default wrong by category (the substance is formalisms and logic, not repo tooling). Registry side lands via hyperpolymath/gv-clade-index#88. This file was worse than the issue recorded: besides primary rm, the secondary was ["gv"] (a mis-abbreviation of nothing this repo does), the prefixed binomial was stale, primary-name was absent (CLADE-006), there was no [status] phase (CLADE-004), and [lineage].parent carried the RSR template's text under a standalone lineage. - prefixed-name: rm-haec -> fv-haec - primary: rm -> fv; primary-name added: Formal Verification & Proofs - secondary: ["gv"] -> ["nl"] - rationale: filled with the registry description - lineage.parent: template text -> "" (standalone, per the registry) - [status] phase = "active" added (CLADE-004's prescribed default) Verification: CLADE-004/005/006 checks pass; uuid re-derived from github.com/hyperpolymath/haec matches the stored value (90db7939-1d8d- 5fec-9dbf-f2674b7818f5); cross-checked against the registry export (worker/data/repos.json on gv-clade-index#88: fv/["nl"]/fv-haec). Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. Preview blast radius → · Advanced feature ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Free Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe Clade registry entry changes from ChangesClade registry metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Note 🎁 Summarized by CodeRabbit FreeThe PR author is not assigned a seat. If you are a newly provisioned user and your organization has automatic seat assignment enabled, open a new pull request to trigger seat assignment. Otherwise, ask an organization administrator to assign a seat through the team management page at https://app.coderabbit.ai/settings/team-management. A rabbit checks the registry line Comment |
|



Summary
Adopts the real registry values for haec's
CLADE.a2ml, following the registry's ruling on gv-clade-index#58 (reclassify rm → fv, secondary nl — landing via hyperpolymath/gv-clade-index#88). Per that issue: "haec's in-repo.machine_readable/6a2/CLADE.a2mlcarried the rsr-template's identity until haec#47; it now needs the real registry values, which will follow whatever this issue decides."Changes
prefixed-name:rm-haec→fv-haec[clade]:primaryrm → fv;primary-nameadded (Formal Verification & Proofs) — it was absent entirely, so the file could not satisfy CLADE-006secondary:["gv"]→["nl"](the oldgvwas a mis-abbreviation with no relationship to this repo)rationale: filled with the registry description (was empty)[lineage].parent: template text ("RSR template — scaffold for new repos") →""— the registry lineage isstandalone, and a standalone repo has no parent[status]phase = "active"added — CLADE-004 requires a lifecycle phase; its prescribed default isactiveRSR Quality Checklist
Required
just testor equivalent)unsafeblocks without// SAFETY:commentsbelieve_me,unsafeCoerce,Obj.magic,Admitted,sorry).envfiles includedAs Applicable
.machine_readable/STATE.a2mlupdated — n/a (identity metadata only)Testing
fv✓active✓fv|Formal Verification & Proofs✓github.com/hyperpolymath/haecmatches the stored value (90db7939-1d8d-5fec-9dbf-f2674b7818f5) — identity unchanged by reclassification ✓haec → fv/["nl"]/fv-haec✓Screenshots
Not applicable — identity metadata.