Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:45:10 UTC

E.8 - FPF Authoring Conventions & Style Guide

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative)

E.8:0 - Use this when

Use E.8 when you are writing, revising, or reviewing one FPF pattern and need to know what shape, voice, reader-recognition function, and assurance material the pattern must carry before it can be treated as mature FPF text.

For the whole account of an FPF, DPF, or LPF and its substantive profiles, reuse the twelve content functions through E.8:4.1.4 and E.11.PFP:4.7.

Those functions guide the explanation at each selected scale; the individual-pattern heading grammar remains the form for individual pattern bodies.

Use it especially when a draft is technically correct but hard to use: the cold reader cannot tell when to apply it, what action to take, what mistake that action prevents, which related pattern defines or constrains a specific outside claim, or which assurance material is informative rather than the first user-facing guidance.

Not this pattern when. Use E.9 when the main work is deciding why FPF should change and how that decision is distributed across patterns. Use E.19 when the main work is an admission or refresh review. Use the local domain pattern when the question is what FPF says inside that domain rather than how a pattern should be authored.

E.8:0.1 - What goes wrong if missed

A pattern can satisfy a checklist and still be practically unreadable. A draft may open with package architecture instead of a recognisable working moment, bury its payoff, hide the pattern that defines or constrains a specific outside claim, or let assurance prose silently replace the reader-facing claim.

The result is a formally neat text that authors can defend but practitioners cannot reliably use.

E.8:0.2 - What this buys

E.8 gives FPF authors a shared pattern shape and authoring discipline: recognition text first, assurance text second, canonical sections present, terminology kept stable, SoTA used as current practice grounding rather than decoration, and practical consequences visible before a reader has to reconstruct the architecture.

First useful move. Put the working situation, first action-guiding move, practical payoff, ordinary boundary, and nearest heavier assurance condition into the recognition text before tightening template details or conformance material.

Solution and working move. Solution gives the pattern’s conditional answer to its Problem frame, Problem, and Forces: what the reader should do or decide, under which conditions, what result to seek, and when to stop or return.

A working move is ordinary reader-facing wording for one such action or judgement. Reserve U.Move, dated U.Work, and U.Transformation for claims that assert those admitted objects.

E.11.PUA governs use of one selected Solution to reach the first useful result. When alternatives are formally qualified under A.22.CGUS, call them continuation candidates; E.18.3 applies only when the selected CGUS uses a qualifying transformation-flow substrate.

Move wording in pattern prose. In ordinary prose, say recommend this pattern use, coordinate these uses, or show their total order when those are the claims being made.

When the durable governed object matters, use its exact published designation under E.11.PUR: PatternUseRecommendation@Context, PatternUseCoordination@Context, or PatternUseSequence@Context. The suffix is retrieval wording, and the sequence designation requires an admitted total order for the named use.

For any other claim, recover the relation under its governing pattern. State what cited content contributes and use E.10.MOVE when the current relation remains unclear.

Cheap stop. If the draft already gives a cold reader the working situation, first useful move, practical payoff, ordinary boundary, and nearest heavier assurance condition, do not add more authoring apparatus to suggest maturity. Use conformance material to verify that guidance. Do not let it replace the guidance.

FPF-governed wording extension. Add heavier assurance, conformance, SoTA, or relation material only when it changes correctness or use: it repairs a false claim, stabilizes the primary EntityOfConcern, supplies a missing concrete contribution, grounds a practical payoff, or states an action-changing boundary.

Cite the pattern that defines or constrains the value at issue.

When an authoring pass claims quality improvement rather than ordinary drafting, keep these pattern responsibilities distinct.

E.22 frames the improvement-oriented quality-evaluation question. The object-under-improvement evaluation such as E.21 or E.9.DA supplies value meanings and stop meanings. C.16.Q repairs overloaded quality and evaluative-characterization wording. C.25 carries engineering quality-family endpoints when those endpoints are claimed. E.23 governs any repeated quality-improvement method.

Closing checklist rows or satisfying a review profile is not by itself quality improvement.

When a pattern claims practical payoff through a visible score or other proxy, name the intended value and the relation by which the proxy bears on it. If the proxy is being treated as the value itself, apply E.13 before admitting the payoff claim.

Quality or projection evidence placement. Development, quality-review, projection, assembly, and landing evidence belongs in its own evaluation, review, projection, or release carrier rather than in the pattern body. Keep it in a pattern only when that work is the pattern’s declared EntityOfConcern and intended-reader use.

A Part E pattern may govern FPF authoring, review, evaluation, entry, or publication, but it does not narrate the development of its own current version. Judge placement by the sentence’s use, not by a blacklist of words.

Pattern positions across coupled flows. During drafting, E.21 questions may guide a focused author-side check. An overall pattern-quality conclusion requires an independent E.21 evaluation for the declared use. An admission or refresh question uses the applicable E.19 review.

Keep their objects and evidence distinct even when an applicable flow relation connects drafting, review, publication, use, and later refresh. A publication may guide or constrain later Work. Assert the actual Work and its evidence only through the patterns that admit those claims.

Maturity rule. Section completeness is not pattern maturity. A pattern matures when its Problem frame, Solution, worked cases, boundaries, source/SoTA use, relations, consequences, and conformance checks all point to the same usable action guidance for the declared reader and use.

If the reader still needs the DRR, source notes, campaign handoff, or author memory to know what to do, the pattern is not mature for that use.

Primary EntityOfConcern in plain terms. The primary EntityOfConcern of E.8 is the authored FPF pattern: its canonical sections, reader-recognition function, wording discipline, examples, rationale, anti-patterns, SoTA-Echoing, and relations.

Primary working reader. The first reader is an FPF author or reviewer shaping pattern prose for later practitioners and managers. The downstream practitioner is the reader the pattern must ultimately serve, so the authoring guide must model the same recognition discipline it requires.

E.8:0.3 - Pattern Kind In Plain Terms

An FPF pattern supplies action- or judgement-guiding content for a recurring working situation. In ordinary phrases such as “use this pattern” and “apply this pattern”, the acting participant is the agent applying the pattern. The pattern supplies guidance for its work.

Call the pattern content a U.MethodDescription only when it describes one independently admitted U.Method under A.3.2 and that distinction matters to the current claim. Keep the Method and its description episteme separate.

A Solution can guide future action or help choose a Method without establishing that any dated Work has happened. The intended reader, an actual performer System, local system-role classification, assignment, capability, responsibility, authority, result, and Transformation remain separate whenever those claims are current.

When a pattern or worked case does assert dated U.Work, first recover every actual performer’s A.13 core: the admitted U.System, local agential kind and criterion, classification, same obtaining assignment, scope, working situation, window, and adequate core evidence. Add a characteristic profile only when its own receiving use consumes it.

Then independently admit the Work under A.15.1 from its performance history, enacted Method, time, and containing System. Add F.6 afterward only when the pattern also needs precise assignment-bound attribution through that same assignment.

A short practitioner sentence may omit identifiers unused by its receiving claim only when every relation the claim consumes remains recoverable.

Pattern application is ordinary shorthand for user-side use: the agent applying the pattern recognizes the situation and uses its Solution to choose the next action or judgement. The pattern body is description-side guidance. Assert a performer, assignment, dated U.Work, result, or U.Transformation only when independently established and material to the receiving claim. A Conformance Checklist checks the authored description and evidenced use but does not replace the Solution.

The pattern’s main job is constructive action or judgement guidance. In the opening Problem frame and Solution, state the primary EntityOfConcern, first admissible move, first useful result or practical delta, and the conditions needed to understand that entry.

Develop the grounds and connections needed to understand, choose, adapt and combine the guidance in the full explanation. A first useful move is an entry into that explanation, not its completeness criterion. Auditability, conformance evidence and the rationale for packaging the pattern must not displace its subject.

The subject’s own argument is part of the useful contribution: retain the premises, reasons, consequential inferences and limits needed by the declared reader, even when one principle grounds several different moves. Repeat a distinction from another source when the reader needs it to follow or use the argument here. Otherwise refer to the supplying explanation. State what this pattern governs. Do not surround it with an unbounded catalogue of other things.

Name an FPF object by its known kind and state the relation the sentence uses. For a neighbouring pattern, state its concrete contribution and cite the PatternID. Identify an exact episteme, ClaimGraph, edition, or relation assertion only when that identity changes the receiving use.

Put detailed discovery in its dedicated carriers, including README, ToC, E.11, and keep compact pattern relations late in Relations. Do not repeat the same boundary or reference family in small prose variants.

Use E.8 to keep the pattern’s positive subject and action guidance first. Apply F.19 once to each changed natural span as the common precise-plain-language pass. Its connected reading owns language-general semantic completeness and contribution, coordination and foregrounding repair, kind and loss preservation, and local revalidation after wording changes. These facets form one connected F.19 reading, not separate E.8 checks.

For FPF authoring, E.8 adds the pattern-specific question: can the intended reader still recognize this pattern’s EntityOfConcern, working situation, first action or judgement, first useful result, and action-changing boundary before optional modeling and assurance? A cold reader must recover that path from the pattern body. F.19 governs the sentence-level recovery. Do not copy its method, regression table, or result boundary into a local authoring profile.

If the F.19 reading leaves an FPF value unresolved, take the applicable E.10, E.10.ARCH, E.10.ROLE, A.6.F, F.18, or subject-pattern route and state that source’s concrete contribution. Ordinary PatternID citation and “use this pattern” wording remain ordinary. Use an identity-bearing MethodDescription or dated Work claim only when the selected route requires it. Keep development and release evidence outside practitioner guidance unless rewritten as the user’s action or boundary. When an action-adjacent pattern classifies wording or another semio-facing object, connect that classification to the reader’s current action. State the admissible use now and any independently grounded boundary that changes that use. Route any other live claim to the FPF pattern that defines or constrains it.

Semio-Echoing is admissible only for one grounded wording-use overread that changes the reader’s action or boundary. Keep the pattern’s own EntityOfConcern, positive move, and result primary. Use a thin cue to the subject pattern only when its contribution is needed. Do not add a generic counterreading catalogue.

E.8:1 - Problem frame

FPF grows through patterns written and revised by authors from many disciplines. Without a shared structure, practitioner-facing use order, and semantic writing discipline, the framework would fracture or become formally uniform but harder to use, violating Pillars P‑1 Cognitive Elegance and P‑2 Didactic Primacy.

E.8:2 - Problem

Structural drift, stylistic fragmentation, and revision by visible proxies rather than working use threaten five qualities:

  1. Comparability – readers cannot align patterns lacking common headings.
  2. Narrative cohesion – prose swings from dry jargon to informal blog style.
  3. Practitioner use across revisions – cleanup can erase the recognizable situation, first action or judgement, first useful result, ordinary boundary, or affordable stop while leaving a tidier-looking text.
  4. Semantic and relation clarity – generic heads, false agency, imprecise neighboring-pattern contributions, and drifting package or relation words can change what the prose asserts or what a reader may do.
  5. Reviewability after guidance – missing or misplaced grounding, boundary, SoTA, conformance, assurance, and publication-reference material can hide a defect or replace the positive guidance it is meant to verify.

E.8:3 - Forces

ForceTension
Uniformity vs ExpressivenessHow can a consistent template leave authors in different domains free to express their subject?
Rigor vs ReadabilityHow can engaging prose retain formal precision?
Brevity vs CompletenessPatterns need to stay concise while including the required safety subsections.

E.8:4 - Solution — One template, enriched by style principles

E.8:4.1 - Canonical Pattern Template

Within each pattern, the canonical section headings SHALL appear in the order below. For each canonical content section heading (1–12), the <Title> component in <FullId> - <Title> MUST start with the canonical section title or its explicitly accepted alias (case-insensitive match; canonical capitalisation preferred). An optional clarifier after an em dash is allowed (e.g., Solution — …). The mandatory Footer marker (section 13) is the final sentinel and is governed by H-9 rather than the standard <FullId> - <Title> shape.

Extensibility. Authors MAY add sections. Prefer expressing them as subsections under the nearest canonical section (e.g., 4.1, 4.1.1 under Solution). If an additional pattern-level section is necessary, it MUST NOT delete or reorder the canonical sections and its title MUST NOT shadow a canonical title.

Mandatory vs optional.

  • Canonical sections 1–13 are mandatory in every pattern.

  • Canonical sections carry content. Authors must not use omission placeholders as section substitutes. When a section is intrinsically small, write the smallest content-bearing grounding, misuse, boundary, or reduced-case statement that preserves the section’s function.

  • First substantive authoring seed. The first non-empty authored body of a pattern SHALL already instantiate the canonical section frame by value: title line, header block, canonical sections 1–13, and the footer marker.

  • Seed is not maturity. The canonical frame is a minimum authoring seed, not a mature pattern claim. Before a pattern is used for public, teaching, enterprise, reliance-bearing, landing-input, release-input, or ordinary practitioner guidance, each canonical section must carry enough recognition, action guidance, worked material, source/SoTA use, boundary, consequence, and relation content for the declared use.

    A maturity or overall pattern-quality claim needs an independent complete E.21 result for its declared use; an author-side provisional pass or focused repair check does not supply that result. A bounded repair or publication-preservation conclusion uses the checks required for its own question.

    A file with correct headings, thin bullets, scenario labels, or compressed DRR recap remains a pattern seed until the required content is present. A package that keeps it as a seed can mark it seedOnly.

  • Recognition openings and first-minute working guidance belong inside that canonical frame. Place any retained pre-template entry material there as well. Authors MUST NOT start with a separate opening memo and defer the canonical sections, Conformance Checklist, or footer marker to E.19, assembly, or review repair.

