The architecture
Let the model go wild. Then hold every line to proof.
Apodicta doesn’t muzzle the model. It attaches beside it and frees it from the inductive guesswork, not the creativity. The model stays free to explore, imagine, and propose its own theories. What changes is that its output then runs a gauntlet of 30+ rules of executable symbolic logic before a word of it can render.
One run, end to end
Creativity is encouraged. Only the output is bound.
1 · In
The prompt and the record
A question — or simply new discovery landing in the file.
2 · Interpretation
Apodicta says how to see
The interpretation logic tells the model what is relevant and how to read it — the coordinate system, in the authority’s own words.
3 · The model
Go wild
Explore, extract, imagine, propose competing theories. This is where the model is most free.
4 · The gauntlet
Gated by code
Every assertion must carry a cite. Every inference must carry a proof. Theories face reductio. Relationships need exact membership. 30+ rules, run on the model’s own output.
5 · Out
Proven, or quarantined
What passes renders with its receipt. What fails is labelled and set aside — never silently.
The main idea — layer by layer
Trustworthy and inventive, at the same time.
Not a trade-off. Apodicta holds the ideas it invents to the same proof as the facts it verifies. Two of these layers keep the answer honest; two find new ideas — and all four run the identical proof.
Perception, fencedKEEPS IT HONEST
The model reads your material; every fact it lifts comes bound to a source. Unsourceable text never becomes a fact.
The gatesKEEPS IT HONEST
Every source must exist and actually support the claim, and every conclusion must follow by valid logic. What fails is quarantined — visibly, never silently.
The relationship engineFINDS NEW IDEAS
It connects your material at the level of shared forms — the idea beneath the words — and proves every hop, so real connections surface and false ones are excluded.
Theory generationFINDS NEW IDEAS
It proposes new explanations of your material and tests each by the same proof. A theory your material can’t hold is struck; only the grounded survive.
What the code actually does
Five gates, in series. Each one fails closed.
Stated plainly, this is the whole enforcement boundary — and every one of them is executable code the model never gets to touch.
The enforcement boundary · five gates, in series
- Existence. A quoted source must match a real passage in your material, word for word, or the fact is stillborn.FAILS CLOSED
- Support. A second, independent reader confirms the passage actually says what it is quoted for.FAILS CLOSED
- Exact membership. What a fact bears on is decided by exact match to the instruction’s own coordinates, never by word-proximity or “close enough.”FAILS CLOSED
- Inference-proof. Every conclusion must follow by valid logic from grounded premises: “after, therefore because” is struck on structure.FAILS CLOSED
- Render-gating and audit. Nothing renders that didn’t pass, and whatever fails is pulled into a labelled quarantine, never silently dropped.FAILS CLOSED
Fails closed means the default is refusal: a gate that cannot confirm something does not wave it through with a warning, it stops it. That is why there is no free-writing step for a fabrication to slip through — the model may always try to speak unverified, but it cannot land unverified. Retrieval alone does not get you there, for reasons set out inwhy retrieval does not stop hallucination.
The logic — 30+ executable rules
The relationship engine finds what’s connected, and proves the connection hop by hop.
Most of what matters in a pile of records isn’t in any one document. It is in the connections between them that nobody ever stated. Apodicta works at the atomic layer: every fact and every argument broken to its axioms, and two atoms may connect only through a link that points to something real and cited.
Relevance — what even gets considered
The interpretation logic decides, in the instruction’s own words, whether an atom bears on the question at all. Irrelevant material is set aside by rule, before it can colour a conclusion.
Relationship — connect, or exclude
Connections are decided by exact membership, not resemblance. A real link is surfaced with its proof; a false one is excluded — and “no connection” is a result the engine will state plainly.
Reductio — the hypothesis self-tests
Each theory is run against the record for contradiction. A fact that makes a theory impossible kills it: a real reductio ad absurdum, in code.
It proposes its own theories — safely
Using the same relationship logic, the engine generates competing explanations of the record, then makes each earn its place by proof. A wild theory isn’t filtered later; it simply doesn’t survive.
Universe A and Universe B are bodies of fact that never touch, and Universe C is a third beside them; travel a chain of cited links atom by atom and two of them turn out to be connected, carrying the proof of every hop. Where no cited path reaches, the dead end is a finding, not a blank: the connection is simply never asserted.