F.0.2 - Semantic Synthesis across Source Ontologies
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
F.0.2:1 - Problem frame
Use this pattern when sources answer the same inquiry through different concepts, relations or explanations and the difference matters to what someone can conclude or do. The recipient may need the comparison itself, a way to act that depends on it, or a contribution to a framework pattern.
In this pattern, conceptual synthesis and semantic synthesis name the same work. It means comparing and developing claims through the concepts, relations and boundaries used by their sources. It can concern a theory of action or any other subject. When undertaken to construct or revise a method, this conceptual work is part of methodological synthesis. Its conclusions can also answer an inquiry in their own right.
The primary concern is one bounded semantic-synthesis question for one declared receiving use. The first useful move is to state that question and the difference that could change the next decision. Keep each source claim local through F.0.1, choose the source cut through F.1, then compare the claims here.
What goes wrong if missed. An author either leaves a crosswalk or literature narrative where a positive contribution is needed, or merges similar words before checking whether the sources describe the same entity, relation, explanation, and use. A large research package may also be demanded for a question that one bounded comparison can settle.
What this buys. The author can turn heterogeneous source ontologies into one reviewable result: a provisional synthesis claim, a contrast claim, or an unresolved-inquiry claim. When a pattern contribution is proposed, the result also states the practitioner action, first useful result, and later content decision that may accept, change, reject, or reopen it.
Not this pattern when. Cite one source directly when one source claim closes the question. Use F.1 when only source selection is current; F.0.1 when only local meaning is unclear; F.9 when one relation between already recovered cross-context senses is current; and the subject pattern when it already supplies the needed action and result. Use G.2 instead when the work needs a broad, refreshable SoTA Synthesis Pack@CG-Frame and its downstream Part G handoffs.
F.0.2:2 - Problem
Researchers, practitioners and framework authors often receive accounts that use similar terms for different relations or explanations. A correspondence between terms identifies a comparison to make. To decide what follows, recover what each source says about the same inquiry, under which conditions and on what grounds.
Three failures follow:
- a correspondence, shared label, similarity score, or framework fit is treated as permission to merge;
- a source difference that changes action is hidden as terminology variation; or
- missing or weak source material is reported as if the disputed domain claim were false.
Semantic synthesis must preserve source-local meanings while returning a positive next move or a bounded stop.
F.0.2:3 - Forces
| Force | Tension |
|---|---|
| Positive contribution vs source fidelity | The receiving framework needs a usable claim, while sources must not be flattened into one vocabulary. |
| Small first result vs broad inquiry | One authoring decision may need only a bounded comparison, while a large research programme may need the full G.2 pack. |
| Similarity vs identity | Matching can propose correspondences, while sameness, truth, and adoption require separate claims. |
| Integration vs contrast | A synthesis should open a productive move, while a real disagreement or non-fit must remain visible. |
| Progress vs epistemic restraint | Work should continue where the basis suffices, while a load-bearing source gap must prevent reliance. |
| Reuse vs domain dependence | The synthesis method can remain transdisciplinary, while domain claims and their source refresh stay in their subject DPF. |
F.0.2:4 - Solution
F.0.2:4.1 - Bounded synthesis method
- Name the receiving question and use. State what someone needs to establish or do, and which difference between the accounts could change that answer. For a research inquiry, name the conclusion the comparison should support or qualify. If a method or a pattern is being developed, name the operation or practitioner decision the comparison could change.
- Recover source-local claims. For every load-bearing source, identify the claim, its EntityOfConcern, effective ReferenceScheme, edition, source role, and the context in which the claim is used. Apply
F.0.1; useF.9only when the comparison asserts a relation between exact cross-context SenseCells. - Choose a bounded source cut. Apply
F.1. Include the sources needed for the intended use, known rival explanations, action-changing counterexamples, transfer limits, and material non-fit. State why each selected source can change the decision. - Compare the consequences of the source claims. Work the same question in each account. Keep the entities, relations, conditions and grounds identifiable. If two proposed relations coincide in the familiar material, look for an admissible change that preserves one while changing the other. State what each account then lets the recipient infer or do. If their consequences agree throughout the intended scope, show why that agreement holds there. Complementary claims can support a joint conclusion when the premises for using them together hold. If the available grounds do not establish the relation for this use, identify what is missing. B.5.TC develops this comparison for rival theoretical accounts.
- Write one first result. Write a provisional synthesis claim when a positive shared contribution is warranted; a contrast claim when the proposed unification is not warranted for the named use; or an unresolved-inquiry claim when a named source gap prevents either substantive answer.
- Return the result to its intended use. Show which conclusion the recipient can now draw or qualify and on what grounds. When the work informs construction of a method, identify the operation or condition it changes. For a framework contribution, name the content or placement decision it informs. Keep the source edition recoverable and give the result a stable locator when it will be cited or replayed. C.2.1 governs an explicitly identified claim episteme.
- Decide what to do with the result. Use the options for its branch in §4.3. When the receiving use requires a record, state the decision and cite the exact result and source edition. A result awaiting the decision remains a proposal; silence or citation alone is not acceptance.
- Keep the source use revisable. Identify the source claims and editions relied on, why each matters to this result, what was deliberately left local or rejected, and which change reopens the comparison.
Stop when the result answers the receiving question to the extent the sources allow. If a material premise is missing, state what remains open and what would settle it. Enter clustering, Concept-Set development, naming, UTS or broad source harvesting when the next use needs that further result.
F.0.2:4.2 - Source-basis branches
| Source situation | How to use the source | Boundary |
|---|---|---|
| An admitted maintained synthesis already integrates a field | Recover every occurrence that can change the receiving question. Follow its cited sources where a load-bearing distinction or limit depends on them, and compare current alternatives that could change the answer. | The synthesis is a valuable conceptual map, not independent confirmation of its own integrated claims. |
| Several independent sources answer the question | Give each source an explicit role: proposed contribution, rival explanation, counterexample, boundary, evidence limit, or current alternative. | A reading list or source count does not establish coverage or relevance. |
An identified G.2 pack already exists | Reuse its identified source claims, editions, alignment records, and provenance when they answer the bounded question. | Pack conformance, a fusion record, or a coverage measure does not establish the receiving-framework claim. |
| An earlier DPF supplies a lesson | Classify the lesson as direct FPF reuse, a bounded FPF improvement proposal, or a domain/local claim retained in the receiving DPF. | Precedent does not create ecosystem law or prescribe package shape. |
| A derived lookup proposes FPF or DPF contributions | Return each result to the authoritative pattern body and edition. Report a partial result when a source is unavailable, stale, or incompletely indexed, and widen the search when a known contribution is absent. | A lookup result aids discovery; non-return is not evidence that a contribution is absent. |
F.0.2:4.3 - Three result branches
A result identified as a claim-bearing episteme retains its C.2.1 identity <claim content, EntityOfConcern, effective ReferenceScheme>. Keep the result and source edition recoverable for the receiving use. A stable local locator can supply a needed address for later citation or replay; it does not identify the claim by itself.
| Result | What the claim concerns | What it says | Required receiving disposition |
|---|---|---|---|
| Provisional synthesis claim | The proposed account of the subject, with the interpretation used in the comparison and the correspondences to the sources. | A positive cross-source claim with its scope, source roles, retained differences and limits. It is available for the recipient to examine. | The recipient can use the claim with its limits, revise it as a separately identifiable claim, decline it for this use or reopen the comparison. |
| Contrast claim | The candidate unification or proposed shared contribution being tested, interpreted through the receiving scheme and the source-local comparison rules. | Why the inspected comparison does not warrant that unification for the named use. It preserves the source-local claims and any narrower positive claim that remains supported. | The receiving decision keeps the source claims distinct for the named use, adopts a narrower or revised claim, does not use the contrast, or reopens the comparison. |
| Unresolved-inquiry claim | The bounded inquiry state, interpreted through the receiving scheme and the source-currentness, adequacy, and comparison rules available for this inquiry. | A named missing, stale, or too-weak source prevents the inquiry from choosing between a provisional synthesis and a contrast. It states what remains usable and the next source action; it does not assert that the disputed claim is false. | The receiving decision retains the bounded unresolved result and its usable remainder, commissions the named source action, ends the named use, or reopens the comparison. Any later substantive answer is a separately identified result. |
The source gap is the reason and closure condition for an unresolved-inquiry claim, not a fourth result branch. A temporary unrecorded pause is not an F.0.2 result that later work can cite.
F.0.2:4.4 - Bounded method and broad SoTA-pack method
Use F.0.2 when one bounded comparison of source meanings can answer the receiving inquiry with a synthesis, a contrast or a statement of what remains unresolved. Use G.2 when a CG-Frame needs a broad, refreshable harvesting surface with a CorpusLedger, Claim Sheets, palette, inventories, alignment records, examples, and declared G.3-G.5 handoffs.
An author may use identified claims and provenance from a G.2 pack as inputs here. The author must compare retained differences, limits, receiving use, and reopen conditions before writing an F.0.2 result. The bounded comparison does not require the rest of the pack when the question does not use it.
F.0.2:4.5 - Boundary to wording-use precision restoration
Semantic synthesis and wording restoration both pass through ontology, but they answer different questions. Semantic synthesis forms or revises a cross-source claim. Wording restoration starts from an already current subject claim and repairs a consequential wording use so that the intended entity, relation, claim kind, and admissible action can again be recovered.
A recurring wording failure may supply evidence that a subject distinction is missing or unstable. The system maintaining the affected FPF or DPF edition then uses that evidence in a named content decision. The findings can support a proposed revision. The content decision governs changes to the claim maintained in that edition. A DPF keeps its domain wording entries beside the domain patterns that use them; E.10.ARCH supplies the shared restoration method.
A DPF may need a reliable current domain ontology so practitioners can recognize situations, distinguish Methods and results, and use its solution moves. An author can use F.0.2 to synthesize or revise that ontology as a proposed contribution. Ontology alone is not a DPF: use E.4 and E.4.DPF to connect it to recurring problems, constructive Methods, a usable first cut, evidence practice, access, and maintenance.
F.0.2:4.6 - Semantic and methodological results
A conceptual synthesis states what the source accounts warrant about an identified subject, which kinds and relations support the claim, and where a disagreement remains. This can be the result a recipient asked for, including a result about actions or methods.
When the requested result is a new or revised way of working, call the whole undertaking methodological synthesis. Use established concepts where they suffice. If the source accounts disagree about what an operation acts on, what it supplies or what counts as success, compare those accounts. An agreement can supply a shared premise. If different readings are warranted under different conditions, provide for each in the method. If a premise remains open, obtain the evidence, use a way that works under either reading, or withhold the conclusion that depends on it. Trying the method can in turn reopen a conceptual conclusion. When the comparison is also needed as a reusable explanation in its own right, name both deliverables and what supports each. One recipient can need both in a single commission.
Carry each result to the scope at which its recipient will use it. A transdisciplinary way of reasoning can guide the work of a single discipline. Identify the conclusion at stake, examine how the field’s types and relations warrant it and revisit dependent conclusions when a premise changes. In interdisciplinary work, identify what each field supplies and what correspondence lets another field use its result. When two contributions appear to conflict, establish whether they concern the same subject under the same conditions. If the accounts are consistent but the products cannot work together, identifying the incompatibility may answer the inquiry. When the purpose requires joint operation, consider a change to the arrangement or the products and test whether it resolves the incompatibility. If the claims still conflict, identify what further evidence or revised account could resolve the conflict. Carry forward the conclusions whose grounds hold. A discipline supplies the particular means by which those grounds can be obtained or tested. A field method can be complete at this scope before a project selects staff, tools or a schedule. In a project, choose an applicable way and recover the local evidence needed for the next action. Reuse a known way when it suffices. Where several pattern Solutions supply the Method, connect the result of each needed operation with the operation that uses it, including the alternative or return if that result is unavailable. This is how a language of patterns expresses a way to act across cases. Use the mantra in C.39.WA:4.3 when an inference changes what the claim concerns, extends it to other cases, or changes which way applies. Name the relation and the grounds for that particular move. C.39.RO:4.2–4.5 develops the grounds for generalizing an operation.
Use C.39 to construct, connect, explain or change ways of obtaining the needed results. E.4.CM applies that general methodological work to a framework author’s public account of one composite Method or several independent Methods. Those constructions can use the semantic result returned here; trying a proposed way can expose a missing distinction or reopen source comparison. A sufficient existing Method can be used directly.
F.0.2:5 - Archetypal Grounding
F.0.2:5.1 - Systems Engineering use and system concept
A Systems Engineering DPF author must decide what a practitioner should do when a proposed system concept is internally attractive but its connection to outside use is unclear. The author compares a proposed outside-before-inside instruction with the receiving ontology and an external systems-engineering account:
| Input to the comparison | Claim used in this comparison | Role and limit |
|---|---|---|
| Proposed outside-before-inside instruction | Begin with the system’s behavior in its operating environment and only then work inward toward alternative constructions. These linked descriptions remain revisable. | Authoring proposal to test and refine. |
FPF 8, patterns A.14, A.6.F, and C.2.1 | Parthood, function or effect claims, function bearing, and the identity of a claim-bearing episteme are separate questions with their own conditions. | Receiving-ontology boundary. |
SEBoK v2.14, Applying the Systems Approach, permanent revision 78074, 18 May 2026, Application Principles | Apply activities concurrently with attention to their dependencies. Iterate between needs and candidate solutions. | Comparison for dependency-aware concurrent and iterative work; the sequence is tailored to the problem situation. |
A lexical crosswalk that maps both using system and containing system to one parent system entry erases the use-versus-parthood distinction. The author can then no longer compare changing the project system’s construction with changing how an external system uses it.
The comparison concerns priority within an iterative process. Starting from an internal construction can narrow the alternatives before the outside behavior and operating conditions are known. Begin with the outside-use question. Once the information needed for a particular design question is explicit, explore construction and feasibility while refining the use account; leave a dependent construction choice open while its decisive use conditions remain unknown.
The author records the provisional synthesis branch at local locator SE-CS-USE-01 with this claim: “For one Systems Engineering concept decision, first establish the proposed outside behavior, operating conditions and system-in-hand sufficiently to compare internal constructions. Develop and test candidate constructions against that use; refine both accounts as new information arrives, and reopen the use, boundary or construction when realization evidence defeats it. State the subjects and direct relations that change the decision.” This retains the proposal’s outside-before-inside priority, reconciled with dependency-aware concurrent and iterative work.
Replay the clock choice. A team begins comparing gear arrangements for a clock. In this constructed case, asking where and how the clock will be used reveals a requirement for millisecond timing beside a rocket engine, with vibration and 30 g acceleration. The next result is an explicit timing-and-environment use hypothesis; the team compares and tests constructions against it before selecting one. Timing accuracy and vibration resistance can be investigated in parallel once their required operating conditions are stated. If feasibility evidence defeats the proposed clock use, revise that use or the system concept and compare again.
A key/lock case changes another premise: investigating the intended change from a locked to an unlocked door shifts the immediate engineering subject from the key to the lock arrangement, with the key treated as a subsystem in the proposed decomposition. That change of focus does not by itself change the product SoI: recover the extended enterprise, its product and agreements under A.1.STM:4.1 when that designation matters. Recover the selected boundary before comparing mechanical, electronic or biometric realizations. The retained function stays visible while the construction alternatives change.
In this worked case, the later Systems Engineering DPF content decision cites SE-CS-USE-01 with this source edition and records used as proposed. The applied use-and-system-concept move stays in the Systems Engineering DPF; general claim, parthood and function-bearing rules stay in FPF. Reopen SE-CS-USE-01 when a source changes the linked action or boundary, a counterexample shows that the proposal cannot guide the decision, or the receiving decision changes its intended use.
F.0.2:5.2 - Organization change contrast
An organization-change author compares schools that describe organizational flows and partial organizations through different transformations and coordination structures. The sources support a narrower claim about linked transformation and coordination structures, but not one universal organization-flow kind. The author records a contrast claim, preserves the source-local decompositions, and lets a later DPF content decision choose the narrower contribution.
F.0.2:5.3 - Scientific classification inquiry
A cross-disciplinary data framework proposes one shared classification relation between a laboratory ontology and an administrative classification. The available alignment suggests candidate correspondences, but the current edition of a load-bearing clinical source is unavailable. The author records an unresolved-inquiry claim about that bounded comparison, keeps the administrative-only use available, and names inspection of the missing clinical edition as the next source action.
F.0.2:5.4 - Cheap anti-case
An engineer consults a handbook and its later edition only to recover the current pump tolerance. The later edition gives the needed claim, and no ontological difference changes the authoring decision. The engineer uses the tolerance, cites the later edition and stops without semantic synthesis.
F.0.2:5.5 - Compare causal accounts on one sensor case
An author is deciding whether an explanation may treat inference about a hidden condition and changing an observed output as the same operation. Recover the source-local operations first. In the Introduction and “The Generative Model”, Parr and Pezzulo (2021) describe hidden-state inference together with policy-conditioned transitions and preferred outcomes. Pearl, Glymour and Jewell’s corrected primer, p.55 describes intervention as replacing a generating mechanism.
Use the binary load/alarm case in C.28:4.4. Under exact inference from the same stipulated joint distribution, either account obtains a high-load probability of 0.9 after an alarm and 0.1 after an ordinary low reading. In the separately specified intervention model, setting the alarm output low leaves the load mechanism unchanged, so the high-load probability is 0.5.
An active-inference action can be compared with that intervention after its state-transition and observation consequences are specified. An action that changes only the output agrees on this load prediction. An action that initiates cooling requires the later load transition and its time order in both models. Comparing which action to select also needs the objectives or preferences used in selection.
Both accounts give the stated observational inference from the same joint distribution. Agreement about an action requires a correspondence between the specified mechanisms.
The receiving explanation decision can adopt this contrast and keep the two questions explicit. Reopen the comparison when the receiving question, source account, inference approximation or action mechanism changes.
F.0.2:6 - Bias-Annotation
Scope. This pattern is limited to one bounded synthesis question in which differences between source concepts can change an FPF or DPF content decision.
| Lens | Boundary |
|---|---|
| Gov | The author proposes a result; a later content decision records what to use. |
| Arch | Give each source claim, synthesis result and later placement decision its own recoverable content. |
| Onto/Epist | Similar wording, a correspondence, or framework fit establishes neither sameness nor truth. A missing load-bearing source produces an unresolved inquiry, not a negative domain claim. |
| Prag | Use the cheap exit when direct source use answers the question. Keep the comparison bounded, and open G.2 only when its broader source pack changes the intended use. |
| Did | Show the source-local claims and the action-changing difference in ordinary prose. Give readers source editions and locators they can follow; do not make local storage coordinates carry the explanation. |
This pattern favors explicit source roles and positive integration over a single authoritative vocabulary. That stance can overvalue synthesis and make every disagreement look like a new framework contribution. The cheap exits, contrast branch, unresolved-inquiry branch, and subject-pattern placement test keep the work proportional. Domain knowledge, lived practice, institutional authority, and empirical evidence remain source-local until a receiving claim states how they are used.
F.0.2:7 - Conformance Checklist
CC-F0.2-1The receiving question, intended use, and action-changing source difference are stated before comparison begins.CC-F0.2-2Every load-bearing source claim has a recoverable EntityOfConcern, effective ReferenceScheme, edition, and source role; locators are not treated as source-use relations.CC-F0.2-3The source cut covers the intended use, known rival explanations, action-changing counterexamples, transfer limits, and material non-fit by relevance rather than by a universal count or distance threshold.CC-F0.2-4Similarity, correspondence, Bridge, framework fit, orG.2pack conformance is used as input and not as synthesis truth or permission to merge.CC-F0.2-5The result is one provisional synthesis claim, contrast claim or unresolved-inquiry claim whose content, subject, interpretation basis and sources are recoverable. Add a stable local locator when later citation or replay needs it.CC-F0.2-6The result identifies the inference, action or framework decision its grounds support and what remains open for that use. Keep any decision record required by the recipient.CC-F0.2-7The result identifies the source claims and editions it relies on, why each matters, retained differences and limits, and material reopen conditions.CC-F0.2-8An unresolved-inquiry claim concerns the inquiry state, names what remains usable and the next source action, and does not turn missing evidence into a negative domain claim.CC-F0.2-9Domain roles, methods, examples, evidence bases, and refresh lines stay in their subject DPF; the reusable synthesis move remains independent of those DPFs.CC-F0.2-10The author stops after the smallest result that answers the receiving question and opensG.2or later Part F work only for a named additional use.
F.0.2:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | What fails | Repair |
|---|---|---|
| Crosswalk as synthesis | Candidate correspondences are presented without a receiving claim or practical action. | State the receiving question, compare action-changing differences, and write one of the three result claims. |
| Similar words as one concept | Lexical resemblance hides different entities, relations, or explanatory roles. | Restore source-local claims through F.0.1; add an F.9 Bridge only for a relation the comparison asserts. |
| Literature narrative without an answer | The sources are recognizable, yet the reader cannot say what follows from comparing them. | Return the supported conclusion, the consequential difference or the specific question still open. Show which operation changes if a method depends on it. |
| Framework fit as assurance | Material is forced into the receiving ontology and fit is treated as truth. | Keep non-fit visible and separate authoring proposal, evidence use, admission, and reliance. |
| Missing source as falsity | An unavailable or weak source is used to reject the disputed claim. | Make the bounded inquiry state the EntityOfConcern and name the source action that may close it. |
| Heavy pack by default | Every bounded question is expanded into a full G.2 programme. | Use one bounded comparison; use G.2 only when its broad harvesting and handoff result is needed. |
F.0.2:9 - Consequences
Benefits:
- framework authors can produce a useful first claim before a complete account or UTS exists;
- source differences that alter action remain visible instead of being normalized away;
- small and large synthesis investments have separate methods that can reuse the same identified source claims; and
- DPFs reuse one method while retaining their own doctrine, evidence, examples, and currentness.
Costs and trade-offs:
- authors must recover source claims and editions rather than cite files or bibliographies as wholes;
- a contrast or unresolved inquiry can be the correct result even when a positive synthesis was expected; and
- later reliance needs the evidence-use, decision, admission, assurance, or publication claims required by that use.
F.0.2:10 - Rationale
A shared vocabulary can help locate the claims to compare. The comparison earns its cost when it establishes what the sources jointly warrant, where their accounts differ, or which evidence would settle a consequential disagreement. That result can answer an inquiry directly, change a method or inform a pattern. One bounded comparison often suffices.
The three result branches keep the method constructive without forcing agreement. A provisional synthesis opens a positive contribution, a contrast preserves a decision-relevant difference, and an unresolved inquiry turns a source limitation into a defined next action. Ordinary C.2.1 claim identity keeps those results separately revisable.
F.0.2:11 - SoTA-Echoing
| Current practice line and sources | Adopted or adapted move | Effect in F.0.2 | Limit kept visible |
|---|---|---|---|
| Ontology matching: OAEI 2025 campaign and results; Giglou et al., LLMs4OM (2024, arXiv:2404.10317); Qiang et al., OAEI-LLM (2024, arXiv:2409.14038) and its 2025 TBox extension | Adopt inspectable candidate correspondences, source-local identity, benchmark or expert checking, and an explicit missing-mapping boundary. | Correspondence proposals enter the comparison, and a missing load-bearing source can lead to an unresolved-inquiry claim. | Inspect the source meanings and intended use behind a proposed match; benchmark correspondence quality leaves that conceptual comparison to the author. |
| Ontology interoperability engineering: Qiang, An Ecosystem for Ontology Interoperability (2025, arXiv:2507.12311) | Adapt the separation among ontology design, matching, versioning, and deployment validation. | Alignment, receiving-ontology design, revision, and later use remain separate moves and claims. | The proposed lifecycle concerns data integration; applying its moves to framework authoring requires a correspondence between the actual tasks and receiving decisions. |
| Theory synthesis: Jaakkola, Designing conceptual articles: four approaches (2020, DOI 10.1007/s13162-020-00161-0); Okoli, Developing Theory from Literature Reviews with Theoretical Concept Synthesis (2022, DOI 10.2139/ssrn.3452134) | Adopt one synthesis question, explicit source roles, comparison of concepts, relations, explanations, and contexts, and a positive integrated contribution rather than a summary or gap list. | The bounded method returns a practitioner-facing provisional contribution when the comparison warrants one. | These methods organize conceptual-article contributions. A practitioner-facing adaptation must also supply the action and first useful result for the receiving problem. |
| Framework synthesis: Carroll et al., Best fit framework synthesis: refining the method (2013, DOI 10.1186/1471-2288-13-37); Brunton, Oliver, and Thomas, Innovations in framework synthesis as a systematic review method (2020, DOI 10.1002/jrsm.1399) | Adapt use of a receiving framework together with explicit treatment of non-fit and source heterogeneity. | Rival explanations, contrast, non-fit, and revision of the receiving framework remain live in the Solution. | Preserve and examine data that do not fit the initial framework; that non-fit may require changing the proposed explanation. |
For the authoring question in :5.1, a correspondence-only answer can identify similar terms but leaves the outside-before-inside contribution undecided. A full G.2 pack adds a reusable corpus, claim sheets, inventories, alignments and downstream handoffs; these become worth their cost when later questions need that broader result. The bounded method instead retains source-local claims, compares the decision-changing difference and produces one result for the named decision.
Jaakkola’s question and source-role discipline, Okoli’s extraction and iterative synthesis, and Carroll–Brunton’s treatment of non-fit inform steps 1–5 of that bounded route. These contributions organize the comparison; the working case determines what can be integrated and what must remain different. The trade-off is limited coverage for a smaller first result. Reopen the source cut when a known rival or counterexample can change that result, and open G.2 when the receiving work needs its broader reusable outputs.
F.0.2:12 - Relations
F.0.2.MA uses a synthesis, contrast or unresolved-inquiry result to allocate Method contributions without erasing useful differences. F.0.2.RC tests whether the receiving explanation preserves the source’s constructive contribution and follows changed premises to affected uses. These operations can stop on an already adequate synthesis and do not impose corpus-wide extraction on a bounded question.
- Builds on:
F.0.1for source-local meaning andF.1for a relevance-based source cut. - Uses when current:
F.9for an asserted relation between exact cross-context SenseCells;C.2.1for every recorded result claim;A.2.4and the applicable direct relation pattern for a later evidence or decision use. - Coordinates with:
F.2-F.8,F.14,F.17, andF.18when the next authoring question requires harvesting, clustering, Concept-Set, naming, or UTS work. - Coordinates with:
G.2as the optional broad harvesting method. Identified claims and provenance from aG.2pack may supply inputs here; the pack does not replace the receiving comparison. - Coordinates with:
E.4.DPFfor DPF entry and result placement,E.10.ARCHfor DPF-local wording entries under the shared restoration method, andG.11for source-currentness and refresh work. - Coordinates with: C.39 constructs, connects and revises the operations of a method. E.4.CM develops the public explanation when a framework author undertakes this work. A comparison here can supply a premise or expose an unresolved condition for an operation. Trying the method can in turn reopen that comparison.
- Boundary: Domain claims produced through this method remain in the subject FPF pattern or named DPF selected by the later content decision.