#Consequence-Guided Ontological Problem Solving

A.7.1 · Stable · Architectural (A) · Normative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Architectural (A) Status: Stable Normativity: Normative

Use this pattern when a clear or apparently clear engineering claim produces the wrong action, identity, dependence, obtaining, responsibility, or projection consequence, and a typed or constructive distinction may repair it. One grounded counterexample or one direct-owner invariant can trigger the work; you do not need two polished alternative ontologies before starting.

#Keywords

• wrong engineering consequence
• smallest defeated claim
• exact subject and direct owner
• one selected analysis apparatus
• actual system performing under an assignment
• bounded unresolved result.

#Relations

#Content

#Use this when

Use this pattern when a clear or apparently clear engineering claim produces the wrong action, identity, dependence, obtaining, responsibility, or projection consequence, and a typed or constructive distinction may repair it. One grounded counterexample or one direct-owner invariant can trigger the work; you do not need two polished alternative ontologies before starting.

The first useful move is to state the affected engineering result and the smallest defeated or disputed claim, then enter the first diagnostic locus that can change that result. Stop as soon as an admitted working account determines the next move truthfully.

Not this pattern when. If the blocker is missing observation or evidence, return to the domain or evidence owner. If wording alone hides the distinction, use C.2.P or E.10. If the problem is a material premise conflict between FPF methods, use A.7.2. If a missing distinction must become durable FPF ontology, exit to E.24/E.24.UK, A.8, and A.11 rather than admitting it here.

The primary reader is a domain engineer or ontology analyst responsible for the affected use. This pattern is a U.MethodDescription; a named admitted U.System under the current engineering or analysis role assignment performs the dated ontology-analysis U.Work. The reader, performer, method episteme, work, and returned engineering result remain separate.

#Problem frame

A maintenance sentence can be lexically clear and still merge two relation occurrences across removal and reinstallation. A responsibility claim can name the right role word while ignoring whether an assignment relation ever began. A graph or logical type can look exact while omitting the construction that changes the action. In these situations, a glossary is too little and an exhaustive ontology exercise is too much.

The governed concern is the smallest ontology-analysis application that changes one declared engineering use, result, or guarantee. The ordinary product is a repaired statement, method choice, action, direct-owner return, or explicit blocker—not an ontology artifact by default.

#Problem

Ontology work often starts from available vocabulary rather than a failed consequence. That encourages blanket constructive replay, premature kind admission, and durable records even when direct kinds and relations already decide the next action. The opposite failure treats clear words as sufficient and leaves a category error inside work, evidence, role, state, capability, relation, or representation claims.

The practical question is not “How much ontology can we recover?” It is “Which distinction changes the engineering move at the required guarantee, and what is the cheapest truthful return?”

#Forces

#Solution

#Inherit the complete application contract

This A.7.1 description narrows the method claims stated by C.19.2 for consequence-guided ontology analysis. When applying A.7.1, retain the declared use, problem-facing result, claimed guarantee, horizon, useful threshold, separation among method, reader, performer, Work, and result, positive stop, and reopen rule. This is description-level claim reuse; it adds no relation occurrence between the described Methods.

The normal short path uses the already selected A.7.1 analysis method as its one current apparatus. It begins from one exact engineering subject and that subject's current direct owner; subject and owner are inputs and constraints, not apparatus candidates. Use C.18 only when the team must generate or reframe alternative analysis methods, models, formalisms, or other direct-kind apparatuses for the same declared use. Use C.11 only when two or more already-available apparatuses are eligible for that same use and guarantee, making a real local-choice question current. After selection, A.15.2 owns planning and A.15.1 owns dated work; C.24 enters only for tool-call enactment planning.

#Start from the defeated consequence

Name five things in ordinary domain language:

1. the affected engineering result and its required guarantee;
2. the smallest claim whose current reading fails or is disputed;
3. the observed consequence failure, direct-owner invariant, or grounded counterexample;
4. at least one candidate correction or a request to recover one; and
5. the action that must remain blocked until the distinction is settled.

One defeated reading is enough. Recovering or constructing an alternative can be part of the work.

#Enter one of four diagnostic loci

The four loci are a named diagnostic set; they are not a mandatory sequence.

1. Domain inquiry. Ask whether the relevant behaviors, interventions, evidence, and consequences are known. If not, return domain, measurement, or evidence work without ontology invention.
2. Wording use. Ask whether one term or sentence obscures distinct claims. Use C.2.P or E.10 only when wording precision is the live blocker.
3. Working typed account. Test whether direct kinds, participant positions, relation direction, temporal qualification, evidence relation, and occurrence identity suffice for the use. Reuse the relation, role, state, capability, method, work, and evidence owners already in FPF.
4. Subject-specific constructive ground. Return to the exact subject construction only when action, identity, dependence, obtaining, constitution, or decision-changing CT2R loss differs across constructions. Use the direct relation-occurrence, role-assignment, holon-recognition, work-occurrence, state/capability, or structural-construction owner. Do not default to C.13 or a generic constructive calculus.

#Perform only consequence-changing ontology work

