First Principles Framework Architectural Reference (non-normative)
Preface node
heading:first-principles-framework-architectural-reference-non-normative:1053
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
FPF.Reference:1 - What This Specification Is And How To Use It
This Core Conceptual Specification publishes the general pattern content of an edition of the First Principles Framework (FPF), together with this architectural reference and navigation. Its pattern language supports explicit, reviewable and improvable conceptual work in engineering, research, management, governance, and mixed human and AI projects.
This reference introduces FPF terms through familiar engineering distinctions, then points to the patterns that give them a more precise meaning.
FPF's Core brings together shared concepts, constitutional principles and reusable methods for reasoning. The Kernel is the defining content of universal meta-concepts within that Core; all eleven constitutional first principles in E.2 govern the Kernel and other contributions. Domain and local frameworks explain work in their own settings and state which Core content and editions they rely on. This architectural reference explains the overall arrangement. Pattern bodies give the definitions, methods and conditions needed for an exact use; files and websites make those publications available.
For an ordinary problem, use a known adequate domain method directly. Consult a supplying pattern when a missing distinction or operation prevents the needed result. Read the detailed distinctions below when their claim or action is your current question.
FPF is not a domain encyclopedia and not a project-management method. It is a framework for making hard project reasoning coherent when many project entities and relations are easy to mix: systems, bodies of knowledge and models, architecture, descriptions, publications, concern-specific views, local system-role kinds and assignments, methods, plans, performed work, evidence, decisions, options, commitments, and improvement criteria.
FPF starts from holons: project entities that can be treated as wholes and as parts. A holon can be a physical system, software system, organization-as-system, publication system, body of knowledge or model, research program, AI-agent arrangement, work occurrence, discipline, or another entity admitted by a pattern under part-whole treatment.
U.Method is an admitted non-agentive holon kind: methods can be assembled from method parts into whole methods with whole-level preconditions, effects, constraints, and interfaces, and a whole method can become a part of a larger method. This does not make a method an actor, description, plan, or dated work occurrence. Systems can enact methods and can be classified by context-local system-role kinds.
A local system-role kind classifies U.System candidates in one bounded context. The work-facing contribution grounds the kind's local identity and must be recoverable independently; the kind's non-circular KindSignature states how a candidate qualifies. The kind is not the contribution itself, a capability, required effect, participation or functioning relation, work position, assignment occurrence, classification judgement, responsibility, Method, or Work. Eligibility for assignment, or the existence of an assignment, neither defines the kind nor classifies a System by itself. It is not a public root U-kind or a holon kind.
Descriptions of methods or system-role kinds may be epistemes, but a description does not acquire the described value's kind.
When claim-bearing role leaves its object or relation unclear, use E.10.ROLE to recover what the claim concerns—for example, a local system-role kind, an assignment occurrence, participation in a relation, or responsibility. Use a clear ordinary or directly governed claim as it stands.
Management words need the same discipline. An actual project is one qualifying composite U.Work, not a new project kind; for a process, recover the reusable U.Method or the selected structure at issue; for a case, recover the exact subject or claim, its bounded closure basis, and a named downstream use that remains outside the closed case. A system that exists only in a plan remains intended, and project designation, system-role-kind interpretation, and system-role assignment remain separate claims. Use A.15.6 when the familiar label still hides which subject or claim is current.
FPF is written as a pattern language. A pattern is a reusable action-guidance form. A mature FPF pattern lets a working practitioner recover:
- the working situation where the pattern is useful;
- the project entity under concern, which FPF calls the EntityOfConcern, and the relation, claim, or work object being handled;
- what goes wrong when the distinction is missed;
- the forces that make the problem hard;
- the solution and first useful result;
- the consequences and related patterns;
- the checks that keep the result reviewable.
E.8 states the standard pattern form. E.19 and E.21 support review, refresh, and pattern-quality evaluation. Decision-rationale records, or DRRs, are short records explaining why a bounded FPF content decision was made or changed; E.9 gives their ordinary decision kernel and adds exact ClaimGraph, work, or result identities only when the decision or a named later reliance needs them. FPF uses the same discipline to revise its own corpus: explicit decisions, visible losses, recoverable meanings, and repeated improvement.
The FPF Readme provides ordinary examples for direct uses and Practical-Use Cards for questions needing several contributions. Each card starts from a recognizable working situation and a current practical question, points to one or more direct patterns under explicit conditions, names the kind of first useful result, and says when to stop, return, or inspect a stronger neighboring pattern.
When several cards seem plausible, compare them by the situation they recognize, the difference between their first results, and their stop or reconsideration conditions. That comparison may remain in the conversation. Before selecting a pattern, inspect its Problem frame, Problem, Forces, Solution, Consequences, and ordinary non-use boundary.
Once one direct pattern is selected, use E.11.PUA to follow its Solution to a result that answers the current question or a specific blocker. If the expected subject result is absent, keep a supported interim result and leave that expectation open. Keep an ordinary reversible judgement conversational; introduce an exact assertion, result basis, method, work, or reliance support only when that distinction changes the truth or a named later reliance needs it. Name a dependent use only when an actual continuation or later reliance is current. Use E.11.PUR when applicability, recommendation, coordination, or ordering among candidate pattern uses is the current question.
FPF.Reference:1.1 - Four ordinary starts before a PatternID
Sometimes the obstacle is not choosing among pattern titles. A familiar phrase already hides the subject that the next claim needs. The four direct starts below are independent: use those needed by the current question and stop when its answer suffices.
- “We need to refer to the relation that holds, and perhaps to tell one episode from another.” Name the actual participants and state the relation in ordinary language, using the participant meanings, obtaining predicate and applicability needed to make that statement accurate. If a readable assertion that the relation obtains is enough, stop there. Only when later history, comparison, another relation, or an operation application must distinguish repeated occurrences should an agent use
A.6.RELwith the relation's same-versus-new-occurrence rule and return one recoverably individuated occurrence. If exact recovery finds no current direct relation for the needed claim, use theA.6.RCDmissing-basis disposition; missing participants, facts, predicate, identity rule, or establishedmissing-governorresult remain explicit blockers. - “The project, process, or case report no longer tells us what the decision is about.” Use
A.15.6to recover the subject. An actual project is one qualifying compositeU.Work; a process question concerns one reusableU.Method, one exact selectedU.Structure, or oneTransformationFlowStructure; a case follows one exact affected referent or claim through only the change history and closure basis needed now, while naming one later use that remains outside the closed case. When a source says target system, recover whether it means the product System of an extended enterprise under A.1.STM:4.1. Use system-of-interest for that role in the resulting English account. Keep an intended future system in a plan or description, and keep plan or decision designation, actual work-to-system facts, system-role-kind interpretation, and system-role assignment as separate claims. Stop when the direct subject and bounded claim answer the decision; if systemhood of the recovered entity still matters, the neighboring exit isA.1.SCR. - “Someone drew or named a bounded context, but we do not yet know what organization the decision may rely on.” Use
A.1.1to identify the model edition and the place or entity about which it is used. Recover the relation needed for the decision: where the model applies, how it is actually used in assigned Work, or whether a concrete expression agrees with the model's fixed content. Select the optionalBoundedModelUseStructureunderA.22only when their joint organization changes the decision and its exact constituents, obtaining relations, applied constraints, and named selection-use frame are all present. Otherwise stop at the direct relation or state the missing discriminator. The selected organization is a Structure rather than a holon; its model, participants and descriptions remain distinct.Context Mappingremains aU.Method, and a cross-context organization needs its own selection. If the real question concerns an episteme under a viewpoint, the neighboring exit isE.17.0. - “We have a problem card, assessment, or serious concern, but do not know whether an actual problem exists.” Use
C.22.PFRto check whether an actual condition is adverse under the predicate applicable to the named entity, scope, and interval. An obtainingProblematicForRelationrelates one exact actual-condition occurrence and one exact criterion-applicability occurrence whose selected input is actually adverse for that entity and use. A predicate, applicability occurrence, assessment, assertion, evidence posture,ProblemCard, forecast or modal concern, and current-solvability or continuation claim remain different objects. Stop with the supported actual-problem or non-adverse-condition judgement, or the exact missing condition, applicability, adverse input, or governor. If the useful object is instead reviewable problem-side formulation, the neighboring exit isC.22.2. One card may describe no actual PFR, and selecting a method changes current solvability or continuation, not the PFR's participants, obtaining, identity, or adverse condition.
Ordinary bounded use can remain conversational. Create candidate, fit, recommendation, closure or provenance records only when a named receiving use needs them. Such needs may include addressable comparison history, transfer between participants, automation, audit, durable reuse, delayed or expensive feedback, or costly reversal. The semantic schemas are reference models, not user-interface forms or serialization instructions.
The first useful result is one subject entity or obtaining relation under its defining or testing content and current basis. In ordinary use, name it in domain language; add a predicate, identity rule, assertion, pattern locator, ClaimGraph, or Method only when that distinction changes the truth, next action, stop, or named reliance. The selected pattern id locates action- or judgement-guiding content. The result may be a changed physical or clinical state, a capability, an episteme, a relation, dated U.Work, or another value. A note, measurement, dashboard, or card is the result only when producing that episteme was the intended result.
Keep three activities distinct: selecting a pattern, using its guidance to obtain a subject result, and later work that uses that result. Each can have its own result. Selection may remain a conversational judgement or, when later reliance needs it, produce a fit finding, recommendation or selected-candidate episteme.
The agent doing the work uses the selected pattern’s guidance to act or make a judgement. Identify a separate Method only when the Solution describes one and the current claim depends on its identity. Claims about a performer, assignment or dated Work require their own direct basis.
The subject result exists, or its relation obtains, according to its direct predicate, identity or occurrence rule, applicability, and case facts. A positive durable or reliance-bearing account additionally needs the appropriate current assertion and direct support. That result may later be used as an input, tool, context, constraint, or other needed participant in downstream subject Work without becoming the result of that later flow. Treat those positional words as ordinary cues, not relation kinds: name the source position, dependent-use position, and relation occurrence that the claim needs.
With no direct relation kind or predicate, return missing-governor; with undecided facts, keep the relation open; when the case fails the obtaining predicate, assert no occurrence; with an obtaining occurrence but a missing required endpoint binding, return missing-endpoint-binding.
Across these flows, a U.System may select, construct, refine or describe a U.Method, and plan dated work when preparation is current. If the account asserts a particular dated U.Work occurrence, first recover its exact performer through A.13 and let A.15.1 independently admit the Work. Stop there for a Work-only account. Only when the account or receiving use also consumes precise assignment-bound attribution should it name the covering assignment occurrence and its declared U.SystemRoleAssignment species, retain every identity-bearing participant, check holder equality with the already recovered performer, and establish the F.6 relation. Missing or failed F.6 attribution alone leaves independently grounded Work intact and lowers only the attribution. Recheck any consumed A.13/A.15.1 premise invalidated by the same finding and its dependent conclusions.
Public and project epistemes can guide that line. Use E.18 to recover each TFS-local position; use E.18.NET only when independently identified TFS values must be treated together as a network.
A quick three-way test is: same TFS, different valuation; one parent-relative internal portion, subflow; independently identified TFSs, network. A valuation assigns values under E.18 while the same A.22 selection O/R/C/F is retained; replacing a selected actual application or relation occurrence first reopens that identity. A subflow resolves its selected positions and internal relation occurrences in one parent TFS, retaining all required participants. A TransformationFlowStructureNetwork selects independently identified TFS or nested-network members together with exact obtaining relation occurrences whose participants are bound across their positions. DesignRunTag stays local to one exact position binding in one TFS; it is never a network-wide phase label. Use E.18 for a valuation or subflow, and E.18.NET for a network.
Repeat this use as the project changes: ask the current question, compare when needed, inspect a direct pattern description, use its action- or judgement-guiding content, retain the exact subject result and direct basis—or a stop when that basis is missing—and reconsider when a stronger claim, changed basis, or unresolved relation becomes current. Recover a separate Method identity only when the Solution describes one and the current claim depends on it.
A mantra is Plain didactic wording for a repeatable working reminder. It can help the reader find a consequential question before a difficulty is felt, recognize a relevant situation, recall a useful contribution and find the pattern that supplies it. A local mantra keeps one bounded result, often one pattern's contribution, in attention. A long mantra keeps connected reasoning across several areas of knowledge in attention: its questions, grounds, mutually constraining answers, alternatives and returns. It may connect several patterns or several relevant contributions within a larger account. The developed explanation makes those connections understandable; the short formula recalls them. A.6.P's reminder to recover a relation, its participants and its defining ClaimGraph is local; A.1.STM's map from outside use to recursive builders is long. Phrase length does not decide the scope.
A suitable mantra can open inquiry at an ordinary work occasion. Apply its connected questions to a current or possible case and examine whether the answers and conditions suffice for the intended use. B.5.PI:4.2.1 develops this selection, comparison and return: retain a useful answer, turn a consequential gap into a question, or preserve a cue while its meaning is unknown. A noticed difficulty can lead to the same grounds through inquiry. A.1.STM supplies the systemic project application; another inquiry can finish without a project frame.
For a group of jointly used patterns, a long mantra can be read as a compact statement of how their subject knowledge fits together. Readers need to understand why an answer constrains another, which answers must hold together, and what changes when a premise fails. A useful explanation may therefore need substantial connected prose as well as direct returns to full pattern bodies. Its phrases may address the patterns through their Problem frame or Problem, or through their Solution. A question can recall what remains unresolved; an action phrase can recall how to obtain the needed result. Both can point to the same pattern use. For example, these two formulations recall the same contributions to the report-review inquiry developed in §16.1:
Use whichever formulation the intended reader can recognize and apply. A pattern whose title names a difficulty can still be recalled through its Solution. Wording such as “find what the trial establishes” can state both the difficulty and the action intended to resolve it; clarify the difference only when it changes the next useful action.
A long mantra may arrange its contributions as a logical unfolding that makes their dependencies easy to follow. Preserve the order of justification required by the supplying Method: A.1.STM first considers receiving use, then moves from the system boundary to the larger whole and the joint functioning of its parts at the operating time. That account grounds the system's contribution before construction and creation are considered. Other Methods retain their own questions and relations. A selected happy path can help, but it is not the whole reasoning structure: material alternatives, shared constraints and returns remain part of the developed account.
This order constrains the reasoning used to justify a choice. The initial point of attention and the planned or performed Work order have their own grounds. Enter where the needed result is absent, stale, disputed or unsupported. Reuse an adequate result, return when its conditions change, and stop when the intended result is available. On a diagram, name the teaching use and the omitted branches or returns that matter to its intended use; return to the fuller account when those omissions can change the choice. A customer-journey mantra, for example, may show one route to useful product use while omitting a return from an agreed purchase to securing missing operating support.
Keep this reminder, the possible continuations it describes, a work plan and the observed work history distinct. A.22.CGUS applies when the underlying structure has the required constituents, relations, constraints, local loci and potential continuations; a shown traversal of a qualified structure may then be a DemonstrativeUnfoldingSlice@Context. Qualification concerns that structure, not whether its labels are questions or solution phrases. Ordinary local and long mantras require no formal CGUS qualification. Use A.1.STM when the difficulty concerns the system-thinking long map; use E.10.MOVE only when wording about a mantra move still hides the intended contribution or claim.
A pattern body is a pattern episteme containing its Solution, boundaries, checks, action- or judgement-guiding content and the definitions or constraints it asserts. It is a U.MethodDescription only when that membership is established and the distinction matters to the use. A claim about a project remains a separate subject assertion. Readme and Table of Contents references point to the relevant pattern passages and published term rows.
This reference explains how FPF’s practical uses fit together. It condenses, omits or defers individual pattern details, source publications, the history of their use and many relation records. When a decision depends on a claim explained here, consult the relevant pattern for the claim, its conditions and the omitted detail.
Use the Readme for ordinary examples, Practical-Use Cards and direct pattern locators. Use the Table of Contents to find a known pattern family or obtain a search-oriented overview. Read the pattern’s Problem frame and Solution. Recover a specific predicate, ClaimGraph or Method only when the current claim, action or named reliance needs that distinction.
The following Parts organize the published material for lookup. Kernel membership follows the defining content of universal meta-concepts wherever their patterns supply it. Other content can develop a method or state a constitutional requirement.
- Part A introduces foundational distinctions and their uses: holons, contexts, system-role kinds and assignments, capabilities, methods, work, time, scope, signatures, architecture, characteristics, measurement, comparison, and foundations for choosing from candidate sets.
- Part B gives transdisciplinary reasoning, emergence, evidence, assurance, trust, canonical reasoning, creativity, problem-side records and cues, and bridge discipline.
- Part C develops general patterns for characterization, measurement, mathematical modeling, architecture, temporality, causality, option portfolios, quality, problem shaping and precision restoration.
- Part D keeps ethics, conflict, and multi-scale value questions visible where they are live.
- Part E states FPF’s pillars and guard rails and gives guidance on pattern form, lexical precision, descriptions and publication, transformation-flow structures for carrying results through work, admission, review and design rationale.
- Part F gives unification and naming: local meaning units, concept sets, bridges, term sheets, local-first naming, and technical prose repair.
- Part G gives state-of-the-art work, option portfolios, option selection, benchmarks, shipping, evidence, bridges, dashboards, and refresh disciplines for reusable domain work.
- Supporting publication units can carry glossaries, expanded cases, annexes or other material when the pattern body is not enough.
FPF.Reference:2 - FPF As A Project, Not Only A Pattern List
The FPF development project aims to improve how difficult reasoning is written, checked, taught and used by humans and AI agents. The Core Specification is the normative center of that project, but it is not the whole project.
The Core Specification gives the pattern language: the named concepts, distinctions, pattern bodies, conformance checks, and relations that make FPF usable across domains. It says what the reasoning objects are and how exact claims are constituted and checked. When a project needs to know whether a diagram is architecture, whether a dashboard is evidence, whether a model output may be used for a decision, or whether a term is hiding several kinds, the Core pattern bodies provide the relevant action- or judgement-guiding content and the definitions or constraints the claim needs. A separate U.MethodDescription, admitted Method, or exact ClaimGraph locator is recovered only when that distinction is current. Evidence use depends on the relation between an exact episteme and a target claim (A.2.4) and on the direct grounds for its intended use. Use A.10 when the source-to-use account is implicit or must remain replayable; publication alone does not establish the evidence-use relation. Actor, ownership, and external-authority claims need their own direct basis.
Domain principle frameworks explain the methods and evidence practices of their fields and identify the FPF content and editions on which they rely. A local practice framework supplies guidance for a bounded local setting and may also rely on a domain framework. A local guide that applies existing guidance as it stands needs no new framework boundary. E.4 explains when a separate framework or adjacent product is useful and how its dependencies differ from its publication.
Other publications can teach, demonstrate or support this content: companion explanations, worked cases, tooling guides and research notes have different purposes. A companion may teach a method more slowly, and a tool may implement a publication form; the method, its explanation and the implementation retain their own identities. A useful explanation can be brought back into the supplying pattern when ordinary framework use needs it.
An architectural reference explains the named whole: its working subject, contributions, boundaries and connections, why they are arranged this way, and the consequences for use. This First Principles Framework Architectural Reference belongs to the Core edition it explains. A DPF carries the corresponding account of its own pattern language; a DPF Suite explains a composite discipline through its constituent DPFs. A Suite Architectural Reference connects their contributions and explains the grounds, alternatives and limits of that composition. Using a result from another field does not make that entire field a constituent. E.4:4.2, C.20 and E.11.DSG supply those distinctions.
The FPF Library Architectural Reference explains the larger arrangement of Core, DPFs and Suites, including relations across Suite boundaries. One common account does not establish that all described disciplines are parts of one super-discipline. An architectural reference may be embedded in one framework file or published separately at a multifile assembly's scope; its function does not depend on its position or carrier. E.11.PFP:4.7 requires enough shared explanation, source-based reasons, alternatives and worked detail to understand and adapt the whole without internal design records. Complete Method explanations remain in their patterns. The architectural reference is available when that larger question matters; it is not an obligatory stage before using a known sufficient pattern result.
One file or website can expose several such publications. Their shared carrier provides access; each framework, Reference or companion keeps the content, edition and change conditions established for it. Core meanings remain defined in Core. Authors can revise domain and local methods while preserving those dependencies. The Core can therefore remain tool-agnostic while companions, tools and domain explanations change for their intended uses.
FPF.Reference:3 - Why FPF Exists
Project reasoning can drift when an expression or result is given a meaning or use that its basis does not support.
Without the necessary basis, a sketch may be treated as a promise, a dashboard as evidence, a model output as permission, a selected set as a single winner, a method description as performed work, a diagram as architecture, a safety case as safety, or a metaphor as an ontology. Familiar wording then hides a change in what the project claims or does.
FPF addresses that drift while preserving useful early inquiry and communication. Early recognition can use provisional language. When the language supports a consequential claim or action, recover its meaning, applicable conditions and support. Use the defining or constraining pattern when a kind, predicate or support requirement is unresolved; add formal notation or an exact ClaimGraph locator only when the use needs it.
The aim is to keep difficult reasoning alive long enough to improve it. A project should be able to generate alternatives, preserve uncertainty, compare options, choose locally, publish decisions, reopen stale claims, and repair language without losing the EntityOfConcern the reasoning was about.
For humans, FPF gives a shared working memory for complex reasoning. For AI agents, FPF gives typed constraints, named distinctions, and checkable written forms so generated text can be checked against the work and results it describes. For organizations, FPF gives a way to make reasoning transfer across teams while preserving each team’s local meanings.
FPF.Reference:4 - Creativity And Assurance Mature Together
Creative inquiry produces and examines possibilities. Assurance establishes what reliance a claim can support. FPF connects these contributions while keeping their conditions distinct.
A project may generate attractive possibilities that remain untested, or repeatedly reject candidates without developing alternatives worth comparing.
FPF treats creative work as governed search. It offers methods for asking "what could be true?", generating candidate explanations or designs, preserving novelty and diversity, comparing alternatives, and moving from exploration to refinement when the question requires it. The relevant families include abduction, problem shaping, novelty-diversity and open-ended exploration, set-returning selection, publications of current best-known options, and option portfolios.
FPF also treats assurance as more than a final audit. Evidence, assurance, source-publication currentness, source-use currentness, gate validity and decision permission are different claims. They can develop while creative inquiry continues. Preserving a cue does not by itself establish evidence for another claim; keeping a candidate in a portfolio does not choose it for the next action; recording a mathematical proposal does not validate its correspondence to the world.
These contributions do not define a compulsory project sequence. In practice:
- generate enough candidate explanations or designs before converging;
- keep novelty, use value, constraint fit, and comparison characteristics visible;
- explain promising candidates so their claims and conditions can be evaluated for the intended reliance;
- when the receiving use needs the result made available, publish selected options, Pareto-like fronts, or portfolios while preserving remaining uncertainty;
- reopen affected work when changes in evidence, source-publication or source-use currentness, context or state of the art can change its result or justified use.
In a laboratory, an anomaly may prompt candidate explanations, evidence gathering and model comparison. A product concept sketch can be developed into a reviewable claim-bearing account—an episteme—with scope, proposed value and evidence needs. In operations, proposing an emergency workaround may involve abduction; later reliance on that workaround depends on the evidence, assurance and work records required for that use.
FPF.Reference:5 - Local Closure Inside An Open World
FPF assumes an open world. New evidence can arrive. A better mathematical model may appear. A source publication, source-use record, or telemetry relation may become stale. A competitor may change the state of the art. A user need may shift. A new concern may reveal that the same system should be described differently.
Engineering and management still need local closure: for a release, experiment, procurement, safety case or architecture review, establish what evidence and conditions are sufficient for the next action.
The open-world versus closed-world distinction provides a useful picture. Under open-world reasoning, absence of proof is not proof of absence. If a name is missing from a party guest list, the list may be incomplete. By contrast, a comparison can deliberately close over an accepted option set: an unlisted option is not compared in that bounded decision.
FPF supports local closure for declared purposes:
- identify the source, scope, model-use organization, working situation, comparison basis or other subject-defined conditions needed for this decision;
- name the project entity that the reasoning concerns: the EntityOfConcern;
- state the proposed reliance and its conditions in the description;
- qualify the claim’s support using the evidence and assurance required for the local use;
- state the decision or gate result under its applicable rule;
- state when the conclusion must be reconsidered.
FPF patterns use local closure to declare a scope for action while leaving the wider world open.
Before a method, route, or review makes an action mandatory, ask whether a materially plausible result can change a named substantive decision within the nearest substantive horizon, whether the action realizes an already selected result, or whether removing it changes an assurance or recovery condition on which the use relies.
This contribution is necessary but does not by itself make a proposed inquiry obtainable or worth requiring. Use A.11.OP for that screen and its boundary with direct duties and assurance. When the demand's worth remains open, C.11.DUA compares its attainable contribution and whole burden; a current local choice uses C.11. The result can be a qualified answer on the present basis.
FPF.Reference:6 - FPF As An Evolutionary Architecture For Thought
A team can organize its reasoning so that a changed model, new finding, or departing colleague leaves other useful results recoverable. Its participants, reusable Methods, shared descriptions, and actual Work each have a structure and a different way of changing. FPF helps the team keep those differences visible while improving the arrangement.
FPF is an evolutionary architecture for thought. It is an architecture of patterns, relations, checks, publication units, and improvement loops that can evolve as new problems, domains, AI tools, and state-of-the-art lines appear.
In engineering, structures can make guided change possible while preserving chosen constraints. Their descriptions identify the characteristics that matter and the comparison basis for alternatives; decision records explain why a change was accepted.
FPF applies the same idea to reasoning:
- patterns provide stable forms for recurring reasoning problems;
- DRRs record why normative FPF content changes;
- evidence and assurance patterns guide how support and uncertainty affect reliance;
- declared characteristics, scales and comparison criteria make "better" inspectable for the object and intended use;
- precision-restoration patterns repair wording when unclear meanings can change a claim or action;
- state-of-the-art and option-portfolio patterns help find, compare and revise the approaches available to the project;
- review and refresh patterns let FPF itself improve.
This architecture supports producing, comparing, selecting, publishing and improving answers while retaining traceability and semantic integrity.
FPF.Reference:7 - Architectural Characteristics Of Thought
The reasoning arrangements just described can be evaluated using architectural characteristics. The table names qualities of these arrangements and the FPF guidance for examining or improving them.
The table shows qualities that can matter for the arrangement and intended use. A project may enter through architecture, naming, evidence, mathematics, or comparison, with the intended gain of more auditable, evolvable and usable reasoning across those uses.
FPF.Reference:8 - Beyond Bias Hunting
Recognizing cognitive biases—such as confirmation bias, availability bias, planning fallacy, fixation and groupthink—can help diagnose recurring failures in judgement.
Diagnosing a recurring error leaves a constructive question: what arrangement of reasoning and work would prevent it or expose it when it matters?
FPF provides distinct accounts of method description, plan, performed work, evidence and result, with rules for relating them. For a dashboard, recover which claims it presents and what evidence, assurance, gate result or decision the intended use requires. For options, form candidates, compare their characteristics, choose when warranted and refresh retained alternatives.
The constructive task is to organize reasoning so that its subject, claim kinds, support, publication uses, decisions and Work remain distinguishable and connected. The relevant methods explain how to obtain and connect these contributions and how to revise them when their premises change.
The useful next result may be a clearer problem, a justified comparison, a workable method, a revised physical arrangement or an explanation another practitioner can use. Create a card, model or report when that is the result needed.
FPF.Reference:9 - Thinking Through Writing
Writing can help obtain an understanding as well as make its grounds inspectable. Putting claims beside one another, making a relation explicit or trying a provisional formulation can reveal a distinction that conversation or memory had left unclear. The useful result may be a better question, an alternative worth considering, a reasoned decision or a precise limit on what is known.
Choose the written form by the work it should help perform. When the subject is unclear, compare the relevant statements and what each would imply; use the difference to develop the question. When choosing, keep the alternatives and grounds comparable. When another participant must continue or a premise may change, retain enough of the subject, reasoning and conditions to recover the affected conclusion. Revise the form if it hides the distinction that this work needs.
Conversation, memory, chat logs, sketches or tool outputs can suffice for immediate work. Addressable records become useful when delegation, review, reuse, publication, AI assistance or delay requires durable access. An exploratory note can help develop the subject even when it does not constitute one episteme under C.2.1. A filled card can be an episteme; its selected layout can serve as a publication form under E.24.PUB. The claims and their form of expression remain different objects.
Written forms support different reasoning actions. For example:
- developing a problem card can turn an initial complaint into a formulation whose subject, constraints and unresolved relations later work can use;
- a TaskSignature makes an accepted problem usable by later eligibility, acceptance, and method-family selection without selecting the method or planning the work inside the problem record;
- a comparison frame makes explicit what is being compared, by which characteristics and under which conditions;
- declaring a CharacteristicSpace makes its selected characteristics and Scales recoverable before their values are used in an evaluation or comparison;
- a term sheet keeps local meanings from being flattened across teams;
- a DRR makes the decision, its reasons and its intended consequences inspectable;
- a pattern body explains reusable guidance for a recurring problem, with the conditions and limits of its use.
Consider two handover statements that use the word complete. Placing them side by side may show that one refers to sending and the other to acceptance. The writer can now formulate the question of which event the receiving work requires and what supports the claim that it occurred. C.22.2 develops this move from an initial signal to a usable problem formulation. If examination shows that both statements mean the same event, the proposed contrast loses its ground: revise the question. The written comparison helps obtain the next inquiry, and a changed premise sends that choice back.
The medium is not prescribed. Use paper or a digital tool that keeps the needed claims and relations recoverable. Changing the layout can preserve this work; removing a comparison or its grounds can lose it even when all the old field names remain.
For an AI-generated proposal that needs inspection or reuse, identify what result it offers and its grounds—for example, an option comparison, an architecture question or a qualified model-use claim. Choose a form that keeps the necessary distinctions recoverable. The next section explains when the recovered subject needs classification or shared ontological coordination, and when an ordinary statement already suffices.
FPF.Reference:10 - Thinking-Oriented Architecture, Not A Descriptive Upper Ontology
FPF uses ontological distinctions to make reasoning usable across domains. Its practical question is what the practitioner must understand, distinguish, decide or do, and which meanings must remain stable for that use. The architecture connects distinctions with guidance for obtaining a result, inspecting its grounds and reconsidering it when conditions change.
Start from the receiving use and recover the subject and claim it needs. Identify what is being asserted, about which entities, between which participants and under which conditions. Writing can help obtain this meaning before a stable name or classification is available. F.19 restores the predicates and participants compressed by wording; E.10 directs an unresolved meaning to its subject pattern. For a Characteristic, A.18 requires a defined aspect and Scale; A.19 organizes already defined characteristics and Scales without supplying their missing subject meaning.
When a current pattern already gives the needed claim or action, apply it directly. E.24.CD helps find that sufficient use. Several claims may need to be read together without requiring another kind or ontic. A single episteme must satisfy C.2.1; otherwise the claims can remain in separate epistemes or working notes. This choice preserves the subject and useful reasoning.
Classification becomes useful when the work needs to distinguish members from non-members under a stable criterion. C.3 and C.3.1 recover the candidate domain, membership condition and boundary; C.3.2 governs the relevant candidate judgement. The individual kind is an instance of U.Kind. A KindSignature describing its criterion, a judgement about a candidate and a representation of its members remain different objects. Use a reusable signature when a later use needs that declaration. Distinguish a supported non-member judgement from an unknown result or a candidate outside the declared applicability. A local kind can serve its context without acquiring a new public U-name.
E.24.UK governs the stronger proposal to introduce a durable U-kind. It requires an independently identified subject of classification, a defining identity or membership rule, practical need and dependent use, and comparison with sufficient existing expressions. Its root and two dependent-kind dispositions have different grounds: an additional classification may concern the same individual, or a distinct individual may have a separately defined identity dependence. Use that pattern for the full admission conditions.
An ontic answers a different question: which identity or constitution rule and which relations must remain coherent across named dependent uses? E.24 defines this connected ontology unit through its primary subject, the smallest necessary relation set, the defining rules and the reliance of its consumers. This lets several patterns reuse compatible meanings instead of repeatedly redefining them. When existing direct rules already close the uses, keep those rules; when several governed claims need only a bounded joint account, use that account. Concrete cross-pattern disagreement or duplication can justify opening E.24 to determine whether a durable ontic is needed.
A kind and an ontic are therefore not paired one for one. An ontic can coordinate several admitted kinds; a newly admitted kind can use existing coordination or sufficient direct rules. Where both are needed, E.24 and E.24.UK return separately grounded results in one decision.
These distinctions lead to different useful outcomes:
- Recorded values. An evaluation may need several characteristic values, each on its declared Scale, together with the conditions for interpreting them. A selected space or a profile of those values can be named and reused without thereby admitting a new kind of spaces or profiles. Classifying such constructions is a further question only when a receiving use needs it.
- An admitted dependent kind. B.5.2.0 defines
U.AbductivePromptas an additional classification of the same episteme about an unresolved explanatory question. Its consumers need the shared entry distinction and the returns when the question, account or grounds change; the generalU.Epistemeclassification alone does not express that distinction. The subject pattern supplies membership and exclusion conditions. This use retains an admitted kind without adding another ontic. - Shared ontological coordination. A.19 keeps a CharacteristicSpace's basis, characteristic-to-Scale bindings and Coordinate meanings coherent. A.19.ECS uses that organization to construct evaluations, while E.21, E.9.DA and E.2.DA keep their different evaluated subjects, evidence requirements and results. Reusing the common rules makes their meanings recoverable without making their evaluations interchangeable. Changing a selected Scale requires a changed space and reconsideration of comparisons that used the old one; it does not by itself change the common ontic.
When revising any of these expressions, establish what changed. A clearer name or another publication form may preserve the subject and claims. A changed membership condition reopens dependent classifications; a changed characteristic, Scale or relation rule reopens the comparisons and actions that relied on it. Preserve unaffected results whose grounds still hold, and retain the written reasoning needed to locate the affected use. If the necessary subject meaning or evidence is missing, keep that specific question open.
Ontology thus serves practical reasoning together with the writing described in section 9. It helps distinguish a method description from performed Work, a claim from its grounds and a subject from its presentation, then directs the practitioner to the contribution needed next. FPF uses domain ontologies, mathematics, standards and evidence with their own meanings and limits; it does not replace their subject knowledge.
FPF.Reference:11 - When A Scale Claim Calls For Comparison
FPF's Bitter-Lesson Preference in E.2:6 uses the empirical Bitter Lesson to motivate examination of claimed advantages from more compute, data or search capacity in computational work. When that scale or generalization claim is current, or a separately declared local generality policy applies, begin with C.19.1's cheap scale-claim probe. State the receiving task, usable budget range, conditions and evidence needed for the claim.
Compare the usable performance of admissible candidates over the receiving range, including uncertainty in the difference between candidates. A steep improvement curve can remain below the required performance. If the comparison establishes equivalence, finds a trade-off, or leaves the ordering open, report which finding supports no scale-based preference. To choose greater generality on local grounds, identify the applicable project rule and the cost of using it.
An ordinary bounded procedure can be used on its task-specific grounds. For example, a fixed procedure for summing a known finite list needs correct arithmetic and an adequate task budget; the existence of a general learner does not require a scale audit or an adaptation waiver. Independently applicable assurance and oversight still apply.
Positive procedures, prohibitions and autonomous sequencing follow the actual task, control requirements and authorized policy. Minimal prescription and autonomy do not follow from a scale comparison. Adaptation likewise needs its own objective, evidence, permission, change authority and safeguards. Use E.2:6–7 for the exact activation, comparison, heuristic-debt and precedence conditions.
FPF.Reference:12 - Descriptions, Views And Publication Forms
A product, organization, architecture, safety case, research program, model or AI-agent arrangement may need several descriptions for different concerns.
FPF separates the pieces:
- the EntityOfConcern is the project entity under concern;
- a description is a reviewable knowledge object, or episteme, that describes it;
- a view is an identified episteme that conforms to the fixed rules of an identified viewpoint (
E.17.0); - a viewpoint states the concerns and fixed rules used to judge that conformance;
- a publication form supplies independently identified reusable rules for forming or arranging expressions;
- a particular expression is an independently identified sign construction from which the required claims can be recovered for the bounded use; it may conform to a selected reusable form;
- a carrier is independently identified under its physical or digital domain, and its actual state or realization yields that expression;
- a publication occurrence makes that expression of the selected edition obtainable from the identified carrier by the declared audience under the declared use conditions;
- a reliance account explains which uses the evidence supports and where that support ends.
Diagrams, dashboards, model cards and generated explanations support their uses through the relations they bear to the described subjects and claims. Preserve those relations and the grounds required by the use.
Different readers may need different publication forms. A safety case, architecture description, dashboard, model card, evidence graph and management summary can concern the same project entity while addressing different questions. FPF helps keep their source relations and use limits recoverable.
This is also how FPF can work with distributed and AI-generated representations. When a vector representation, solver model, graph, natural-language summary or human-readable pattern carries a claim, identify the claim-bearing episteme and its relation to the project entity. That episteme may be a description under E.10.D2; it is a view only when it conforms to the fixed rules of an identified viewpoint under E.17.0. Recover the source and the relation involved only when the current use depends on a claim about source use, derivation, or construction. Keep its publication and reliance boundary separate from those recognition conditions. Ask which claim the publication can convey on those grounds.
When a narrative or explanatory rendering is published, retain the same source-use distinctions. Its source relation remains inspectable when it states what selected source structure it used, what it preserved, what it deliberately coarsened, abstracted, omitted, or lost, any viewpoint on which the claimed use depends, the source-return condition, and any unresolved neighboring assertion with its subject-pattern locator. If the rendering begins from an architecture description or view, that source basis may already be a coarsened account of actual, expected, or candidate structures; the rendering keeps that earlier loss visible.
FPF.Reference:13 - Architecture As Structure Of Holons
FPF treats architecture as structure of a holon in a context.
This makes architecture broad. There can be architecture of a physical system, software system, organization, work system, body of knowledge, publication system, research program, AI-agent arrangement, or FPF itself. Wherever holons have structure, architecture can be discussed.
An architecture description or structural view makes claims about the architecture. A viewpoint provides concerns and conformance rules for a view; diagrams and models can represent selected structures; a publication form presents selected content. Use each through its own relation to the architecture and its source.
Use the pattern that governs the current architecture question: C.30 for architecture as an EntityOfConcern, A.22 for selected structure, C.30.ASV for architecture structural-view assertions, C.30.AD for architecture-description assertions, and A.6.M for module-interface relation repair. C.31 and related architecture pattern descriptions locate exact rule content for modularity, reusable structure, scale, interlevel tension, and architecture-changing assertions. Architecture, selected structure, each description episteme, each view, each publication, and each change remain separate subjects.
Architecture work asks which structure matters, what characteristic changes, what trade-off is visible, what description is needed, what interface claim is being made, what evidence supports the decision, and which move changes the architecture.
Assess how hard a holon is to understand, change, control, reuse or improve under the declared architectural characteristics and concerns. Keep the structural dependencies that contribute to this difficulty visible in descriptions, including simplified diagrams.
A Method can be a constituent of another Method while having its own constituents. Performing an action can realize several levels of work at once. For example, updating a running total can be part of calculating a result and preparing a report. The report's purpose affects which updates are appropriate. A result that suffices for a final sum may fail a question about the first chronological limit crossing. Recover these connections with B.1.5.EW; compare a replacement across its encompassing uses with B.1.5.RS.
The Method's constituent–whole relations also help identify what performers must be able to do or obtain, and which shared resources must fit their combined work. C.30.ASV:4.5a separates composition, result use and other relevant structures; A.22:4.3a explains how a drawing can represent them vertically or horizontally under a stated convention. A practitioner may know a basic operation and understand the whole procedure while still lacking an intermediate operation needed to connect them. Practise that operation or obtain its performance from a capable participant, then return to the whole task. A.22.CGUS keeps these capability and resource conditions visible when judging an available continuation. Earlier completed work can supply a needed result without being enacted again now.
Extractable structural information is a reader-relative characteristic of a publication, assessed for the intended reader's preparation and available budget. It applies, for example, to a pattern's text, an explanation in a guide or an architecture description. Epiplexity formalizes structural information extractable from data by computationally bounded observers (Finzi et al., §3); C.29:4.2c governs the use of that mathematical lens. A.6.3.NAR supplies the source-to-narrative relation for narrative publications. What counts as an improvement depends on the named object and intended use.
FPF.Reference:14 - Boundary Statements
A team may use compressed expressions such as "The service guarantees it", "The model is synced", "The dashboard proves it", "The interface is stable" or "The process is compliant". They can suffice when participants recover the same warranted meaning from the context.
When participants rely on that wording in an API, contract, safety case, evaluation protocol or operational gate, make the relevant claim and conditions explicit enough for that use.
A boundary statement can be used to:
- define a term or condition;
- say what a mechanism admits;
- assign a commitment or permission;
- claim evidence or work effect;
- publish a view or decision;
- move responsibility across a boundary.
If the participants, conditions or grounds of these claims remain unclear, recover those values before relying on the statement. Apply the governing rules and legitimate decision authority to any remaining dispute.
Use FPF’s boundary guidance, especially the A.6 family, to distinguish the claim kinds and their grounds. Unpack a contract line, interface statement, API schema, compliance note or safety-case sentence into definition, admissibility, commitment, evidence, work effect, publication and decision components as needed. A compact statement is sufficient when the intended reader can recover its participants, conditions and practical effects.
FPF.Reference:15 - Raising Semantic Precision
Compressed or metaphorical wording can be useful. Repair it when a plausible intended reader cannot recover a distinction that changes the claim, action, understanding or reliance.
Use F.19 for the complete connected reading and repair. This summary shows where additional restoration may be needed:
- Read a complete sentence, row, paragraph or other coherent span and state what it needs to convey.
E.10:0.2cues can help locate hidden claims; they do not decide the repair. - Recover the predicate and required participants. Test the complete claim, including negation, modality and conditions; check predicate–participant compatibility and resolve referents and kinds in context.
- Try deleting optional wording. Retain it only when it changes the plausible intended reader’s understanding, judgement or action. A guard also needs an independent local ground for the rejected reading. Ask whether a series is needed before checking its membership, relations and discourse load.
- If an FPF kind, relation, naming or source-use question remains unresolved, use
E.10to find its governing pattern. Add mathematical modeling or a formal signature only for a remaining question it can answer. - Write the ordinary technical statement that preserves the needed meaning, conditions and use boundaries; add technical fields only when the use requires them. Compare it with the source span for lost distinctions or changed obligations.
- Reread the repaired passage and the context needed to interpret it. Check whether the intended reader can recover the claim and intended use without private explanation. Leave any action-changing limit or blocker explicit, then return to the working question.
E.10 supplies wording cues and routes remaining FPF meaning questions; E.10.ARCH directs unresolved ontology questions to their governing patterns. A.6.P, C.2.P, C.16.P, C.16.Q, C.30.P, A.19.SPR, A.6.F and F.18 supply subject-specific restoration or naming guidance. C.29 helps when a mathematical lens is needed. A.6.0 governs formal-substrate declarations when a formal signature is the object at issue. F.19 governs the connected rewrite and local rereading.
A repair succeeds when it preserves the warranted meaning and lets the intended reader use it, obtain a needed clarification or identify what still blocks the work.
FPF.Reference:16 - Big FPF Storylines
FPF connects ways of asking a question, developing an answer, testing its support and using it in further work. The connection matters when one sound local result leaves the next participant unable to act: the measurement concerns a different population, a candidate needs unavailable support, or a useful explanation omits the condition under which it holds. Start with that receiving question and use only the contributions needed to answer it.
Open-ended development connects several of these general contributions. C.40.OD connects a consequential difficulty, problematisation, a worthwhile direction, construction of a way, its provision, actual work and continuation from the position reached. C.40.JD distinguishes development of the way, development of its holder and provision; C.40.NP uses a result to find further worthwhile and attainable problems. C.39 supplies a missing way, C.32.MWA.PP compares who performs and provides it, and the cultural Methods in C.36 explain reconstruction and renewal among further carriers. E.23.CDI concerns improvement of the means of development themselves.
The general construction states which result a concrete use needs and the conditions under which it can be consumed. How that result is obtained can differ for a person, an organization, an AI system or another subject. Acquiring a capability and receiving an adequate external performance remain different results; neither establishes self-development unless the subject makes the relevant contribution to conducting its own development. The FPF Library Architectural Reference (Library.Reference:9.1) explains how these Core contributions connect with the Library's domain languages. That wider account is useful when the work needs those connections.
FPF.Reference:16.1 - Follow one question through several contributions
When a question, surprising result or promising construction leaves the next useful reasoning contribution unclear, use B.5. State what an answer should let its recipient understand or do. If an available result already suffices for that use, return it and stop. Otherwise, identify and obtain the missing contribution, explain what it establishes for that use, and return the result with its conditions and limits. Continue with a further question only when its possible answers could change understanding or action and investigating it is worth the cost. If no question has yet been recognized, use B.5.PI on an ordinary work occasion, such as a handover, demonstration or explanation.
Consider a constructed example. A team is deciding how to help engineers review technical reports. A purchased assistant and a locally operated assistant remain candidates. The local candidate appears faster on the small set tried so far. The current question is whether that is enough to begin relying on the proposed review arrangement.
Use C.16 to make the reported speed interpretable: which reports, which part of review, which assistance, which result, and which uncertainty does it cover? A time for extracting passages leaves open the time for checking their relevance and correcting errors. Use B.3 when the next decision needs an assurance answer: what exact claim does that trial support, what could defeat it, and which reports or operating conditions remain outside its basis? If the trial omitted reports containing tables, retain its result for the tested class and identify the table-handling limitation. That missing comparison becomes a probe proposal only when the receiving choice and attainable contribution warrant the inquiry.
The proposed arrangement also needs extraction, independent checking and final release review. Suppose their estimated weekly demand on the same engineer is respectively 3, 8 and 4 hours, while only 10 hours are available. The estimates apply to the same workload and the hours cannot be shared between these activities. Each activity fits individually; together they require 15 hours. The useful whole-arrangement result is a five-hour shortfall. The team can reduce the workload, provide additional qualified capacity, or change the arrangement and compare again. Even if extraction took no time, independent checking and final release review would still take 12 hours, two more than the engineer has.
B.1.5 becomes relevant if the team is also designing these contributions as one reusable Method: it asks how the part Methods, preconditions, results, order and failure handling make the whole action possible. For the present capacity question, the explicit workload and resource comparison are sufficient.
With these two candidates and the missing table-handling comparison, use C.11 when the team must decide whether another bounded probe is worth its cost before choosing. The proposed probe must be able to change that choice; the current candidate descriptions and qualified results remain available. A different question arises when the team needs a continuing research archive, a front or generation of further possibilities: C.18 then supplies that contribution. Use C.19 when the team must decide or reassess the exploration or exploitation policy for its still-live pool, such as the allocation of effort across several continuing lines. The local choice can proceed directly when neither of those broader questions is current.
This example ends with three usable results: a qualified reading of the existing speed result, an explicit five-hour capacity shortfall, and a specific missing comparison. It leaves the deployment decision open. A later addition of qualified capacity changes the resource conclusion; a failure on tables changes the affected claim about report handling. Neither event erases the result on the original report class. This is how a reader can combine FPF contributions and then reopen only what a changed premise affects.
Inquiry can stop earlier. A laboratory may need to explain why several performances differ before it has any preferred intervention. A.3.1.MR helps recover a candidate reusable way from the performance evidence; a counterexample can leave the candidate unresolved and identify what to observe next. The useful result is then a sharper hypothesis and discriminating observation. Choosing or deploying a solution becomes current only when the research question and evidence make that next move useful.
FPF.Reference:16.2 - Architectural Rationale
The organization supports several useful scales. A practitioner may apply one pattern, use several contributions together, or develop a recurring domain Method described by many patterns. A professional DPF supplies the domain difficulties, mechanisms, evidence and judgement; a local LPF supplies the arrangements of a particular practice. A narrower profile can reuse several broader contributions and explain its changed conditions. Further useful narrowing remains possible. Pattern reuse, Method composition, specialization and publication grouping therefore need their own stated relations.
An individually addressable pattern lets a reader inspect the Problem frame and Solution at the point of need. The whole account explains the connections, shared conditions and reasons that would otherwise have to be reconstructed from many bodies. The two scales have different reading costs: a direct answer is cheaper for one familiar question; the broader explanation helps when a reader must adapt the arrangement or understand why several local answers fail together. E.11.PUA supports the selected direct use and E.11.PUR the current choice or coordination among uses.
A single prescribed project sequence is a serious alternative when the same regulated or reproducible procedure must be followed repeatedly. FPF instead keeps the contribution structure open to direct entry because research, engineering, operations and management repeatedly need different first results. A local practice can select a required procedure and its assurance conditions. A.11.OP screens additional mandatory actions for contribution to a real decision, selected result or relied-on assurance/recovery condition. A contribution alone does not justify the demand's cost or establish its force; the applicable choice, advice, assurance or authority method completes that question.
A shared vocabulary alone is another useful alternative when classification is the entire problem. FPF pairs the distinction with the difficulty, usable move, evidence and limits because a team usually needs to do something with the classification. A collection of independent best-practice summaries is cheaper to assemble, but the receiving user must then reconcile their meanings, assumptions and result uses. FPF makes those relations explicit where that reconciliation changes action. When one existing domain Method already answers the question sufficiently, use it directly; the benefit of an additional FPF contribution must exceed its reading and coordination cost.
This architecture also explains the separation between descriptions and their subjects. An alternative can be considered before it is realized; the same Method can be described in prose, diagrams or another suitable medium; several views can answer different questions about the same system. A.3.2 governs an exact MethodDescription claim, and the E.17 family governs the relevant view and publication uses. This allows a representation to improve without treating every publication change as a change to the described Method or system.
FPF.Reference:16.3 - Shared sources and the choices they support
FPF uses source traditions for particular answers and states the adopted contribution in the subject pattern. The following connections explain why several families work together. The pattern bodies identify the source editions, stronger technical conditions and refresh triggers.
Constructional ontology contributes a demand to explain constituents, construction and identity. A.1 adapts Florio and Linnebo's construction-sensitive account and the applied choices discussed by Borgo and Righetti; it keeps part relations and whole recognition explicit instead of importing an external category system wholesale. B.1.5 carries the corresponding question into Method composition and also adapts scoped-effect and protocol work: usable joins depend on preconditions, order, boundary interactions and failure routes. This combination helps a reader test a proposed whole while keeping its diagram and description separately inspectable.
Measurement and assurance supply different parts of an evidence-based answer. C.16 adopts the JCGM VIM result boundary and adapts GUM measurement-model discipline so that the reported value, relevant information, assumptions and uncertainty can be recovered. B.3 adapts the claim-argument-evidence structure of ISO/IEC/IEEE 15026-2 and GSN to the particular reliance question. Its dependence-sensitive calculation also rejects a universal weakest-link arithmetic. Together they let the report-review team ask both what a time value means and how far the trial supports the proposed use.
Open-ended search and sequential decision research explain why exploration is kept beside assurance. C.18 uses quality-diversity research to distinguish retained alternatives, current fronts and generation of further possibilities; its source account states the limits of inferring useful exploration from archive occupancy. C.19 draws on bandit and Bayesian-optimization work for explicit cost, uncertainty and policy-change pressures. FPF retains those contributions. Choose the algorithm and domain evaluator on grounds appropriate to their use.
The synthesis is use-specific: construction explains what whole is proposed, measurement makes a relevant observation interpretable, assurance qualifies reliance, and search preserves alternatives or asks for another result. A successor source matters when it changes one of those answers. G.11 returns the affected use to that source; E.19 and E.23 support preservation and improvement of the resulting pattern content. This lets stronger knowledge change the framework without requiring every unaffected practitioner result to be obtained again.
FPF.Reference:16.4 - What to examine when adapting the arrangement
For a combined use, ask whether the outputs still answer the receiving questions, whether shared workload and resource assumptions are compatible, which missing premise changes the result, and what remains usable if that premise changes. Keep the whole-set condition where that combination is explained and use the relevant direct pattern for its technical test. The 15-hour example shows why locally acceptable contributions can still require a different joint decision.
The examples here assume readers who can supply subject expertise and recognize relevant evidence. A fluent assistant or an experienced engineer may supply explanations that a new learner needs from the publication. The reader can use a bounded walkthrough to test recoverability of an answer; claims about learning, retention or transfer require observations suited to those claims. Likewise, engineering and software source examples indicate particular contributions; applicability in a laboratory, organization or other setting depends on its own mechanisms and evidence.
Using the arrangement costs attention and, when later reliance needs them, addressable source and result records. Its practical gain is that a new participant can find why a result was used, what it enables and what would change the answer. Stop when the current question has that useful answer or an explicit missing premise. Keep unresolved questions available for later inquiry rather than adding a pattern use merely to complete a familiar sequence.
FPF.Reference:16.5 - Construct a usable whole with existing methods
Use this account when useful contributions are available but the intended whole cannot yet be obtained or used. This occurs in practical design and when an author allocates a source's construction to familiar patterns but loses the instructions that connect their contributions. Identify the next missing result, obtain it through the relevant subject method and return it to the use that required it.
The account assumes enough subject knowledge to recognize the required result and judge whether a proposed contribution fits. Obtain subject assistance when that knowledge is missing. If one known method already answers the question, use it directly. The explanations below help select and combine contributions.
Semantic synthesis develops claims and distinctions: what the relevant objects and relations are, how source accounts can be compared, and what remains unresolved. Methodological synthesis constructs ways of acting and their material relations: how to obtain and use results, under which conditions, and where to return when an operation fails or its result cannot be used. They can develop together. Distinguishing assistance from a performer's own capability can change the method; attempting the method can reveal that this distinction was missing. Use F.0.2 for source-ontology comparison and C.39:4 for general construction, connection, explanation and change of Methods.
One account can explain composition within a Method and relationships among independently usable Methods. C.39:4.3–4.6 develops their connections for an ordinary practitioner: distinguish composition from enactment, reuse from generality or refinement, and cross-domain use from those relations; explain result uses, independent branches and what a changed condition reopens. E.4.CM applies this general foundation to framework authorship and public pattern form. C.32.MWA supplies an architecture account of Methods together with their performance, support and development.
The two worked cases use stipulated facts and numbers. One presents a partial comparison of night-service options and requirements for a conditional external arrangement; the other derives an assessment from measurement inputs. They show conditional reasoning, including what changes when a consequential input changes. A real project requires its own inputs and evidence.
FPF.Reference:16.5.1 - Start outside the proposed boundary
State the use for which the whole is needed and the result that would make a difference there. Identify the relevant recipient and affected parties. Ask what must remain true when the result is used. This helps determine what belongs to the proposed whole and which outside contributions it requires. A missing contribution may require a new provision or a changed boundary.
The outside question need not identify a containing system. A pump belongs to an installation; a claim about that pump concerns it; a decision uses the claim. These are different relations. Looking outside first establishes the grounds for the inward choice. The work can begin elsewhere. When an available invention initiates the inquiry, look for a useful occasion, then test the invention against the conditions of that occasion.
Choose what must be obtained now. A usable assessment, a proposed service arrangement and an operating service have different completion conditions. A proposed arrangement can be the complete answer to a design question while leaving the original service need unmet. Keep that larger need visible when returning the smaller result.
FPF.Reference:16.5.2 - Recover the construction and select the next operation
When a source already supplies a construction, recover its whole before allocating its components: what it tries to achieve, what is connected, how the connections work, and where it returns when a premise fails. Retain distinctions that change the operation even when all the component ideas have familiar names. When sources give different accounts of the same objects or relations, state the difference and determine whether it changes the receiving operation, its assumptions or permitted use. Keep consequential alternatives separate until an applicable subject comparison justifies their combination or selection.
Useful methods can also have arisen independently, with no source that already explains their joint use. Start from the receiving difficulty and develop the missing connections through C.39:4.3–4.6. For a framework publication, E.4.CM:4.1–4.7 applies that construction to its readers, public owners and pattern form. Recovering a source's ready-made assembly is one entry, not a prerequisite.
Attempt the intended use with the contributions available. Locate a required result that the next operation cannot yet use. State that operation, who performs it, what it needs and what is supplied instead. For night response, diagnosis needs an available qualified operator; the explanation describes a conditional response calculation. For pressure assessment, comparison needs absolute pressure values with their uncertainty; the record supplies a gauge reading. These failures select different work.
Ask which change would make the supplied contribution usable. If a clear explanation would still leave the operator absent, explanation is not the missing contribution. If an applicable measurement record already exists but its indication has not been interpreted, taking another measurement may add work without settling the comparison. This test distinguishes an unavailable contribution from an unavailable description or interpretation of one.
Select an available pattern that teaches how to obtain the required result. Read its working situation and operation. In the two applications:
- C.16 recovers the measurement subject, reference, model and uncertainty. Use the measurement model to determine which values fit the indication and whether they settle the receiving question. The pressure example below performs the necessary interval calculation and threshold comparison in full.
- C.38 develops comparable ways to obtain the same result; C.11 governs the subsequent choice when the comparison is ready. Their results are a comparison and a choice, not an available service.
- A.15.9 helps use or request one bounded result from another practice, such as a qualified assessment of a proposed response time. It does not govern obtaining continuing provision. The night-service case specifies what the service owner must obtain before selecting and relying on a service; it does not supply the required procurement and operating methods.
- C.2.1 identifies the resulting episteme through its claim content, entity of concern and reference scheme. Its constitution distinguishes that result from the measurement Work and the pump about which the claims are made.
These patterns supply parts of the two applications; the night-service case also exposes a missing way to obtain and operate the service. Another subject requires its own selection. For a missing physical connection, identify the required behavior and participants, then use the relevant engineering method or obtain that operation from a capable provider. A.1.STM can help reconsider the system boundary and outside use. C.39 develops a missing obtaining way or connection at the needed scale. E.4.CM applies it when the result must become a developed framework explanation.
Perform the selected operation and return its result to the operation that needed it. A proposed contract can settle a terms question while leaving service provision absent. A resolved pressure comparison can inform a release decision while leaving its other requirements open. If the result still cannot be used, locate the remaining condition and repeat only the affected work.
If a source disagreement still changes which construction would be usable, return the bounded semantic-comparison question to F.0.2. If no existing method or competent provider supplies the needed operation, retain the precise gap and use C.39 when further construction can change the answer. Use E.4.PFAD when the unresolved question concerns the resulting framework contribution or its placement. A recurring operation absent from the available suppliers can justify a new contribution.
The table distinguishes several results a practitioner can seek and the completion conditions that change their use.
A design description is knowledge about a proposed System, whereas realizing that System requires its constituents and relations to obtain. An ontic description states the distinctions between objects and the relations required by its modeling question. For a larger ontic description, use the definitions and relation rules of its subject; this pressure example supplies only the distinctions required for its assessment.
FPF.Reference:16.5.3 - Compare constructions and return to use
When the recipient needs an appraisal of proposed ways to obtain the same result, use C.38 to establish what each can supply on the same receiving terms. Two names may describe one way. If one or none of the named ways meets the terms, that finding can complete their comparison. When the recipient also needs another way, develop one or explain what excludes every further eligible way within the permitted range. If the search has yet to establish either result, identify the work still needed. Preserve unknowns that could change the comparison. Use C.11 for the resulting choice when its basis is ready. A narrower result can be proposed with its consequences. Assess it against the revised need once the person authorized to change the terms has accepted that revision.
For each required contribution, check that its result, meaning and conditions fit the operation that uses it. Return the resulting whole to the outside question. If it cannot yet serve that use, say what is available and which precise dependency still blocks the remainder. Retain useful partial results.
When the recipient needs to know how the whole could adapt, vary a condition that matters to its use. A change already under way or an uncertainty that could alter the present conclusion also warrants this examination. Trace its effect on the relevant constituents, relations and boundaries. Preserve contributions whose premises still hold and explain what the resulting whole can provide.
C.39:5.3 works this return across several Methods without requiring framework authorship. Preparation supplies a qualified recording to movement analysis and demonstration viewing. The constant correction no longer meets the tighter analysis tolerance, while the previously qualified viewing use remains available. The case explains composition within preparation and result-use and development relations among independent Methods. E.4.CM:5.4 then shows what framework authorship adds: a shared public explanation, its content functions and placement, and direct returns to its suppliers.
FPF.Reference:16.5.4 - Explanation and night coverage
FPF.Reference:16.5.4.1 - Recover the receiving result
An engineer explains a reduction in response time from eight to five minutes, conditional on an operator being present. A colleague asks about night coverage, when no operator is present. Preserve the conditional explanation. The next useful contribution is a way to obtain the required night response.
For this worked example, define the operational requirement as follows: a qualified, authorized operator must start the applicable mitigation within five minutes of alarm detection during the seven nightly eight-hour windows. The requirement concerns the start of appropriate mitigation, not resolution of every incident. It applies to the declared incident class and at most one incident at a time. These added conditions make comparison possible; a real practitioner must obtain their actual counterparts from the service need.
FPF.Reference:16.5.4.2 - Compare proposed ways to meet the need
The nightly windows require 56 hours of coverage per week. Qualified members of the internal team have 12 hours available without conflicting with their other assignments. No night assignment has been established. Even if the owner assigns those 12 hours and verifies the required response, another 44 hours still need staff.
Assume an external provider offers all 56 hours for 600 units per week, within a budget of 800. The proposed service includes a qualified operator and replacement coverage. For the declared incident class, its proposed serial bounds are 0.5 minutes for alarm delivery, 1 minute for the operator to take responsibility for the incident, 1.5 minutes for diagnosis and 1 minute to start mitigation. Their sum is 4 minutes. These are offer terms to verify, not observed performance.
The existing automation can route an alarm but cannot select and start the required mitigation within its current authorized function. A day-only promise would be cheaper, but the stated receiving use requires night coverage. These are consequential reasons for rejecting those alternatives in this case.
Continuing the current arrangements leaves night coverage unverified. To assess a full internal roster, identify who could cover the other 44 hours, on what assignments and at what cost. To assess the external offer, qualify its total cost, terms and operating conditions. If a comparison is due, a second provider or a mixed roster could also supply a credible alternative. If the commission is to secure coverage and one qualified offer suffices, the owner can proceed within the purchasing authority. The parties must agree on terms and verify actual provision before anyone can rely on night coverage.
FPF.Reference:16.5.4.3 - Specify the missing procurement and operating results
Before committing to the external service, the service owner needs an adequately supported external proposal. It must identify the covered hours, response obligations, full cost, replacement and withdrawal conditions, the provider's required access, and who can authorize and make the proposed commitments. If a sourcing choice is due, use those same conditions to compare the ways under C.38 and take the choice to C.11.
That proposal is still missing. No procurement method or qualified provider result that establishes it is supplied here. A.15.9 can help request a bounded specialist result, such as an assessment of the proposed response time; it cannot supply the missing procurement operation.
After a supported choice and agreement, the service owner needs qualified staffing and replacement throughout the covered hours. Alarms must reach the responsible operator in an interpretable form, the current configuration must be accessible, and the operators must have authority for the permitted mitigation. Verification must provide evidence that the connected response meets the stated requirement. No service-operations method or qualified provider result supplying this provision is given in the case. The connections below specify requirements for that missing contribution. A technical operator who explains the mitigation may lack authority to purchase the service or permit operational access.
Connect alarm detection to delivery, delivery to the operator taking responsibility, diagnosis to the applicable mitigation, and the provider's report to the service owner's verification of the response. Preserve the time origin and incident identity through those connections. The verification exercise must test receipt, configuration access and use of the replacement operator as well as the nominal serial path. Its coverage of actual incident conditions must be stated.
Before authorizing the arrangement, examine a relevant consequence outside the immediate service team. Suppose the original night alarm would wake residents who cannot participate in the purchase discussion. Their exclusion from that discussion does not remove the consequence. The candidate uses silent delivery to the responsible operator instead, provided that the changed channel can deliver and be noticed within the required conditions. If it cannot, the arrangement needs another change.
FPF.Reference:16.5.4.4 - Return the result and its remaining conditions
The planner can identify staff time for 12 of the 56 required hours. The remaining 44 are a gap in the proposed internal roster. The external offer is still a proposal. The next procurement task is to obtain and qualify that offer. A commission to compare two ways also needs a credible second way or a statement of what prevents the comparison. After agreement, the service still needs staffing, working access, authority and operating evidence. Take the procurement and operating gaps to E.4.PFAD when deciding which subject-domain practice can supply each result. The original conditional daytime calculation remains valid.
Once the service has been authorized and the commitments and operating evidence are in place, the owner can decide whether to rely on the night service at the stated scope. Communication then conveys the qualified result and its remaining limits. Understanding, commitment, acquired capability and observed response remain different outcomes along this construction.
Change the whole condition to two simultaneous incidents. The offered bounds apply only to one. Compare parallel provision, a second authorized responder or a justified prioritization with a changed service promise; return an unmet requirement if no continuation is supported. Retain the verified meaning of the alarm and each applicable diagnosis; reopen concurrent capacity and its implications for time, cost and authority.
FPF.Reference:16.5.5 - An interpretable pressure assessment
FPF.Reference:16.5.5.1 - Recover the pressure question and its inputs
An engineer needs a pressure assessment for a decision about pump P17: does the available information establish that its pressure, in the stated configuration and operating regime, is at or below a 300 kPa absolute limit at the measurement occasion? Other conditions and authority for releasing the installation remain separate.
Assume three source contributions. A model manual states the absolute pressure limit. A configuration record establishes that this limit applies to P17 in the regime being considered. A measurement record reports 195 kPa above the local atmospheric pressure, with an error bound of 5 kPa; local atmospheric pressure is 100 kPa absolute with an error bound of 2 kPa. For this illustration the bounds are enclosing intervals under the stated conditions, not confidence intervals. The records are assumed applicable to the same regime and measurement occasion.
Use C.16 to recover the measurement subject, reference and uncertainty. Here the addition relation is available, so an interval calculation can determine what comparison the supplied bounds resolve.
The construction needs the applicability connection, the pressure reference and the calculation consumed by the decision.
FPF.Reference:16.5.5.2 - Form and interpret the pressure assessment
Keep P17 as the entity the resulting assessment concerns. State the regime and measurement occasion as conditions of its claims. The reference scheme uses kPa, an absolute pressure datum, the relation between gauge and absolute pressure, and the meaning of the stated bounds. The claim content includes the applicable limit, the converted pressure interval and what follows for this comparison.
The manual states the limit; the configuration record states its applicability to P17; the measurement record supplies the indication and uncertainty assumptions; the calculation derives the comparison from those premises.
For these readings, absolute pressure equals gauge pressure plus local atmospheric pressure: p_absolute = p_gauge + p_atmosphere. Apply that relation to the stated intervals:
- gauge pressure lies in [190, 200] kPa;
- atmospheric pressure lies in [98, 102] kPa absolute;
- absolute pump pressure therefore lies in [288, 302] kPa.
For a conservative enclosing interval, adding lower endpoints and upper endpoints requires no independence assumption. It does require the stated intervals and addition relation to apply together. The stipulated relation admits the central values, which give 295 kPa absolute. The enclosure's upper endpoint exceeds the limit while its lower endpoint does not. This enclosure therefore establishes neither compliance nor a violation. Distinguish an enclosure spanning a threshold from two feasible cases with different answers: the enclosure alone leaves the threshold question unresolved, without proving that both outcomes are possible. Comparing only the central value of 295 kPa with 300 kPa would lose the reason the uncertainty matters.
The resulting episteme is a coherent answer: under these inputs, compliance is unresolved. It tells the decision-maker what cannot be concluded and why. A measurement that narrows the pressure interval enough to resolve the comparison, a changed operating regime, or a governing decision that permits reliance under residual uncertainty are different next possibilities. Such a decision must identify the uncertainty it permits and the scope of that permission.
FPF.Reference:16.5.5.3 - Change the input and retain the applicable reasoning
Suppose a later applicable measurement keeps the same central readings but bounds gauge error by 2 kPa and atmospheric error by 1 kPa. The new absolute interval is [292, 298] kPa. Its upper endpoint is below 300 kPa, so the stipulated information now supports the pressure-limit comparison for this regime at the later measurement occasion. Actual release can still require other conditions that this assessment never claimed to decide.
The assessment still concerns P17 under the stated regime. Its unit, pressure reference and applicability rule remain, while the later measurement changes the input, derived interval and threshold conclusion. The engineer reuses the conversion relation and comparison rule and updates the affected claims.
C.2.1 distinguishes the assessment's claim content and reference scheme from the pump those claims concern. To ground the assessment in an installation, the records must refer to applicable measurements of P17, and the calculation must warrant its claims from those measurements. The stipulated inputs here illustrate the inference without establishing that measurement relation or installation-side grounding. The assessment informs the release decision; its other conditions and authority remain separate.
FPF.Reference:16.6 - Develop a useful way from received material
A practitioner may receive a chapter, paper or discussion before knowing which of its ideas deserve adoption. Begin with what the material could help someone do or understand. Follow a proposed result into its receiving use and recover what the source supplies. B.5.PI makes that ordinary occasion available without requiring a known error; B.5.RC helps recover a construction, and C.39:4.2–4.6 develops the way needed by the receiver. An adequate direct answer can finish the work.
For example, a historical discussion connects proposing an action, exposing its reasons to criticism, revising the proposal and taking the outcome seriously. C.39:5.4 follows that material into an instruction for examining a proposal and deciding how to continue. It preserves the constructive connection while distinguishing a useful proposal from an action whose necessary conditions and grounds have been established. Recovery begins with the source's constructive proposal; following its application exposes a question about the grounds for action.
Source interpretation, development and evaluation contribute different results. F.0.1 can settle what a consequential passage means; F.0.2 compares source accounts when their difference changes the receiving claim. C.39 constructs and explains the missing operation or connection. A.10 qualifies reliance on the claims used; C.11 makes a choice among available continuations. E.22 asks what the evaluation must establish for that use, and A.19.ECS is needed when no adequate evaluation exists or an actual failure warrants developing it. Start at the contribution whose inputs are present.
The distinction between Kernel and broader Core has a practical consequence here. The definitions of Episteme, Method and Work keep a source claim, a proposed way and a performed action apart. Those definitions alone do not construct the instruction: general Methods such as C.39 supply that work. Domain Methods and evidence supply the particular operation and its conditions. E.4.CM adds the framework author's publication work only when the resulting contribution is to be maintained in a framework.
An architectural reference can explain how independently useful contributions meet in this situation. Their direct bodies retain the reusable operations and governing distinctions; an appropriate DPF retains its domain contribution. A short entry can point to the connected explanation. This provides a smaller return path for a familiar use while leaving the reasons needed for adaptation accessible.
Evaluation follows the same receiving use. A good summary and good constituent patterns are evidence for their own questions. To judge whether the reader can obtain the promised result, examine the connecting explanation and its application on the material, including necessary support. E.22:4.3 and its source-to-method example show how to frame that question without changing the meanings of the constituent scales. A supported conditional next inquiry can be a useful complete answer to an inquiry-selection question; it does not fulfil a request for a performed intervention.
Finally, change a premise that one application uses. In C.39:5.4 a tighter timing requirement reopens the movement-analysis proposal while demonstration viewing can retain the same prepared recording under its unchanged conditions. Follow the relevant claim and result use, update the explanation that the receiver needs, and preserve what the change does not affect. Separate publication units can help obtain the right explanation; only the semantic dependency determines which conclusion needs reconsideration.
Conceptual compactification here keeps a developed connection available for reuse, together with the distinctions and reasons needed for application and change. Its effect on a particular reader's effort, acquired capability or work result remains a question for observations under that reader's actual conditions.
FPF.Reference:16.7 - Develop and use methods with distinct claims and results
These connected questions help a reader improve a way of working without treating its description, support or observed performance as the same result. The full Methods retain their individual entries; the explanation below shows why their answers can differ and when they need to be used together.
When it is unclear which work deserves improvement, C.39.WI follows work that consumes substantial resources, causes avoidable loss or cannot yet supply a useful result. It compares complete consequences and burden, then selects an attainable Method, explanation, access, provision or execution change, a retained possibility or continuation of current practice. Use C.39.MF when the selected development question still has an ambiguous subject. An adequate professional improvement Method can be used directly.
When a selected failure survives correction, C.39.WI:4.4.1 connects the failed receiving use with the conditions that directed production, checking and the earlier repair. It uses a supported diagnosis to change the operative source or provision, makes that change available in the working form, and follows the changed basis through dependent results. C.28.CM supplies a needed causal distinction, B.5.RR preserves independent grounds during revision, and A.3.1.MI supports introduction and adaptation. Existing adequate results can supply these contributions. A corrected source, restored output, changed performance and worthwhile effect retain separate grounds.
Partial work earns its contribution through a particular relation to the originating question. A model calculation requires a justified return to its subject; a component result requires the whole's composition and operating conditions; a worked case requires an explicit operation and grounds for its wider use. C.39.QR recovers the original question, establishes that relation and its warrant, and separately judges which part of the requested result is now available. A valid subject inference can still leave an explanation or operating capability to be constructed. The next move follows that remaining need.
When the missing result is an account of an organized whole or broad field, C.39.WA develops the common grounds, constituent contributions and relations that make the account useful together. Those grounds explain choices about parts and which choices change with a premise. Findings in the parts can in turn change the common explanation. A discipline's knowledge–practice organization, a Method's obtaining relations and a system's functioning call for different subject constructions. The relevant subject patterns supply them; the common Method preserves the question through their use.
Grounding makes an explicitly explained construction concrete. In a Method explanation, distinguish the reusable operation, its displayed performance and the material worked on during that performance. Choose varied cases for consequential differences within the claimed range, and return from each to what it reveals about the operation and its conditions. Generalization also needs the elements and relations being generalized, the wider class and the grounds for that extension. E.8 and EXD.2 develop these explanatory moves; E.19 and E.21 connect their examination with the promised subject and use.
FPF.Reference:16.7.1 - Method, MethodDescription, WorkPlan, and Work remain distinct
A Method is a reusable way of doing. A MethodDescription is an episteme about one admitted Method. A candidate Method account can be improved, compared, and tested while its candidate status remains explicit. A WorkPlan is about intended Work. To assert a dated Work occurrence, use the full independent A.15.1 admission basis, including its A.13 performer, construction and actual performance, enacted Method, temporal extent and required containing-System relation. Ground its result and any additional relations separately when those claims are needed.
A team that writes a playbook, schedules a trial and publishes the text still needs separate grounds for Method qualification and for actual enactment.
FPF.Reference:16.7.2 - Several structures and several views can coexist
A Method decision may depend on a Method composition structure, a Method unfolding, simultaneous Work, an allocation structure, a subject-and-support arrangement, a description structure, or cultural relations. These structures need not be isomorphic. Name the structure and relation that changes the decision.
Project, process, and case views can expose different claims about the same Work. A project viewpoint may expose dates, allocations, authorities, and decision slots. A process viewpoint may expose recurring input/result and coordination correspondences. A case viewpoint may expose the changing evidence, exception, and next decision.
FPF.Reference:16.7.3 - Reader route and result dependencies do not prescribe Work order
One reading route through this family begins by selecting and recovering the Method-development subject: later decisions need a well-founded account of what is being developed. It then moves through qualification and architecture, description and support, and trial and change. This order helps a reader find prerequisites. Repertoire recovery, description, support repair, trial planning and source refresh can overlap; a known support or evidence defect can be repaired without traversing every earlier pattern.
Begin with the entry that can supply the result needed for the current decision. Follow a dependency only when that result relies on it. Stop when the answer already resolves the working difficulty.
Constituent actions in ongoing work. During a trial of a proposed review Method, asking a participant to explain a unit conversion can constitute part of testing that Method, while the trial constitutes part of developing the team's way of reviewing. If the trial asks about unaided recognition, supplying the conversion during the attempt changes what the trial can establish. The facilitator needs both the subject knowledge and the ability to elicit performance without supplying the answer. C.32.MWA.PP's worked case develops this connection; FPF B.1.5.EW recovers it and B.1.5.RS helps compare a substitute constituent. Preparing the trial remains earlier work, not an activity presumed to continue throughout it.
Learning to recover and change a way of working. If you know the work and want to learn how to explain and change its method, use the Reference's practice with records, first attempts and explained answers (Engineering.Reference:16). You can save an attempt, compare it with the discussion and correct it yourself. Individual feedback requires a qualified helper and agreed time; the text supplies material for self-checking.
FPF.Reference:16.7.4 - Status, evidence, and assurance decisions are preserved
Identification, qualification, selection, trial, and effectiveness are different claims. A candidate account does not become a Method because it is coherent, selected for trial, represented well, supported by a tool, or used in Work. A successful occurrence establishes only the observations and results supported by that occurrence.
A.3.1.CC checks coherence among the claims on which a use relies. A.3.1.FT checks bounded fit or transfer. C.11.MV judges
practical worth against current alternatives. The results can disagree. A Method can be coherent yet poorly fit,
fit one situation yet fail transfer, or produce a useful result whose burden makes another alternative preferable.
FPF.Reference:16.7.5 - What this Method-development family foregrounds and leaves outside
This family foregrounds choosing and recovering the Method-development subject; qualifying candidates and comparing architectures; authoring and comparing descriptions and configuring enactment support; obtaining actual trial evidence and making separate judgments; maintaining variants, introducing Methods into practice and changing cultural continuation; and producing and using connected pattern-language knowledge.
Obtain the specialist Methods, implementation work and authorized decisions needed for a domain task from the relevant discipline or practice. Open a neighbouring DPF when its specialist result is needed and its publication is available.
FPF.Reference:16.7.6 - Why these Method-development questions stay separate
A practitioner often receives a proposed Method as a package: a procedure, a diagram, a tool, a training course and a success story. The costly failure is to change the whole package without knowing which contribution is missing. This family separates the questions because their useful results and grounds differ. A truthful description may still describe an unsuitable Method; a suitable Method may have poor support; a well-supported trial may still leave practical worth unresolved.
The gain is an appropriately bounded answer that the owning practice can use to continue its work. The EC-417 application in FPF.Reference:16.9 illustrates how these questions connect. Direct domain work remains outside until a Method-related question blocks it.
Check the subject, receiving use, relied-on conditions and first useful result before accepting a more ambitious account. If a known direct answer already settles the difficulty, stop there.
The cost is maintaining several answers and their dependencies instead of one undifferentiated success claim. Keep them separate only where a difference changes selection, action or reconsideration. C.39.MF selects the Method-development subject needed for the receiving use; A.3.1.QM, C.32.MWA.PP and B.1.5.CM supply qualification and architecture; A.3.2.DE, C.37.MP and A.15.8.MS supply description and support; A.3.1.WT, A.3.1.CC, A.3.1.FT, C.11.MV, A.3.1.MV, A.3.1.MI and C.36.MC separate evidence, judgments and maintenance. RMP.11 can explain why a professional architecture differentiated without treating that history as a justification of its present worth.
Mathematical modeling can contribute both to comparison and to construction. MMP.21 asks which consequences follow from proposed arrangements: does regrouping preserve the answer, can shared resources meet a deadline, or can an intervening operation invalidate a result? MMP.22 uses a mathematical transformation to construct a changed way of working, then returns its preserved properties and changed demands to the practical comparison. A different notation for the same way of working remains a description change.
The mathematical operations are developed in Mathematical Thinking (MATH), especially MATH.17 and MATH.18. Computational Thinking (CMP), including CMP.14, supplies constructions for interactions among computations. FPF C.29 connects a derived consequence to the work it describes. These contributions let practitioners reuse mathematical behavior while preserving the question about the actual method, its performers and conditions.
FPF.Reference:16.8 - Produce pattern-language knowledge and use it under changing conditions
Source-grounded pattern-language knowledge is useful when recurring Method-development questions need connected answers, or when those answers must be produced and maintained from unlike sources. C.37.CF compares content and form outside this use as well.
For source-grounded production in pattern-language form, use E.4.CM:4.8. C.39 governs Method development outside framework publication; C.39.MC supplies the separate situated-use Method. The H, L and W application follows their connection and a changed source condition in full.
FPF.Reference:16.8.1 - Situation, problem and first gain
A practitioner developing Method knowledge has a handbook, current research, an existing pattern library and a returned account of local practice. They partly agree, but neither chapter boundaries nor a ready-made process tells the practitioner which reusable actions, conditions and unresolved claims should survive. Later, a new fact can change the useful next question or the basis of an earlier answer.
The first gain can be very small: one justified source allocation, one description comparison, a language relation that prevents a wrong continuation, or a localized reconstruction failure. An already sufficient source passage, MethodDescription or prior result is an ordinary exit. A language becomes worthwhile when maintaining these connected answers saves consequential repeated reconstruction.
Several forces remain in tension: source fidelity and a usable synthesis; reusable knowledge and situation-specific judgment; enough preserved context and affordable reading; local repair and hidden cross-pattern dependence. This arrangement keeps serious alternatives visible. A direct description or small synthesis note may be cheaper. A stable source-processing sequence may be appropriate.
FPF.Reference:16.8.2 - Production and situated use are different contributions
The production side engineers source-grounded Method-description knowledge in pattern-language form. A.3.1.DR recovers documentary contributions; F.0.2.MA reconciles and allocates them; E.8.ML architects the useful language; F.0.2.RC challenges promised coverage and localizes refresh. A.3.1.QM and A.3.2.DE supply Method qualification and one-Method description content when needed. C.37.CF is used when an actual revision question requires separating content and form.
The situated-use side, C.39.MC, starts from the result needed now and follows only a contribution whose conditions support that use. A practitioner can use a finished language without performing its production Method. An author can repair one allocation without enacting all other production actions.
This account concerns the connected uses of knowledge. Its material relations include a description relying on an allocated claim, a reconstruction finding returning to that allocation, an alternative description supplying the same receiving use, and a source change invalidating a dependent current-use premise. Those relations matter because they change what may be used or must be reconsidered.
A body may describe one Method, part of a description, or a neighboring evidence or maintenance question. Several bodies can concern the same Method; one source contribution can support several bodies. Use A.3.1.QM, B.1.5.CM and B.1.5 for an actual whole-and-part claim. Smaller Methods can be parts when the whole-forming relations support that account.
FPF.Reference:16.8.3 - Unfolding a use, including a changed situation
A practitioner recognizes the current difficulty, asks which result is missing and tests the conditions for the contribution that could supply it. An available earlier result may already suffice. New observations can change a current judgment, expose another missing result or make the present use stop.
When the needed claim concerns the identity and qualification of a selected structure with potential continuation branching, use A.22.CGUS for its structural and case-judgment semantics. Identify its constituents, relations, constraints and use frame, then judge each continuation from the applicable condition evaluations or obtaining relations. Preserve enabled, disabled, unknown and error outcomes as distinct. A condition evaluated as notSatisfied has a known outcome; it is not an unknown result or an evaluation error.
Changing facts within the same use frame requires a fresh applicable judgement. A change in the question, governing conditions or stop rule can require identifying a different frame. Reconsider the situation as the work progresses. A local dependency or causal relation can constrain the next action and its timing. The account leaves the overall causal path and timetable open.
Situational Method Engineering (SME) already includes intention-sensitive, evolutionary and continuous-composition approaches. The particular choice here is the relation between source-grounded pattern knowledge, independently qualified Method semantics and situated result use.
FPF.Reference:16.8.4 - Practical checks, recurring failures and costs
Recognition and assurance answer different questions. First identify the missing result and a plausible contribution. Then check only the claims on which the actual use relies, with the evidence and independence that their conclusion needs.
For a production result, ask whether the receiving action and stop are recoverable; whether sources and candidate evidence retain their roles; whether each merge, split and omission has a reason; whether the language keeps Method identity separate from body allocation; and whether a changed premise has an identifiable return. When the promised use spans several patterns, challenge the material relations on which that use depends. Broaden a check when the dependency boundary is unknown, not merely because the language is large.
The recurring failures have distinct repairs. A chapter copied as a Method returns to recovery and qualification. A tidy graph that loses a condition returns to description content. A comparison that changes both content and form returns a bundled result, not a form advantage. A coverage table that counts topics returns to reconstruction. A source-access failure stops a required new recheck; it does not retrospectively falsify everything derived from the source.
Source familiarity, preference for a neat architecture and enthusiasm for pattern languages can bias all these judgments. Keep relevant alternatives available, including an adequate direct route when one exists. AI-assisted recovery or comparison retains its model, input and interaction limits when they matter to the claimed result.
The intended benefit is reuse of source decisions and targeted reconsideration when their grounds change. Compare it with the initial reading and continuing maintenance that the language requires. Use a simpler account when maintaining the language does not repay its burden. A claim of improved total effort, correctness or practitioner performance needs evidence under the intended conditions.
FPF.Reference:16.8.5 - Architectural Rationale and source comparison
Situational Method Engineering (SME) contributes situation dependence and deliberate construction of reusable ways of working. This arrangement keeps both premises. It selects one profile in which patterns expose problems, forces, actionable contributions and useful relations, while Method identity and composition remain separately governed. The reuse unit is therefore not indiscriminately a source slice: it can be an independently qualified smaller Method, a description contribution or a neighboring non-Method answer.
This explains the distinct production results. Recovery must remain faithful even when allocation later rejects a proposal. Description comparison must not be replaced by either a cross-use representation profile or a judgment of Method worth. Language architecture must make material relations useful without creating parthood. Reconstruction must be able to find a missing contribution before a contradictory maintained claim and its owner are already known. A.3.1.DR, F.0.2.MA, C.37.CF, E.8.ML and F.0.2.RC keep these differences actionable.
The following sources supply questions and alternatives for comparing this profile:
Alexander et al.'s A Pattern Language (1977) supplies the historical problem-first, connected-guidance idea. Minsky's frame account (1974) connects situation knowledge, expectations and adaptation. The architectural analogy drawn here concerns those knowledge-use roles. Declarative and case-management approaches, including CMMN 1.1, remain operational comparison targets, not the ontology adopted by this language.
The selected arrangement uses Core's general qualification, architecture, representation and assurance Methods. Their shared use does not establish a separate discipline or require another framework. A domain framework would need a different justified field promise. A prose-only synthesis remains a serious lower-maintenance option; a fixed route remains legitimate under stable conditions. Reopen the arrangement choice when current supply removes a distinct result, reconstruction fails for a promised use, source conditions change, or the maintenance burden defeats the practical gain.
FPF.Reference:16.8.6 - Relations and scope of the whole account
The Method-development families described in §16.7 remain directly available, with C.37.CF available for non-pattern description comparisons. C.39.MC supplies situated use; F.0.2.MA, E.8.ML and F.0.2.RC supply the production questions connected in E.4.CM:4.8. The documentary branch of A.3.1.DR supplies both ordinary single-source and plural-source recovery.
Core supplies the governing patterns for Method and episteme identity, whole-forming relations, conceptual synthesis, representations, structures, CGUS, Work, evidence, next-action decisions and framework publication. A new general result returns to its Core owner with its claimed generality and limits explicit; professional or corpus-specific operations remain with their domain owners. Local evidence can inform that return without making the general result normatively dependent on a local profile.
Professional and local profiles may specialize conditions, select use-bounded claims or reuse a contribution. State the relation used. A formal mathematical or structural claim uses its applicable FPF governor. An independently supported direct Method-development result can finish the receiving question.
FPF.Reference:16.9 - Choose the Method-development result needed for release EC-417
The team must release engineering change EC-417, but signed supplier pinout evidence is expected thirteen days after the target software-integration slot. The team calls the difficulty its “release methodology”. That label hides several possible subjects: relations among Methods, test-rig support, evidence currentness, human decision authority, and allocation of supplier and safety Work. Choosing the wrong subject can delay the release, overload the safety engineer, expose confidential geometry to an AI provider, or turn an observed timing association into an unsupported causal claim.
Use this application when a receiving-Work difficulty is described as one methodology problem while several unlike practice objects may be responsible. The practical gain is a supported Method-development result that resolves the present question. Stop when one known capability or support defect, a source-currentness repair or an individual qualification answers the question.
The first move is to name the receiving result and ask which result is needed now. Continue only when an unresolved relation changes the release choice:
EC-417 continues beyond the early returns because evidence timing, Method relations, allocation, support, authority, and recovery burden jointly change the release decision. All identifiers, dates, observations, capacities, and outcomes below are scenario assumptions for this worked decision.
FPF.Reference:16.9.1 - 1. Bound the EC-417 receiving result and recover the subjects of its management accounts
The project must release engineering change EC-417: controller firmware 4.8 together with harness revision H-17. The receiving result is one released controller change whose affected safety requirements, implementation revisions, supplier pinout, verification results, evidence status, and release authority are traceable.
The release is day D0. The target software-integration slot is D-21; signed supplier pinout is expected at D-8; software remains reversible until D-1. An AI provider may propose requirement-to-test links. It has no release authority and cannot receive confidential supplier geometry.
The project, process, and case questions here concern different subjects. Use the claims below before choosing a representation; a U.View claim additionally needs its own positive E.17.0 judgment against an exact viewpoint edition:
These accounts expose connected Method and support questions without sharing one EntityOfConcern. Their correspondence must be recovered wherever the release decision uses it: the signed-evidence date, reusable guard, and claim about the evidence actually used answer different questions. Later, the completed-trial reading in C.37.MP may concern one independently admitted Work; that bounded use does not change the subjects above.
FPF.Reference:16.9.2 - 2. Choose the subject before redesigning it
C.39.MF compares materially different subjects:
The selected Method-relation focus contains identified Methods M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, and M-Release-Authorize, plus candidate accounts C-Evidence-Reconcile-Internal and C-Evidence-Reconcile-Supplier.
Reopen to the test-rig capability/resource decision if two of the next three comparable delays occur while required evidence is complete and the rig is unavailable. That observation changes the subject rather than merely lowering a Method score.
FPF.Reference:16.9.3 - 3. Separate observed differentiation, causal support, and today's decision
The twenty-release window records eight reopened releases. Six of those eight had a late supplier-pinout/integration-bundle mismatch before rig reservation. The rig was available in seven of the eight reopened releases; two rig-outage cases elsewhere in the window completed under the same procedure when backup capacity appeared. Two earlier comparable quarterly-cadence releases reconciled the same versioned input before their safety boards and did not reopen.
DA-EC417-CadenceDifferentiation-1 retains a partial descriptive account of the counts and timing/co-occurrences above. This application does not supply the dated source editions, variant appearances, selection decisions, and diagnostic rival comparison needed to complete the differentiation history. Keep that reconstruction gap; these observations neither complete RMP.11's historical result, choose B2, nor identify a causal effect. RMP.11:5.1 supplies a filled constructed signoff history to show that separate operation.
The receiving causal-use question is CUQ-EC417-CadenceEffect-1: would entering provisional-evidence reconciliation at D-21, rather than waiting for signed evidence at D-8, reduce mismatch-related reopenings in EC-417-like releases for this team, supplier, and change class? CUR-EC417-CadenceEffect-1 records causalUseClaimKind = causalEffectClaim and target rung interventionalActionRung.
Its components are:
evidencePathRefs = [EP-EC417-BundleSequence-20, EP-EC417-RigAvailability-20, EP-EC417-QuarterlyCadence-2];empiricalDataRegimeRefs = [EDR-EC417-NaturalReleaseHistory];- no identification result and no estimate result;
- common threat screen
CTS-EC417-CadenceEffect-1, withcausalUseQuestionRef = CUQ-EC417-CadenceEffect-1.
The threat screen keeps intervention consistency, confounding/exchangeability, overlap, interference, missingness/selection, measurement, and target transport as live threats; temporal ordering alone is clear. routedThreatRefs = []: no specialist result closes a live threat. The C.28 verdict is therefore unsupported.
No positive interventional causal reliance is supported. The observed timing and co-occurrence remain in separate non-causal result DC-EC417-CadenceMismatch-1 as a trial hypothesis and design constraint. Unsupported uses include the claims that cadence mismatch caused the reopenings or that B2 will reduce them. Reopen only when a governed comparison or replayable identification/bound result varies reconciliation timing while rig availability, approver capacity, outcome definition, and evidence access are controlled or explicitly modeled.
Today's architecture decision remains separate. AD-EC417-B2-Trial-1 may consume the non-causal mismatch result, capacity calculation, the covering trace/safety/release assignments, PERM-TraceAcceptReject-17, the two independently supported direct authority relations, and reversibility to choose a bounded trial. It may not consume the unsupported causal-use result as positive evidence.
FPF.Reference:16.9.4 - 4. Recover candidate accounts only when ordinary Method recovery is insufficient
Ordinary A.3.1.MR recovery suffices for M-HW-Verify and M-SW-Integrate. The evidence-reconciliation question enters RMP.10 because oral version judgments and supplier/internal workarounds are absent from the records and the receiving decision needs a stronger account.
The evidence programme keeps its moves distinct:
- occurrence observation and artifacts record overt evidence handling;
- Critical Decision Method probes recover recalled cues, options, judgments, and counterfactual reflections;
- event-log comparison records recurrence and deviation;
- the expert selects the twelve-plus-one sample, claim-to-evidence matrix, contradiction-by-scope rule and held-out discriminator for this bounded inquiry.
Four firmware-only and four internal harness-plus-firmware releases accepted versioned provisional pinout evidence before safety closure. Four supplier-originated releases required signed evidence at closure. Four boards were observed. CDM probes involved two supplier, two software, one hardware, and one safety practitioner.
The thirteenth supplier-originated case is reserved unseen. Before inspection, the internal account predicts that explicit version/uncertainty plus later reconciliation is sufficient; the supplier account predicts that supplier-originated geometry will require the signed-evidence branch; the rig-capacity rival predicts that progress follows rig availability. In the held-out case the team faced supplier-originated geometry, waited for the signed evidence and completed the work. This is consistent with the predicted route. The record also fits a team free to proceed provisionally that chose to wait. To establish that the signature was necessary in this case, recover the applicable closure rule or evidence ruling out the permitted alternatives. The outcome alone does not distinguish the two accounts or establish the effect of rig availability. Transfer to other cases remains open.
C-Evidence-Reconcile-Internal and C-Evidence-Reconcile-Supplier remain scoped candidate Method accounts, with Method identification and transfer still unresolved.
FPF.Reference:16.9.5 - 5. Build the repertoire and criteria without preselecting an architecture
C.39.RP returns an inspectable repertoire for the relation comparison:
The four Methods alone remain in local comparison locator LG-EC417-ReleaseMethods; the three accounts are adjacent repertoire entries with preserved statuses.
The values in the table are pinned for reliance from D-21 through D0. For an identified Method, rely on its current A.3.1 identity result, description edition, evidence window, and only each established relation needed by the use. For a candidate account, rely on its current account edition, named source contents or source window, preserved status and limits, and only already-established relations needed by the use; missing Method identity or a generic input/result relation remains an open limit, not a required field. If a required value is absent or has changed, stop the affected repertoire reliance and reopen the C.39.RP entries that depend on that value.
At D0 this application's reliance window ends; later recovery is outside this case.
For later non-AI recovery, obtain the applicable independent C.39.RP qualification/currentness, readiness, assignment, and permission/authority results. Create a new A.15.2 WorkPlan when coordination needs one. Ground any claimed later dated occurrence independently under A.15.1, whether planned or unplanned.
This application ends with withhold/next-slot. C-EC-Release-v2 stays outside the membership table as a proposed-whole architecture subject; missing family, Method-lineage, account-identity, and AI-transfer bases block only the claims that require them.
C.39.RQ states candidate-neutral contributions and locates every condition with its subject. The case separately names the Systems, performed decision Work and results, covering assignments, and independently obtaining permission or direct decision-authority relations:
The baseline B2 branch relies on one filled A.2.8.PER grant occurrence rather than inferring permission from a charter or register:
The occurrence identity is the tuple SA-GrantTraceAcceptReject-17, beneficiary assignment ref ASG-TraceReview-17, action-specification edition ACT-TraceAcceptReject-EC417-e1, policy edition TraceReviewCharter-17-e1, ClaimScope CS-EC417-AITraceSuggestions, and the D-21..D0 effective interval. A change in any member ends or splits the occurrence.
Only one provider suggestion is used in the filled case: AI-TraceSuggestion-EC417-01. At D-21 10:00..10:20, admitted System TraceReviewer-17 performs W-TraceAcceptReject-17-01 under ASG-TraceReview-17; the Work instantiates ACT-TraceAcceptReject-EC417-e1 within the grant scope and returns RES-TraceAcceptReject-17-01=accept. PEX-TraceAcceptReject-17-01 : PermissionExerciseRelation@Context connects that dated Work to the exact PERM-TraceAcceptReject-17 occurrence, with beneficiarySystemRoleAssignmentRef=ASG-TraceReview-17, exerciseScope=CS-EC417-AITraceSuggestions, and exerciseInterval=D-21 10:00..10:20. EV-PEX-TraceAcceptReject-17-01 is the ledger evidence about this exercise and remains distinct from the exercise relation. Every later used suggestion would require its own dated Work, result, currentness check, and Work-to-grant exercise relation.
Establish assignment, permission or authority, performed Work and decision result on their respective grounds. Capability, responsibility, access, currentness, readiness, and evidence remain separate as well. The AI provider holds none of the human assignments or relations. ASG-TraceReview-17 and PERM-TraceAcceptReject-17 end at D0; continuing safety or release assignments and authority extend neither the trace-review assignment nor the permission grant. For this worked application, after D0 no new AI suggestion is requested, accepted, or used. Every earlier trace-review occurrence and result remains in the evidence history.
Signed-first, provisional-first, supplier-preparation, and safety-preparation variants remain serious possibilities.
FPF.Reference:16.9.6 - 6. Recover package contributions and qualify individual subjects
The incumbent “release methodology” mixes unlike material. A.3.1.DR returns open navigation sections while preserving kinds:
- Methods: the four identified Methods;
- candidate accounts: the two reconciliation accounts,
C-AI-Trace-Review, and proposed wholeC-EC-Release-v2; - descriptions and source claims: stage table, release checklist, supplier procedure, AI prompt, bundle records, and evidence grades;
- Systems/support/access: PLM, CI, test rig, AI provider, and provider-access relation;
- capabilities/assignments: safety competence, supplier-configuration responsibility, and
ASG-TraceReview-17,ASG-SafetyReview-17, andASG-ReleaseDecision-17; - permissions/authority:
PERM-TraceAcceptReject-17,AUTH-SafetyEvidence-17, andAUTH-ReleaseDecision-17, distinct from the assignments, performed Work, and decisions; - inputs/results/premises: pinout schema, evidence bundle, verification result, and confidentiality premise;
- relations: production/use, schema correspondence, provider access, allocation, responsibility, permission, and authority.
These dossier navigation sections supply the relevant material for qualification. Only identified Methods and candidate accounts travel to individual qualification, each with the dependency slice needed to judge it.
A.3.1.QM returns status-preserving individual results:
A.3.1.QM cannot qualify the provider-default AI proposal as currently supplied: neither an identified Method nor a candidate Method account has been provided. Independently, implementing the proposal would expose confidential geometry to the AI provider, and the proposal names no admitted human performer, covering assignment, or permission/authority relation. Those failures would block this use even if a candidate account were supplied.
Local schema correspondence A-17 maps signed or explicitly provisional pinout-version fields to the integration bundle, preserves the edition and uncertainty used, and is supported on five stored bundles for the named editions. Later signed evidence does not erase a provisional basis.
Another project needing only hardware verification can stop with the individual qualification of M-HW-Verify; it does not need a package-recovery or architecture-comparison result. A project whose only useful result is the bounded qualification of C-Checklist-Reconcile can retain that subject as a candidate account with A.3.1 identity still open and stop without calling it a Method. A project investigating supplier reconciliation can likewise stop with the retained supplier account. EC-417 continues because combined evidence timing, allocation, support, authority, and recovery burden change the release decision.
FPF.Reference:16.9.7 - 7. Compare A, B, B2, and R across the structures that change the decision
The alternatives share the receiving result but arrange Work and burden differently:
For this constructed comparison, 2.07 h is safety-engineer time for traceability and safety-closure work: checking the current requirement–implementation–verification correspondences and preparing or recording the closure disposition. It excludes the separately counted signed-delta preparation and 0.33 h board, and any additional affected verification or integration rework.
The provisional board occurs on D-21; the signed-evidence board occurs on D-8. Both last 20 minutes (shown as 0.33 h in the calculations) and therefore remain under the separate 45-minute limit. They do not occur on the same day. Per-release safety effort is 4.73 h for B and 3.13 h for B2 after the separate D-21 board is included. The selected D-8 peak-day result and per-release totals answer different burden questions.
FPF.Reference:16.9.7.1 - Signed-delta preparation for B2
Under B2, the supplier-configuration practitioner prepares the comparison of the signed supplier pinout received for closure with the exact provisional pinout edition used in D-21 integration. Retain both edition identifiers and the provisional uncertainty and use history; identify the changes, and use schema correspondence A-17 to locate the affected integration-bundle fields. SafetyReviewer-17 checks that comparison and identifies the affected traceability and verification checks for the safety board. The preparation result is a version-linked pinout-difference record with the affected checks. The assumed preparation burden remains 1.60 h supplier plus 0.40 h safety; performing affected verification, deciding safety closure, and any integration rework remain separate. Missing signed evidence invokes R as described in section 8.
C.32.MWA.PP keeps several structures distinct:
- Method relations: the four identified Methods are co-used; every composition/order relation for
C-EC-Release-v2remains proposed; - Work relations: A is signed-first; B/B2 are provisional-first then signed reconciliation; each B2 branch that uses AI suggestions contains bounded human Work set
W-TraceAcceptReject-17with one accept/reject occurrence per used suggestion; R can occur only after B2 entry, retains already-performed Work, and repeats that trace-review Work for every repeated AI suggestion; - allocation: B overloads the safety engineer, while B2 transfers
1.60 hand stays within the peak bound; admitted SystemsTraceReviewer-17,SafetyReviewer-17, andReleaseDecider-17, their three covering assignments, trace permissionPERM-TraceAcceptReject-17, and the two direct authority relations remain separate; - subject/support/permission/authority: the three decision Systems and their Work remain distinct from their assignments, the trace permission, and the two direct authority relations; supplier configuration, PLM, test rig, and AI provider retain separate responsibility/access/support relations;
- description correspondence: checklist order corresponds only partially to Work overlap and branch stops;
- cultural relation: retention of a weekly-integration practice remains a later cultural-continuation question.
AD-EC417-B2-Trial-1 selects only a prospective three-release B2 trial under ASG-TraceReview-17, ASG-SafetyReview-17, ASG-ReleaseDecision-17, PERM-TraceAcceptReject-17, AUTH-SafetyEvidence-17, AUTH-ReleaseDecision-17, capacity, confidentiality, evidence, and reversibility conditions. It consumes DC-EC417-CadenceMismatch-1 as a non-causal rationale and treats the causal-use verdict as unsupported. A remains a pre-entry alternative. R is a post-entry recovery and can never become a retrospective A occurrence.
FPF.Reference:16.9.8 - 8. Return a proposed-whole account and a bounded trial
B.1.5.CM receives C-EC-Release-v2 with:
- intended result: a traceable safety-relevant release under named evidence and authority conditions;
- reusable invariant: reconcile the exact provisional or signed evidence edition with the integration bundle before safety closure;
- participants and contributions: the four identified Methods, two reconciliation accounts, the three admitted decision Systems, their decision Work/results and covering assignments, and separately governed support/capability/permission/authority subjects;
- inputs/results: pinout/evidence state, implementation revision, verification result, signed approval or stop, and release authorization;
- variation: signed-first A or bounded provisional-first B2 before entry; post-entry recovery R;
- bounds: confidentiality, human AI-suggestion decision, evidence edition/uncertainty/history, signed-before-closure reliance, peak burden, board duration, rollback, covering assignments, and named permission/authority relations;
- reidentification rule: the account changes when its receiving result, invariant, participant contribution, evidence branch, or authority/stop rule changes materially.
The four participant Methods are identified, but the proposed whole is not. The result is therefore a prospective candidate Method account, proposed relation sets, guards, adapters, fallbacks, stops, variation points, and a trial WorkPlan.
At D-21, ReleaseDecider-17 performs W-ReleaseDecision-17 under ASG-ReleaseDecision-17 and AUTH-ReleaseDecision-17, after SafetyReviewer-17 performs the needed evidence decision under ASG-SafetyReview-17 and AUTH-SafetyEvidence-17. B2 entry also requires TraceReviewer-17 to perform accept/reject Work under ASG-TraceReview-17 and the current PERM-TraceAcceptReject-17 for every AI suggestion actually used by the branch. The filled baseline is W-TraceAcceptReject-17-01 and PEX-TraceAcceptReject-17-01 from section 5; any additional used suggestion would require a distinct dated Work, result, currentness check, and exercise relation.
The decision chooses A before integration if signed evidence is already available or if versioned provisional evidence, supplier preparation, confidentiality, the trace-review assignment or permission, or a safety/release assignment or authority condition for B2 is absent. Under the baseline D-8 assumption and with every B2 entry condition satisfied, it may authorize only three B2 releases.
Each B2 occurrence must keep confidential geometry outside the provider, record TraceReviewer-17 accept/reject for every AI suggestion under ASG-TraceReview-17 and PERM-TraceAcceptReject-17, hold its boards on the named days, stay at or below 3.20 h peak safety effort, obtain signed evidence before closure, and reach the target slot or record why it did not. A confidentiality, assignment, permission, or authority breach stops B2 immediately.
If signed evidence is missing at D-8, withhold release and enter R. R preserves the performed integration record, provisional edition, uncertainty, and earlier decision use. If signed evidence arrives by D0 while the existing evidence and reversibility guards still hold, the team records its relation and delta to provisional, re-baselines the bundle, repeats the comparison and affected verification, and records whether early integration was retained, rolled back, or repeated.
If closure is still unresolved at D0, ReleaseDecider-17 returns withhold/next-slot and this application's R occurrence ends as a failed B2 trial. All AI-supported continuation stops at D0. Any later non-AI recovery is outside this application and follows the future-recovery boundary in section 5.
These boundaries do not rewrite any earlier Work or evidence basis. Signed evidence supersedes provisional only for safety-closure reliance. For the constructed series of at most three B2 trials, count one failed trial when that release has a capacity or mismatch failure or enters R. Count that trial only once even if several categories or events occur; retain all categories as reasons for analysis. Entering R counts once for its trial even if recovery later succeeds.
After two distinct failed trials, ReleaseDecider-17, within the applicable AUTH-ReleaseDecision-17 scope, returns B2 for revision or rejects further B2 use. The required safety-evidence accept/reject remains a separate SafetyReviewer-17 result under AUTH-SafetyEvidence-17; revising the candidate account is separate work, not an authority granted by this release decision. The existing decision covers at most three trials regardless of the failure count: any further release requires a new applicable decision. The immediate confidentiality, assignment, permission, and authority stops above do not wait for two failures.
FPF.Reference:16.9.9 - 9. Configure and test the enactment-support arrangement before claiming that a Method Base works
Use A.15.8.MS to test support for the three named user tasks. The bounded support use USE-EC417-B2-Support-1 asks whether TraceReviewer-17, SafetyReviewer-17, and ReleaseDecider-17 can use the B2 material for WP-EC417-B2-Trial-1 under the existing confidentiality, evidence, assignment, permission, authority, reversibility, and D0 conditions.
FPF.Reference:16.9.9.1 - 9.1 Fix the same three task rows before comparing support configurations
Published files and manual lookup are candidate configurations with no performed task evidence for these three rows, so those configurations remain untested rather than failed. Adding an interaction with SYS-EC417-AIProvider-1 and feedback Work or a feedback receiving relation also remains untested: no mandatory row needs either.
The bounded PLM/CI candidate configuration is the only one with one observation for every current row. The described observations support retrieval, branch selection and the tested tailoring actions; the missing tailoring definition and permission/authority-stop observation prevent a pass for the full tailoring row or complete task set.
FPF.Reference:16.9.9.2 - 9.2 Admit the two entry epistemes to the Method Base
MBC-EC417-B2-1 is the project Method Base entry collection for this support purpose and window. It keeps its project namespace, current entry-disposition rule, and continuity condition. The two candidate entries are separate C.2.1 epistemes:
ECA-EC417-C-Release-v2-1states the explicit candidate status and current account ofC-EC-Release-v2;ERP-EC417-WP-B2-1is about WorkPlanWP-EC417-B2-Trial-1, not about performed release Work.
Entry membership is an instituted relation, not a folder listing. SYS-EC417-MB-PermissionGrantor-1, its obtaining grantor assignment RA-EC417-MB-PermissionGrantor-1, and admitted permission-granting SpeechAct SA-EC417-MB-PermissionGrant-1 ground exact permission PERM-MBENTRY-EC417-1 for curator assignment RA-EC417-MB-Curator-1, action specification PAS-EC417-MB-AdmitRemove-1, scope SCOPE-EC417-MB-Entries-1, and the D-21 through D0 window. AG-EC417-MB-Curator-1 and the obtaining curator assignment supply the A.13 performer core.
MECH-EC417-MB-EntryDisposition-1 declares reusable operation settleEntryDisposition(entry, collection, admissionWork) -> entryDisposition. Its closed local value kind contains exactly MBEDV-EC417-Admit, MBEDV-EC417-Remove, and MBEDV-EC417-Stop. A completed application requires the curator to identify the entry episteme, the collection, the entry-disposition rule, and the admission question; check kind and status, provenance, purpose fit, applicability, return condition, and current membership; and then perform one observable branch-closing act. Without that act there is inspection Work but no completed application or result binding.
At D-21 10:00–10:08, admitted Work W-MBA-EC417-ECA-1 applies the operation to the candidate-account episteme. At 10:10–10:18, admitted Work W-MBA-EC417-ERP-1 applies it to the WorkPlan episteme. Each Work has its own performance history, extent, WorkContainedInEC417MethodEngineering occurrence, A.13 core, A.15.1 admission, post-admission assignment attribution, and PERM-MBENTRY-EC417-1 exercise. Applications APPL-MBENTRY-EC417-ECA-1 and APPL-MBENTRY-EC417-ERP-1 end only at their pair-specific positive approval acts; terminal bindings RB-MBENTRY-EC417-ECA-ADMIT-1 and RB-MBENTRY-EC417-ERP-ADMIT-1 carry exact value MBEDV-EC417-Admit.
Those facts institute MBB-EC417-ECA-1 and MBB-EC417-ERP-1 as the two MethodBaseEntryBelongsTo@Project episodes. Each episode is identified by its exact entry, collection, and maximal continuous interval. A repeated positive result during an open episode creates no second membership; removal requires its own permitted negative application and result. No such removal obtains through D0.
FPF.Reference:16.9.9.3 - 9.3 Test actual use and keep the structure claim separate
The collection makes the two epistemes eligible for the support use. Three separately admitted Work occurrences supply the following observations; the tailoring row's mandatory permission/authority stop remains untested:
Each SupportSystemUsedInWork@EC417 occurrence requires the independently admitted Work, one exact admitted System, an actual input/output interaction, and use of the returned value in that task. Each Work keeps its own enacted support-use Method, performer core, containing-System relation, assignment, and post-admission attribution.
RES-MESUP-EC417-B2-1 returns task-pass for retrieval and branch selection, retains the observed tailoring fixture, signed-before-closure and stale-edition results, and returns missing-task-set[tailoring-input-action-result] plus the separate missing-task-test[tailoring-permission-authority-stop] for the full tailoring task. The branch-selection stop cannot supply an observation of another user's tailoring action. A later failed task would need its own repair and rerun Work, with the earlier histories preserved.
PSO-EC417-B2-Use-1 remains a proposed organization whose four A.22 candidate groups stay separate: identified constituents; the two membership episodes and three direct PLM/CI-use occurrences; current-edition, status, confidentiality, signed-evidence, assignment, permission, authority, reversibility, and D0 constraints; and the named support-use frame. This support account makes no selected-U.Structure claim. If a named receiving use requires one, establish the four actual A.22 values for that use from the case facts. ESA-EC417-B2-1 returns missing-selection-basis only when a value or judgement required for that use remains unresolved.
A claim of dated selection Work separately needs its selecting System, enacted Method, independently admitted Work and any claimed participation or operation binding. The observed task results and separate missing tailoring test retain their own grounds.
Keep the membership episodes and their assertion or evidence epistemes distinct from the optional construction account MBCA-EC417-B2-1, edition episteme MBE-EC417-B2-1, publication occurrence PUB-MBE-EC417-B2-1, named-use reliance episteme, proposed organization and any required selection-basis result. The bounded usability claims rest on their task observations.
FPF.Reference:16.9.9.4 - 9.4 Stop separately at the remaining Method-development questions
FPF.Reference:16.9.9.4.1 - 9.4.1 Preparation now, reopening after performed trials
Invoke C.37.MP only for Method representation profile MRP-EC417-B2-Review-1, because two unlike actions must be related without becoming one view. Both return to candidate C-EC-Release-v2 and current candidate-account episteme ECA-EC417-C-Release-v2-1.
Preparation now. C.37 claim group C37-EC417-B2-Prepare-1 has receiver SafetyReviewer-17 and action ‘check the supplier-prepared signed-versus-provisional pinout comparison and identify the affected safety checks before release’, using the instruction in section 7. Episteme ERP-EC417-WP-B2-1 supplies the proposed allocation and order, evidence entry, confidentiality, recovery and stops, with WorkPlan status preserved. A.2.4 classifies that preparation use, and A.10 path P-APP-EC417-Prepare-1 returns pass in its current-edition window. Select these qualified planning premises for the preparation operation. Apply §16.9.7.1 to the signed and provisional editions and schema correspondence A-17 to obtain the version-linked pinout-difference record and affected checks. That preparation remains to be performed: the WorkPlan supplies its premises, while the comparison produces its result. Missing required comparison material, capability, support, permission or authority stops the dependent preparation action under §16.9.5.
C.32.MWA.PP decision AD-EC417-B2-Trial-1 separately governs the trial alternative: its predicate compares A, B and B2 against the receiving, capacity, confidentiality, assignment, permission, authority, evidence and reversibility conditions; its actual outcome selects no more than three prospective B2 trials under those conditions.
Reopening after performed trials. C.37 claim group C37-EC417-B2-Reopen-1 has receiver MethodEngineer-17 and later action ‘decide which findings from performed trial Work reopen the candidate’. The three-release statement remains WorkPlan WP-EC417-B2-Trial-1: no corresponding release Work has yet been admitted, and no candidate-episteme/viewpoint-edition pair has been tested under E.17.0. The claim group remains unresolved on those missing Work and conformance grounds. When they obtain, use the qualified trial findings to decide what to reopen under the conditions in §16.9.8; obtain the reopening result in that operation. A.2.4 classification or an A.10 path supplies neither the trial Work nor the required conformance result.
The relation between the uses. The profile connects the shared evidence-entry, confidentiality, recovery and stop conditions. It retains the preparation use of qualified WorkPlan premises, its still-unperformed comparison and the resulting record to be obtained, alongside the reopening use blocked by missing trial Work and conformance. Each action keeps its own candidate claims, conditions and result.
FPF.Reference:16.9.10 - 10. Apply sensitivity without rewriting past Work
If signed supplier pinout is available at D-21, the prospective choice reverses to A before integration. A then reaches the target slot with one final board and avoids the provisional board, later signed-delta preparation, and post-entry recovery exposure. B2 remains only if another named conflict justifies its extra branch.
The changed input affects the prospective decision. If B2 or recovery Work has already occurred, preserve what was performed, its conditions and the evidence used at the time.
FPF.Reference:16.9.11 - Result and stop
The application returns:
- one selected Method-relation focus and a named non-Method reopen observation;
- an inspectable status-preserving repertoire and situated criteria set;
- a kind-preserving package dossier and individual qualifications;
- two scoped candidate reconciliation accounts with held-out limits;
- partial descriptive differentiation account
DA-EC417-CadenceDifferentiation-1, with its reconstruction gap retained; unsupportedcausal-use resultCUR-EC417-CadenceEffect-1and separate non-causalDC-EC417-CadenceMismatch-1;- architecture decision
AD-EC417-B2-Trial-1, with A pre-entry, B rejected on peak demand, B2 selected only for bounded trial, and R post-entry; - proposed-whole account
C-EC-Release-v2and its trial WorkPlan, with no obtaining composition claim; - two instituted Method Base entry-membership episodes for the candidate-account and WorkPlan epistemes, with collection, edition, publication, construction-account, evidence, and reliance results kept separate;
- bounded support result
RES-MESUP-EC417-B2-1as specified in section 9.3: passes for retrieval and branch selection, the observed tailoring fixture, signed-before-closure and stale-edition results, and the separate missing tailoring definition and untested permission/authority stop; - the proposed support organization and unestablished AI-provider-use, feedback and holder-capability claims; a requested selected-Structure use returns
ESA-EC417-B2-1=missing-selection-basisonly when its required A.22 basis remains unresolved; and - the separate Method-development results and stops listed in section 9.4.
Stop before release when signed evidence, verification, confidentiality, capability/support, named human authority, peak capacity, board duration, or rollback conditions fail. At D0, if R has not closed successfully, issue withhold/next-slot, close this application's R occurrence, and stop all AI-supported continuation. Preserve all earlier Work and evidence history. For later non-AI recovery, apply the section 5 boundary.
Stop only the enactment-support task or claim whose mandatory criterion fails or whose required task result, membership, capability, provider, feedback or selection basis is missing. Retrieval and branch selection retain their passes, and the observed tailoring fixture, signed-before-closure and stale-edition results remain. The missing tailoring definition and untested permission/authority stop prevent a complete task-set pass; unused AI/feedback features and the unselected A.22 proposal do not cancel the supported observations. Stop Method development at an earlier sufficient result when no whole question remains. Reopen the affected results and dependent uses when their subject or grounds for reliance change.
FPF.Reference:16.10 - Control as a connected transdisciplinary construction
The control construction connects what can be known about a present situation, what can influence it, which continuation is suitable, how that continuation can occur and what a later result changes. The subject may be a technical system, a person, an organization or another system. Control can also organize changes to the knowledge, Methods and capabilities used in later work.
C.43 explains the connected reasoning as a separately usable Method. Its control mantra holds the dependencies together: assess the situation; construct possible continuations; compare and choose; realize the influence; examine its consequences; revise the affected basis. This is a logical unfolding for learning and attention. Actual work proceeds where the required information and means are available, with returns and simultaneous constraints under A.22.CGUS. A result may be a justified continuation, a sufficient explanation of an observed arrangement, or a specific unresolved connection requiring further work.
FPF.Reference:16.10.1 - Why the related Methods retain their own results
These are relations of use among independently useful Methods, with composition where the receiving operation requires it. A contribution comparison can serve an experiment, operational action, architecture design or development direction. A local choice can select a whole conditional policy. Development can change the alternatives, criteria and means that a later local choice temporarily holds fixed.
Advice can contribute to control by changing what a recipient investigates, chooses or performs. Following it also uses means and can alter the actions that remain available. The common basis for connecting C.11.DUA with control is this whole continuation. Use compatible accounts of the receiving result, present configuration, affected participants, horizon and feasible means when joining the contributions. DUA can begin before a local option set is ready, by recovering the work hidden in the advice. C.43 then connects the warranted proposal to the actual observation, choice, realization and revision relations. A sufficient present answer or a justified stop can finish the receiving question.
The connection changes the organization of control. Frequent inexpensive reasoning can support occasional advice; presenting that advice, committing to change and carrying it out can have different useful occasions and burdens. C.43:4.3–4.5 explains how to construct those continuations and their timing. Section 4.8 applies the same relation to development of capabilities and Methods, including changes to the way development is recommended and directed. An explanatory gain or a new possibility is appraised at its receiving horizon, even before it supports an operational intervention.
When a person directs an AI agent, an instruction naming a Method can bring it into consideration. A.15.11 supplies that encounter when needed; the subsequent work must establish whether the agent can obtain and apply the operation and whether its use improves the receiving result. Recover the failed connection before choosing the repair. Recognition, execution and benefit remain distinct questions when choosing between a clearer instruction, better support and a changed Method.
Use C.11 for a local choice. Ongoing control may require connecting such choices to observation, realization and revision through C.43. Use C.32.LCA when the control arrangement itself needs redesign. The common construction keeps specialist results and their different assumptions available for the subject at hand.
FPF.Reference:16.10.2 - Common relations and different mechanisms
The common account first recovers what the arrangement does. Open-loop execution within an interval, distributed decisions, a combined physical bearer of several functions and an unsuitable feedback rule can all be described. The distinction between controller and controlled concerns their participation in particular relations; it need not partition the whole into two permanently separate devices. An explanation in terms of internal parts must satisfy A.12's parthood conditions. Controlled self-change additionally connects the intervention to how future action is changed and revised.
Description, explanation and design therefore have different conclusions. A zero coupling can be a justified degenerate case of a model; an unknown relation cannot be filled with zero. A model can explain feedback that increases an unwanted deviation without making that rule desirable. C.43:5.5 demonstrates this distinction and its change when observations are delayed. Different dynamics can require a different subject model while retaining the common control relations.
Technical control can add state-transition equations, admissible inputs, estimation bounds, stability or joint feasibility. Economics can add opportunity cost, preferences, prices, incentives and finite or marginal measures. Biological inquiry can test hypotheses about regulated variables and mechanisms without attributing an explicit optimizer to the organism. C.43:4.7 explains these correspondences; C.11.CRC:4.2 preserves the mathematical and economic meanings of marginal comparison.
For example, a laboratory initially seeks independent capability to handle a new sample family. Its current work relies on external judgement. The connected developmental question includes what the staff and their tools can learn, what working Method must change and what help must remain. If the agreed result changes to reliable delivery with an available qualified service, the previous training programme loses that justification. The required capability and acceptable dependence have changed. A grounded recommender revises its advice from that new configuration. Further development can form a different attainable problem from this changed result. C.43:4.8 and C.40 retain these connections.
The same control relationship can be expressed in the language of operations management, technical regulation or another field. C.43:4.1.4 recovers the actual claim while preserving established discipline names and the organizational or physical relations that make it work. E.10:9.8 makes that recovery findable from the ambiguous wording.
C.43:4.5.1 constructs the needed temporal coordination. It distinguishes recurring contributions from separately timed actions, relates their preparation and recovery, preserves useful timing references and repairs the lost relationship. C.27.TA supplies the temporal-claim discipline; it does not by itself construct that coordination. The control mantra retains the connected questions without imposing a common execution clock.
FPF.Reference:16.10.3 - Grounds and limits of the synthesis
This construction combines existing Core Methods with subject contributions whose scope remains explicit. Matni, Ames and Doyle (2024) provide technical constructions for joining control layers and distributed contributions; their guarantees depend on the specified models. Brooks, Frankel and Kamenica (2024) show why information comparison depends on the receiving decision and joint information. Nuijten and de Vries (2026) distinguish incentives to obtain information from the ability to condition future actions on it in a controlled computational comparison. C.32.LCA:11 explains the incorporation and limits of Matni, Ames and Doyle. C.43:11 states how its information, decision and development sources change the Method and where their results stop.
The architectural decision is to share the explained relations whose use survives the change of subject, while retaining the constructions and assumptions that determine performance in each subject practice. A counterexample requiring different information, actuation, purpose formation or developmental connections can reopen this common account. A missing field-specific construction calls for a developed subject contribution, potentially a separate pattern language, rather than a more abstract name for the missing work.
FPF.Reference:17 - Transdisciplinarity As A Meta-Theory Of Thinking
People from different disciplines may use the same word for different objects in their work, or different words for the same object. They may also rely on different forms of proof, measures of quality and grounds for action.
In FPF, transdisciplinary reasoning supplies distinctions and methods that a practitioner can use inside different disciplines. One discipline can use them on its own. Ontology can examine the types a field uses, logic the warrants for its inferences, and methodology the ways it obtains results and divides the work. These inquiries may draw on one another. A teaching sequence for them alone establishes neither a hierarchy of types nor a part–whole relation. Ask what the discipline needs to distinguish, which conclusion the distinction warrants and what operation would obtain the required result. The discipline supplies the evidence, techniques and criteria appropriate to its subject.
For instance, distinguish a reusable procedure, a performance and what that performance establishes. In metrology this can lead to a decision about the measurement of a particular instrument. In mathematics it can lead to a decision about the validity of an inference in a particular calculus. The distinction guides both inquiries. The rules that justify a measurement and a proof come from their respective disciplines.
Interdisciplinary work connects contributions from different disciplines to obtain a joint result. Identify what each discipline supplies, how another can use it and which conditions of interpretation or acceptance matter at that connection. A group can use transdisciplinary reasoning to achieve this integration. C.20 explains what makes knowledge and reproducible practice a discipline. C.39.WA:4.3 and F.0.2:4.6 explain how to carry a distinction into a method and how to test a change of scope. In systems engineering, the 2019 INCOSE Fellows report discusses both aspects of the work. Systems Engineering and System Definitions, pp. 5–6
Establish a term’s meaning in its source context before using it elsewhere. A term sheet can align senses while retaining their local differences. A bridge can say how meanings correspond, where they lose structure and what cannot be transferred. A comparison states the criteria and grounds needed for its claim. A mathematical lens can reveal shared structure while stating what it preserves and what it loses.
FPF.Reference:18 - The Culinary Architecture Of Collective Thought
FPF combines familiar ideas about evidence, roles and comparison into a shared account of how reasoning can be organized. A kitchen analogy helps explain the contribution.
A documented procedure is like a recipe for obtaining a particular result. A skilled practitioner may also perform the task using tacit knowledge.
FPF's architectural guidance concerns how such contributions work together. In the analogy, this is the arrangement of stations, instruments, roles, timing and checks that lets people prepare different dishes. In reasoning, it is the relations that make different Methods and results usable together.
In FPF terms:
- system-role kinds distinguish recurring work-facing contributions, while system-role assignments identify which systems are assigned to them;
- Methods and MethodDescriptions distinguish a reusable way of doing from a claim-bearing account of it;
- Work patterns distinguish performed Work from plans;
- evidence and assurance guidance helps make a claim’s grounds and reliance limits inspectable;
- characteristic spaces organize the dimensions of assessment; criteria and scales determine how the object can be compared;
- architecture patterns keep structure distinct from diagrams;
- naming and term sheets expose the meanings being compared across contexts;
- state-of-the-art comparisons and option portfolios make alternatives available for selection and later revision;
- improvement loops connect results to reconsideration of the Methods and arrangements that produced them.
Compare the effort of making these connections explicit with its contribution to inspecting, reusing or revising the reasoning. For a familiar problem that one practitioner can answer adequately, a direct answer may suffice.
FPF.Reference:19 - The Intellect Stack As A Pedagogical Map
The phrase "Intellect Stack" names a learning map of capabilities. In this specification it is pedagogy, not a prescribed sequence or a new ontology.
The map helps a learner identify the different capabilities needed for a reasoning task.
Use the map to distinguish a missing input from a capability that must be developed. An architecture inquiry may expose missing evidence; a naming question may reveal that the object of concern has not been identified; mathematical modeling may require characteristics for a comparison. Each gap calls for its own response and does not by itself establish a capability deficit.
FPF.Reference:20 - Purpose, Scope, And Non-Goals
FPF aims to help people and AI agents develop reasoning whose object of concern, grounds and conditions remain recoverable when it is used, shared or revised.
The Core Specification defines conceptual patterns, distinctions, publication forms, and checks. It is tool-agnostic; projects choose the tooling and organizational arrangements needed for their work.
Use the domain knowledge and evidence needed for the task, including applicable mathematical results and standards. FPF helps make their contributions to reasoning inspectable and comparable across contexts; practical judgment remains with the responsible practitioner.
Use FPF as guidance for the current question and finish with a sufficient direct answer when one is available. Evidence and accountable decisions retain their own requirements.
FPF.Reference:21 - How To Continue After The readme
Use the Readme to decide whether FPF can help a working project. Read this architectural reference for the ideas that connect the first practical entries. Use the Table of Contents when you need to find a pattern family suited to the working question. Within that family, choose a pattern whose Problem frame and Solution address your question. Start with the action or judgement the pattern guides.
You can also read the specification in order when studying it is the goal.
For a consequential project statement, identify its subject and claim, the grounds and limits of reliance, and the guidance needed next. Identify a MethodDescription, admitted Method, predicate or ClaimGraph when the distinction changes the truth of the claim, the action, the stopping condition or a named use that relies on it.
FPF.Reference:End
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)