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:30:10 UTC

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.