fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 85079–85124

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:30:20 UTC

E.8:7 - Conformance Checklist

CC style (canonical). Conformance Checklist items are authoring checks: they test whether the pattern guidance has been applied and written correctly in a pattern or companion text that claims conformance. They do not replace Solution, do not make the pattern a control form, and do not state deontic obligations about the modeled world. A CC clause of the form “X SHALL …” is to be read as “In a conforming pattern or companion text, X SHALL …”.

Passing a Conformance Checklist supports the selected conformance claims, not a claim that all anomalies were excluded or that the result answers every receiving use. A.15.11 explains how relevant checks can become an execution aid with an actual occasion, inspectable conditions and a continuation for unresolved items. Preserve the difference between that aid, the method’s Solution and inquiry into a concern that the list does not cover.

Preferred wording for new or edited CC items: start with an explicit conformance subject (e.g., “Authors …”, “Reviewers …”, “A conforming implementation …”, “A validator …”). If a CC item is enforcing an admissibility predicate, it SHOULD cite the predicate’s identifier (from a Definition: / Invariant: / Well-formedness constraint: block) rather than restating the predicate as “X MUST …”. For boundary/interface/protocol/declaration patterns, prefer A.6.B-scoped claim IDs (L/A/D/E) or cite an existing Claim Register (A.6.B:7) instead of restating mixed prose.

