Skip to content

Classify register 5: groundwork reckon's Navigational Principles — the register the synthesis missed #2

Description

@pentaxis93

Outcome wanted

SOURCES.md covers a fifth source register — tesserine/groundwork skills/reckon/SKILL.md §Navigational Principles — with every item classified per the established taxonomy (ascended / projection / retained / out of scope), and any content lacking a canonical home landed in the corpus per its document conventions. After this, no principle that groundwork's reckon directs reasoning from is homeless: each either lives here or is named methodology-local with a stated reason.

Why this exists (grounded)

Epic #1 synthesized four registers. Verified Jun 10 2026: a fifth exists. Groundwork's reckon skill carries five named principles — Parsimony, Elegance, Sufficiency, Traceability, Independence — explicitly defined as "first principles you reason FROM during reconstruction." That is this corpus's own discriminator for principle-hood (SOURCES.md: "a principle is a domain-neutral invariant reasoned from"). They were never classified, so reckon is today a second editable principle register — the exact condition the synthesis existed to end (Single Home).

Divergence is already observable, not merely risked:

  • Reckon's Parsimony is defined as "one mechanism over two" — the corpus locates that invariant in Single Home (projection one mechanism, not two), not in Parsimony. The two registers disagree about which universal owns the maxim.
  • Reckon's Sufficiency restates the Parsimony universal's "disciplined completeness" clause nearly verbatim, as a separate principle.
  • The corpus's Parsimony document already claims sufficiency and elegance as faces of its one invariant; reckon lists them as three independent principles. Same material, different structure, no derivation between them.

Candidates for genuinely unique content, on first reading: Traceability (every inference earns its chain to ground or principle), Independence (reason from this problem's constraints, not an adjacent solution's), and possibly the form-isomorphic-to-problem content of Elegance (distinct in emphasis from the corpus's "shape compressed to what the need demands"). These observations are evidence for the classification, not predetermined dispositions — the per-item sort is the work, exactly as it was for registers 1–4.

Scope note on the drifted copy

pentaxis93/with-claude _shared/methodology/reckon.md is a diverged copy of the groundwork source (acknowledged in groundwork#327's out-of-scope note; divergence re-verified Jun 10). It is not a sixth register — its principle content classifies through the groundwork source, and its repair is the copy-vs-source defect, separate from this corpus work.

Acceptance criteria

  • SOURCES.md contains a Register 5 section listing every item of reckon's Navigational Principles, each with exactly one classification and a destination (or stated reason, for retained / out of scope).
  • Every ascended or attached item lands inside its destination principle document following the corpus conventions: the projection/corollary names its source register item, and the document's Relations and Sources sections are updated.
  • If the classification produces a new universal, the README topology table includes it with its movement; if it produces none, the README requires no structural change.
  • Each classification's reasoning is traceable to the discriminator (invariant reasoned-from vs. methodology instrument), stated in the SOURCES.md row or the destination document.

Downstream

A groundwork issue (filed next, linked here) re-points reckon's principle selection at this corpus and removes the restated register. It is gated on this issue landing — content unique to reckon must have a canonical home before reckon can consult instead of carry, or the wisdom is lost in the move.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions