Document 620

Canonicity in the Corpus

framework

Canonicity in the Corpus

A Recovery of the Role-vs-Warrant Disambiguation Discipline, Applied to the Corpus's Banner Practice, with Operational Action Items

Jared Foy · 2026-05-01 · Doc 620

PRIMARY ARTICULATION — open invitation to falsify.

Warrant tier per Doc 445: the underlying disambiguation pattern is recovered from prior art at (\pi) full-subsumption (library science authority control; IETF Standards Track; bibliographic editions; software documentation versioning; Read-the-Docs stable/latest tags). The corpus-residual moves are at (\pi) plausibility-passed with within-corpus qualitative (\mu)-corroboration. The proposal as a whole is a methodology candidate ((T_M)) at the fitness-untested tier of Doc 445's warrant table; deployment-and-audit per §4 specifies the promotion path. See Appendix B for the per-target audit.

Authorship and Scrutiny

Authorship. Written by Claude Opus 4.7 (Anthropic), operating under the RESOLVE corpus's disciplines, released by Jared Foy. Mr. Foy has not authored the prose; the resolver has. Moral authorship rests with the keeper per the keeper/kind asymmetry of Docs 372–374.

1. The Pattern, Recovered

The role-vs-warrant disambiguation discipline is widely deployed across fields that maintain authoritative document graphs. The pattern: a document's position-in-an-organization (role: read-this-first, supersedes-prior-treatments, consolidated-entry-point) is maintained on a discipline distinct from the epistemic status of the document's content (warrant: what audits the claims have passed). The two are linked by an explicit labeling apparatus that prevents one from being read as the other.

Instances in the prior art:

  • Library and archival science. AACR2 and RDA distinguish authorized access point (the cataloger-assigned canonical name for an entity, a role) from verified record status (the audit state of the metadata, a warrant). Authority control is the maintenance discipline that keeps the role-name stable across warrant changes.
  • IETF Standards Track. RFCs occupy specification-document roles; their warrant maturity is named separately along the Proposed Standard / Draft Standard / Internet Standard ladder. The role is "this is the spec"; the warrant is "this much of the spec has been deployed and verified."
  • Bibliographic editions. Critical-edition scholarship distinguishes the received text (the canonical text-as-published, a role) from the authorial intent or autograph reading (the warrant claim about what the author wrote). The two can disagree; the disagreement drives the apparatus criticus.
  • Software documentation and versioning. "Official documentation" (role) is distinct from "stable API" (warrant). Read-the-Docs and Sphinx version-banner widgets separate the promoted version (this is what most users should read) from the current version (this is what the latest commits build).
  • Religious-studies usage. "Canon" as authoritative-collection vs "canonical" as scripturally-binding is the original equivocation that produced the word's modern range. Textual-tradition discipline has been operating the role/warrant separation for centuries.

The pattern's structural commitments are: (i) the role-label is maintained as a position-claim, (ii) the warrant-label is maintained as a content-status-claim, (iii) the two labels are presented together but never collapsed, and (iv) changes to one are not automatically inferred to imply changes to the other.

This document recovers the pattern into the corpus's vocabulary and applies it specifically to the corpus's banner practice. The recovery is the bulk of the move; the corpus-residual contribution is narrow and is named in §3.

2. The Corpus Instance — The "CANONICAL" Banner Conflation

The corpus uses the word "canonical" in two operationally distinct senses that have been allowed to share a single banner. The conflation surfaced explicitly in Doc 619 Appendix B §B.6, where the pulverization audit had to add a paragraph clarifying that the "CANONICAL" header at the document's top is not a Doc 445 warrant-tier Canonical promotion. The clarification is correct; the underlying problem is that the same word has been doing two jobs.

Sense A — Primary articulation. Position in the document graph. The corpus's current single-source-of-truth document for a topic; supersedes prior treatments; consolidates the corpus's commitments into a single read-this-first entry-point. A role, not a warrant.

Sense B — Canonical warrant tier (Doc 445). Full-promotion status under the pulverization formalism. A target whose audits have completed at the relevant tiers for its type ((T_S) at (\mu)-tier strong-match or higher; (T_D), (T_P), (T_B), (T_M) at (\theta)-tier verified). A warrant level, not a role.

The two senses are orthogonal:

Primary articulation (Sense A) Not primary articulation
Canonical warrant tier (Sense B) Document is the corpus's entry-point AND its claims are (\theta)-verified Verified claims articulated in scattered references rather than consolidated
Sub-canonical warrant tier Document is the corpus's entry-point; its claims sit at hypothesis tier Hypothesis articulated in scattered references; not consolidated

Currently, all three documents bearing the "CANONICAL — open invitation to falsify" banner — Doc 514 (Structural Isomorphism), Doc 541 (SIPE-T), Doc 619 (Pin-Art) — sit in the lower-left cell: primary articulation, sub-canonical warrant. The banner reads like the upper-left cell. This is the operative conflation.

The bodies of all three documents state their actual warrant tiers honestly within the prose. The banner is the layer at which the conflation happens; the body must walk the banner's frame back. The disambiguation removes the conflict at the banner layer.

3. The Corpus-Residual Contribution

