DAEPOLIS is designed so a serious reader can move from source intake to claims, evidence, review, ledger state, method checks, external anchors, and later error memory. The proof path does not ask the reader to trust a fluent answer. It shows the operational objects underneath it.
This is the minimum public path a DAEPOLIS record should be able to show when it is mature enough for outside inspection.
Source packs and uploaded documents become excerpts, candidate claims, source metadata, source gaps, and hardening tasks. Unverified material can assist a record, but it cannot silently become source-grounded proof.
Claims are separated from the generated brief so each assertion can carry support status, verification state, evidence links, falsifiers, and later updates or disputes.
The ledger distinguishes provisional, source-assisted, source-grounded, contradicted, primary-supported, expert-supported, journalistic-only, inferred-only, stale, and contradicted states.
A Decision Record holds the question, decision context, claims, evidence graph, forecasts, dissent, review state, monitoring triggers, and outcome memory.
Creation, review, challenge, correction, approval, dispute, export, and retraction events become immutable record events instead of disappearing into chat or document history.
The public ledger and API expose claim proof, forecast criteria, preregistration hashes, resolution state, canonical claim activity, and audit completeness without exposing private source material.
OpenTimestamps anchors SHA-256 digests only. Calendar-pending proofs stay pending; only Bitcoin-attested proofs are labelled anchored.
Deterministic game-solver receipts, base-rate gates, adversarial audits, and bottom-line revisions can attach to the ledger chain when a method check weakens or rejects the visible judgement.
Resolved misses can carry Brier score, attribution payload, source adjustments, argument adjustments, evaluator status, and repair instructions for future analyses.
The public trust surface is split across concept, demo, ledger, JSON, and integration views. Each view answers a different due-diligence question.
The first live proof-path target is the public PFA Defence End-Use seed. Its JSON surface at `/api/proof-path` compiles one public analysis into claims, evidence links, a Decision Record, immutable events, hardening tasks, and forecast/resolution hooks.
Publication is a proof-readiness boundary, not a visibility switch. Records that cannot show the minimum chain should remain private, draft, pending, or visibly incomplete.
The path proves that DAEPOLIS creates durable judgement objects: claims, evidence, events, hashes, reviews, method receipts, and correction memory. It does not prove that every judgement is correct. It makes correctness, incompleteness, dispute, and later failure inspectable.