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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

A.7.1:4 - Solution

A.7.1:4.1 - Retain the complete application boundary

The analysis described here narrows C.19.2’s method claims to consequence-guided ontology questions. Retain the declared use, problem-facing result, claimed guarantee, horizon and useful threshold. Keep the description episteme, described Method, reader and result distinct; add the performer, assignment and dated Work basis in §0 only when such a Work is asserted. This relation between descriptions alone establishes no relation occurrence between their described Methods.

The normal short path uses the already selected A.7.1 analysis method as its one apparatus. It begins from an engineering subject, subject predicate, and the pattern content locating that predicate; subject and predicate 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 and a local choice is needed.

Apply A.15.2 when planning remains necessary, the §0 basis when dated Work is asserted, and C.24 when tool-call enactment planning is the remaining question.

A.7.1:4.2 - 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, subject-pattern invariant, or grounded counterexample;
  4. at least one candidate correction or a request to recover one; and
  5. any action that must remain blocked until the distinction is settled, with the rule or consequence that requires that stop.

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

A.7.1:4.3 - 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 F.19; continue to C.2.P or E.10 only when a semantic question remains.
  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 direct relation, local system-role-kind, system-role-assignment, state, capability, Method, Work, responsibility, and evidence patterns already in FPF.
  4. Subject-specific constructive ground. Return to the subject construction only when action, identity, dependence, obtaining, constitution, or decision-changing CT2R loss differs across constructions. Use the direct relation-occurrence, local system-role-kind, direct U.SystemRoleAssignment species, system-recognition, Work-occurrence, state or capability, responsibility, or structural-construction pattern. Do not default to C.13 or a generic constructive calculus.

A.7.1:4.4 - Perform only consequence-changing ontology work

  1. Select the first locus capable of resolving the delta.
  2. Perform the required domain inquiry, wording repair, typing, evidence assessment or construction analysis.
  3. Cite A.7.CP claim IDs when their contents are load-bearing. Use ClaimUsedAsReasoningBasisRelation@Context when the receiving use needs to recover the Work, receiving result, posture, scope, or interval of that reliance. Do not traverse the compact by default.
  4. Preserve direct evidence, currentness, source-use, kind-admission, and subject-construction patterns.
  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;
  • unresolvedWithBlocker.

These are method-result dispositions, not new U-kinds. Each names the affected use, practical result or blocked claim, and stop/reopen condition.

A.7.1:4.5 - 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.

Save the ontology result when reuse, dispute, consequence, automation or cross-pattern change makes persistence valuable.

Admission of a proposed framework pattern or U-kind follows E.24 or E.24.UK respectively; a local distinction follows its subject rule. Persistence alone opens no new-kind admission. If a needed predicate or kind remains unadmitted, return the missing governor or affected blocked claim; rely on it only after the applicable positive admission.

A.7.1:4.6 - 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 subject-pattern distinction. Reopen only the affected engineering and ontology decisions.

A short presentation of the domain inquiry, wording repair, typed account or constructive ground may remain an ordinary explanation. Identify any claim-bearing episteme under C.2.1 when its identity matters; persistence is a separate choice.

A reusable CGUS requires one identified A.22 structure, local locus bindings, selected relations and applied constraints, and at least two potential continuations; its present-case continuation results remain separate.