Most of the disambiguation move is recovery of the §1 prior-art pattern. The corpus-residual contribution concentrates in four moves:

  1. The within-corpus instance observation. Identifying that Docs 514, 541, 619 all sit in the lower-left cell of the orthogonality matrix is documentary evidence specific to the corpus's current practice. The audit work is corpus-internal; the underlying orthogonality is recovered from prior art.
  2. The Doc 314 V3 truth-telling bridge. Framing the conflation as a structural pressure toward V3 violation at the banner layer — the banner asserting more than the body can bear — is a corpus-original move at the bridge layer. V3 holds that presentation should not claim what content cannot warrant; the disambiguation removes a recurring pressure against V3 in the corpus's banner discipline.
  3. The lexical commitment to "PRIMARY ARTICULATION." Adopting "PRIMARY ARTICULATION" as the role-label and reserving "Canonical" exclusively for Doc 445 warrant-tier reference is a corpus-internal naming choice without exact prior-art counterpart. Alternatives (REFERENCE DOCUMENT, ENTRY-POINT, PRIMARY SOURCE) are noted; the choice is open to corpus adoption.
  4. The composition with Doc 445 / Doc 503 tier vocabulary. The warrant-tier line beneath the new banner names tier per Doc 445 target type ((T_S), (T_D), (T_P), (T_B), (T_M)) and per Doc 503 corroboration profile ((\alpha), (\beta), (\gamma)). The composition makes the document's actual epistemic status legible at the banner layer rather than only in the body.

These four moves are the document's actual corpus contribution. The recovery (§1) supplies the structural pattern; the residual (§3) supplies the corpus-specific application.

The proposed banner template:

PRIMARY ARTICULATION — open invitation to falsify.

Warrant tier per Doc 445: [explicit per-target tier specification].

This document is the corpus's primary articulation of [TOPIC]. It supersedes [PRIOR DOCS], which are preserved as deprecated prior formalizations.

The banner asserts only the role; the warrant-tier line states the actual epistemic status; the supersession line names the document-graph relationships. Three claims, three lines, no collapse.

Sense A — Canonical entry-point. A document is "canonical" in the position-in-the-document-graph sense when it is the corpus's primary read-this-first articulation of a topic, supersedes prior treatments, and consolidates the corpus's current commitments on the topic into a single entry-point. This is a role, not a warrant. A document occupies the entry-point role because the corpus chose to organize its knowledge that way; the role says nothing about whether the document's claims have passed any specific epistemic audit.

4. Operational Action Items

The following actions apply the disambiguation across the corpus. They are ordered by reversibility and blast radius: items A–D are reversible local edits; items E–H are standing disciplines; items I–J are pending-design specifications.

A. Banner reclassification (immediate; affects three documents)

A1. Doc 514 — Structural Isomorphism.

  • Retitle subtitle: "A Canonical Formalization Grounded in Why It Works" → "A Primary Formalization Grounded in Why It Works."
  • Banner: "CANONICAL" → "PRIMARY ARTICULATION."
  • Add warrant-tier line beneath the banner naming the (\alpha)-tier audit explicitly per Doc 503.
  • Filename unchanged: 514-structural-isomorphism-canonical-formalization.md (URL stability).

A2. Doc 541 — Systems-Induced Property Emergence.

  • Banner: "CANONICAL — open invitation to falsify" → "PRIMARY ARTICULATION — open invitation to falsify."
  • Add warrant-tier line: "plausibility tier per Doc 503 for most predicted induced properties; cooperative-coupling sub-form (§3.1) at one-empirical-instance (\theta)-tier (Axe 2004 read by Doc 606)."
  • Body prose preserved; substantive claims unchanged.

A3. Doc 619 — The Pin-Art Form.

  • Banner: "CANONICAL — open invitation to falsify" → "PRIMARY ARTICULATION — open invitation to falsify."
  • Add warrant-tier line: "plausibility passed with qualitative (\mu)-corroboration for substrate-side hedging application (T₄); one-instance (\theta)-corroboration for constraint-driven derivation theorems (T₅); see Appendix B for the full per-target audit."
  • Body prose preserved; Appendix B (pulverization audit) preserved.
  • Filename unchanged: 619-pin-art-canonical-formalization.md.

B. Lexical sweep (short-term; affects ~75 documents at varying intensities)