1. Select the first locus capable of resolving the delta.
2. Have the admitted system perform the required domain, wording, typing, evidence, or construction work.
3. Use exact A.7.CP claim IDs through ClaimUsedAsReasoningBasisRelation@Context only when those claims are load-bearing in the work. Do not traverse the compact by default.
4. Preserve direct evidence, currentness, source-use, kind-admission, and subject-construction owners.
5. Return the repaired result immediately when the next action is truthful at the declared guarantee.

The method result uses one of these closed local dispositions in its result episteme: repairedEngineeringStatement, methodChoice, actionSelected, noOntologyIntervention, returnToDirectOwner, or unresolvedWithBlocker. These are method-result dispositions, not new U-kinds. Each names the affected use, practical result or blocked claim, and stop/reopen condition.

#Decide whether the working account is enough

A working account is sufficient when admitted direct kinds and relations determine the next move and plausible constructional alternatives do not change the result or guarantee. Stop without declaring the alternatives false. Do not create an occurrence ledger, evidence apparatus, publication package, or ontology record whose distinctions cannot change the use.

Create a durable ontology result only when reuse, dispute, high consequence, automation, or cross-pattern change makes persistence valuable. If the work exposes a missing distinction that must persist, send the candidate to its admission owner and return after admission.

#Reopen and teach without premature structure admission

Reopen on a consequential counterexample, changed guarantee, failed use, projection loss, changed occurrence identity, or a newly admitted direct-owner distinction. Reopen only the affected engineering and ontology decisions.

A short domain/wording/typed-account/constructive-ground presentation may be kept as a ProvisionalUnfoldingDemonstrationDescription@Context. It is a teaching episteme, not an admitted CGUS, method, plan, work occurrence, or result. A reusable structure requires the full A.22.CGUS admission coordinates.

#Archetypal Grounding

Support occurrence repair. A maintenance claim says bearing B1 continued supporting shaft S1 after removal and reinstallation. The direct relation identity rule defeats that reading before a second ontology is written. The A.7.1 analysis method is already selected, while the current support-relation owner constrains the disputed claim; neither the bearing/shaft subject nor that owner is an apparatus candidate, so the work creates no option set. Ontology-analysis work uses A7CP-01 and A7CP-10, recovers two support occurrences, repairs the warranty and incident-attribution claim, and returns it to maintenance. No new relation kind or U-kind is created.

Missing telemetry non-use. A team cannot determine pump state because telemetry was never collected. State kinds, evidence relations, and candidate actions are already clear. The result is returnToDirectOwner for measurement and evidence work with the blocked state claim; no premise-use occurrence or ontology artifact is minted.

Construction-changing case. A maintenance set uses “part” for both MemberOf and ComponentOf. Removal action differs only in the structural construction case. The work returns the disputed item to C.13, repairs the direct maintenance claim, and leaves unrelated set membership unchanged.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: engineering uses in which ontology may change a practical result.

Ontology-display bias favors elaborate category systems even when direct owners already decide the case. Lexical bias treats clear wording as proof of sound ontology. Evidence bias converts unresolved reliance into a third world state. The mitigation is a defeated consequence, first-capable locus, direct-owner return, and positive stop.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

The pattern gives ontology work a practical exit. It can repair a consequence-changing conflation, return to the real blocker, or stop at an adequate working account without pretending the rest of ontology is false. The cost is naming the defeated claim and the work/result boundary. The benefit is less speculative ontology and more reliable engineering action.

#Rationale

Ontology effort should scale with changed consequence, not with available vocabulary. A direct-owner invariant or grounded counterexample provides a better start than a universal checklist because it exposes why the current account fails. Four loci preserve the common places where repair occurs without forcing an order. The description-level narrowing of C.19.2 carries the economics, work separation, and truthful one-apparatus path instead of duplicating them loosely.

Repair only the ontology that changes the engineering move.

#SoTA-Echoing

These sources change the working method and its cases. They do not license a fixed explication ladder, exhaustive ontology traversal, or replacement of domain evidence by conceptual work.

#Relations

• Description-level specialization: A.7.1 narrows the method claims stated by C.19.2. On the ordinary one-apparatus path, the already selected A.7.1 analysis method is the direct-kind apparatus; the engineering subject and its direct owner remain inputs and constraints. A.7.1 retains the declared use, problem-facing result, claimed guarantee, horizon, useful threshold, separation among reader, performer, Work, and result, stop, and reopen. It retains C.18 and C.11 candidate and choice behavior only for alternative analysis methods, models, formalisms, or other applicable apparatuses eligible for the same use and guarantee. This wording adds no relation occurrence between the described Methods and asserts neither U.SubkindOf nor a world relation.
• Consumes: exact A.7.CP claim epistemes through ClaimUsedAsReasoningBasisRelation@Context only when the ontology-analysis work relies on them.
• Coordinates with: A.7.2 when a material cross-pattern premise conflict is current; neither method is the other's parent or premise owner.
• Returns to: direct relation, role, holon, state, capability, method, work, evidence, temporal, structural, and domain owners for the claim being repaired.
• Escalates durable ontology to: E.24/E.24.UK, A.8, and A.11; it does not admit U-kinds or relations itself.
• Preserves: current A.7 Strict Distinction and A.22.CGUS admission law.

#A.7.1:End

---

Last Updated: 2026-07-20 — this section last modified in upstream FPF commit d6af871b (github.com/ailev/FPF)