IDRequirementPurpose
CC-SG.0 (Heading discipline).Pattern and subsection headings SHALL follow H-1 … H-9 (FullId prefix, reserved punctuation, heading levels, ellipsis discipline). The Footer marker SHALL follow H-9.Makes chunks self-contained; reduces ambiguity between author elision and retrieval truncation.
CC-SG.1Every new pattern SHALL follow the section order defined in the Canonical Template (Title block -> … -> Footer marker).Guarantees structural comparability.
CC-SG.1a (Initial pattern draft shape).The first non-empty authored version of a pattern SHALL already use the canonical section frame (Title block -> Footer marker). Authors MUST NOT start from one pre-template opening memo and promise to backfill canonical sections later.Prevents large late-stage structural rewrites and keeps drafting aligned with E.8 from the first substantive pass.
CC-SG.2 (Grounding required).Every pattern MUST include an Archetypal Grounding section with at least one content-bearing Tell, Show, reduced grounding case, or ordinary/non-use boundary. A placeholder saying that grounding is absent is nonconforming.Keeps patterns teachable and reduces “definition-only” ambiguity.
CC-SG.3The Bias-Annotation section SHALL cite the five Principle-Taxonomy lenses and declare either “Universal” or an explicit scope limitation.Keeps cross-disciplinary neutrality explicit (ties to Guard-Rail 4).
CC-SG.4Deontic normative sentences MUST use only RFC-style keywords (see H-8); RFC keywords MUST NOT appear inside Definition:/Invariant:/Well-formedness constraint: blocks. When enforceable, admissibility/validity predicates SHOULD be referenced by id from the Conformance Checklist (rather than duplicated as “X MUST …”). Informal deontic verbs are prohibited in normative clauses.Prevents ambiguity between obligation language and model validity; improves auditability.
CC-SG.5Pattern prose SHOULD demonstrate adherence to Style Principles S-0 … S-19; reviewers are empowered to request revision when clarity or didactic quality suffers.Embeds common narrative voice without rigid policing.
CC-SG.6 (SoTA-Echo required).Every pattern SHALL include a SoTA-Echoing section. It names the practice question and either gives the smallest adequate best-known comparison or states an honest source gap. Architectural patterns SHALL use the full comparison contract below. A definitional pattern may use a reduced comparison, but it still names the ambiguity or terminology question, the best-known current line, the serious default it improves or rejects, and the pattern locus changed. Internal coherence, official status, or a current edition is not a substitute.Keeps source use tied to the pattern’s working problem and prevents an empty mandatory section from becoming a prestige shelf.
CC-SG.7 (Current-best, by-value SoTA).Every positive SoTA use SHALL state the practiceQuestion, bestKnownLine, seriousAlternativeOrDefault, defectOvercome, patternMutation, sourceRolesAndLimits, and reopenCondition in ordinary readable prose. Compare the serious answers at comparable application effort, explain why the selected line is no worse on the relevant values and better on at least one or state the chosen trade-off, and mark each material move adopt, adapt, or reject with its receiving locus.Makes the best-known-line judgement and its practical consequence independently replayable.
CC-SG.7a (Typed source roles; no currentness laundering).Authors MUST distinguish best-known-line candidates, serious current rivals, failure or counterexample evidence, official or popular comparators, lineage-only sources, and identity/currentness-only sources. Official, popular, maintained, canonical, highly cited, recent, or academically praised status supplies no positive evidence of SoTA rank. These are roles in one comparison, not permanent source classes: an official or widely used source may be the best-known-line candidate only when its substantive answer wins independently of that status. Keep lineage-only and identity/currentness-only roles outside the pattern body; keep an official or popular default as comparator only when its named defect is necessary and changes a governed locus. If no adequate best-known comparison is available, state the gap instead of substituting a catalogue page, standard, or fresh paper.Prevents source identity, prestige, prevalence, and freshness evidence from masquerading as the current best answer without excluding a source whose content actually wins.
CC-SG.8 (Actual cross-local or plane relation).When SoTA-Echoing uses an obtaining semantic Bridge, it MUST identify the two exact F.17 local senses, the F.9 relation, and a separate bounded-use claim; CL remains optional evidence shorthand. A ReferencePlane use cites its applicable plane relation. Any penalty cites a named current policy and its applicability; none follows from context, plane, Bridge, or CL alone.Safe, auditable reuse without fictitious relations or automatic penalties.
CC-SG.9 (Lexical hygiene).Authors MUST state what a mapping relates and which rule governs it. Ordinary mathematical mappings remain available; use a specialized Map or F.9 Bridge only when its defining conditions apply.Preserves relation meaning without replacing a mathematical mapping by a semantic Bridge.
CC-SG.10 (No keyword soup).SoTA-Echoing entries MUST state complete claims. Labels, bullets, and table cells may structure those claims but MUST NOT replace the practice question, selected answer, comparison, and pattern consequence with a noun catalogue.Keeps source structure readable without forcing artificial sentence form on labels or values.
CC-SG.11 (Anti-patterns).Every pattern SHALL include a Common Anti-Patterns and How to Avoid Them section grounded in observed misuse, a text-invited misreading by a plausible intended reader, or an ordinary non-use boundary that changes application. An already established boundary may be referenced. Apply F.19 to the proposed contrast; neither an invented error nor a placeholder saying no anti-pattern applies supplies a useful case.Makes relevant misuse and application boundaries recoverable without inventing an opponent or repeating a warning solely to fill the section.
CC-SG.12 (Boundary claim discipline).If boundary-facing prose mixes the logical jobs identified by A.6.B, authors MUST separate and classify the claims and preserve material dependencies by claim ID or canonical location. A clear local claim may remain ordinary prose; add a Claim Register or separate publication form only when reuse, decision, audit or cross-face citation needs it.Keeps definitions, admissibility, deontics and evidenced results distinct while retaining ordinary use.
CC-SG.13 (Didactic sufficiency).New patterns and substantial revisions MUST remain understandable without project-planning notes. Apply §4.2.1.1 to develop any missing instruction for the declared use and preserve it in the public reading; essential connections cannot be left to reader invention. When a pattern introduces a new named family, profile, or specialization, or adds a non-trivial note derived from another pattern, its Solution and Grounding SHALL carry enough didactic content: the relation to the pattern that defines or constrains the specific claim, ordinary-vs-FPF-governed wording guidance, at least one concrete source and resulting-publication slice where applicable, and visible related-pattern or project-side FPF kind and reference named by value cues.Prevents skeleton-only patterns and project-context leakage.
CC-SG.14 (Controlled prose, not free shorthand).FPF-governed prose SHALL NOT rely on bare relation words or planning shorthand whose actual relation or cited-pattern contribution is left implicit (e.g., bare “species”, “branch”, “flow”, or API-like “input/output” language). When that relation matters, authors MUST name it explicitly—for example, specialization of … with delta …, profile projecting … for use …, or overlay over …. When a neighboring pattern supplies a definition, constraint, test, method, or lookup needed by the sentence, state that concrete contribution and cite its id.Keeps pattern prose precise and self-identifying without inventing a universal locator relation.
CC-SG.15 (Package-form and relation-word discipline).When a pattern names a package form or a relation within a family (primary carrier, specialization, profile, overlay, family, bundle, cluster, suite, pack, kit, record, umbrella), the chosen word MUST match the intended ontology and MUST NOT be swapped for stylistic variety or left to implication. Any cited neighboring pattern MUST be accompanied by its concrete contribution.Prevents semantic blur while keeping family, membership, projection, and related-pattern relations auditable.
CC-SG.16 (Intended-reader discipline).Every pattern section MUST remain user-facing. Architectural reasons that explain or change the user’s Method choice, combination, adaptation, or use belong in the public account. Current development and review history belongs in its companion carrier. A Part E pattern may govern authoring, review, evaluation, entry, or publication; its body teaches that work rather than narrating development of the same pattern version.Keeps the usable explanation and its reasons together.
CC-SG.16a (Referent-index discipline in pattern prose).Pattern sections MUST keep design-time, run-time and normative-publication referents distinct when they change the claim. Truth conditions MUST concern the declared subject and use; authoring, review or publication can themselves be that subject. Keep this edition’s drafting, review and landing history under §4.2.3, separately from reusable rules and use-changing reasons.Prevents development history from replacing user guidance without excluding authoring practice.
CC-SG.16b (Quality or projection carrier separation).Pattern text MUST NOT report development, review, evaluation, projection, assembly, or landing evidence as practitioner guidance. Keep those facts in their own carriers unless that work is the pattern’s declared EntityOfConcern, or rewrite the supported result as the user’s action or boundary.Prevents package evidence from masquerading as pattern content.
CC-SG.17 (Recognition text and assurance text).A canonical pattern MUST expose recognition text before its heavier assurance text, and the latter MUST NOT silently change the recognized claim. The recognition text states the working situation, first move, payoff, grounded non-use boundary, and primary EntityOfConcern in plain user-facing terms; the assurance text supplies the typed detail and checks needed for the same claim. A claimed universal or transdisciplinary reach MUST be demonstrated through heterogeneous situations adequate to that claim.Keeps the first reading usable while preserving assurance depth.
CC-SG.17a (Problem-frame recognition signature and E.11 boundary).Authors SHOULD put the working situation, primary governed object or claim, first move, payoff, and ordinary non-use boundary in Problem frame rather than in a separate navigation block. Add entry-disambiguation cues only for an actual E.11 discoverability problem; keep expanded cases in I.2. Local Start here, First output, or neighbouring-pattern blocks SHOULD NOT replace Problem frame and Solution.Keeps recognition in the canonical pattern frame without turning it into a navigation catalogue.
CC-SG.17b (Epistemic precision repair preserves action guidance).A C.2.P repair MUST preserve the first admissible action-guiding move or name the exact neighbouring pattern that now carries it. Plain or didactic wording maps back to the governed Tech reading when it carries an FPF-governed claim or use boundary; otherwise engaging ordinary prose remains admissible. A type-correct rewrite that leaves the reader’s move unrecoverable is still under-authored.Prevents precision repair from making guidance inert.
CC-SG.17c (Action-changing expectations and return).Authors of method guidance SHOULD make relevant expectations, conditions and usable returns recoverable in Solution, including a way to retain or pursue a consequential concern not settled by listed checks. Adequate direct use may stop without extra inquiry; no generic monitoring section is required.Connects method execution with its receiving use without treating conformance as comprehensive adequacy.
CC-SG.17d (Reader preparation and sufficient connected reading).Authors MUST preserve the content required for the pattern’s declared uses in the publication and its actual available suppliers, while qualifying a compact reading by its intended use and preparation. A condition that changes the current action MUST be available before that action; a needed fuller explanation MUST have a usable return. Apply §4.2.1.1 without imposing full reading, a fixed length or parallel audience versions.Separates sufficient content from the amount read on one occasion; a capable reader’s invention cannot backfill a missing explanation.
CC-SG.18 (Precision before relaxation).Every changed FPF-governed natural span MUST pass the current F.19 connected reading before a Plain, didactic, or coarsened rendering is accepted. If a head, qualifier, relation, or admissible-use boundary remains unresolved, the author MUST take the exact E.10, E.10.ARCH, or subject-pattern route and keep the recovered reading available. E.8 adds no rival sentence algorithm.Keeps simplified prose precise without duplicating the shared language method.
CC-SG.18a (Semio-Echoing auxiliary placement).Semio-Echoing or comparable material MUST remain auxiliary to the pattern’s positive EntityOfConcern, first move, result, and boundary. Add it only for a grounded wording-use overread that changes the reader’s action, route any unresolved claim to its exact subject pattern, and omit a generic counterreading catalogue or row-atomic conformance form.Prevents a guard inventory from replacing constructive method guidance.
CC-SG.18b (Positive subject content and precision-restoration profile control).A conforming pattern’s first substantive Problem frame and Solution content MUST state its positive EntityOfConcern, first useful move, practical delta, and action-changing boundary. Apply F.19 as the common precise-language pass and cite a neighboring pattern only for its concrete contribution. Ordinary PatternID use remains ordinary. Keep current development, review, quality, and projection evidence outside practitioner prose; publish the subject’s architecture and use-changing reasons under E.8:4.2.3.Keeps precision restoration auxiliary to the pattern’s own work.
CC-SG.18c (Kind-preserving wording repair).After words or syntax change, authors MUST apply F.19’s local reread to the changed sentence and meaning-dependent neighbours. The pattern’s EntityOfConcern, practitioner action, first result, and boundary must remain recoverable, and every live kind, relation, use, scope, and action-changing detail must pass the shared kind/loss comparison or an accepted change decision. No per-facet form or authoring ledger is required.Prevents wording cleanup from becoming ontology or use drift.
CC-SG.19 (Use-value carry-through in material revisions).For a materially changed edition, authors MUST apply E.8:4.1.2 once to the actual predecessor and candidate: preserve or deliberately replace useful action, result, boundary, and effort; give candidate-only use an accepted basis; keep positive guidance before optional assurance; and repair every determinate discovery cue and true direct consumer of a changed interface. Each changed natural span, including a list, MUST pass the connected F.19 reading. A clean comparison requires no card, score, or row per idea or list member.Makes source preservation and plain-language repair executable without a per-idea ledger or second enumeration algorithm.
CC-SG.19a (Distinctness is not worth).Under E.8:4.1.3, an action-changing difference MUST NOT by itself justify retain or merge. The changed action, result, boundary, or saved reconstruction MUST also be warranted and useful for the declared reader, use, and scope under the applicable domain, evidence, currentness, affordability, and architecture checks. A distinct but wrong, stale, unsafe, unsupported, incompatible, or needlessly burdensome contribution is repaired, rejected, or left as an explicit gap.Prevents a specificity test from preserving harmful novelty while keeping ordinary comparison proportionate.
CC-SG.20 (Publication-token use discipline).Authors and publication tooling MUST apply H-10’s seven-class inventory. A PatternRef MUST use a PatternID whose surrounding text identifies the framework and MUST resolve in the publication being checked to one complete addressable body; a reference selecting the body published in one edition MUST also name that edition. Authors MUST keep PlannedCatalogEntry mentions explicitly future-facing, preserve complete SectionRef and declared local or alias scope, use <base>.* for family selectors, and keep NonReferenceToken explicitly non-referential. A checker MAY verify and report these facts but MUST NOT decide pattern identity, status, or authority.Lets people and deterministic tooling resolve the same token without treating identifier shape or current position as pattern meaning, inventing missing semantics, or hiding failed references.
CC-SG.20a (Part publication boundary).An assembled FPF publication MUST satisfy H-11 for every compact ToC Part label and corresponding body Part heading, including blank table/label separation and exact ASCII-separator/title agreement; it MUST NOT add an empty compact table merely for a reserved body Part.Keeps Part boundaries portable across readers and Markdown/RAG parsers without duplicating the structural Part view.