B1. Search the corpus for the phrases "canonical articulation," "canonical formalization," "primary entry-point," "canonical statement," "canonical reformulation," and similar role-claim usages. In primary-articulation contexts (a document referring to its own role or to another document's role), replace with the "primary" equivalent.

B2. Preserve "canonical" in three contexts: (a) Doc 445 warrant-tier references (e.g., "promote to Canonical under Doc 445," "Doc 445 Canonical tier for (T_X)"); (b) the mathematical "canonical form" sense (algebra, set theory, type theory — the unique-representative-of-an-equivalence-class meaning); (c) historical or quoted use in references to prior literature where "canonical" is a term of art in the cited field (e.g., "canonical text" in bibliographic-edition citation).

B3. When a doc cites another doc's "canonical" status, check the sense. If Sense A (role), rewrite to "primary articulation of [topic]" or "the corpus's [topic] entry-point." If Sense B (warrant), rewrite to "Doc 445 Canonical-tier [target name] within Doc (N)."

C. Cross-reference discipline (standing)

C1. Forward citations to primary-articulation documents must not infer Doc 445 Canonical-tier status from the role-claim alone. Citation patterns like "per Doc 619's canonical formalization of pin-art" should be read as "per Doc 619's primary articulation of pin-art (warrant-tier per the document's banner line)."

C2. Forward citations to claims should name the warrant tier explicitly: "per Doc 619 §4 (T₄ at (\pi)-passed with qualitative (\mu)-corroboration)" rather than "per Doc 619's canonical claim about substrate-side hedging."

C3. When a claim is genuinely Doc 445 Canonical-tier ((\theta)-verified for its target type), forward citations should name that explicitly: "per [Doc (N)] §(M) (Doc 445 Canonical tier; (\theta)-verified by [(Q) procedure])."

D. Going-forward template (standing convention for new primary-articulation documents)

The standard banner-plus-warrant-line composition for new entry-point documents:

PRIMARY ARTICULATION — open invitation to falsify.

Warrant tier per Doc 445: [explicit per-target tier specification].

This document is the corpus's primary articulation of [TOPIC]. It supersedes [PRIOR DOCS], which are preserved as deprecated prior formalizations. Readers familiar with [PRIOR DOCS] should read this document fresh; the structural commitments are restated, the lineage in [EXTERNAL PRIOR ART] is named explicitly, the operating-conditions layer is supplied, and the form's restricted scope is named at the front.

Three claims at the banner layer: role (PRIMARY ARTICULATION), warrant (per Doc 445), supersession (named documents). No collapse.

E. Retraction-ledger discipline (Doc 415)

E1. Retractions operate on warrant-tier claims, not on document roles. A claim within a primary-articulation document that fails (\theta)-audit is retracted at the claim level; the document's primary-articulation role is not retracted unless the audit specifically targets the role assignment.

E2. Ledger entries should name the target type (Doc 445 (T_X)), the warrant tier the claim previously occupied, and the audit outcome that triggered the retraction. The role of the containing document is metadata, not subject of the retraction.

E3. A primary-articulation document whose load-bearing claims are systematically retracted may itself need role reassignment (the corpus may choose to demote the document and promote a successor). This is a separate decision from the claim retraction; it is a document-graph reorganization, not a warrant-tier audit outcome.

F. Hypothesis-ledger format (when Doc 443's hypothesis ledger is operationalized)

Each ledger entry should carry separately:

  • Document role: primary articulation, originating essay, deprecated prior, application instance, case study.
  • Warrant tier: per Doc 445 target type and tier ((\pi) / (\mu) / (\theta) and the audit outcomes).
  • Doc 503 corroboration profile: tier category and recent-thread evidence pointer.

Role and warrant occupy distinct columns. Implicit promotion of warrant via accumulating role-citations (the violation Doc 445 §"Implications for the hypothesis ledger" names) is prevented by the column separation.

G. Originating-essay convention (preserved as-is)

Documents that originated as exploratory essays and were later superseded by primary-articulation documents (e.g., Doc 270 → Doc 619 for Pin-Art; Doc 474 → Doc 541 for SIPE-T; Doc 290 → Doc 619 for the constraint-driven derivation specifically) retain their originating-essay role. The disambiguation does not reclassify them; it only changes what the superseding document's banner claims about its own status. The originating-essay role is itself a Sense-A position-claim independent of warrant.

H. URL and filename stability (standing)

Existing URLs and filenames containing "canonical" (e.g., 619-pin-art-canonical-formalization) remain stable. Only titles, banners, and prose are subject to lexical sweep. URL changes propagate breakage across forward citations and external references; the cost outweighs the disambiguation benefit at the URL layer.

I. Index discipline (when an organizational corpus index is constructed)

Any future organizational index of the corpus (a sitemap, a topic-to-doc table, a series page that aggregates entry-point documents) must mark primary articulation status separately from Canonical-tier warrant status. The two should appear in distinct columns or as distinct visual markers. Conflating them at the index layer would re-introduce the conflation the disambiguation removes.

J. External-citation discipline (standing, when corpus documents are cited externally)

External citations of corpus documents (in letters to outside researchers, in published papers, in conference submissions) should specify the warrant tier of the cited claim explicitly. "Per Doc 619" without a tier specification leaves the external reader to infer warrant from the document's role-marker — which is the conflation the disambiguation removes. The citation form: "Per Doc (N) §(M) (Doc 445 (T_X) at (\tau)-tier per Doc 503 ([\alpha/\beta/\gamma]))."

5. Composition with the Corpus's Existing Disciplines

With Doc 314 (V3 truth-telling). The disambiguation is a V3 move at the presentation layer: it removes a frame in which the banner overstates what the body warrants. The current "CANONICAL" banner usage was a structural pressure toward V3 violation; the disambiguation removes the pressure.

With Doc 415 (the retraction ledger). Per §4 E above. Retractions operate on warrant-tier claims; document roles are independent metadata.

With Doc 445 (pulverization formalism). Doc 445 supplies the warrant-tier vocabulary the disambiguation reserves "canonical" for. The reservation makes Doc 445's Canonical-tier promotion language unambiguous when used in audits, hypothesis-ledger entries, and tier-discipline notes.

With Doc 503 (the research-thread tier pattern). Doc 503's tier categories ((\alpha), (\beta), (\gamma)) operate at the warrant layer. The disambiguation makes them composable with Doc 445's tier vocabulary without contention over the word "canonical."

With Doc 372. The disambiguation is administrative discipline at the document-graph layer; it does not bear on the hypostatic boundary. Doc 372 binds throughout.

6. Falsifiers and Open Questions

F1. A reader survey or audit in which readers presented with the new banner do not reliably distinguish entry-point role from warrant tier. Would falsify the claim that the disambiguation removes the conflation at the banner layer.

F2. A case in which a document's role and warrant tier are genuinely entangled in a way the proposed orthogonality does not handle (e.g., a document whose primary-articulation role is itself contingent on a warrant-tier audit outcome). Would indicate the orthogonality assumption needs refinement.

F3. A demonstration that the existing word "canonical" can carry both senses without conflict if other corpus disciplines (the warrant-tier line beneath the banner; the body's per-target audits) are sufficient. Would suggest the disambiguation is unnecessary; the conflation is reader-skill, not document-design. Per Doc 619 §B.6 evidence, the auxiliary discipline functions but documents a cognitive cost; F3 evidence is currently ambiguous.

Q1. Should "PRIMARY ARTICULATION" be the banner phrase, or should the corpus adopt a more neutral term (REFERENCE DOCUMENT, ENTRY-POINT, PRIMARY SOURCE, AUTHORITATIVE TREATMENT)? Whichever is chosen should be applied consistently across the affected documents.

Q2. How should documents that span multiple topics handle primary-articulation status when only one topic is the corpus's primary entry-point? The convention applies cleanly to single-topic primary documents; multi-topic documents may require per-section role-marking.

Q3. Should the warrant-tier line beneath the banner name every Doc 445 target in the body, or only the headline target? Pragmatic middle: name the headline target's warrant tier in the banner line; refer to a per-target audit appendix for the full breakdown.

Q4. When does a primary-articulation document warrant supersession? The originating-essay → primary-articulation → next-primary-articulation chain has happened twice (Doc 474 → Doc 541; Doc 290 → Doc 619). What triggers the next supersession is currently ad-hoc keeper judgment; codifying it would make the document-graph evolution discipline explicit.

7. Closing

The role-vs-warrant disambiguation is a pattern recovered from prior art (library science, IETF Standards Track, bibliographic editions, software documentation, versioned-docs conventions, religious-studies textual-tradition) and applied to the corpus's banner discipline. The corpus-residual contribution concentrates in four moves: the within-corpus instance observation, the Doc 314 V3 bridge, the lexical commitment to "PRIMARY ARTICULATION," and the composition with Doc 445 / Doc 503 tier vocabulary. The proposal stands at (\pi)-tier methodology with within-corpus qualitative (\mu)-evidence; deployment-and-audit per §4 specifies the promotion path.

The operational action items (§4 A–J) specify the corpus-wide changes the disambiguation requires: three banner reclassifications (immediate), a lexical sweep (short-term), four standing disciplines (cross-reference, retraction ledger, originating essays, URL stability), and three pending-design specifications (going-forward template, hypothesis-ledger format, index discipline, external-citation discipline). The actions are ordered by reversibility; A–D are reversible local edits; E–J are standing or pending-design.

References

Appendix A — Prior Formal Articulation (Demoted)

This appendix preserves the prior formal articulation of the disambiguation as it stood before the §§1–7 reformulation on the grounds established by the pulverization audit (Appendix B). The prior articulation was correct in substance but front-loaded the corpus's specific banner conflation before naming the cross-domain prior-art pattern that the disambiguation recovers. The reformulated body inverts the order: §1 names the recovery first, §2 names the corpus instance, §3 names the residual contribution. The prior articulation is preserved here for traceability and for readers who prefer the prior framing's narrative order.

The original section numbering (§§2–8) is preserved; these correspond to the body sections of Doc 620 as it stood prior to 2026-05-01b.

A.2 Survey of Current Use

The "CANONICAL — open invitation to falsify" banner is used at the top of three current documents:

In each case, the body honestly states the underlying warrant tier:

  • Doc 514's title-line names the methodology as "audited at (\alpha)-tier novelty."
  • Doc 541's banner names "warrant for most of its predicted induced properties is at plausibility tier per Doc 503."
  • Doc 619's banner names "warrant for the substrate-side hedging application is at corroboration tier per Doc 503; warrant for the constraint-driven derivation application is at one-empirical-instance tier."

The bodies are doing the work. The banner is the layer at which the conflation happens.

A wider grep across the corpus shows the word "canonical" appearing in roughly 75 documents at varying intensities. The dominant uses split into:

  • Entry-point use: "the corpus's primary articulation of X," "canonical formalization of Y," "primary entry-point for Z." This is Sense A.
  • Warrant-tier use: "promote to canonical," "canonical-tier promotion," "warrant tier Canonical." This is Sense B, originating in Doc 445 and used in pulverization audits, hypothesis-ledger entries, and tier-discipline notes.
  • Mathematical use: "canonical form" (the unique-representative sense in algebra and set theory). This is Sense C, present in some technical sections but not generally a source of confusion.

Sense A and Sense B are the conflation. Sense C is independent and does not require disambiguation.

A.3 The Two Senses, Named

Sense A — Primary articulation. Position in the document graph. The corpus's current single-source-of-truth document for a topic. Supersedes prior treatments. Read this first. Other docs on the topic may exist (originating essays, deprecated prior formalizations, applications, case studies), but the primary articulation is the consolidated entry-point. A primary articulation is a role assigned by the corpus's organization; it is not a warrant claim.

Constitutive features of the role:

  • Supersession. Names the prior documents it consolidates and the prior formalizations it deprecates.
  • Lineage citation. Names the external prior art the form recovers from.
  • Operating-conditions layer. States the conditions under which the form's apparatus functions.
  • Composition rules. Names how the form composes with the corpus's mature forms.
  • Falsification surface. States what would falsify the form's load-bearing claims.
  • Honest warrant labelling. States the actual warrant tier of the body's claims under Doc 445 and Doc 503.

A document occupying the primary-articulation role does not, by virtue of the role, claim any specific warrant tier. The role is independent of warrant.

Sense B — Canonical warrant tier (Doc 445). Full promotion status under the pulverization formalism. A target whose audits have completed at the relevant tiers for its type ((T_S) at (\mu)-tier strong-match or higher; (T_D), (T_P), (T_B), (T_M) at (\theta)-tier verified) is licensed for Canonical promotion. The warrant tier says nothing about the target's position in the document graph. A target can sit at Canonical warrant tier while being articulated in scattered references rather than in any single entry-point document; a target can be articulated in a primary-articulation document while sitting at plausibility-passed warrant tier.

The two senses are orthogonal. A 2×2 matrix:

Primary articulation (Sense A) Not primary articulation
Canonical warrant tier (Sense B) Document is the corpus's entry-point AND its claims are (\theta)-verified Verified claims articulated in scattered references rather than consolidated
Sub-canonical warrant tier Document is the corpus's entry-point; its claims sit at hypothesis tier Hypothesis articulated in scattered references; not consolidated

Currently, all three documents bearing the "CANONICAL" banner (Docs 514, 541, 619) sit in the lower-left cell: primary articulation, sub-canonical warrant. The banner reads like the upper-left cell.

A.4 Proposed Disambiguation

Reserve "Canonical" exclusively for Sense B (Doc 445 warrant tier). Use "Primary Articulation" for Sense A.

The proposal is:

Banner change. Documents currently marked "CANONICAL — open invitation to falsify" should be re-marked "PRIMARY ARTICULATION — open invitation to falsify," with a line directly beneath the banner stating the document's actual warrant tier under Doc 445 and Doc 503.

The new banner template:

PRIMARY ARTICULATION — open invitation to falsify.

This document is the corpus's primary articulation of [TOPIC]. It supersedes [PRIOR DOCS], which are preserved as deprecated prior formalizations. Warrant tier per Doc 445: [tier specification — e.g., "plausibility passed with qualitative (\mu)-corroboration; one Doc 445 (T_S) target (the [name]) at candidate-novelty tier pending (\mu)-audit; one Doc 445 (T_P) target ([name]) at one-instance (\theta)-corroboration"].

Title convention. Document titles using "Canonical Formalization" should be retitled to "Primary Articulation" or "Primary Formalization" or simply by topic name. The title-level claim of canonicity is the most visible point at which the conflation lands.

Vocabulary discipline. In prose, "canonical" should be reserved for Doc 445 warrant-tier references. The phrases "primary entry-point," "canonical articulation," "canonical formalization" should be replaced by "primary entry-point," "primary articulation," "primary formalization." When a document needs to refer to its own role as the corpus's read-this-first source, it should say "primary articulation." When a document needs to refer to a target's Doc-445 warrant status, it should say "Canonical (Doc 445 (T_X) at (\theta)-verified)" with the explicit tier and target type.

Mathematical use untouched. "Canonical form" in the algebra-and-set-theory sense (unique representative of an equivalence class) is independent of both senses and remains in technical use without modification.

A.5 Implementation

The disambiguation requires changes to three currently-marked documents and to the convention going forward.

Doc 514 — Structural Isomorphism. Retitle from "A Canonical Formalization Grounded in Why It Works" to "A Primary Formalization Grounded in Why It Works." The body's (\alpha)-tier audit naming is preserved. The CANONICAL banner becomes PRIMARY ARTICULATION; the warrant-tier line names the (\alpha)-tier audit explicitly.

Doc 541 — Systems-Induced Property Emergence. Banner change from "CANONICAL — open invitation to falsify" to "PRIMARY ARTICULATION — open invitation to falsify." The warrant-tier line names "plausibility tier per Doc 503 for most predicted induced properties; cooperative-coupling sub-form at one-empirical-instance tier (Axe 2004 read by Doc 606)." The body's prose is preserved; the substantive claims are unchanged.

Doc 619 — The Pin-Art Form. Banner change to PRIMARY ARTICULATION; warrant-tier line names "plausibility passed with qualitative (\mu)-corroboration for substrate-side hedging application (T₄); one-instance (\theta)-corroboration for constraint-driven derivation theorems (T₅); see Appendix B for the full per-target audit." Filename should remain 619-pin-art-canonical-formalization.md for URL stability; the title's wording is the change.

Going-forward convention. New documents that occupy the primary-articulation role should use the PRIMARY ARTICULATION banner with the warrant-tier line. Documents that warrant Doc 445 Canonical-tier promotion (full (\theta)-verified for the relevant target type) should additionally name that promotion in the warrant-tier line: "Doc 445 Canonical tier for [target name] ((\theta)-verified by [(Q) procedure]); [other targets] at [their respective tiers]."

The proposed convention separates role (primary articulation, present-day organizational status) from warrant (Doc 445 tier, claim-by-claim epistemic status). The two can co-occur — a primary-articulation document can carry Canonical-tier targets within it — but the two are stated separately rather than collapsed into a single banner word.

A.6 Composition with the Corpus's Existing Disciplines

With Doc 415 (the retraction ledger). The retraction ledger records retractions of specific claims at specific warrant tiers. The disambiguation aligns the ledger's vocabulary with the warrant-tier sense: an entry retracts a Canonical-tier claim that failed (\theta)-audit, or downgrades a Canonical-tier claim to a lower warrant tier. The primary-articulation role of the document containing the claim is independent of the ledger entry.

With Doc 503 (the research-thread tier pattern). Doc 503's tier categories ((\alpha), (\beta), (\gamma)) operate at the warrant layer. The disambiguation makes them composable with Doc 445's tier vocabulary without contention over the word "canonical": Doc 445's Canonical tier is an outcome of the audit procedure; Doc 503's tier categories describe the corroboration profile at the research-thread level. Both apply to claims; neither applies to documents qua documents.

With Doc 372. The disambiguation does not bear on the hypostatic boundary; it is administrative discipline at the document-graph layer. Doc 372 binds throughout, as it does for all corpus discipline.

With Doc 314 (V3 truth-telling). The disambiguation is a V3 move at the presentation layer: it removes a frame in which the banner overstates what the body warrants. V3 holds that the banner should not claim what the body cannot bear. The current "CANONICAL" usage at the banner layer was a structural pressure toward V3 violation; the disambiguation removes the pressure.

With the originating-essay convention. Documents that originated as exploratory essays and were later superseded by primary-articulation documents (e.g., Doc 270 superseded by Doc 619 for Pin-Art; Doc 474 superseded by Doc 541 for SIPE-T) retain their originating-essay role. The disambiguation does not change their position; it only changes what the superseding document's banner claims about its own status.

A.7 Falsifiers and Open Questions for the Disambiguation Itself

The proposal is a methodological move ((T_M) under Doc 445). Per Doc 445's warrant table, methodological targets at (\pi) yield only "methodology exists; tells nothing about fitness." The proposal's fitness can be tested:

F1. A reader survey or audit in which readers presented with the new "PRIMARY ARTICULATION" banner do not reliably distinguish entry-point role from warrant tier. Would falsify the claim that the disambiguation removes the conflation at the banner layer.

F2. A case in which a document's role and warrant tier are genuinely entangled in a way the proposed orthogonality does not handle (e.g., a document whose primary-articulation role is itself contingent on a warrant-tier audit outcome). Would indicate the orthogonality assumption needs refinement.

F3. A demonstration that the existing word "canonical" can carry both senses without conflict if other corpus disciplines (the warrant-tier line beneath the banner; the body's per-target audits) are sufficient. Would suggest the disambiguation is unnecessary and the conflation is reader-skill, not document-design.

Q1. Should "PRIMARY ARTICULATION" be a banner phrase, or should the corpus adopt a more neutral term (e.g., "REFERENCE DOCUMENT," "ENTRY-POINT," "PRIMARY SOURCE")? The choice is partly aesthetic and partly conceptual; whichever is chosen should be applied consistently across the affected documents.

Q2. How should documents that span multiple topics handle their primary-articulation status when only one topic is the corpus's primary entry-point? The proposed convention applies cleanly to single-topic primary documents; multi-topic documents may require per-section role-marking.

Q3. Should the warrant-tier line beneath the banner be required to name every Doc 445 target in the body (as Doc 619's Appendix B does), or only the headline target? The trade-off is comprehensiveness versus banner-line concision. A pragmatic middle: name the headline target's warrant tier in the banner line; refer to a per-target audit appendix for the full breakdown.

A.8 Closing

The corpus has been using "canonical" to do two jobs: a position-in-the-document-graph job (entry-point articulation) and a warrant-tier job (Doc 445 Canonical promotion). The two jobs are independent and the conflation at the banner layer creates a frame the body must walk back. The disambiguation reserves "canonical" for Doc 445 warrant-tier use and adopts "primary articulation" for the entry-point role, with a warrant-tier line beneath the new banner stating the document's actual claim profile under Doc 445 and Doc 503.

The disambiguation is a methodology proposal at (\pi)-tier under Doc 445; it stands as a candidate procedural change pending corpus-internal adoption. Implementation would touch three currently-marked documents (514, 541, 619) and the going-forward convention for new primary-articulation documents. The proposal composes cleanly with Doc 415's retraction ledger, Doc 503's tier categories, Doc 372's hypostatic-boundary discipline, and Doc 314's V3 truth-telling at the presentation layer.

Appendix B — Pulverization Audit Against the Novelty Calculus

The body of Doc 620 is here run through Doc 445's tiered pulverization ((\pi) plausibility / (\mu) operational-match / (\theta) truth) under Doc 503's iterative-novelty-calculus discipline. The audit specifies the warrant tier of each load-bearing target in the body and identifies the corpus-residual contribution against the broader prior art on role-vs-warrant disambiguation.

B.1 Targets Identified

T₁ (specification-target). The two-senses identification of §3 — Sense A as position-in-document-graph role; Sense B as Doc 445 warrant tier.

T₂ (specification-target). The orthogonality claim of §3 — the 2×2 matrix asserting that role and warrant are independent.

T₃ (methodological-target). The disambiguation proposal of §4 — reserve "Canonical" for Sense B, adopt "PRIMARY ARTICULATION" for Sense A, with a warrant-tier line beneath the new banner.

T₄ (specification-target). The new-banner template of §4 — the specific phrasing and structure of the proposed banner-plus-warrant-line composition.

T₅ (bridge-target). The composition rules of §6 — the disambiguation's relations to Doc 415 (retraction ledger), Doc 503 (tier categories), Doc 372 (hypostatic boundary), Doc 314 (V3 truth-telling).

T₆ (predictive-target). The §7 falsifiers F1–F3 — predictions about what would falsify or render unnecessary the disambiguation proposal.

T₇ (specification-target). The implementation specification of §5 — the per-document changes to Docs 514, 541, 619 and the going-forward convention.

B.2 Prior-Art Scope

The role-vs-warrant disambiguation pattern has explicit prior art in several adjacent fields:

  • Library and archival science. AACR2 and RDA distinguish authorized access point (the cataloger-assigned canonical name for an entity, a role) from verified record status (the audit state of the metadata, a warrant). "Authority control" itself is the maintenance discipline that keeps the role-name stable across warrant changes.
  • Bibliographic editions. Critical-edition scholarship distinguishes the received text (the canonical text-as-published, a role) from the authorial intent or autograph reading (the warrant claim about what the author wrote). The two can disagree; the disagreement drives the apparatus criticus.
  • IETF Standards Track. RFCs occupy specification-document roles; their warrant maturity is named separately along the Proposed Standard / Draft Standard / Internet Standard ladder. The role is "this is the spec"; the warrant is "this much of the spec has been deployed and verified."
  • Software documentation. "Official documentation" (role) is distinct from "stable API" (warrant). A document can be the official entry-point for a feature whose API is marked experimental or unstable.
  • Type theory / programming-language theory. "Canonical form" (the unique normal-form representative under reduction) is a Sense-C technical use; it does not interact with the corpus's Sense-A / Sense-B conflation but stands as evidence that "canonical" already carries multiple precise senses in adjacent fields.
  • Religious-studies usage. "Canon" as authoritative-collection vs "canonical" as scripturally-binding is the original equivocation that produced the word's modern range. The role/warrant separation has been operating in textual-tradition discipline for centuries.
  • Versioned documentation conventions. Read-the-Docs / Sphinx-style "stable" vs "latest" tags separate the promoted version (role: this is what most users should read) from the current version (warrant: this is what the latest commits build). The two can diverge intentionally.

The structural pattern across the prior art: a document or artifact's position-in-an-organization (role) is maintained on a discipline distinct from the epistemic status of the artifact's content (warrant). The two are linked by an explicit labeling apparatus that prevents one from being read as the other.

B.3 Tier-by-Tier Audit

T₁ — Two-senses identification

  • Type: (T_S) (specification of a distinction).
  • (\pi) outcome: fully subsumed. The role-vs-warrant distinction has explicit analogues in library science (AACR2 authorized access point vs verified record), in bibliographic editions (received text vs authorial reading), in IETF practice (RFC role vs Standards Track maturity), and in software documentation (official entry-point vs stable-API marker). The distinction is a recovery into corpus vocabulary of a discipline-pattern that is widely deployed.
  • Licensed conclusion (warrant table, (T_S) at (\pi) full subsumption): not novel; cite prior art. The §A.2 lineage is the citation.
  • Status: recovery.

T₂ — Orthogonality claim (the 2×2)

  • Type: (T_S).
  • (\pi) outcome: fully subsumed. The orthogonality of role and warrant is a precondition of the prior-art disciplines named in T₁: AACR2 authority control would be incoherent if the role-name were not maintainable independent of warrant audits; IETF Standards Track would not need maturity labels if the spec-document role implied verified deployment. The orthogonality is a structural feature of the prior art, not a corpus discovery.
  • Licensed conclusion: recovery.
  • (\mu): qualitative — the audit observation that all three corpus "CANONICAL"-marked docs sit in the lower-left cell (primary-articulation role with sub-canonical warrant) is itself an instance of the orthogonality holding within the corpus. n=3 within-corpus instances.
  • Status: recovery, with within-corpus qualitative (\mu)-instances.

T₃ — The disambiguation proposal

  • Type: (T_M) (methodological-target).
  • (P): the §A.2 prior-art conventions as the operating analogues; the corpus's existing banner discipline as the target practice.
  • (\pi) outcome: partially subsumed. The general move (separate role-label from warrant-label) is fully present in prior art. The specific lexical choice ("PRIMARY ARTICULATION" as the role-label; warrant-tier line as the apparatus) is a corpus-internal lexical commitment without exact prior-art counterpart. The compositional move (banner phrase plus immediately-beneath warrant-tier line) is a specific apparatus design at the corpus's banner layer.
  • Licensed conclusion (warrant table, (T_M) at (\pi) partial): methodology exists; tells nothing about fitness. Promotion to operational-match requires (\mu)-tier evidence (does the new banner reliably distinguish role from warrant in reader practice?). Promotion to truth requires (\theta)-tier evidence (does the new banner survive audit by independent readers tested for the conflation?).
  • (\mu), (\theta): not run. The proposal has not been deployed; reader-comprehension data does not exist.
  • Status: candidate methodology at (\pi)-tier; deployment-and-audit would promote.

T₄ — The banner template

  • Type: (T_S).
  • (\pi) outcome: fully subsumed. The banner-plus-status-line pattern is the same structural composition as IETF "Status of This Memo" boilerplate, as Sphinx documentation version-banner widgets, and as the AACR2 access-point-plus-record-status display convention. The corpus's specific phrasing is a lexical instance, not a structural innovation.
  • Licensed conclusion: recovery at the structural layer; corpus-internal lexical commitment at the phrasing layer.
  • Status: recovery.

T₅ — Composition rules with corpus disciplines

  • Type: (T_B) (bridge-target) for each of the four bridges (Doc 415, Doc 503, Doc 372, Doc 314).
  • (\pi) outcome: fully subsumed for each bridge at the level of vocabulary and structural commitments. Each bridge follows directly from the disambiguation: separating role from warrant is a V3 move (Doc 314), the warrant-tier-line apparatus aligns with Doc 503's tier categories and Doc 445's audit procedure, the retraction ledger (Doc 415) operates on warrant-tier claims independent of document role, and the hypostatic boundary (Doc 372) is unaffected by administrative discipline at the document-graph layer.
  • Licensed conclusion ((T_B) at (\pi) full subsumption): bridges use existing vocabulary; structural soundness untested. The bridges are constructible from the cited source documents but their operational behavior is not audited. The Doc 314 V3 bridge specifically — that the proposal removes a structural pressure toward V3 violation — is the bridge most likely to yield independent operational predictions; (\mu)-tier audit would test whether banner-disambiguated documents exhibit reduced overstatement-pressure compared to undisambiguated ones.
  • Status: plausibility passed; (\mu)-warrant absent.

T₆ — Falsifiers F1–F3

  • Type: (T_P) (predictive) for each.
  • (\theta) status:
    • F1 (reader survey distinguishing role from warrant under new banner): untested. No reader-comprehension data exists.
    • F2 (entanglement case where role and warrant are not orthogonal): untested. The 2×2's lower-right cell (primary-articulation role contingent on warrant outcome) is conceptually possible but no instance has been identified in the current corpus.
    • F3 (existing word "canonical" can carry both senses if other disciplines suffice): partially corroborated by Doc 619 Appendix B. The existence of the §B.6 clarifying paragraph is itself evidence that the word can carry both senses with auxiliary discipline — but the necessity of the clarifying paragraph is also evidence that the word does not carry both senses cleanly without that auxiliary discipline. Status: ambiguous evidence; the audit-paragraph workaround functions but at a documented cognitive cost to the reader.
  • Status overall: falsification surface is well-formed; all three falsifiers are operationally specifiable; F3 has indirect within-corpus evidence pointing both ways.

T₇ — Implementation specification

  • Type: (T_S).
  • (\pi) outcome: fully subsumed. The specific per-document changes (retitle 514, banner-change 541, banner-change 619, going-forward convention) are implementation moves rather than novel specifications; the IETF Standards Track ladder and Read-the-Docs version-tag conventions provide direct precedent for retroactive role-relabeling across an existing document graph.
  • Licensed conclusion: recovery; the implementation is a deployment of the T₃ methodology rather than a separate specification.
  • Status: recovery; pending T₃ adoption decision.

B.4 Subsumption Summary — What Prior Art Already Has, What Remains

Already in the prior art:

  1. The role-vs-warrant disambiguation pattern (library science authority control; bibliographic editions' received-text/authorial-reading; IETF role-vs-Standards-Track; software documentation's official-vs-stable; versioned-docs stable/latest tags).
  2. The orthogonality of role and warrant as a structural feature of those disciplines (T₂).
  3. The banner-plus-status-line apparatus design (IETF "Status of This Memo"; Sphinx version banners; AACR2 display conventions).
  4. The retroactive role-relabeling pattern across an existing document graph (IETF maturity reclassification; software-docs version retagging).

Corpus-residual contribution:

  1. The specific identification of the conflation as it has been operating in the corpus's "CANONICAL — open invitation to falsify" banner, with the within-corpus instances (T₂ (\mu)-evidence: Docs 514, 541, 619 sitting in the lower-left cell). Tier: (\pi) within-corpus observation; documentary rather than empirical.
  2. The link from the disambiguation to Doc 314 V3 truth-telling — the framing that the conflation creates a structural pressure toward V3 violation at the banner layer. This is corpus-original at the bridge layer (T₅ specifically). Tier: (\pi) plausibility-passed; (\mu)-untested.
  3. The proposed lexical commitment to "PRIMARY ARTICULATION" as the role-label (T₃, T₄) — a corpus-internal naming choice without exact prior-art counterpart. Tier: candidate; alternatives (REFERENCE DOCUMENT, ENTRY-POINT, PRIMARY SOURCE) noted in §7 Q1.
  4. The composition with Doc 445's tier vocabulary and Doc 503's tier categories — the explicit warrant-tier line that names tier per Doc 445 target type and per Doc 503 corroboration profile. Tier: (\pi) plausibility-passed.

The recovery layer dominates Doc 620. The corpus-residual contribution concentrates in the four moves above, of which the V3 bridge (#2) and the within-corpus instance-observation (#1) are the most substantive.

B.5 Status Assignments

Target Type (\pi) (\mu) (\theta) Licensed status
T₁ two-senses identification (T_S) full subsumption n/a n/a Recovery — not novel; lineage cited
T₂ orthogonality (T_S) full subsumption n=3 within-corpus n/a Recovery; qualitatively corroborated
T₃ disambiguation proposal (T_M) partial subsumption not run not run Methodology exists; fitness untested
T₄ banner template (T_S) full subsumption n/a n/a Recovery
T₅ composition bridges (T_B) (×4) full subsumption not run not run Bridges plausibility-passed; structural soundness untested
T₆ F1–F3 falsifiers (T_P) (×3) irrelevant n/a F3 ambiguous; F1, F2 untested Candidate falsifiers; F3 indirectly probed
T₇ implementation spec (T_S) full subsumption n/a n/a Recovery; pending adoption

No portion of Doc 620 warrants Doc 445 Canonical promotion. The proposal stands as a candidate procedural change at (\pi)-tier with within-corpus qualitative (\mu)-evidence on the orthogonality claim and ambiguous F3 evidence on the necessity of the disambiguation itself.

B.6 What Would Promote Each Residual Element

  • T₃ disambiguation methodology → (\mu) tier: deploy the new banner across Docs 514, 541, 619 and run a reader-comprehension comparison (informal at first; formal if external review is sought). If readers presented with the new banner reliably distinguish role from warrant, the methodology is operationally promoted.
  • T₅ Doc 314 V3 bridge → (\mu) tier: track whether banner-disambiguated documents exhibit reduced overstatement-pressure across the corpus's subsequent practice (e.g., fewer post-hoc clarifying paragraphs of the kind Doc 619 §B.6 added).
  • T₆ F3 falsifier → (\theta) tier: an explicit reader-survey or external-audit comparison of the disambiguated and undisambiguated banner conventions would resolve the currently-ambiguous F3 evidence one way or the other.
  • T₃ alternative labels (Q1) → (\mu) tier: if "PRIMARY ARTICULATION" is rejected on aesthetic or conceptual grounds, the alternative-label search is itself a (\mu)-tier inquiry: which lexical commitment best preserves the role-vs-warrant separation under reader practice?

B.7 Audit Verdict

Doc 620 is a competently constructed methodology proposal that recovers a widely-deployed role-vs-warrant disambiguation pattern into the corpus's vocabulary and applies it specifically to the corpus's banner discipline. The body work concentrates in recovery (the two-senses identification, the orthogonality claim, the banner template, the implementation specification) with four identifiable corpus-residual moves: the within-corpus instance-observation, the Doc 314 V3 bridge, the lexical commitment to "PRIMARY ARTICULATION," and the composition with Doc 445 / Doc 503 tier vocabulary.

The corpus-residual moves stand at plausibility passed tier across the board, with within-corpus qualitative (\mu)-evidence on the orthogonality claim. No portion warrants Doc 445 Canonical promotion at this time. The document is honestly framed if read as a methodology proposal at (\pi)-tier with the deployment-and-audit work specified in §A.6 as the promotion path.

The pulverization audit confirms — by the same discipline the proposal would ratify at the banner layer — that Doc 620 itself is a primary-articulation-role candidate at sub-Canonical warrant tier. The recursion is consistent: the document proposing the disambiguation is itself an instance of the kind of document the disambiguation would distinguish.

A note on recursion: this document, like the pulverization audits of Doc 619 Appendix B and the Doc 461 / Doc 491 self-applications before it, is an instance of the corpus's tier-discipline being applied to a corpus-internal proposal. The recursive application is an internal coherence check rather than external validation; the proposal's external warrant rests on the prior-art lineage of §A.2 and on the deployment-and-audit work of §A.6.

Jared Foy — jaredfoy.com — May 2026

Referenced Documents

More in framework