A.7.CP - Constructive-Premise Compact and Reasoning-Basis Use
Type: Architectural (A) Status: Stable Normativity: Normative
A.7.CP:0 - Use this when
Use this pattern when reasoning, ontology analysis, choice, or reconciliation relies on a broad constructive claim and another reader must be able to recover which claim, receiving claim or result, posture, scope, work occurrence, and interval carried that reliance.
The first useful move is to name the dated reasoning work, each claim-bearing result or receiving decision it is forming, the A7CP-* claim IDs used for that result, and whether each use is an adoptedPremise or conditionalAssumption. Leave the other compact claims latent.
Not this pattern when. Use the relevant subject pattern for citation, publication, shared vocabulary, ordinary A.7 category-error repair, source currentness, or domain/evidence questions when no compact claim is used in reasoning. No reasoning-basis occurrence obtains in that case.
The primary reader is an author or reviewer who must make one load-bearing constructive premise use recoverable. The object is one ClaimUsedAsReasoningBasisRelation@Context occurrence and the compact claim content it cites.
A.7.CP:1 - Problem frame
Dated work applying an FPF method can rely on broad claims such as “a publication does not create world-side obtaining” or “a MethodDescription episteme does not perform Work”. A U.MethodDescription episteme may state or cite one of those claims as a declared premise or branch condition for its described U.Method.
ClaimUsedAsReasoningBasisRelation@Context obtains only when one inference, comparison, or choice in dated Work relies on that claim for the receiving result.
Copying the claim into every method description makes it drift; leaving the dated reliance implicit hides whether a result used an adopted premise, a conditional branch, or no common claim at all.
The compact publishes twelve stable claim contents once. A U.MethodDescription episteme can declare an intrinsic premise or a branch condition for its described Method; a dated application records only the compact claims used in its reasoning. Ordinary Work therefore does not acquire a foundation checklist.
A.7.CP:2 - Problem
Three conflations make premise use unreliable:
- claim content is confused with the posture in which one work occurrence uses it;
- citation or co-location is confused with reliance in reasoning; and
- a support pattern is treated as a method that performs or governs the consuming work.
The result is either hidden premises or a copied catalogue that becomes a second ontology authority. Both failures obscure occurrence identity and reopen behavior.
A.7.CP:3 - Forces
| Force | Tension |
|---|---|
| Stable claims vs local use | Claim content should be durable, while posture, work, context, and interval vary per use. |
| Recoverability vs cheap first use | Load-bearing use needs a trace; ordinary method use should not traverse twelve claims. |
| Shared support vs subject rules | Common claims coordinate patterns while evidence, currentness, construction, Work and kind admission keep their own rules. |
| Adopted premise vs conditional assumption | Both can support reasoning, but their defeaters and reopen conditions differ. |
| Reuse vs copied variants | One authoritative source avoids divergent copies; consumers still need locally intelligible action guidance. |
A.7.CP:4 - Solution
A.7.CP:4.1 - Publish the compact once
The compact carries these stable claim contents:
-
A7CP-01 Existence and obtaining. World-side obtaining is not created by a claim, database row, predicate, or publication merely representing it. -
A7CP-02 Constructive settlement. When identity, constitution, dependence, or obtaining changes a consequence, name the construction or direct governing relation that grounds it; a reconstructible trace is not itself the world construction. -
A7CP-03 Constitution and social objects. Constituting acts, admitted systems, and the relations they institute remain distinct from descriptions of those acts and relations. -
A7CP-04 Epistemic openness and fallibility. Evidence and reliance may remain unresolved without turning unresolved evidence into a third world-side obtaining mode. -
A7CP-05 Representation boundary. Descriptions, logical forms, database rows, graphs, and publications represent or carry claims under their applicable relations; their form alone does not establish the truth of their world-side claims. -
A7CP-06 Agency and work attribution. AU.MethodDescriptionepisteme describes an admittedU.Method; for a performed-Work claim, recover each performer through A.13 and let A.15.1 independently admit the datedU.Work.Only when the claim or its receiving use expressly consumes precise assignment-bound attribution does F.6 separately relate that Work to the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer, neither the system-role kind nor the assignment acts, and missing or failed attribution alone leaves independently admitted Work intact.
Recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1. A result follows only through its own separately established relation—for example, a production, operation-result, measurement, evaluation, decision, delivery, or acceptance relation—not from Work in general.
-
A7CP-07 Kind discipline. Use direct existing kinds and local admission before proposing a universal kind, root relation, or role-like surrogate. -
A7CP-08 Scoped pluralism. Different source traditions or apparatuses may be useful for different receiving claims; compatibility is tested by consequences, not achieved through prestige hierarchy. -
A7CP-09 Structure and wholeness. A description of structure is not the structure; not every construction is mereology, andC.13alone defines constructional mereology. -
A7CP-10 Time, identity, and currentness. World-side temporal qualification, occurrence identity, claim/publication currentness, and source supersession are separate questions. -
A7CP-11 Subject-pattern separation. Capability, state, architecture, role, method, work, evidence, permission, and relation families retain their subject patterns even when an ontology method diagnoses a conflict among them. -
A7CP-12 Formal projection non-reversal. CT2R and formalization may preserve, collapse, or omit structure. Logical validity or representation form alone establishes no unique world construction.
The twelve IDs form a stable closed compact in this pattern. They are not steps, completeness criteria for every ontology use, or twelve intrinsic premise kinds.
A.7.CP:4.2 - Record reasoning-basis use
Premise and assumption name postures of claim use, not disjoint claim kinds.
ClaimUsedAsReasoningBasisRelation@Context <: U.Relation
RelationSignature:
BasisClaimSlot:
SlotKind: BasisClaimSlot
ValueKind: U.Episteme
refMode: U.EpistemeRef
ReasoningWorkSlot:
SlotKind: ReasoningWorkSlot
ValueKind: U.Work
refMode: WorkRef
ReceivingReasoningResultSlot:
SlotKind: ReceivingReasoningResultSlot
ValueKind: U.Episteme
refMode: U.EpistemeRef
semanticDirection: BasisClaimSlot -> ReceivingReasoningResultSlot
through the named ReasoningWorkSlot
ReasoningBasisPostureValue ::= adoptedPremise | conditionalAssumption
RelationOccurrenceQualifiers:
basisClaimAddress: ClaimAddress
posture: ReasoningBasisPostureValue
reasoningUseScope?: U.ClaimScope
modelUseStructureRef?: SelectedStructureReference
OccurrenceIdentity:
<basis-claim edition and claim ID,
reasoning-work occurrence,
receiving-result edition,
posture,
reasoningUseScope when present,
maximalContinuousRelianceInterval>
BasisClaimSlot is the claim-bearing episteme used, and basisClaimAddress is a C.2.1 ClaimAddress selecting the claim inside that same edition by its intrinsic ClaimGraph identity. ReasoningWorkSlot is the dated reasoning, choice, ontology-analysis, or reconciliation U.Work that relies on it. ReceivingReasoningResultSlot is the claim, comparison, decision, or other claim-bearing result episteme whose content that Work forms or revises using the basis claim. If the practical result is world-side, use the direct result claim that bears on it; the world-side object retains its subject pattern.
Use A.13 to identify the admitted U.System that performs the Work and retain the obtaining occurrence of the separately declared U.SystemRoleAssignment species used by A.13. Independently admit the dated Work under A.15.1. Recover the obtaining F.6 attribution for that Work-assignment pair only when the claim or its receiving use expressly consumes assignment-bound attribution; the assignment holder must be the same System. The assignment’s existence, holder, or interval does not establish that attribution; the independently identified System performs the Work.
Claim episteme, described Method when one is used, Work occurrence, assignment occurrence, attribution, use posture, receiving result, and any world-side result remain distinct. The words “premise” and “assumption” are not relation participants.
The relation obtains during the maximal continuous interval in which the named work relies on the basis claim to form or revise the receiving result. Access, citation, publication, co-location, or use of the claim elsewhere in the same work is insufficient.
reasoningUseScope appears only when this premise use is narrower than or otherwise differs from the receiving result’s declared claim scope; modelUseStructureRef appears only when an independently selected BoundedModelUseStructure changes interpretation. Source currentness, evidence, publication, work method, and the receiving result’s own governance remain with their subject patterns.
One occurrence is identified by the basis-claim edition and ID, reasoning-work occurrence, receiving-result edition, posture, optional narrower use scope, and maximal continuous reliance interval. If one Work uses the same basis claim for two independent results, record two relation occurrences that share the Work participant but name different receiving results; do not duplicate the Work. An actual change to any of these identity values identifies a different or later result-specific occurrence. Correcting a later assertion about the same historical use does not itself change that occurrence.
A.7.CP:4.3 - Keep posture and transition explicit
adoptedPremise means the named work presently uses the basis claim as accepted support for the receiving result. conditionalAssumption means the work uses it for that result only in a narrower model, scenario, proof, or branch with an explicit test, defeater, or reopen condition. Every conditional assumption used can function as a premise inside that bounded subargument; not every adopted premise is conditional. Neither posture changes the basis-claim episteme’s intrinsic kind.
The same claim can have different postures in different Work or for different receiving results of one Work. An actual posture transition creates a later occurrence for the affected receiving result. Reconsider that result and its dependents; another result remains reusable when its own premise use and all other consumed grounds remain unchanged.
A.7.CP:4.4 - Use the cheapest truthful path
- Name the reasoning work and each receiving claim, decision, comparison, or other claim-bearing result it is forming.
- For each receiving result, cite only the compact IDs that are load-bearing.
- Record one relation occurrence per basis claim, receiving result, posture, and continuous reliance interval; reuse the same work reference across independent results.
- Name a narrower
U.ClaimScopeor selectedBoundedModelUseStructureonly when it changes this premise use. - Keep evidence, currentness, source use, kind admission, subject construction, work method, and result governance with their subject patterns.
- Stop when every load-bearing receiving result points to its premise-use occurrences. Do not inspect unused compact entries.
A.7.CP:5 - Archetypal Grounding
Relation-occurrence inquiry. Ontology-analysis work returns SupportOccurrenceInquiryDecision-17: the receiving claim requires an occurrence distinction, but the applicable subject rule does not yet establish whether removal and reinstallation identify one occurrence or two. The result relies on A7CP-01 and A7CP-10 to keep the represented relation, its obtaining, occurrence identity, and currentness separate; it returns the missing subject rule instead of inventing that rule. Two reasoning-basis occurrences name the same work and receiving result but different basis claims. The other ten claims stay latent.
Role/chart reconciliation. Reconciliation work returns AssignmentConstitutionDecision-42, which distinguishes assignment constitution from a chart that evidences the assignment. Four result-specific relation occurrences connect that decision to A7CP-01, A7CP-03, A7CP-05, and A7CP-06. Source-use and evidence relations stay under their subject patterns.
Same-work selective reopen. ReasoningWork-19 returns WarrantyClaimAnalysis-19 and AlternativeOntologyComparison-19. Each has its own relation occurrence to A7CP-10.
The warranty analysis uses that claim as an adopted premise. The comparison uses it only as a conditional assumption in a named branch separating temporal qualification, occurrence identity and currentness.
If the comparison later adopts that separation as an accepted basis, its changed posture and revised result receive a later reasoning-basis occurrence. Reopen the comparison result and its dependents. In this case, the warranty analysis does not depend on that comparison and its other grounds are unchanged, so its earlier result and premise use remain reusable.
No compact use. Missing telemetry blocks a state claim while the relevant state and evidence distinctions are already clear. Work returns to measurement/evidence. No compact claim is load-bearing, so no reasoning-basis occurrence is created.
A.7.CP:6 - Bias-Annotation
The main biases are foundation maximalism, premise-kind inflation, and trace-by-citation. The mitigation is one compact publication source, claim IDs, two context-local postures, work participation, and a non-use rule that keeps ordinary reasoning cheap.
A.7.CP:7 - Conformance Checklist
| ID | Check |
|---|---|
CC-A7CP-1 | Every relation occurrence names one basis-claim episteme/ID, dated reasoning-work occurrence, receiving-result episteme, posture, optional narrower use scope, and maximal continuous reliance interval. |
CC-A7CP-2 | The work relies on the claim for that receiving result; citation, access, publication, or use elsewhere in the work is insufficient. |
CC-A7CP-3 | adoptedPremise and conditionalAssumption are use postures, not intrinsic claim kinds. |
CC-A7CP-4 | An actual change of posture or another occurrence-identity value identifies a different or later result-specific occurrence and reopens that result and its dependents. Correcting knowledge of a historical use changes the assertion, not the occurrence; reuse other results only when their consumed grounds remain unchanged. |
CC-A7CP-5 | Consumers cite only load-bearing claim IDs and do not copy the compact. |
CC-A7CP-6 | The support pattern is not a Method, performer, work plan, result, or mandatory catalogue traversal. A U.MethodDescription episteme may declare a premise or branch condition for its described Method, but only an admitted U.System performs dated reasoning Work. Any assignment, F.6 attribution, and result relation used by the case must obtain separately. |
CC-A7CP-7 | Evidence, currentness, source use, subject construction, kind admission, and work method remain with subject patterns. |
CC-A7CP-8 | The twelve compact claims retain their stable IDs and contents as one closed support set. |
A.7.CP:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| Require every ontology use to check all twelve claims. | Cite only load-bearing claims; unused entries remain latent. |
| Treat a citation or work-wide claim use as a premise-use occurrence for every result. | Name the dated work, receiving result, and inference or comparison that relies on the basis claim; use separate relation occurrences for independent results. |
| Define “premise” and “assumption” as separate episteme kinds. | Keep one claim episteme and record the context-local posture. |
| Let the compact, a MethodDescription episteme, its described Method, a system-role kind, or an assignment perform the consuming Work or bring about its result. | Name the admitted U.System that performs the dated reasoning U.Work and retain the assignment species and obtaining occurrence used by A.13. When the claim or its receiving use expressly consumes assignment-bound attribution, name the obtaining F.6 attribution for that Work-assignment pair. State any result only through the direct result relation that the case independently establishes. |
Copy the compact into A.7, A.7.1, or A.7.2. | Keep one authoritative source and use claim-ID references. |
| Hide evidence or currentness inside the relation. | Cite direct evidence/currentness results without turning them into relation fields. |
A.7.CP:9 - Consequences
The compact makes consequential constructive reliance recoverable from one claim source. Ordinary use requires no traversal of unused claims. For a load-bearing use that another reader must recover, identify the basis claim, Work, receiving result and posture. That account supports reconsidering only results that depend on a changed ground.
A.7.CP:10 - Rationale
Claim content and reasoning posture vary independently. One source for the content and a separate relation for its use let readers recover both without treating premise and assumption as different claim kinds. The System performs the reasoning Work; the episteme supplies the claim on which that Work relies.
Use only the premise the work relies on.
A.7.CP:11 - SoTA-Echoing
| Practice question | Source contribution | FPF alignment | Disposition |
|---|---|---|---|
| Can exact claim content be reduced to possible-world equivalence? | Fine 2017 argues for exact truthmaker content beyond coarse modal equivalence. | Compact claims retain contents and IDs; FPF does not merge them into one modality field. | Comparator only. No truthmaker ontology is imported. |
| How should formal claims preserve typed behavior? | Homotopy type theory and related typed proof practice preserve exact proposition/type roles (Rijke, Shulman & Spitters 2020). | Reasoning-basis use cites a claim episteme and does not infer world ontology from formal form. | Adapt as formal comparator. Direct formal patterns keep proof semantics. |
| Do bearer and realization distinctions matter for capability claims? | Applied-ontology capability work retains bearer and realization conditions (Toyoshima et al. 2022). | A7CP-11 keeps capability claims under A.2.2 rather than importing a compact capability ontology. | Comparator only. The external hierarchy is not imported. |
| Do weak permission, strong permission, and action satisfiers have the same content? | Moltmann 2024 distinguishes those contents and their use. | A7CP-11 protects direct permission patterns; claim IDs can support analysis without becoming permission objects. | Adapt as separation pressure. No modal-object U-kind is added. |
A.7.CP:12 - Relations
- Defines: the twelve
A7CP-*constructive claim contents andClaimUsedAsReasoningBasisRelation@Context, whose direct result-specific edge states that dated reasoning work used one basis claim to form or revise one receiving result episteme. - Is consumed by: dated Work applying the Methods described by
A.7.1orA.7.2, which cites compact claims and exposes relation occurrences only for load-bearing reliance. Their procedural epistemes may separately declare premises or branch conditions; any MethodDescription membership satisfies A.3.2. Neither a MethodDescription nor a Method is a participant ofClaimUsedAsReasoningBasisRelation@Context. - Coordinates with:
A.7for the object and relation distinctions needed by the receiving claim. - Retains subject rules:
A.10andG.11govern evidence/currentness;E.24/E.24.UKgovern applicable pattern/U-kind admissions; subject construction patterns govern constructive settlement;A.7.2governs ontology source-use relations. - Does not define: a premise method, source authority, evidence relation, work plan, performer kind, common realism checklist, or universal foundation ontology.