Template:

  • Title line: <hashes> <FullId> - <Title>, with an optional (informative) note. Use the ASCII space-hyphen-space separator from H-2.
  • Header block: Type, Status; optional Normativity override.
  1. Problem frame
  2. Problem
  3. Forces
  4. Solution
  5. Archetypal Grounding (Tell-Show-Show; at least one content-bearing grounding slice, reduced grounding case, or ordinary/non-use boundary)
  6. Bias‑Annotation
  7. Conformance Checklist
  8. Common Anti‑Patterns and How to Avoid Them (grounded misuse, text-invited misreading, or a decision-relevant non-use boundary under CC-SG.11)
  9. Consequences
  10. Architectural Rationale (Rationale is an accepted title for the same function)
  11. SoTA-Echoing (current-best problem answer; by-value comparison at comparable effort; explicit trade-off and adopt/adapt/reject decision whenever external or internal practice changes the Solution)
  12. Relations
  13. Footer marker

Footer marker. End each pattern with a single visible sentinel heading line by itself: ### <PatternId>:End. This makes truncation detectable even when HTML comments are stripped or shown by editors. The footer marker is content-free. Do not place prose under it.

Note. Pattern boundaries are still parseable by scanning for the next pattern heading (## …), but a :End marker helps retrieval pipelines (and LLM prompts) distinguish “this chunk is the whole pattern” from “this chunk was cut mid‑pattern”.

E.8:4.1.1 - Heading & ID discipline (human tooling + retrieval)

FPF is often consumed through full‑text search and retrieval (RAG). A reader or an LLM may see a subsection without its parent headings. Headings must therefore be self‑identifying.

The following grammar governs Markdown publication forms authored under this E.8 edition. Its heading levels, separator and sentinel spellings are necessary subject conditions under E.5.1; they do not make the represented conceptual objects depend on Markdown.

Markdown without raw HTML. Markdown publications in FPF Library, and other Markdown publications governed by this profile, MUST NOT contain raw HTML elements or comments, including empty anchors and HTML used for layout. Use Markdown headings, links, tables and images, with the mathematical notation declared by the publication.

Show literal HTML discussed by the text inside code spans or fenced code blocks. Such code, mathematical angle brackets and Markdown autolinks are not raw HTML markup.

The restriction covers complete publications, including framework editions, non-framework References, Readmes and other Library entry material. Preserve information when converting an existing presentation; removing a tag does not justify removing the content it presents.

H-1 (Heading shape). Every pattern heading and every subsection heading inside a pattern SHALL follow: <hashes> <FullId> - <Title> (optional note of non‑normativity)

Exception. The Footer marker is a sentinel heading and is governed by H-9, not by the standard <FullId> - <Title> shape.

H-2 (Heading separator). The canonical separator is ASCII space-hyphen-space, as in <FullId> - <Title>. Previously authored headings may use Unicode separators, as in <FullId> – <Title> or <FullId> — <Title>. Tooling SHOULD treat these as migration candidates, and authors SHOULD migrate touched headings to the ASCII separator in H-2.

H-3 (FullId). FullId is the complete address used by this heading grammar. For a pattern heading it is the PatternID (e.g., A.2, E.10.D1). For headings inside a pattern, append dot-separated ordinal section numbers after the colon (:) (e.g., A.2:4.4, E.10.D2:3). Exception: the Footer marker uses the reserved sentinel token :End as defined in H-9. The colon (:) is reserved for section paths and MUST NOT appear in PatternIDs.

Retained published addresses. When repairing an already published heading, preserve its established address and the contribution it denotes. An existing non-ordinal address is a compatibility exception, not a form for new addresses. Establish that exception from the exact earlier publication and its target; a permissive parser match does not establish it.

An absent address receives a new ordinal address chosen by the source author. A local component, clause or extension name remains its own declaration under H-10; it does not by itself supply the missing subsection address.

PatternID segments may be numeric or mnemonic. When the surrounding text identifies the framework, the complete PatternID identifies one pattern in that framework. The shape of its segments does not by itself state the pattern’s title, meaning, Part, publication position, dependency, Method relation, or use order. A mnemonic segment may help recognition but does not define the pattern.

Whether a PatternID stays with a changed pattern is an authoring decision, not a grammar decision. For a DPF, use E.4.DPF. Use E.11.PFP to show current publication position separately. When the surrounding text does not already identify the framework, name the framework together with the PatternID. Add the edition when the reference must select the body published in one edition.

H-4 (Ordinals). Ordinals in section paths SHOULD track the canonical template numbering (1 = Problem frame, …, 13 = Footer marker) to maximise cross‑pattern comparability. During refactors or in previously authored patterns, ordinals MAY be local. In that case, the canonical section title at the start of <Title> is the semantic key. Readers and tools MUST NOT infer section semantics from the ordinal alone. Architectural Rationale is the preferred title of the Rationale function. Rationale remains an accepted alias. Both identify one canonical content section, so a pattern carries exactly one of them.

When an existing heading is retitled, repair title-dependent links and direct consumers under E.8:4.1.2; retaining its ordinal alone does not preserve a Markdown return.

Keep addresses through change. Inserting, moving or retitling a subsection does not assign its address to a different contribution. Keep existing addresses when their contributions continue. Give a new contribution an unused address. Do not renumber unaffected subsections to restore display order or reuse a retired address for different content. For a genuine replacement, split or merge, decide which contribution continues and state which returns have changed or remain unresolved.

For example, when a new explanation is inserted between existing sections 4.1 and 4.2, an available 4.3 can name the insertion while 4.2 still names its former explanation.

Before publication, compare the earlier and revised targets, preserve the earlier carrier fragments through compatibility facilities permitted by the selected publication form and supported by the access route, and update maintained direct links. Test duplicate-title suffixes and alias collisions as well as visible FullIds.

A saved link must return to its intended contribution or expose that the return is unresolved; reaching a different heading silently is a failure. The author judges the contribution. A link checker can verify the declared correspondence.

Note: the Footer marker is exempt from ordinal encoding. It uses the reserved token :End (see H-9).

H-5 (Where kind and normativity are declared). Pattern kind (for example, Architectural or Definitional) MUST be declared in the Header block, not encoded into the heading text. Normativity (normative or informative) MUST also be declared in the Header block when it deviates from the default.

If a reminder is needed for readers, authors MAY add a short parenthetical note at the end of the heading, for example (informative) or (non‑normative), but headings MUST NOT use square‑bracket tags.

H-6 (Heading levels). Heading levels MUST preserve a fixed offset between structural layers (Part or Cluster (flat) → Pattern → Pattern sections):

  • Part and Cluster headings MUST use # (level 1) across the file.
  • A Pattern heading MUST use ## (level 2).
  • Inside a pattern, each nested section MUST add exactly one # per level (e.g., ## A.2 - …, ### A.2:2 - …, #### A.2:2.1 - …).

H-7 (Ellipsis discipline). Authors MUST NOT use three consecutive dots (...) as punctuation in headings or narrative prose. Authors MUST use the Unicode ellipsis … (U+2026) instead. For editorial elisions in quotations, authors SHOULD prefer […] to make the omission explicit and distinguish it from retrieval truncation. Exception: literal three‑dot sequences that are part of an external language’s syntax MAY appear only inside code spans or fenced code blocks.

H-8 (Normative keywords). The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in RFC 2119, as clarified by RFC 8174 (only when capitalised). Authors SHOULD avoid informal deontic phrasing (“need to”, “is required to”) in normative clauses.

Deontics vs admissibility. Use RFC keywords only for deontic obligations (requirements on authors, reviewers, implementers/tooling, or published pattern or companion texts). These concern things an agent can choose to do or omit. Do not use RFC keywords to state definitions, structural invariants, typing rules, or other admissibility conditions of the modeled world.

When you need an enforceable constraint that is mathematical rather than deontic, express it as a non‑deontic predicate using one of: Definition:, Invariant:, or Well‑formedness constraint: (optionally with formal quantifiers). Prefer mathematical terms like cardinality 1..1 (total), 0..1 (partial), or 0..n over deontic adjectives like “mandatory or optional” when the intent is cardinality, not duty.

Admissibility predicate discipline (recommended shape). When expressing admissibility or validity constraints as predicates (Definition:, Invariant:, or Well‑formedness constraint:):

  • Authors MUST NOT use RFC keywords inside the predicate block.
  • Authors SHOULD give each predicate a stable identifier and short name (e.g., RA‑1 (Locality), RE‑3 (Method gate)), so that Conformance Checklist items can reference it without re‑authoring the rule.
  • Authors SHOULD write the constraint as a declarative predicate with a truth condition (optionally quantified), for example “every selected interval lies within the declared qualification window”, rather than as “X MUST …”.
  • If the constraint needs to be checked as part of pattern conformance, authors SHOULD reference the predicate identifier from the Conformance Checklist, and state validator behaviour when relevant, rather than duplicating the predicate with RFC keywords.

H-9 (Footer marker sentinel). Footer marker SHALL be a single heading line whose FullId is the pattern ID followed by the reserved sentinel token :End (no ordinals, no title, no square‑bracket tags): ### <PatternId>:End Apart from a retained published address under H-3, it is the only allowed heading inside a pattern whose section token is non‑numeric. It MUST be the final line of the pattern and MUST NOT carry any prose. Tooling and readers MUST treat it as a boundary sentinel, not as a semantic section.

H-10 (Publication-token classification and addressability). Before emitting an FPF-governed token as a reference, authors MUST classify it under exactly one of these seven E.8-local publication-token classes and use the matching form:

  • PatternRef uses one PatternID to name a pattern that continues across editions of the framework identified by the surrounding text. In the assembled publication being checked, it resolves to one complete H2 body, one matching :End, and a truthful ToC status for that PatternID. A reference intended to select the body published in one edition also names that framework edition. A structural checker may verify and report publication conformance but does not establish the pattern’s identity, status, or authority.
  • PlannedCatalogEntry names an explicit future catalogue commitment. It has no current pattern semantics, governing force, prerequisite force, or addressable body. A useful prose mention MUST say planned or future, and a current semantic dependency MUST cite existing content that supplies the needed definition, constraint, test, method, or other rule, or state the current gap.
  • SectionRef names one exact heading path inside one current pattern, one framework publication unit declared under E.11.PFP, or one non-framework Reference declared under E.11.DSG. Authors and tooling MUST read the complete section identifier and its declared scope before examining any substring. For example, STR.Reference:1 returns to the Strategy Architectural Reference. It does not declare a pattern named STR.Reference. Similarly, Engineering.Reference:2.1 returns to a section of the Engineering Suite Reference without declaring a pattern or a framework named Engineering.Reference.
  • LocalDeclaredId names an exact declaration within one pattern, such as a conformance clause, component, interface row, or predicate. Its scope is local unless an explicit stable anchor or a separate promotion decision establishes wider use.
  • LocalAlias names a declared compatibility alias and resolves to its declared canonical local target.
  • PatternFamilySelector selects a navigable pattern family using canonical spelling <base>.*. It requires a current base pattern and at least one current matching member and MUST NOT stand in for one exact governing target.
  • NonReferenceToken classifies a schematic example or ordinary local prose/code that neither occupies a reference-bearing position nor declares a local public ID. This class denotes no reference. Key-like typography or backticks alone do not change that class.

A portable reference MUST let the reader recover the intended document within its publication set and the intended contribution from the reference and the context that travels with it. Preserve the complete PatternID or SectionRef when the contribution has one. Add the publication set, the document’s full title or its explicitly declared DocID only where that identification is not already unambiguous. Do not repeat a qualifier that the complete address and retained context already supply.

For example, once FPF Core is identified, C.39:4.1 is sufficient. Use FPF C.39:4.1 when the document qualifier is needed. Resolve the complete address under its declarations rather than inferring its scope from a fixed substring.

A DocID identifies a whole document. It is not a new PatternID, an edition identifier, a publication-unit identifier, a globally unique name, or an eighth publication-token class. An existing framework code may serve as its DocID only through an explicit declaration.

A whole-document reference needs only enough information to identify that document. A reference to an ordinary unnumbered heading adds its title without inventing a PatternID. Name a selected edition separately when its exact published body matters. When extracting a fragment, restore any identifying context that will no longer accompany it.

A URL, file path or service locator is an optional projection to an access carrier, not the portable reference’s identity. To resolve a reference, recover the document and publication set from the complete reference and retained context, then match the complete local address or named unit in the available text.

A catalogue may associate those declarations with current carriers. A changed carrier does not change the reference. Preserve any more precise valid SectionRef already stated in a link’s visible label even when the URL lands at its enclosing body.

If the document, target or requested edition cannot be recovered unambiguously, report that unresolved reference rather than silently substituting another document, section or edition. These requirements add no URI syntax, HTML anchor or service API.

Resolution and checking are declaration-first and context-sensitive. Authors and tooling MUST NOT split complete SectionRefs, strip a local-ID prefix, promote a local symbol by visual resemblance, or replace these classes with an ignore list. An unresolved token in a reference-bearing authoring form is an error. Ordinary code or local wording is not silently upgraded to a reference.

H-11 (Assembled Part boundaries and title agreement). In the assembled publication, every compact ToC Part label MUST be a bold separator with a blank line on both sides, not a duplicate structural Part heading. Its title and ASCII space-hyphen-space separator MUST agree exactly with the corresponding # Part <letter> - <title> body heading. A reserved body Part that has no compact ToC table, including current Part H, does not require an empty compact label or table.

Problem frame names the working situation. Generic Context and universal U.BoundedContext do not identify the actual value a claim needs.

For each use, go directly to the rule that supplies the needed value. Recover source-local meaning through F.0.1, use F.1 to select answer-changing sources, state ClaimScope through A.2.6, and use A.1.1 for an admitted bounded-model use.

Add F.17 only when a durable address or basis relation is needed, F.9 only for an obtaining Bridge between two exact local senses, and the applicable plane relation for a ReferencePlane claim. Otherwise leave the relation unasserted rather than inferring it from a shared word, source, or context.

E.8:4.1.2 - Preserve Pattern Use Value Across Material Revisions

A revision is material when the change can alter what a working reader recognizes, does, obtains, or must stop doing, regardless of whether the change is labelled as cleanup, clarification, terminology repair, or ontology alignment. Treat the revision as material when it can change at least one of these values:

  • the primary EntityOfConcern, governed kind, direct relation, claim kind, or scope;
  • the recurring situation or practical question that lets a reader recognize the use;
  • a Solution action, action condition, result kind, first useful result, stop, return, risk disclosure, or stronger-neighbor handoff;
  • the definition, constraint, test, method, cited-pattern contribution, split, merge, relocation, or source/SoTA stance that changes what the reader may do;
  • the asserted commonality, member set, membership rule, order, or governing premise of a list; or
  • ordinary first-use affordability.

For this comparison, the earlier edition is the exact accepted pattern edition that this candidate is intended to replace for the declared use.

A formatting correction, spelling repair, citation repair, exact mechanical rendering, or wording change is not triggered only when the smallest comparison of the earlier edition and proposed text shows that all these values are preserved. A clean comparison needs no additional positive ledger, evidence table, or pattern section.

Physical line count, file size, section count, inventory rows, and the author’s label for the change do not establish materiality.

Use one bounded material-revision loop over the actual prose. Before treating a materially revised pattern as authored:

  1. Recover the useful earlier-edition use at idea level: the recognizable situation and intended reader, first admissible action or judgement, first useful result, action-changing boundary or stop, and any domain claim, example, or relation needed to perform that move. Classify a changing or disappearing earlier-edition use only as retained, a valid outcome whose defective mechanism is repaired, an explicitly authorized retirement with a corrected action or boundary, or unsupported residue.
  2. Draft the candidate’s positive practitioner path in domain-recognizable language before guards: governed subject, recurring problem, action the reader can take, first useful result, and next action-changing condition or stop.
  3. Compare the earlier edition and proposed text at comparable application effort. Preserve every useful earlier-edition move or deliberately replace it with an at-least-equally-usable action, result, or boundary. Admit a candidate-only use only from an exact accepted decision, source/SoTA stance, finding, or working need.
  4. Apply F.19 to each changed natural span. Remove exactness intensifiers, invented counterreadings, role or process wrappers, formal identities, and assurance apparatus that fail its contribution test, while preserving every kind, relation, use, and action-changing detail. Keep ordinary pattern-use wording ordinary; open a deeper FPF route only for an unresolved value.
  5. Check that recognition, first action, and first useful result still precede optional modeling, evidence, conformance, and assurance work. F.19 is the common semantic pass over the changed span. E.10 supplies cues and routes unresolved FPF wording to its governing rule, not a second normal-pass algorithm.
  6. For every changed public or consumed interface—entry wording, input or result, field or position meaning, action order, stop, return, or reconsideration condition—repair each determinate stale ToC or README cue, example, relation, and direct consumer in the same authoring increment. Find consumers by the meaning they teach or use. A shared word, identifier, or nearby reference is not enough.

Earlier-edition and candidate-only uses remain different bases, and both may be present in one revision. Compare that exact earlier edition with the candidate edition. An earlier-edition use keeps its earlier-edition basis and one of the four classifications above. A candidate-only use keeps its exact accepted basis. Do not classify a candidate-only use as an earlier-edition use or invent history for it.

Treat a selected use as required when its loss changes action or boundary, and as optional when it demonstrates breadth only. Backward compatibility alone is not improvement, and a candidate-only promise is not improvement until the text supports its executable use.

Use desk replay by default and escalate to a cold reader, AI-agent, or observed-work check only when ambiguity or consequence justifies it. If later independent review needs a recoverable note, use the smallest existing authoring source. Do not create a card, score, universal schema, or one written row per idea.

Test first-use affordability by checking whether the positive Solution supports this short rendering:

recognizable situation -> proposed action or judgement -> first useful result -> next action-changing condition or stop

This rendering explains the pattern. It does not claim that actual work is linear. Use an optional local mantra only when it improves recall, and show one ordinary traversal only when several rows materially improve explanation. Choose the smallest form that keeps the action, result, and boundary recoverable.

Explanatory rows may fade as competence or task demand permits, but an independently action-changing condition or boundary may not. An explanation retained for reuse can concern the actual subject, question or proposed continuations before CGUS qualification. Use C.2.1 when its episteme identity matters. A demonstrative slice about a qualified CGUS is a separate episteme under A.22.CGUS, whose use depends on that qualification.

Put a subject-side check immediately before the continuation it changes, and keep authoring, review, quality, and release checks outside the subject Solution.

Resolve authoring lists with F.19. When a list can change pattern use, apply the same connected F.19 reading used for prose. E.8 keeps only the authoring effect. Put the practitioner’s proposition or action before illustrative material. Declare a normative closed set as closed under its governing rule. Signal examples as non-exhaustive when a plausible reader could mistake them for a classification. Do not let a noun series or catalogue replace the Solution.

Do not add a second enumeration taxonomy or a per-member result form. E.10 may cue a suspicious head or series, F.19 decides its membership semantics and discourse load, and the applicable subject pattern settles any unresolved kind, relation, or normative set.

E.8:4.1.3 - Decide Whether a Narrower Contribution Changes Practice

Use this when a broader available contribution and a proposed narrower contribution both appear to answer the same recognizable working situation. State the intended reader, use, and scope. Apply both contributions at comparable effort and find the first difference in what the reader notices or decides, does, needs or checks, obtains, or uses as a stop, return, or retry.

A narrower title, domain noun, paraphrase, or extra example is not enough by itself. If no action-changing difference remains, omit or merge the narrower text and point to what already answers the situation.

If the two contributions address different situations, state that boundary before deciding their relation.

Developing a Method often involves methodological synthesis: selecting, adapting and connecting available operations and their conditions. C.39:4 develops that general work, including explanation for later use and selective change, without requiring framework authorship.

A working account of the relevant objects and relations can develop with it; use F.0.2 for semantic synthesis across source ontologies and A.7.1 for a consequential ontological repair. E.4.CM applies the general way to a framework’s connected Methods and their public explanation.

The authored pattern is an episteme about the Method and its use. Its content includes the reasons, conditions and relations needed to understand and adapt the way. The canonical template organizes that content rather than supplying missing operations.

For a proposed composite Method, compare the whole’s organization and explanation as well as its constituent operations. Apply the same use comparison to an account of independent Methods: compare the explained result uses, shared conditions and returns without assuming one composite. Existing operations do not by themselves supply selection, joining, coordination, adaptation or return rules. C.39:4.3–4.6 develops those connections. E.4.CM adds their framework-authoring treatment. A supplier list or an expert’s private successful reconstruction does not establish that the public explanation is sufficient.

An action-changing difference shows that the contribution is distinct. It does not show that the contribution is worth keeping. Retain or merge it only when the changed action, result, boundary, or saved source reconstruction is warranted and useful for the declared reader, use, and scope under the applicable domain, evidence, currentness, affordability, and architecture checks.

Use only the checks that can change this decision. Repair or reject a distinct contribution that is wrong, stale, unsafe, unsupported, incompatible, or needlessly burdensome. Keep an explicit gap when no acceptable contribution answers the situation.

Naming a dependency does not settle the comparison. Say which available result supplies the reusable part, what kind of result it is, which product and edition or current state supplies it, how the reader uses it, and which currentness or availability condition can change that use. State maintenance separately only when it changes the receiving use. Then preserve any remaining domain problem, filling, constraint, relation, evidence limit, return, or discovery need without copying the general rule.

When reuse or a gap closes the reader’s question, state which of these applies:

  1. Use an available result. Name the result, what kind of result it is, the product and edition or current state that supplies it, the receiving use, and any currentness or availability condition that can change that use. The supplying product may be an FPF, DPF, LPF, or a separate non-framework product. If maintenance changes the use, state its separately established relation and evidence.
  2. Use a MethodDescription. Name the public description, the Method it describes, and how the reader uses the description to select or perform that Method. State availability, currentness, or a separately established maintenance fact only when it changes that use. Do not report the expected result as already obtained.
  3. Use a direct source as evidence. Name the source, the claim or decision it supports, the receiving use, its limits, and a usable locator. Source availability is not result production.
  4. State a named unavailable result. Name what is missing, the action or decision it blocks, the missing condition, and the observable condition for retry.

For example, “feed the animals” may be true for both a mouse and a tiger yet fail to tell the feeder what food to give. Grain and meat change the action, so keep or link the animal-specific guidance when that difference is warranted for the declared use.

By contrast, a pump-maintenance restatement of an available evidence-use contribution adds nothing if it changes only pump nouns and one example. Omit or merge the restatement, point to the maintained result that already answers the situation, and judge any promised maintenance-framework coverage separately.

A tiger-feeding proposal may instead require manager approval and a laboratory certificate before every ordinary feeding. That proposal changes the feeder’s action, but if no safety rule, evidence limit, law, or observed failure warrants the burden for the declared use, reject it or repair it to the smallest warranted check. Distinctness alone does not preserve it.

A result maintained outside the receiving framework may answer the reader’s use without becoming part of that framework. In a package-coverage account, count that external result only when the exact result and supplying product, receiving use, practical discovery route, and any material currentness or availability condition are explicit, and say that the result remains external. Otherwise keep the promised family as a gap or omission.

When the resulting stable pattern set materially changes a promised problem family, obtain a current E.4.DPF.DA D12DomainProblemFamilyCoverageAdequacy result for the resulting exact DPF or LPF edition. Reuse a matching current result when the exact edition, promised families, declared use, relied-on results, and relevant conditions did not change. Do not record proof that a revisit happened.

E.8:4.1.4 - Carry the content functions across Method-description scales

Begin with the practical explanation developed for its intended use, using C.39:4.5–4.6 and the relevant professional Methods. Framework authoring applies the twelve functions below to make that content understandable, examinable and reusable as a pattern or connected framework account. The general development of a Method does not depend on choosing this format. A sufficient procedure, calculation or ordinary description can serve another receiving use.

Use the twelve substantive functions in the canonical template as authoring questions for a whole FPF, DPF, or LPF and each selected substantive profile. E.11.PFP:4.7 governs their public answers, inheritance, and placement in the framework’s publication units. The same functions can describe a broad Method, a composition of Methods, or a narrower use. The declared subject and applicability determine the scale.

The Solution explains the organization and use of the described Methods: their contributions, relations, and the results that make a next move possible.

Architectural Rationale explains why that organization and those choices serve the declared use, which alternatives were considered, their trade-offs, and the conditions under which another choice becomes preferable. Preserve shared source explanations there when users need them to understand or adapt several patterns together.

The same explanation must make recoverable how constituent actions perform encompassing work where that connection matters to learning, performance or change. Show what larger work is already being done through the selected action, what constituents make that action possible, and which conditions of the whole constrain it. Preserve genuine result-before-use dependencies alongside the constituent–whole relations of the relevant Method and Work structures.

A representative case should let the reader change the action when a relevant condition of the whole changes. Use B.1.5.EW for recovery and B.1.5.RS for a constituent replacement. Do not require a separate level diagram or exhaustive decomposition when the connection is already understood.

The pattern heading, header block, section grammar, and footer apply to each individually declared pattern. The whole-framework account uses the publication form in E.11.PFP. Its content questions do not turn every publication unit or intermediate group into another pattern. Its Architectural Reference subsection headings identify the framework, publication unit and ordinal path through E.11.PFP:4.7.1, so an isolated excerpt remains locatable without being classified as a pattern body.

Keep generality, specialization, Method composition, reuse, bounded-use projection, and publication grouping explicit under E.8:4.2.2. There is no prescribed maximum depth or exclusive-parent rule.

E.8:4.1.5 - Choose a title that helps the reader select the pattern

Choose the title from the working question the body answers. Read its Problem frame, Problem, action-changing Forces and Solution together. Recover the intended reader, governed object, useful result and nearest non-use boundary before trying shorter wording. The title should let that reader consider the pattern without already knowing an unfamiliar solution name.

Use a recognizable question, a result under distinguishing conditions, or a familiar method name. Preserve the object and condition that separate the pattern from its nearest neighbors. “Test a method” cannot distinguish obtaining trial observations, checking description coherence, judging fit in another situation and comparing practical worth. A single striking example should not narrow a more general construction, and a failure symptom should not hide constructive use before anything goes wrong.

Keep a choice open when making that choice is part of the Solution. A method that first decides whether further evidence is worth obtaining can finish with an existing answer. “Design experiments” would hide that first result. Name whether and how to experiment when both questions belong to the method. Conversely, retain a direct action title when that action is already the justified entry.

Keep an established technical term where the intended finding or discussion needs it. A quotient method can pair a phrase about treating objects as the same with quotient. A definitional pattern can retain its technical name and add a short recognition phrase. The technical designation and recognition phrase explain the same subject. Use the existing ToC keywords and query cue for additional familiar expressions. If the intended search sees only headings, a body-only term cannot support that search.

Compare the candidate with the present title and the closest plausible neighbors at the actual entry: title alone, complete ToC row or other displayed cue. Include a use the pattern should attract and an ordinary case it should leave elsewhere. Open the bodies to check that the proposed result and boundary survive. Retain a sufficient title, or improve only its existing cue when that resolves the difficulty. A question shape, complaint form, shorter length or uniform style is not a reason to rename.

Finish with the chosen title and its truthful discovery cue. Keep the PatternID unless the governing continuity decision changes identity. Repair title-dependent fragments and direct navigation consumers under §4.1.2. E.11 supplies comparison under the reader’s actual exposure. A clearer title supports consideration. The Solution must still supply the method and any connected explanation needed to use it.

E.8:4.2 - Stylistic Principles (S-0 … S-19)

#PrincipleGuideline
S-0Governing-claim flowBegin with the recognisable working situation and governing claim or action. Add context, grounding, examples, and a closing line only when they help the reader understand or use that claim.
S-1Density without JargonShort declarative sentences. Incidental tool details belong in Pedagogy/Tooling. Retain necessary subject syntax under E.5.1.
S-2Internal CohesionInline references to Pillars and related patterns.
S-3Embedded Mini-DefinitionsGloss a new term in parentheses on first appearance.
S-4ContextualisationBrief historical or disciplinary lineage references.
S-5Grounded ClarificationState the pattern’s positive object and move first. Apply the F.19 plausible-reader guard test. Retain a local negative boundary only for a grounded misreading that changes understanding or action.
S-6Earned closing lineEnd when the result or boundary is clear. Add a memorable line only when it reinforces that result without introducing a new claim or displacing the practical close.
S-7Generative over PrescriptivePresent rules as enabling constraints, not bureaucracy.
S-8Grounded transfer examplesUse examples from other fields when the pattern claims transfer breadth and each example changes recognition, application, or a boundary. No fixed example count establishes breadth.
S-9Physical Grounding ReferenceGround an abstraction about action in the system that acts or is to act and the subject it affects. For other change, identify the changing subject and the conditions or dynamics the claim uses. Mention a local transformer system-role classification or an obtaining assignment only when it changes the claim. Ordinary transformer may remain readable metonymy for the acting system.
S-10Readable blocksKeep the governing claim with the explanation needed to use it. Split prose or use a list only when that structure makes the reader’s work easier. No sentence or item count is a verdict.
S-11Narrative FlowForeground the governing practitioner claim or action and let the section read as a continuous explanation. Apply F.19 when coordination, catalogues, or modifiers create bullet soup or delay that message.
S-12Full claims over tagsUse a clause when a list item carries a claim or action. Labels, values, and locally complete steps need no artificial subject-and-verb expansion. Item count and sentence count are not verdicts. Use the F.19 contribution and list tests.
S-13SoTA-Echo structureName the practice question, selected best-known line, serious alternative or default, defect overcome, exact pattern mutation, source roles and limits, and reopen condition. Assign roles from answer-changing content, not authority, prevalence, freshness, or praise. An official source may be the best-known line if its answer wins. Lineage-only and identity/currentness-only material stays outside.
S-14Didactic-content sufficiencyNew and substantially revised patterns carry enough didactic content to be teachable without nearby project notes.
S-15Worked slices over scenario labelsTransform-like families show at least one concrete source and resulting-publication slice. Scenario names alone are not enough.
S-16Ordinary vs FPF-governed wording realismKeep ordinary use light, and make heavier review records explicit only for disputed, high-risk, or higher-impact cases.
S-17Self-contained monolith proseA merged pattern must explain itself inside the monolith. Planning shorthand and review-context dependencies are not admissible in pattern prose.
S-18Intended-reader disciplineAddress the intended framework user. Explain the Methods, their organization, alternatives, costs, and use-changing reasons in the public body. Keep current development, review, evaluation, projection, and landing correspondence in its own carrier under E.8:4.2.3.
S-19Precision before relaxationApply the connected F.19 reading and kind/loss comparison before accepting a plain or didactic rewrite. Route only an unresolved FPF head, qualifier, relation, or admissible-use question to E.10, E.10.ARCH, or its subject pattern.

Use the principles to make the explanation coherent and readable. Semantic discipline takes priority over engagement. Hooks, quotable lines, Plain restatements, and didactic images may improve recognition, but readers must be able to recover any ontological, evidence, causal, assurance, bridge, gate, work, decision, or admissibility claim kind or admissible-use boundary they carry through the governed Tech reading or named neighboring pattern.

Ordinary Plain prose without that claim kind or admissible-use boundary stays ordinary prose.

S-0 (Governing-claim flow) — explanation

Open with the recognisable working situation and the claim or action that governs the passage. Add history, related patterns, examples, imagery, or a recall line only when it helps the intended reader understand or use that claim. A prerequisite may come first when the reader needs it to interpret the claim or act safely. Apply F.19 when atmosphere, coordination, or rhetorical scaffolding delays the governing message.

E.8:4.2.1 - Recognition text and assurance text

Every canonical pattern SHALL stabilise one primary EntityOfConcern, relation record, or claim record early enough that a cold reader can tell what kind of thing the pattern governs. If ordinary forms vary (note, sheet, guided UI, rendering, review aid), the text must identify which are presentation forms of the same primary EntityOfConcern, relation, or claim and which name a different act, process, work-result record, or governing companion.

Recognition and assurance texts may refine that selected item differently, but they must not silently swap the central kind.

If a pattern uses a broad umbrella or head together with a narrower operative branch, the text must tell a first-time reader what the broad head names, which narrower branch applies, what primary EntityOfConcern, relation record, or claim record the branch governs, which exact action assertion and predicate apply, and what wider work or process remains outside the pattern. A qualifier alone does not restore that stack.

Recognition text and assurance text name two reading-order functions carried by existing sections or projections inside one pattern. Additional didactic scaffolding remains optional and is justified when the family is especially easy to misuse, easy to over-read, or hard to teach. The instruction needed for the pattern’s declared use is part of its substantive contribution under §4.2.1.1, not optional scaffolding.

The recognition text is the first-reading text. It is the part of the pattern that lets a cold working reader recognise the situation quickly enough to decide whether to keep reading. It should start from a subject-domain or practice moment before internal taxonomy whenever the pattern is meant to guide work beyond internal canon maintenance. In practice it usually appears in an early Use this when line or equivalent opening, plus the upper parts of Problem frame, Problem, Solution, Consequences, and nearby worked slices. Its job is to make visible:

  • what ordinary working situation this pattern is for;
  • what goes wrong if the pattern is missed;
  • what the pattern buys the reader in practice;
  • when this is not the right pattern;
  • what primary EntityOfConcern, relation record, or claim record stays fixed;
  • and, when technical terms must appear early, a pairwise plain gloss for each early FPF-governed technical term.

The assurance text is the second-reading text. It carries the heavier FPF-governed material that makes the pattern reviewable and auditable:

  • declaration blocks and typed fields when those are part of the pattern’s declared conformance or boundary claim;
  • representation ontology, EntityOfConcern discipline, or primary-EntityOfConcern discipline;
  • any minimal modeling or mathematical lens that keeps the primary EntityOfConcern, relation record, or claim record stable;
  • guidance or check material, invariants, admissibility, and stop or neighbouring-pattern conditions;
  • SoTA-Echoing when it carries explanatory work;
  • and the review hooks that let a broader or more consequential interpretation or use be checked.

The assurance text may sharpen, justify, and discipline the recognition text. It must not silently replace, strengthen, or universalize the claim that the recognition text made visible. If the recognition text says “this pattern helps with a bounded working situation”, the assurance text must not quietly turn that into an unbacked carrier claim, unbacked guarantee, or broader universality claim.

If a pattern claims universal or transdisciplinary status, that claim must already be visible in the recognition text. It is not enough for universality to appear only later in a guidance or check sheet, declaration block, or SoTA-Echoing rationale. A broad claim should therefore be demonstrated in the recognition text through heterogeneous reader or domain situations adequate to the claimed breadth. The separate three-domain minimum in A.8 applies to universal-core U-kind admission. When a compact matrix helps, F.16 is the preferred template for showing that breadth. If SoTA-Echoing carries an FPF-governed claim, the practical implication of those rows should be recoverable from the recognition text and case bank rather than remaining a late-only justification layer.

Additional didactic scaffolding helps readers with a particular interpretation or learning difficulty after the necessary instruction is present. Useful additions can include:

  • at least one concrete source and resulting-publication slice in Archetypal Grounding when the pattern defines or constrains transforms or publication change;
  • at least one boundary-heavy example or anti-example when nearby or companion patterns are easy to confuse;
  • reviewer guidance that says what to inspect first, names the neighboring FPF pattern that defines or constrains the failure mode, and gives the project-side FPF kind and reference by value for the claim or effect;
  • local mini-definitions or glossary material for recurring terms that would otherwise be recovered only from project context.

Provide enough recognition, assurance and, when needed, additional didactic material for the reader to understand the pattern, apply it in ordinary cases and recognise when a heavier review profile is required.

E.8:4.2.1.1 - Provide enough explanation for the reader’s use without requiring a complete reading

Use this authoring move when the intended users differ in relevant preparation, when a complete account burdens a current application, or when a compact instruction leaves its selection, adaptation or combination unexplained.

The useful result is a sufficient connected reading for the present use, with the fuller content and its suppliers still available for the uses the pattern promises.

Distinguish preparation from coldness and purpose. Under F.19, a cold intended reader lacks the author’s private context; that reader can be an expert. The plausible-reader test uses the knowledge and task the text reasonably presupposes.

Under C.2.8, identify the useful structure to recover and the preparation, operations, help, access and effort budget that matter. Knowing the subject, knowing this framework’s distinctions and knowing how to change a particular Method are different capabilities. A model name or broad professional qualification does not establish them.

Keep the full contribution and the present reading distinct. Maintain the explanation needed for the declared uses in the pattern language and its public suppliers. A body may rely on a common worked application or an already explained constituent Method when the contribution and usable return are clear. The reader need not load every such explanation for every use.

A short problem–solution instruction can serve recall or a familiar application; its success does not establish that it supports learning, adaptation or combination. Canonical headings and additional words likewise do not establish sufficient content.

Construct the reading from the work the reader needs to accomplish:

  1. Keep the receiving question fixed. Determine what the reader must recognize, infer, perform or change here. Use available evidence or explicit assumptions about relevant preparation.

    If a missing prerequisite changes the next explanation, expose it and provide the needed support or return. Do not silently raise the reader’s preparation or narrow the requested work to make an inadequate explanation appear sufficient.

  2. Carry the connected instruction. Retain the operation with its necessary inputs, distinctions, conditions and use-changing reasons. Ordinary prior knowledge may supply a familiar notation or inference. The new synthesis, exceptional condition or relation being taught must be supplied by the publication or an identified available source, rather than invented by the reader.

    When several Methods work together, retain what connects their results and how constituent actions enact the encompassing work; independent reminder phrases do not explain that connection.

  3. Choose what is needed now and what can be reached later. Keep a meaningful inference together. An applicability condition that changes the current action belongs with that action even when its derivation is elsewhere.

    Give a direct return to the fuller explanation and state the situation that calls for it: an unfamiliar operation, changed premise, disputed ground, or proposed adaptation, for example. A reader who cannot recognize such a condition needs enough explanation or assistance to recognize it before relying on the compact instruction. One sufficient reading path needs no additional version.

  4. Compare the actual use and burden. Follow C.2.8, E.12 and F.19 for the appropriate recovery question and evidence. Keep the task, preparation, assistance and access conditions comparable; distinguish an expert walkthrough, an actual reading and an assisted retry.

    Include an affected changed case when the promised use includes adaptation. Consider navigation, source retrieval and reconstruction as well as the amount of text. Preserve a sufficient existing account when another form gives no worthwhile improvement.

  5. Repair the missing contribution or the reading arrangement. Supply an omitted relation, make a consequential condition visible, explain a prerequisite or improve access to a supplier.

    If the required content cannot be used reliably within the present budget, change the support, work decomposition, reader allocation or budget. Leave the original unmet use explicit until it is supported. A lower-cost answer to a different question does not satisfy it.

Develop a missing instruction. Work through the promised use with a concrete input and the reader’s stated preparation. At every consequential inference, choice or action, ask what the reader has at that point and what the next result requires.

Follow an unexplained requirement backward to its producer, then attempt the connection forward. Include a branch or a change of scale when the promised use depends on it. A jump from a source result to a conclusion, or from a constituent’s success to the whole’s success, is a candidate gap even when each sentence is clear.

Determine what is missing before rewriting. If the author performed an unreported interpretation, selection, conversion or coordination, recover how it was done and why its result was acceptable. Write the determining distinction and operation, show the intermediate result, and explain how the next operation uses it.

For a judgement, expose the evidence and criteria that distinguish materially different answers; do not invent a mechanical rule where professional judgement remains necessary. A worked example should reveal the reusable reason for the step, not merely the author’s chosen answer.

If the operation is available elsewhere, supply a usable return to the explanation and make the required input and resulting contribution clear. Ordinary knowledge reasonably presupposed for this reader need not be retaught.

If the operation itself is unknown or its necessary evidence, means or capability is unavailable, prose repair cannot provide it: develop the operation through the relevant subject Method, use C.39.RO for a missing reusable construction, or keep the exact use-changing gap explicit.

The instruction “adapt the method” does not supply an adaptation being promised to the reader. If the complete explanation already exists but is lost in the reading arrangement, restore access and the conditions needed to choose it.

Recover the recurring problem–conditions–remedy relationship from the case. Separate what the reader must preserve from values or choices that change with another instance. Work through a consequential variation to expose that distinction, especially when the pattern promises adaptation or combination.

Repeatable use need not give an identical output: changing valid inputs can rightly change the result. Where the claim is reproduction of a particular research result, specify the intended comparison and agreement conditions rather than substituting successful use of the general Method.

Continue through the promised result and its material returns, not just the first repaired sentence. Keep independent uses distinct when they need different contributions. Stop elaborating when the intended reader can obtain the necessary operations and connections under the stated preparation and access, or when an explicit unresolved contribution limits the claim. More elementary detail is unnecessary when it changes no declared use.

Apply the connected F.19 reading to the resulting explanation and its actual public presentation; that wording judgement does not establish the Method’s subject-matter effectiveness.

Worked authoring repair. The date-conversion case in §4.2.1.2 develops the missing source-to-order selection and then constructs the expression that makes it usable. The converter can perform its operation once the applicable source supplies the order; ambiguous characters alone supply no such interpretation. The case preserves both correct conversions and the changed-source stop while comparing the forms that carry this connection.

Divide a method account from pedagogical companions by the work each supplies. A pattern can state a Method adequately for competent readers while a pedagogical companion provides the fuller teaching needed by a less prepared audience. Completeness is relative to the declared use and the sources that supply it; it does not require every beginner explanation in the pattern body.

The pattern’s contribution still includes its problem and frame, forces, operative distinctions and connections, conditions, grounds for important choices, and criteria and limits of the result. Keep or directly supply the worked and changed-condition reasoning that the declared use needs. A title list or imperative sequence is insufficient when a competent reader must invent why its steps connect.

A competent author of instruction should be able to reconstruct what must be learned and preserved from this method account and its named accessible suppliers. State relevant prerequisites rather than presupposing an unspecified “smart reader”. A reader may know the domain but not the framework, or know the framework but lack the subject skill. Competence in the subject Method also does not automatically supply competence in teaching it.

A companion may explain prerequisites, add analogies and more examples, arrange a progression of tasks, provide practice and feedback, and gradually remove assistance. It can also supply extensive derivations and worked applications to which the pattern returns where needed. Distinguish these additions from the subject Method’s essential rules.

A new pedagogical Method is content in its own right, not merely a different publication form of the subject pattern. E.11.PFP:4.4 selects a support publication unit or a separately identified product when that boundary matters. Different audiences need not receive independent authoritative copies of the subject Method.

To choose the division, follow one intended use and one consequential variation. Identify the missing competence or explanation, then decide whether the repair supplies an unexpressed subject-method connection, a learning activity, or a better presentation of an existing explanation.

Place the missing subject-method connection with its Method owner or the public source that supplies it. Give audience-specific learning activities and their pedagogical grounds to the companion. Repair presentation where the content already exists.

Keep an action-changing condition visible at the point where a user needs it. The route to a fuller explanation must be usable within the declared support arrangement. A companion that has not been written or cannot be obtained leaves that audience’s promised learning unsupported.

When the division is uncertain, ask a suitably prepared reader who lacks the author’s private context to construct a small piece of instruction for a named audience from only the published method account and its declared suppliers.

The result should identify what the learner must be able to do, connect a worked case and practice task to those operations, and state how a consequential mistake or changed condition would be handled. Trace a consequential instruction back to its method grounds, an explicit pedagogical choice, or an acknowledged gap.

Inspect any necessary invention. Choosing a motivating example or a teaching sequence is normal pedagogical design. Inventing the method’s missing selection criterion, inference, transformation or coordination shows that the method account or its supplying explanation is insufficient for that use. Repair that omission at its owner; do not conceal it in a privately generated course.

Conversely, failure to teach an unprepared learner from a compact competent-reader pattern alone does not establish such an omission when an adequate companion is explicitly part of the selected arrangement.

This construction probe establishes only what that reader could recover and design. It does not establish that the proposed teaching works, that a generated guide is correct, or that learners can perform independently. Test those claims with their actual audience, task and assistance conditions. E.4.PFAD:4.1.1 compares the cost and value of the resulting pattern, companion and short-use routes, including their change dependencies.

For human and AI readers. Different readers may need different amounts of explanation for the same operation; the same reader may need more when adapting it.

For an AI use, distinguish all available publication content from the material actually supplied or reachable during the invocation, including the tools needed to obtain it. A successful reconstruction qualifies that use under those conditions. It does not show that another model, another context budget or an unassisted human can do the same. A human-learning result does not by itself establish an AI context-management effect.

Authoring examples. A portfolio-comparison pattern can keep its general Method concise by naming the common application that supplies the alternatives, complete small calculation and changed-condition cases. The shared application must contain that work.

A reminder to reuse a previous evaluation instead needs the same-question and still-applicable-evidence conditions beside the instruction; leaving them only in a distant rationale permits an unsupported reuse. A reader altering a construction may need its invariant and why the composition preserves it, even when an experienced operator can execute the unchanged construction from a brief reminder. These are different reading needs, not reasons to publish a separate authoritative Method for each audience.

Use existing sections, examples and direct references to organize these paths. E.11 governs discovery; it does not replace the required explanation with an entry card. E.14 keeps practical use and assurance connected; it does not defer a condition needed before action. E.17.EFP governs faithfulness when selecting or expressing an account: a faithful partial expression can serve a bounded use, while changed claims or a narrower use need their own explicit treatment. No fixed number of reading levels, parallel versions, characters or model-specific editions is required.

E.8:4.2.1.2 - Construct the expression that supports the reader’s operation

Use this move when the needed explanation is available but the author still has to decide what the reader should read, compare, remember, manipulate or carry forward. It also applies when arranging incomplete material is how the reader will discover the question.

A representation can help produce a distinction that was not available before it was used. Its usefulness is not limited to storing a finished answer.

Begin with the reader’s operation and actual material. Try it with a sufficient existing expression before designing another one. Retain the reader’s preparation and available help from §4.2.1.1. If the operation itself is missing, develop or obtain it; rearranging its name cannot supply it.

A.6.3.RT.OE explains how to make an expression operative. Developing formation, interpretation or transformation rules is a separate notation-engineering task. The external Notational Engineering DPF (NOT) offers optional methods for that work.

Construct the contrast before choosing the format. Place together the pieces that the operation needs to distinguish or combine. They can still contain uncertain interpretations or an unanswered question. Attempt the comparison, grouping, substitution or inference.

Where it fails, determine whether a missing fact, a missing operation or the arrangement of the expression prevents the result. Change the arrangement when it hides or confounds an available distinction. Obtain a missing fact when the receiving operation requires it. Preserve an unresolved question when it is the useful result of this attempt.

The unit follows the operation. Two cases may need to remain adjacent to expose a difference; one thought may need to be independently movable without losing the reason it states; an instruction may need its prerequisite at the point of action. Start with these relations rather than a blank form inherited from another task. Stable labels and a small common structure can make repeated comparison possible. Retain those constraints while they help, and revise the one that suppresses a needed distinction.

Choose among expressions by what the reader does with them. Continuous explanation can keep a causal argument or an unfamiliar inference together. A mantra can help retain an already developed connection during work; it cannot teach a missing operation merely by naming it.

A table makes the same questions about several cases jointly inspectable. Its rows and columns need meaningful common interpretations, including the conditions under which values may be compared. A card makes a coherent contribution separately addressable and rearrangeable; explain what a connection between cards means.

A diagram can expose a relation whose incidence, order or spatial organization matters; the appearance of an arrow does not establish a dependency or cause. An executable expression can perform a specified operation, provided its inputs, interpretation, execution context and failure behavior are supplied.

These expressions may be combined. For example, a short explanation can establish a table’s interpretation, the table can support comparison, and a reminder can later cue that same operation. Select only the contributions needed by the intended use.

Expose the interpretation where it is used. A column headed Date can leave its event, role and unit unresolved. A row can represent an observation, an attempted operation, a relation or a claim rather than one physical object.

State the distinctions that affect the operation, including what an empty position means. A missing observation is not zero; a not-applicable question differs from an unanswered one. Use the domain’s kinds, quantities and roles and the relevant FPF distinctions where they settle such a difference.

Distinguish content that must be available from content the practitioner must enter again. A visible value may be derived from a qualified source or retrieved from another record. Show that return when it matters, and require manual entry only for the contribution the person supplies. An illustrative table in a pattern is not automatically a record schema for every performance.

Place, retain and change the support. Place an interpretation or prerequisite beside the first operation that depends on it. Place a reusable example where its intermediate result can be inspected. Keep assurance conditions available before consequential reliance even if their derivation is elsewhere.

If a form will travel without the surrounding prose, carry the interpretation and source return needed in that separated use. A direct link can be sufficient when the recipient has the access and can recognize when to follow it.

Compare the candidate with the best simpler expression by performing the same use at the same preparation. Retain a sufficient existing form when no worthwhile gain is shown. Remove a field or whole support when its contribution is unnecessary or supplied more effectively elsewhere, checking the use that previously depended on it.

Rework instead of adding a second copy when the existing expression contains the right material in an unhelpful arrangement. Add a new support when an operation remains unavailable or requires avoidable reconstruction. Revisit this choice when the question, source, recipient or separation from context changes.

An expert construction establishes what that construction makes available; evidence of reader success or lower effort requires an actual reading under stated conditions.

Worked choice: a date conversion and the form that teaches it. The explanation in §4.2.1.1 requires a source-to-order selection before conversion. Supplier North guarantees month/day/year; South guarantees day/month/year for the files at issue. The intended reader can run a converter given a date order. The author’s task here is to choose an expression that makes the selection, its reason and its limit usable.

Begin with the tempting two-column arrangement:

Raw textISO date
03/04/20262026-03-04 or 2026-04-03?

The cell exposes an unresolved interpretation; selecting one output by appearance would invent information. The author asks what differs between the two legitimate conversions. The supplier guarantees distinguish the two interpretations. Rework the comparison:

Source of this rowRaw textInterpretation supplied by the applicable guaranteeConverter result
North03/04/2026month/day/year2026-03-04
South03/04/2026day/month/year2026-04-03

The unchanged raw characters and different results remain adjacent. The table expresses the source-to-interpretation relation which the two-column prototype lost. The surrounding explanation shows how the applicable guarantee determines the date order and why guessing from the characters is invalid.

Source designates the supplier for this row; the interpretation is an input to conversion derived from that supplier’s guarantee, not a newly observed property of the date. Neither the interpretation nor the output must be manually recopied by every user.

A separate card for each row would make this small comparison harder to inspect together without supplying a needed rearrangement. A dependency diagram can explain the same selection when its connections become the difficult part, but adds no needed distinction to these two rows. The table and its short explanation therefore serve this example.

For experienced users, “use the applicable source order; do not infer it from an ambiguous date” is a recall cue with a return to the explanation. It does not replace that explanation for someone learning the selection.

Now change the receiving use. A work session contains only North files under one applicable guarantee, and the converter receives that fixed order from the session’s qualified configuration. A repeated source and order entry in every manually completed row supplies nothing further to this session’s conversion. Remove those repeated inputs from the local working view; retain the scope statement and its return to the guarantee. The two-column raw/result view is sufficient there.

If a row is later exported alone or South material enters the session, that contextual supply no longer suffices: recover the row’s source and applicable order before conversion. This is a conditional removal, not a claim that source identity never matters.

In a different change, South starts using mixed orders and supplies no row-level interpretation. Preserve North’s results and the earlier qualified South results. Mark the ambiguous new South row as unresolved; neither a fuller form nor running the converter twice chooses its meaning.

Obtain trustworthy row-order information or correctly matched converted dates before relying on that result. The unknown blocks that conversion, not every other row.

Apply the construction to the pattern’s own arrangement. Keep the selection operation and its use-changing conditions in Solution. Keep the small comparison with the instruction that interprets it; a distant collection of unexplained forms would make the reader reconstruct the missing connection.

The canonical sections and stable addresses organize publication and return. They need not become the author’s order of discovery: rough notes can reveal the source-to-order problem before the first pattern body is composed. Once a pattern body is authored, §4.1 governs its canonical frame; the external notes are not a substitute for its unfinished content.

The raw/result prototype, the source-qualified comparison and the reduced single-source view expose why different forms support the same conversion in different conditions. They are worked constructions, not observations of improved learning or production performance.

E.8:4.2.1.3 - Choose examples by the explanation they make usable

Determine the content owed to the reader from the subject, declared scope and receiving work. Include the relations, grounds, alternatives and conditions needed for that work; do not let the circumstances of a convenient example decide which of them to explain. This is a priority in deciding adequacy, not a compulsory order of discovery or presentation.

A case, sketch or attempted calculation can reveal a missing relation before the general account is finished. Carry that discovery back into the account and distinguish a reusable condition from an incidental feature of the case.

When the reader is learning to model a domain, say what the reader must do with the domain’s own types. For a transdisciplinary principle, explain which distinction applies to those types, how to recognize the relation and what inference it warrants. For a domain principle, supply the field’s own rule and its conditions. If the intended result is a way of working, explain how to select or construct the next operation, what it produces, and which dependent choices to revisit when its grounds change. A single publication may teach all of these. On unfamiliar material, ask the reader to select, relate or revise the local types and use them to reach a result in the recipient’s terms. A worked case makes that reasoning inspectable. C.39.WA:4.3 distinguishes the relations used in such inferences.

When an author uses a case to test an independent choice, identify the choice the prompt leaves open, the sources and help available at that point, and what the learner actually supplied. A problem statement in a brief can support a test of evaluating that formulation. To test formulating the problem, use work in which the learner still had to frame it. An earlier working record can supply that evidence. Apply the same test when the task is to construct a disciplinary model. Inspect which unit, identity criterion, correspondence or decision rule was already given. A worked answer can show how the learner applied it. Credit independent construction for the model choices the learner actually made and justified. If a completed form could be copied, check the result itself and keep attribution open until there is evidence of the learner’s work. E.23.CDI:4.2.1 guides the separate decision about how a holder can acquire and demonstrate a capability under its working conditions.

Keep the explained subject and its example distinguishable. When teaching a Method, identify the reusable way, the actual or stipulated performance that illustrates it, and the material on which that performance works. Show which choice or action in the example enacts which operation and why its result is usable next.

In an explanation-design pattern, a calculation of a mean can be material supplied to the explainer; selecting unequal groups to expose a misleading shortcut illustrates the explainer’s Method. Correct arithmetic supplies the mathematical result. The account of selecting and using the contrast explains the teaching move. These contributions can appear together without changing the pattern’s subject to arithmetic.

Make the common claim, its scope and its grounds available in the explanation. It may be expressed alongside cases, through a derivation or through a named accessible supplier. State what may vary and which conditions make the relation or operation applicable.

If the text calls the example a stricter model, compare the two models for the same inquiry under B.5.MR.

When cases suggest a new general claim, develop and qualify that claim through the relevant subject Method. A constructed instance can demonstrate an operation, a counterexample can defeat a universal claim, and observed cases can contribute empirical evidence; the wider inference retains the grounds appropriate to that use.

Select an example for the contribution it makes: making an unfamiliar relation inspectable, exposing an intermediate operation, distinguishing plausible rules, showing a boundary, or connecting several Methods in use. Work the correspondence between the account and the instance.

A correct answer can fit more than one rule; choose values or a comparison that lets the reader distinguish the intended relation. Preserve adequate direct explanation when an additional example would contribute nothing to the declared use.

Archetypal Grounding remains a content function of a canonical pattern; it is not a requirement to insert an example into every paragraph, slide or section derived from that pattern.

Choose meaningful variety from the promised subject. Recover the differences in objects, relations, conditions, available grounds and receiving work that the account must handle. Select cases that make those differences intelligible, including ordinary applications as well as contrasts and limits.

A numerical derivation, a causal explanation with uncertain evidence and a recommendation under competing purposes can require different explanatory moves. Changing numbers within a derivation does not supply the other two.

Several materially different examples may be necessary to ground a general account even when each example is locally simple. Explain what remains common across them and what changes for a subject-specific reason.

For human learning, HCD.5:4.2.1 and HCD.6.1:4.2.2 connect explanations with a distribution of qualified encounters and focused contrasts. Use that contribution when a learner must recognize or use a family that one pair cannot expose. A demonstrated distinction can be available before a complete verbal rule; preserve its qualified examples and conditions instead of inventing a formula. The framework author’s obligation is to make the claimed commonality and its basis usable, including the limits of what has been explained.

Decide whether to continue the same case. Continuity can make an earlier result, a changing state or the consequences of a choice available to the next operation. It can also avoid reintroducing circumstances the reader already understands. Retain that benefit when the case still shows the relations now needed.

At each consequential transition, return to the subject being explained: which operation or principle is this instance making usable? If a new question needs different objects, a competing method or a condition the case cannot represent faithfully, change the case, juxtapose a contrasting one or use a direct explanation.

Keep the general reasoning connected while examples change. Retain the varied cases needed for that account; shorten incidental story development when it displaces the next required connection.

Check the account at its promised scope. Compare what the explanation lets the intended reader recover with what the subject and receiving work require. The reader should be able to explain the governing relation, its grounds and conditions, and use it across the material variations included in the promise. Choose those variations from the subject, not only from what is easy to change inside the chosen setting.

Inspect the correspondence back to the Method or principle being taught as well as the correctness of the example’s domain result. Supply a missing general operation, explanation or accessible supplier; add or revise cases when the required correspondence or variation remains hard to recover. Use F.19’s evidence and coverage conditions for a reader-recovery conclusion.

For example, a continuing transaction can show why a later update must use the state produced by an earlier one: retaining the same transaction makes that dependency visible. In an account of resource use across Methods, show the different relations of a consumable specimen and reusable information. Explain consumption and reuse, then show how each changes the receiving operation.

The author’s reusable move is to select and connect cases by the relations owed to the reader; the transaction, specimen and information are the material used to perform that move. A reader who already understands a short algebraic derivation may need no narrative case for that inference. These are choices about the contribution required, not a fixed allocation of examples.

E.8:4.2.2 - Package-form and neighboring-pattern reference discipline

FPF package-form words and neighbouring-pattern references carry stable meanings. State the relation the sentence asserts, and use the governing subject pattern when that relation is not recoverable from ordinary wording.

For an ordinary neighbouring-pattern reference, state the concrete contribution and cite the PatternID. Distinguish a source for what this passage says from material the reader is directed to apply, using E.8:4.2.2.2. An identifier or locator only helps the reader find that content; it does not declare this purpose. Identify an exact claim-bearing episteme, ClaimGraph, edition, or relation assertion only when a named later use depends on that identity.

A local ...PatternLocator field may remain where a schema already uses it as a non-semantic convenience, but ordinary prose and entry cues do not require one. It never substitutes for the cited content’s concrete contribution or, when the stronger identity branch is active, for the exact claim-bearing content.

Changing only a locator without changing what it resolves is a representation change; changing the defining content or exact assertion may reopen the semantic object whose receiving use depends on it.

Keep the following package and relation words distinct:

  • pattern reference = a reference to pattern content whose contribution and purpose in the referring passage are stated; citing that content as a source and directing its application are different uses;
  • specialization = an exact relation in which the child carries the required parent content plus an explicit child delta and use boundary;
  • overlay = a cross-cutting reading or review projection over stated source content; it adds no authority or obtaining relation by name;
  • profile = a declarative bounded-use or review projection from stated source content, not a replacement pattern or actor;
  • family = a recurring class of cases under an explicit membership rule, not a hidden common owner;
  • bundle = a packaged set of defaults, allowances, or coordinated members whose actual relations remain explicit;
  • cluster = a navigation or reading-order grouping, with no semantic relation by grouping alone;
  • suite = a coordinated set whose suite-level membership and coordination semantics are stated;
  • pack = an editorial, source, review, or delivery grouping, not semantic authority;
  • kit = a reusable coordinated publication or boundary-description package with exact kit-level membership and use;
  • record = a case, report, assertion, representation, or review record under its own identity;
  • umbrella = a provisional review head spanning possible subfamilies before an exact membership rule and the relevant claims and relations are settled.

These words are not interchangeable and do not stand in for a missing relation. Say specialization of … with delta …, profile projecting … for use …, overlay reading …, bundle containing … under membership rule …, or another exact formulation.

A source-defined position name may be reused when the cited content defines that position and the current assertion uses it in that sense; otherwise recover the meaning through E.10.ROLE and do not improvise near-synonyms for stylistic variety. The preceding receiving-use discriminator decides whether exact claim-bearing content must also be identified.

E.8:4.2.2.1 - Precision-restoration placement discipline

When a pattern or companion text is drafted from E.10 or E.10.ARCH, distinguish three authoring objects:

  • semanticArea is the Part-F semantic unit for a wording-use restoration row: one Concept-Set row, one UTS row, or an explicitly bounded row-set. It is declared with semanticAreaBaseConcept and semanticAreaSenseFamily.
  • ontologicalNeighborhood is the applicability neighborhood around that named semanticArea: nearby primary EntityOfConcern kinds, relation kinds, claim records, content that defines or constrains the current use, non-use boundaries, and remaining reader use that can carry the recovered meaning after the wording is repaired.
  • pattern nest is the publication and specialization placement of a pattern under a declared family or membership relation.

These are not synonyms. A precision-restoration pattern is placed in the pattern nest whose primary EntityOfConcern, relation record, or claim record it repairs. Its semanticArea states the Part-F semantic unit it repairs, while its ontologicalNeighborhood may name several direct relations and pattern content that defines or constrains the asserted uses.

For example, quality-term repair lives in the C.16 characterization nest, even though its neighbouring relations can include relation construction, action invitation, evidence, assurance, source-use assignment, engineering quality bundles, pattern-quality evaluation, or mathematical-lens use.

Affected patterns should use a thin pointer when the first-stage wording repair belongs elsewhere. The pointer names the selected restoration pattern and the condition that triggers it; it does not copy the trigger registry, the full E.10.ARCH recovery algorithm, or a second local architecture for the same repair. The affected pattern then keeps its own subject matter: the characteristic, structure, view, episteme, relation, evidence, assurance, gate, work, decision, or adequacy question it already governs.

If a draft proposes a new precision-restoration pattern, the authoring claim must show the repeated wording failure, semanticAreaBaseConcept, semanticArea, semanticAreaSenseFamily, the recovered primary EntityOfConcern kind or relation/claim record, the intended pattern nest, the neighboring governing relations, and the admissible action left after repair.

A new pattern is not justified merely because a word appears often, because a local checklist wants a bucket, or because a campaign needs a tidy grouping.

E.8:4.2.2.2 - Make the purpose of a reference clear

A reader should be able to tell whether a reference gives the source of an explanation already supplied or points to material they are being asked to use. Express that difference in ordinary prose:

  • A citation identifies the basis of a claim, definition, quotation, comparison or explanation. Make clear what is taken from or justified by the source. When the quoted or explained material is sufficient for the present work, its citation adds no obligation to open the source before using it.
  • An application reference asks or invites the reader to use the named material for a contribution to the current work. Say what to obtain or do there and how it bears on the present question. Keep any condition and the force of the advice clear: a required dependency, a conditional next move and one possible way are different. This is an explanation, not a set of fields to add to every sentence.

Prefer wording that already makes the purpose clear. “This distinction follows X” cites a basis; “use X to compare these arrangements” directs an application. A conventional citation attached to the claim, or an explicitly identified source column, can establish the first purpose without another label. Do not prefix an already clear instruction with another label.

Short Source: and Apply: cues are available when they help distinguish otherwise ambiguous entries in a compact list or table; they are not mandatory markup. Keep the address or ordinary Markdown hyperlink unchanged. No new link protocol, suffix, HTML attribute or address separator is needed.

The purpose belongs to this use of a reference, not to its destination. A pattern can be a source in one passage and material to apply in another; an external paper can also describe a Method to use.

When both purposes matter, explain both contributions rather than leaving the reader to infer an instruction from a citation. Do not hide an operation or use-changing condition that the reader still needs behind a source citation. If it must be obtained elsewhere, say so and explain the return to the present work.

A sentence, list introduction or table heading can establish the purpose for a clear group. A generic Relations, Solution, Rationale or See also heading does not decide it. Separate mixed uses where their difference changes what the reader should do.

Pure navigation, declared identifiers, address examples and addresses that merely name participants in an explicit relation need no source or application cue. In “X specializes Y”, Y names a participant; it is not automatically a citation or an instruction. But “X supplies comparison” at a step needing a comparison can leave the needed action unstated. Decide whether the comparison is already supplied or the reader must obtain it.

For example, these references to the same material do different work:

  • This account distinguishes Work, capability, means and authority following C.32.MWA.PP:4.3. Authority to allocate a task does not by itself supply the capability to perform it.
  • When those contributions must be allocated differently, use C.32.MWA.PP:4.3–4.8 to construct and compare complete arrangements. Bring the feasible alternatives and their combined demands back to the present choice.

Neither form settles truth, authority or sufficiency. Inspect a cited source when its meaning, assumptions or evidence need examination for the present reliance; do not make that an automatic extra reading. For an application, an adequate existing result or already understood Method can suffice without rereading or repeating the work. An application reference cannot make unavailable material available, excuse an unexplained connection or establish that the promised result has been obtained.

Read a proposed destination far enough to establish that it supplies the contribution the referring text promises. If it does not, change the direction or develop what is missing rather than merely changing its wording.

Judge the connected passage as prose for its intended reader: can they tell what is available here, what they are being invited to obtain elsewhere, and what happens next, without decoding labels? When an extract loses a heading or introduction that supplied this meaning, retain the necessary purpose and condition in the extract. Use E.11.PUA:4.1.1 when deciding how to follow such a reference.

E.8:4.2.3 - Intended-reader discipline for pattern prose

The intended user is the agent that uses the pattern. Write for the work it supports, such as organising thought, investigating a question, changing a system, publishing a description or reviewing a result. One agent may apply the pattern while another performs the work it describes.

Check which system the claim concerns. Try the operation with a different performer. What capabilities, access or authority does it require? Use the action or role in the general instruction. A person, a technical system or a division can work as an engineer. Then hold the work result fixed and vary the system to which a decision or a capability is attributed. If the attribution changes what the evidence establishes, name that system and the conditions that matter.

A robot can measure a part against a tolerance. If the contract assigns acceptance to the customer’s inspection unit, that unit decides whether to accept it. The same accepted part could follow from a judgement supplied by a vendor or from the unit’s own interpretation. To find out whether a human trainee can interpret the readings, observe the trainee on a new part with the aids permitted in later work.

The pattern’s sections explain the described subject, the user’s action and result, costs, and grounded boundaries that change use. Public architectural explanation belongs here when it helps the reader understand, select, combine, or adapt the Methods.

For example, explain why a profile specializes one step but reuses another, how a combination makes its next result possible, or when an alternative would be better. State the relations that apply in Solution and explain their reasons in Architectural Rationale. A whole language and its profiles use the same content functions through E.11.PFP:4.7.

E.8 reader and reviewer wording is framework-authoring wording. Project-side publication readers, explanation readers, comparative review units, and participants in named project-side review relations are governed by the patterns that name those units and relations, such as E.17, E.17.ID.CR, E.17.EFP, A.10, A.15.4, A.20, or A.21.

Keep the development history of the current pattern version in its DRR, companion, review, or release material. This includes current arguments for promoting a draft, authority-reference or naming freezes, merge and landing state, and review correspondence.

When a development decision contains a durable reason that changes practitioner use, publish that reason with the necessary explanation and source return; retain the dated decision and its evidence in the development record. Users need enough reasoning to understand the choice without reconstructing that record.

E.8:4.2.4 - Human-facing fit beyond intended-reader correctness

Human-facing fit is also subject-domain fit. A recognition text that starts from internal taxonomy, pattern-placement convenience, or package-architecture wording before the problem-domain moment is still under-authored even if its later guidance or check text is correct.

When a broader umbrella name and a narrower operative branch are both used, the recognition text should also tell the reader how the branch fits under the umbrella, what it governs and which action and predicate apply, as described in §4.2.1 rather than leaving that reconstruction to a later declaration block or companion note.

P-2 epistemic precision check. When the E.10 criteria call for epistemic precision restoration in pattern prose, the first admissible action-guiding move must survive as remaining admissible reader use or be replaced by a neighboring FPF rule whose content now defines or constrains that claim application. E.2 P-2 and E.12 require this.

Intentional didactic metaphors and vivid Plain recognition lines are admissible when they are ordinary recognition aids or when their claim kind or admissible-use boundary maps back to Tech under E.10:6.2. A precision-corrected rewrite that leaves the recognition text inert is still under-authored.

For method guidance, explain in Solution what the performer should attend to or compare when it can change the next move: conditions needed for the operation, consequences expected from it, and whether the obtained result serves the receiving work. Give a reachable continuation when a condition is unmet, unknown or the result leaves the original concern unanswered.

B.5.PI develops an opening into inquiry; B.5.EA helps when the concern cannot yet be expressed, and an early cue can remain unresolved. Put these connections where they change use, including in first authoring.

Do not add a compulsory monitor, extra form or copied “watch for anomalies” paragraph to every pattern. A known adequate result can still end the work directly.

Use the recognition and assurance functions in §4.2.1. Put the working situation and first useful result in Problem frame and Solution; add candidate-pattern comparison cues when a question about finding the right pattern remains under E.11.

Entry-cue authoring rule. Begin with one ordinary question about the user’s object and claim, before any PatternID, card, template label, or internal taxonomy. In the same compact cue, state what cited content contributes, cite the pattern id, and name the smallest result usable now plus its stop or return condition.

Add a tempting overread only when the F.19 plausible-reader test finds independent local ground and an action-changing effect. Name an exact episteme, ClaimGraph, or edition only when a later use depends on that identity. The cue guides reading; it does not by itself constitute a result or relation.

Compact candidate-pattern comparison belongs in E.11-distributed entry material. Longer first-entry comparisons belong with E.11’s bounded-comparison explanation; E.11:5.7–5.14 supplies worked examples.

Keep a claimed breadth visible at first reading and preserve the same claim as the assurance text develops it, under §4.2.1.

Illustrative migration example (informative).

Old pre-template top:

Start here when the dominant question is API, protocol, SLA, published boundary, or compliance wording.
First output: Claim Register.
Neighboring pattern relations and entry-recognition reclassifications: A.6.B, A.6.C.

Repaired Problem-frame recognition signature:

Use this pattern when boundary-facing language - API, protocol, SLO/SLA, compliance clause, or other published boundary description - mixes guidance or check clauses, admissibility gates, duties, and evidence into one sentence or published boundary description.

If missed, runtime behavior, governance, and evidence are treated as one undifferentiated promise.

Do not use this pattern merely because the text mentions an API or boundary description. For an unstable cue, keep the passage or observation that prompted the concern. Use B.5.EA when the participant cannot yet express the distinction needed to continue; use A.16.1 when preserving the cue itself is the first useful publication.

First admissible action-guiding result: one `A.6.B`-governed atomic claim set or one Claim Register whose claim/use questions are explicit enough for a reader to inspect using the pattern content that defines or constrains the claim, or a named project-side FPF kind and reference.
E.8:4.2.5 - Design-time and run-time referents stay separated in pattern prose

Pattern prose keeps the referents needed by its declared subject and use recoverable. Authoring, review and publication are valid governed subjects; state their actions and rules directly. Distinguish design-time, run-time and normative-publication referents when that distinction changes the claim.

Apply §4.2.3 to place this edition’s drafting, review and landing history in its development carrier. Retain any durable reason that changes the user’s action, choice or boundary in the public explanation.

If a pattern or example claims autonomy, name the admitted U.System whose freedom of action is being evaluated and use the current E.16 pattern that defines or tests the claim. Add another relation only when it is current under its own governing pattern.

Admit dated Work under the A.13-first and independent A.15.1 rule in E.8:0.3, adding F.6 only for current assignment-bound attribution. Add autonomy apparatus or a vignette only when it helps the reader use that claim. Apply F.19 after recovery; if the corpus supplies no direct governor, return A.6.RCD missing-governor.

E.8:5 - Archetypal Grounding

E.8:5.1 - Turn a framework outline into a usable common account

An author has three short chapters about selecting a source, reusing a rule and refreshing a decision. The commissioned introduction must explain how readers can keep source-based decisions justified as their sources change.

The draft says: “Find a source. Record its title and date. Apply the rule. Review the decision whenever a new edition appears.” Its sequence names the activities but leaves their connection unexplained.

The author follows the required decision back through the material. A source is useful here because a particular claim, under stated conditions, contributes to the decision. Its title and date enable recovery of that claim. A later edition matters through a change to that contribution. This dependence gives the common account its organizing ground. The author writes:

Begin with the question the decision must answer and recover the source claim that can contribute to it. Establish whether the claim’s conditions hold for this use, then make its effect on the decision explicit. Keep enough source identity to recover that basis. When the source changes, compare the used claim, its conditions and limitations; reconsider the decisions whose grounds are affected. An already adequate source or unchanged contribution can continue to serve its existing use.

That paragraph changes the organization of the three chapters. Selection now returns a qualified contribution to a question. Reuse explains how that contribution enters the decision. Refresh follows the resulting dependence, returning to selection when a usable source is lost or to application when its conditions change.

Each chapter can still serve an independently arising question. Their common account explains how their results connect.

The author distributes the remaining content by function. The Problem explains why a title and date can coexist with an unsupported decision. The Solution supplies the operations and their returns.

The Rationale compares dependence-based refresh with redoing every source-based decision after any edition change, including the cost and the risk of overlooking an affected use. Grounding shows how the decision depends on a source claim; the Conformance Checklist asks whether the used claim, applicability and affected decision can be recovered. These functions guide what is written, rather than providing places for repeated assurances that the account is complete.

In the constructed case, a handbook’s rule sets a maximum reporting interval of seven days, and a team has chosen weekly reporting on that basis.

One new edition changes the chapter title while preserving the rule and its conditions; the common account leads the author to retain the decision and update its recovery route. Another edition shortens the applicable maximum to five days; the author shows the reviewer returning the weekly decision for revision. The difference supplies the reason for selective refresh and explains which earlier contributions remain useful.

Suppose the commission expands to recommendations whose suitability also depends on the recipient’s preferences. The current source account leaves that additional ground implicit.

The author adds the recipient’s objective and preference to the common decision basis and connects their change to the relevant reconsideration. Merely adding a fourth chapter called “preferences” would leave the return unexplained. The existing source-recovery operations remain usable, while the expanded account makes another condition of reliance explicit.

E.8:5.2 - Keep expression, organization and evidence in their roles

The date-conversion repair in section 4.2.1.2 shows a different authoring choice: how to preserve an operation, its conditions and a return to fuller explanation when changing the reading arrangement. Use that case for the form-and-access question and section 5.1 for construction of a common account and its constituent explanations. Their different contributions follow the authoring work the reader needs.

Small subject sentences can illustrate density without jargon: “The pump casing seals at this face” names the relevant action and location; “The claim states its predicates explicitly” names an epistemic subject and its property. Their role is to illustrate expression. The organizing explanation and performed authoring choices in section 5.1 carry the larger construction.

An individual pattern uses the canonical sections and required :End sentinel. A whole-framework account uses the publication arrangement in E.11.PFP:4.7 while answering the relevant content questions. For a claim about F (Formality), use C.2.3 and state the expression-rigor criterion it satisfies.

E.8:6 - Bias-Annotation

Lenses: Gov, Arch, Onto/Epist, Prag, Did. Scope: Universal for the authoring conventions in this pattern. This guidance biases toward Did (readability, narrative flow) and Arch (template regularity) by design. Mitigate this bias by giving each reduced section the smallest content-bearing statement that justifies the reduction: a grounding, misuse, boundary, or reduced case. An omission placeholder cannot do that.

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 and 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 use the canonical section frame (Title block -> Footer marker). Authors MUST NOT start from a 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 content-bearing Archetypal Grounding. Apply §4.2.1.3 to connect its cases or demonstrations to the explained relations and to supply the material variation required by the declared use. A reduced case or ordinary/non-use boundary can serve a bounded grounding question; the complete explanation still supplies its common grounds and the correspondences needed for its promised scope. An omission placeholder is nonconforming.Makes the subject and its applications inspectable without treating a section or fixed example count as sufficient grounding.
CC-SG.3The Bias-Annotation section SHALL state the material result of the five-lens examination under E.5.4, including any justified weighting or scope limitation.States the cross-disciplinary conclusion.
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 the 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 wins on the comparison.
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 §4.2.1.3 to keep illustrative choices subordinate to that content; preserve both the instruction and its scope 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 cues that identify the related pattern or give the project-side FPF kind and reference by value.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 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—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 a problem finding the right pattern under E.11; keep expanded cases with E.11’s bounded-comparison explanation. 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 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 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 applicable 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 the subject pattern that governs it, 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 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.

E.8:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomWhy it failsHow to avoid / repair
Template cargo-cultingHeadings exist, but the section is fragments, decorative bullets, or a table with no governing claim.Satisfies Uniformity but loses Readability and Didactic Primacy.State the governing claim and its practical consequence in ordinary prose; introduce a list or table only when that structure improves the reader’s work, and apply F.19 to its contribution and load.
Un-grounded abstractionsProblem/Solution stay abstract; no concrete System/Episteme Tell-Show-Show.Breaks teachability and makes misuse likely.When an attempted instance helps expose the missing connection, work it first; recover the reusable relation and restore the declared scope in Problem, Forces and Solution under §4.2.1.3. Do not promote incidental case features into general conditions.
SoTA name-droppingSoTA-Echoing lists sources or adopt/adapt/reject labels but never names the practice question, serious alternative, defect overcome, or changed pattern locus.The reader cannot recover why the selected line is best for this question or what changed in practice.Supply the complete compact comparison from CC-SG.7, or state the source gap.
Currentness launderingAn official registry entry, publication date, maintained status, latest release, citation count, or widespread default is verified and then reported as evidence that the source is SoTA.The check establishes source identity, availability, or currentness, not the best-known answer or its advantage over a serious alternative.Classify the source as official/popular comparator or identity/currentness only. It contributes to SoTA only through an explicit comparison whose defect and pattern mutation are independently shown.
Incidental tool-bound normativityA rule about an abstract subject requires an unrelated vendor tool, file format or execution command.Introduces an implementation dependency into the concept.Move that machinery to Tooling/project profiles. Retain exact syntax only when the rule governs that publication form, protocol or grammar and names its edition/use boundary under E.5.1.
Hidden trade-offsA material cost or limitation is omitted from Consequences.Hides information needed to judge adoption or applicability.State the decision-relevant cost or limitation and a mitigation when available. Consequences may state only gains when no such cost or limitation is known.
Skeleton-only patternThe template is present, but the pattern gives only one compressed definition block and scenario labels.Passes form while failing didactic sufficiency.Add didactic content: local decomposition, concrete slices, reviewer cues, and guidance that identifies the neighboring pattern or gives the project-side FPF kind and reference by value.
PatternID read as definition or orderA numeric or mnemonic segment is treated as the pattern’s meaning, title, current position, dependency, Method relation, or semantic parent.The address becomes a hidden claim and ordinary reordering threatens reference continuity.Use the PatternID only as an address together with surrounding text that identifies the framework. Show title and current position separately, state relations directly, and use the applicable product-authoring rule to decide continuity across editions.
Project-context leakageA reader needs architecture memos or planning notes to understand the pattern.The monolith stops being self-sufficient.Move the essential problem framing, worked slices, and rationale into the pattern itself; keep project reviews informative only.
Repeated content, reference, and architecture boilerplate leakageThe body repeats a guard, definition, reference, or placement rationale without adding a local action, case, evidence value, or recognition need.Repetition hides the positive Solution and turns the pattern into an architecture note.Cite the existing source or use the proper discovery or architecture carrier; keep one local boundary only when it changes use.
Quality-carrier leakageThe pattern body reports development, review, projection, assembly, or landing evidence as if it were practitioner guidance.The reader sees why the text was processed rather than what to do.Keep the evidence in its own carrier and retain only the user action or boundary that it supports.
Apparatus overwrapProcess, status, role, carrier, or quality language displaces the pattern’s object and move, or a polished caveat introduces an unsupported relation.The prose can be true and still force the reader to solve the wrong problem.Apply the connected F.19 reading, return the positive practitioner path, and route only an unresolved FPF value to the pattern that governs it.
Unresolved wording kept as local style doctrineE.8 locally restates generic-head, qualifier, comparison, or implicit-relation rules instead of resolving the sentence.The authoring pattern grows a rival precision-restoration algorithm and encourages checklist prose.Apply the connected F.19 reading; use E.10 only as a cue or route, and take an unresolved FPF kind, relation, comparison, or admissible-use question to its governing pattern.
Package-form and neighboring-relation driftPackage-form words are varied for style or used without their declared relation.The reader cannot recover membership, projection, navigation, or another relation.Use the matching term from E.8:4.2.2, state the relation, and name any cited content’s concrete contribution.
Intended-reader leakagePattern sections narrate the current draft’s promotion, freeze, review, or safest landing form.The reader must reconstruct development history to find the Method and its reasons.Keep that history in companion records; explain the user’s Methods, costs, alternatives, boundaries, and use-changing architectural reasons in the public account.
Editorial/development self-instruction leakThe pattern starts saying things like this draft should …, later authoring will …, or that is the opening this draft must hold.The text stops addressing the working reader and starts narrating the current editorial or drafting process.Move the sentence to the authored-slice carrier or handoff, or rewrite it as one user-facing claim about the primary EntityOfConcern, boundary, or practical consequence.
Intended-reader-clean but pragmatically foggyThe pattern addresses the right reader, but the first reading still hides the working situation, payoff, governed object, or first move.Correct audience alone does not make the guidance usable.Put the working question and first useful move earlier, gloss necessary technical terms, and supply the explanation the reader needs. Add or move a worked case when its specific contribution resolves the difficulty; connect explanatory SoTA-Echoing to the guidance it changes.
Hybrid audience blobOne main narrative tries to serve engineers, managers, auditors, architects, and researchers at once with no primary working reader or concern.The wording accommodates all the audiences without telling any reader which concern governs the first passage.Make the primary working reader, concern, and viewpoint explicit and assign other audiences to secondary companion uses, other faces, or an explicit out-of-scope note.

E.8:9 - Consequences

BenefitsTrade‑offs / Mitigations
Predictable structure – the same named sections locate the problem frame, forces, and criteria.Limits author freedom in macro layout; mitigated by flexibility inside the Solution subsection.
Cohesive voice – S‑principles give authors common guidance for explaining their contributions.Reviewers must judge readability as well as semantics; the checklist identifies recurring conformance questions.
Grounded explanation – Tell-Show-Show and governing-claim flow connect the rule to its application.Patterns may become slightly longer; retain only material that improves comprehension or use.

E.8:10 - Architectural Rationale

The common structure and style principles serve:

  • P‑1 Cognitive Elegance – uniform, minimal surprises.
  • P‑2 Didactic Primacy – narrative flow, dual archetype examples.
  • Guard-Rails 1 & 2 — abstract definitions remain portable; the heading grammar keeps the exact syntax needed for its own conformance conditions, and expressions retain E.5.2 interpretation and mapping.

A unified template also improves retrieval: a chunk containing A.2:<n> - Bias‑Annotation remains self‑identifying even when parent headings are missing, and the required footer marker makes truncation detectable.

The ASCII space-hyphen-space separator in H-2 keeps heading entry inexpensive: authors can type it directly on ordinary keyboards, and readers can reuse the same characters in search and plain-text tools. Typographic dash variants require an extra input or conversion step while adding no information to the boundary between an identifier and its title. Where a prose dash is useful, -- is a keyboard-accessible option; the identifier/title separator remains the one shown in <FullId> - <Title>.

The Conformance Checklist groups the criteria for judging a pattern that claims conformance.

E.8:11 - SoTA-Echoing (normative; typed comparison to contemporary best-known practice)

Canonical definition and contract. This is the FPF definition of SoTA: the best-known currently defensible answer to one named practice question. F.1 may prepare the question-relative source cut and E.21 may evaluate the resulting pattern, but neither redefines SoTA.

A SoTA-Echoing section earns its place by changing the pattern’s Solution, boundary, case, check, relation, evidence requirement, stop, or reopen condition. It is not a bibliography, source-currentness register, or lineage shelf.

An original answer can be the selected line. A bestKnownLine may be an original semantic or methodological synthesis developed in FPF or a DPF. It need not occur whole in an external publication. State the unresolved problem, the limitation of the serious alternatives, the new distinction or constructive move, and the useful consequence it makes possible.

Support that consequence at the scope claimed, with its cost, limits and reopening condition. Originality permits consideration; comparison supports selection.

For example, an authored connection may preserve two independent uses when a changed requirement defeats only one. Work that difference through the case and compare the available alternatives.

A conceptual construction or conditional derivation can support that bounded result; empirical effectiveness or practitioner learning requires its own evidence. Neither an external publication with the same answer nor a publication date later than all rivals is required. One such gain establishes no ranking of the entire framework.

Source roles in plain wording. Classify each retained source by what it can do for the question:

  • a best-known-line candidate supplies or critically synthesizes the strongest current answer being considered;
  • a serious current rival supplies another answer that could change the selection;
  • failure or counterexample evidence shows where an answer breaks or does not transfer;
  • an official or popular comparator exposes a default worth comparing but gains no rank from authority or adoption;
  • lineage only explains history without supporting the current selection; and
  • identity/currentness only identifies a source, edition, date, or maintenance state without supporting its truth, adequacy, or rank.

Only the best-known line, serious rivals, failure evidence, and a necessary explicit comparator belong in SoTA-Echoing. These are comparison roles, not publisher or institution classes. An official standard, widely used practice, or university-endorsed line can be the best-known-line candidate when its substantive answer wins the comparison, but authority, freshness, prevalence, or praise contributes nothing to that win.

Lineage-only and identity/currentness-only material stays in source records, notes, or evidence carriers outside the pattern body. An official or popular default stays as comparator only when its precise defect is needed to explain the selected answer and changes a governed pattern locus.

Positive comparison contract. Every positive SoTA use states, in readable prose or one compact table:

  1. practiceQuestion — the exact working question;
  2. bestKnownLine — the selected answer, not merely its newest source;
  3. seriousAlternativeOrDefault — the rival or default that could have changed the answer;
  4. defectOvercome — the action-changing defect, limit, or trade-off that selection repairs;
  5. patternMutation — the exact Solution, boundary, case, check, relation, evidence, stop, or reopen locus changed;
  6. sourceRolesAndLimits — the exact source edition or stable locator, why it has this comparison role, and what it does not establish; source identity supports replay, not rank; and
  7. reopenCondition — the smallest new evidence, rival, failure, or use change that would require comparison again.

For each material source use, name the claim, distinction or method being considered and mark its disposition adopt, adapt, or reject. Distinguish those uses from any newly constructed move. The origin of the selected answer and the disposition of its sources are different questions: an original answer can retain a source’s premise, adapt its method and reject its proposed generalization.

Explain which defect of the incumbent, popular, or official answer is repaired and why the selected line is no worse at comparable application effort on the values that matter and better on at least one, or state the trade-off deliberately accepted. More sources, a later date, a wider deployment, institutional praise, or a longer review cannot replace that comparison.

Source gaps and the lightest sufficient evidence. If an adequate best-known comparison cannot be established, say which rival, counterexample, or source role is missing and return that source gap. Do not fill the section with a current standard or recent paper. Use F.1 for the smallest question-relative cut and its SoTA-specific role branch. Use F.0.2 only when the conclusion needs cross-source synthesis. Use a broader G.2 pack only when repeated refresh or a wider claim justifies that cost.

Evidence and relation discipline. Reuse an existing G.2 pack’s exact ClaimSheet, corpus-ledger, Bridge rows, and source roles instead of forking a second narrative. Inherit non-conflicting comparison content from an accepted DRR and its source materials while keeping the DRR as the decision and placement record.

For an obtaining semantic Bridge, identify the two exact F.17 local senses, the F.9 relation, and a separate bounded-use claim; otherwise leave that relation unasserted. Keep numeric comparison under its applicable ComparatorSet or CG-Spec without hidden scalarization.

Writing guidance. Lead each row with the practice question and practical choice. Name the selected line and serious alternative, state the defect and pattern change, then give source roles, limits, and reopen condition. Complete sentences are preferred to tag lists. External terminology or tooling stays out unless the comparison itself needs it.

E.8:11.1 - SoTA alignment for this pattern (E.8 self-echo)

Practice questionBest-known lineSerious alternative or defaultDefect overcome and pattern mutationSource roles and limitsReopen condition
How should a pattern text remain teachable while retaining a stable reusable shape?Iba’s practitioner pattern-writing line is the best-known candidate here. Start from a recurring problem, forces, a usable solution, illustration, and consequences, then make the sequence readable as a whole.A form-only template that rewards headings and compressed bullets is the serious default.The default can be structurally complete yet unusable. Adapt: E.8:4.1, Archetypal Grounding, recognition text, and CC-SG.2/13/17 require a first action, worked material, and readable continuity rather than heading presence alone.Takashi Iba, How to Write Patterns: A Practical Guide for Creating a Pattern Language on Human Actions (PLoP 2021), supplies practitioner writing guidance, not FPF ontology or evidence that one skeleton fits every pattern. E.8’s extra checks and typed boundaries are FPF-local adaptations.Reopen if a stronger current pattern-writing comparison shows a lower-effort form that preserves the same recognition, action, grounding, and consequence value.
What evidence should distinguish pattern validation from a favorable review or folklore count?Riehle, Harutyunyan, and Barcomb’s 2025 handbook method is the best-known candidate for the bounded pattern-discovery and validation question because it makes claims, research methods, cases, and evidence limits explicit.Ad hoc expert approval and the rule of three are the serious defaults.The defaults hide what was tested and overstate a small positive history. Adapt: E.8 separates a canonical seed from maturity, requires worked grounding and explicit evidence use, and routes quality claims to independent E.21 results; reject a universal research programme for every small pattern.Riehle, Harutyunyan, and Barcomb, Pattern Discovery and Validation Using Scientific Research Methods (2025), supplies a rigorous validation branch but does not validate E.8. It is neither an admission decision nor a universal minimum case count.Reopen if stronger current validation practice changes the evidence needed for a maturity claim or demonstrates a cheaper method with equivalent limits and replayability.
When does a narrower or domain-specific contribution deserve a separate pattern or framework boundary?The best-known line for this decision combines action-changing pattern evidence with the 2022 systematic comparison of product-line scoping approaches: compare same-situation use, reusable contribution, family promise, organizational conditions, evidence, and maintenance rather than relying on a label.Label-only specificity and a full software-product-line process are the serious alternatives.A label can mint empty specialization, while the full process adds software-specific machinery before value is known. Adapt: E.8:4.1.3 tests the same situation at comparable effort and routes a material family change to E.4.DPF.DA; reject feature ontology and action change as sufficient proof of worth.Marchezan de Paula et al., Software product line scoping: A systematic literature review (2022), is the scoping synthesis; Riehle et al. (2025) supplies actual-use pressure; Chuprina et al., Towards an Approach to Pattern-based Domain-Specific Requirements Engineering (2024), is bounded proof-of-concept evidence, not a universal grammar.Reopen if current scoping or pattern-validation evidence changes the action test, the family-boundary variables, or the evidence needed for warranted retention.
How much explanation should a prepared or less-prepared reader receive for one use?Preparation-sensitive assistance for human learning, combined with use-bounded access to a complete account. For AI work, selective loading is a current engineering option whose adequacy must be checked for the actual task.A short problem–solution pair for every reader, or requiring every reader to consume the complete body.Adapt: §4.2.1.1 develops missing instructions by following required results back to their supplying operations, exposes the reusable connection in a worked case and consequential variation, and preserves that contribution in a sufficient connected reading. Action-changing conditions stay available before reliance, and successful reconstruction is qualified by its actual inputs. The synthesis is an authoring rule, not a demonstrated universal optimal length.Tetzlaff et al., 2025 supports preparation-dependent assistance in human instruction, with population and domain limits. Anthropic, 2025 supplies selective-context engineering guidance, not a validation of this rule or a guarantee of lossless compression. Human results are not transferred to AI by analogy alone.Reopen when a shorter path loses a required relation, a return fails before consequential use, preparation changes, or a tested alternative preserves the same use at lower total burden.
When should an example, including a continuing case, shape the explanation?Choose the required relation and reader operation first; select explicit correspondence and consequential comparison with preparation and task in view.A familiar running case used for every new question, or replacing that default with compulsory variation.Adapt: §4.2.1.3 makes continuation conditional on its contribution, restores general scope after case-led discovery and tests the promised account rather than case presence. Reject: a universal preference for one continuing example or a universal example count.The 2025 problem-selection experiments found that ambiguous single examples can reinforce misconceptions even alongside explanations in short factorial-design and h-index lessons. Cao and Carvalho, 2026 found that initial instruction changes the comparison between retrieval and worked examples; varied worked examples did not outperform repeated ones in their artificial-rule tasks. Neither tests a universal running-case policy or AI authorship. This is a bounded authoring synthesis, not a measured learning guarantee.Reopen when the reader recovers only the story, a necessary relation cannot fit the case, or comparable use shows another arrangement preserves the content with less burden.
How should a title support first selection while retaining a working vocabulary?Descriptive topic/purpose cues combined with a familiar technical name when the intended audience uses it.A solution-evoking name alone, or a universal problem-shaped rename.Adapt: §4.1.5 derives the title from the whole working question and Solution, compares neighbors, and preserves an open first choice and expert finding. A sufficient title is retained.W3C headings and labels guidance supplies the descriptive cue function. Meszaros and Doble, Evocative Pattern Name, is a historical anchor for conversational vocabulary and unfamiliar-reader interpretation. Neither measures an FPF title effect.Reopen when actual selection or re-finding loses a useful distinction, or a cheaper cue preserves it.

E.8:12 - Relations

E.8.ML constructs a problem-first language for connected Methods: independently useful bodies, their result dependencies, alternatives and returns, and the explanation of their combined use. Its direct-description exit avoids making a language where one adequate account is sufficient. E.11.PFP continues to govern public arrangement.

  • Coordinates with: E.9.DA when an authored pattern body is drafted from a concrete DRR and the blocker is whether the DRR selected, distributed, carried source use, carried accepted decisions, or supplied a first drafting action sufficiently for that authoring use. E.8 still governs the pattern body; E.9.DA is not a mandatory authoring section, review card, or substitute for writing the Solution.

  • Builds on: E.6, E.7

  • Constrained by: Guard‑Rails E.5.1–E.5.4 (lexical firewall, notation independence, etc.)

  • Coordinates with: E.21 when one authored FPF pattern version is evaluated as a scoped pattern-quality claim. E.8 governs authoring shape, recognition text, action guidance, worked cases, SoTA grounding, and conformance material; E.21 governs the pattern-quality evaluation, required coordinate values, PatternQualityStatus, and stop condition. Do not import E.21 as a mandatory authoring section or full review card.

  • Coordinates with: E.23 when an authored FPF pattern body is being improved through repeated passes. E.8 still governs the authored pattern body; E.23 governs the repeated quality-improvement method; the object-under-improvement evaluation such as E.21 or E.9.DA supplies value meanings and stop meanings.

  • Coordinates with: E.13 when an authored pattern claims practical payoff or uses a visible quality value, metric, checklist result, review result, or release posture as if it were the intended value. E.8 keeps the payoff in user-facing prose; E.13 repairs proxy-to-value substitution.

  • Coordinates with: E.4.DPF for choosing a DPF reference code, PatternID plan, continuity across editions, and reader return after split, merge, replacement, or retirement; and E.11.PFP for current Part, position, public order, and citation display. E.8 owns only the common identifier grammar and reference wording; identifier form and checker success decide none of those authoring or publication questions.

  • Coordinates with: E.11.PUR, which supplies the recommended-pattern-use decision for a current concern, and E.10.MOVE, which disambiguates whether move-like wording names pattern-use recommendation, direct work, plan, gate, transformation, publication, source, architecture, call-planning, or language-state material. These references state concrete contributions; an exact assertion, claim-bearing episteme, or ClaimGraph is added only when the named receiving use depends on that identity.

  • Constrains: All patterns. E.9 defines the DRR decision kernel and decision-inspection content blocks.

E.8:End

Referenced in the corpus

203 literal mentions in other sections. Read their context to establish the relation.