Repository navigation
Nat fork census - #7537
Merged
Merged
Nat fork census#7537
Conversation
The dag↔v2 nat fork is catalogued in a per-concept design doc (declarations, importers, entanglements, target authority) so the grounding-cluster repoint can proceed after algebra. Re-measured floor import closures: 138 entries now co-import std.nat and v2.std.nat (was 4 at 351 entries in 2026-06). Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
State the census counting rule explicitly (^import line vs loose grep): 61 live dag/ std.nat importers, reconciled against parent's 63 (two witness fixture strings). Add HandAuthoredDocBind for nat-grounding-unification-design so doc-reachability orphan wall covers it. Co-authored-by: Cursor <cursoragent@cursor.com>
Split is_zero into category A′ — re-express via nat_cata, not verbatim match port. Replace file:line integer fork evidence with std.integer.Int and v2.std.integer.Int symbols (DESIGN §3). Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Addressed review 45861 in 1. 2. Symbolic citations (DESIGN §3) — §5 integer-fork row now cites — sent from jolly-bat-372 |
9 of 10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retroactively completed 2026-08-01: this PR merged carrying the auto-opened session title and a TODO body with unchecked attestation. The census content was substantive and correct; the handback wrapper was not. Operator ruling — worker attestation is advisory rather than admission — so this is repaired in place (same repair pattern as #7530).
Follow-up status repair landed in #7548 (BLOCKED + LAST removed after prerequisites discharged).
What this PR landed
Execution-based Nat fork census and per-concept design authority:
docs/plans/nat-grounding-unification-design.md— full census, fork shape, target authority (coproduct wins), worker classification, atomic wave table, §7.6 gatesdag/gunbc/plans/dag_v2_defork_audit.dag— nat row updated to 138 co-occurrence, grounding-cluster statusdag/gunbc/doc_graph_roots.dag—HandAuthoredDocBindfor nat design docCensus conclusions (execution, 2026-08-01)
The fork is representational, not nominal:
std.nat.Nat = CommutativeSemiring<Magnitude>(no constructors) vsv2.std.nat.Nat = Zero | Succ(Peano coproduct). Exactly one homonym:nat_compare— live §13 ambiguity in mixed closures.*_test.dagentries scanned{algebra (75), nat (138)}dag/std.natimporterssrc/v2/v2.std.natimportersstd.natinsidesrc/v2/What 138 means: import closures where both nat authorities are reachable — a risk and closure-population measure, not 138 migration tasks. Gate unsafe facts (§7.6), not the integer.
Exclusion rule (why 61, not 63)
Importer counts use authored top-level
^importlines only. Loose grep finds 63dag/files mentioningstd.nat; two match only inside embedded fixture strings and are excluded.Commands run (census session)
Worker attestation (retroactive)
Note: BLOCKED + LAST status on main was stale (prerequisites discharged); corrected in follow-up #7548.