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:15:20 UTC

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.