A lightweight formalism for managing claims across fragmented knowledge domains — preventing the silent conversion of results from one mode of reasoning into another.
Primitives
1) Fragment (primitive, local scope)
A fragment is a container for reasoning under controlled assumptions.
- F := ⟨A, K, Π⟩
- A: assumptions (axioms, constraints, conventions)
- K: claims currently admitted in the fragment
- Π: provenance map, Π(c) = minimal support record for claim c (sources, derivations, or trusted inputs)
Assumption dependence is not optional: every non-axiom claim must have a provenance record.
2) Support edge (primitive, local scope)
A support edge is a directed relation where is a set of claims/assumptions and is a claim. It is the atomic unit of “why.”
3) Compatibility predicate (primitive, local scope)
answers whether fragments can be combined without immediate contradiction under declared assumptions.
Derived operators
4) Closure (derived, local scope)
adds all claims derivable from using the allowed inference rules in that fragment.
depends on the rule set (explicit) and optional resource bounds (depth, time, or permitted theory). Closure is never global by default — it is scoped and parameterized.
5) Minimal support extraction (derived, local scope)
For , define as the smallest (by set inclusion) support set that still entails according to . If there are multiple minima, keep the set of minima.
6) Delta (derived, cross-fragment)
is the smallest set of assumption/claim changes required so that holds, plus the induced provenance edits.
This is debugging at the level of model boundaries rather than sentences.
7) Tension index (heuristic)
A number or ordering estimating how expensive it is to merge fragments: contradictions, support overlap, and closure explosion. Not truth — a steering function.
Worked example: illicit globalism
Suppose a research program constantly switches among math, architecture, and implementation. The classic failure mode is illicit globalism: something proven in math mode quietly becomes a design invariant in runtime mode, then becomes a test oracle in implementation mode, even though each move silently changed assumptions.
Model each mode as a fragment:
- (math): includes axioms/definitions; includes proof rules.
- (architecture): includes design constraints (latency, ergonomics, versioning); includes refinement rules.
- (implementation): includes language/tool constraints; includes operational semantics, testability constraints.
The useful question is not “is claim true?” It is:
In which fragments does survive closure, and what is the delta cost to make it survive elsewhere?
Example claim
Let := “Normalization is confluent.”
- In , includes with support (Newman’s lemma), plus precise definitions.
- In , the same sentence might mean “canonicalization yields unique normal forms,” which additionally needs determinism of the strategy, stability under version changes, and a representation invariant compatible with serialization.
- In , the chosen strategy may not terminate on some inputs (resource bounds, recursion limits), so fails.
Delta analysis instead of argument
Compute :
- Add a restriction on the term language (exclude constructs causing divergence), or
- Add a fuel/step bound and weaken to “confluent up to steps,” or
- Change implementation strategy and update provenance.
The point: don’t debate — refine it into fragment-compatible variants with explicit cost.
Closure is the silent killer
In practice, most incoherence comes from uncontrolled closure:
- Import a powerful rule set into a fragment meant to be lightweight.
- explodes and drags in commitments never priced in.
- Later fragments inherit those commitments as axioms.
An operationally useful invariant:
Every fragment must declare its closure regime (rule set + bounds). Otherwise “what follows” is undefined, and provenance becomes theater.
If a claim is used as an invariant across modes, it must come with (i) fragment labels, (ii) minimal supports, and (iii) the delta plan if the claim fails under another closure regime.
Extensions
Two natural directions that stay coherent:
- Typed claims: distinguish semantic claims (about objects) from governance claims (about allowed rules/assumptions). Governance claims should not be imported casually.
- Bidirectional deltas: is not symmetric. The asymmetry encodes where you pay the complexity tax.
Appendix: test for situating claims
Given a claim and a context :
- Enumerate the operations that actually performs.
- For each , ask: does constrain ?
- If constrains nothing, mark = decorative.
- If constrains but is never consulted, mark = ceremonial.
- If is consulted but violations are tolerated, mark = aspirational.
- If violations cause repair, mark = operative.
- If repair changes ‘s future structure, mark = structural.
- Only structural claims may be exported. All others decay locally.