Systems make claims.
Arcifact proves which ones are earned.
Arcifact turns declared constraints into exact, independently verifiable answers. Each instrument is narrow. The method behind them is not.
Exact · source-bound · independently verifiable
// § 01 · the common failure
The claim outruns the evidence.
A skeleton argument relies on an authority the register has never seen. A merge gate turns green without covering every check the team meant to require. An agent reports an action it cannot show it performed. Different systems, one failure.
Arcifact models what the declared constraints actually permit, determines what the evidence settles, names what would settle the rest, and binds the result to its source so someone else can check it. Checking me must not require trusting me.
// § 02 · now · arcifact authority
Every authority in the document, checked against the register.
For UK litigation. Arcifact Authority reads a filing and checks each recognised citation against the published copies at The National Archives’ Find Case Law and legislation.gov.uk: the citation resolves, the case name matches, the quotation is verbatim, the pinpoint holds. Each run ends in a sealed record with a standalone verifier that recomputes every claim from the register’s bytes, offline, with none of my code. Where the register cannot decide, the verdict is unresolved and names the fact that would settle it.
// § 03 · arcifact gate
A green merge gate is a claim. Check what it proves.
GitHub Actions can run dozens of validations while branch protection requires one aggregate status. Arcifact Gate reads the declared workflow and finds the ways that status can turn green without the validation behind its claim succeeding: what it misses, whether it can fail at all, what it accepts as passing, and what it cannot see because the work is in another file. Every finding is bound to your exact file bytes and ships with a verifier that recomputes it from your copy, with no network access and none of my code.
It proves whether a job sits inside the effective merge closure. It does not decide whether it ought to. That remains your policy, and the report says so.
// § 04 · the method
One method. Several instruments.
01
Model
Read the declared source, constraints and evidence boundary.
02
Resolve
Determine what is certain, what is possible and what is impossible under those constraints.
03
Settle
Where a claim is unresolved, name the missing fact that would decide it. Unknown stays unknown.
04
Bind
Attach the result to the source and issue a record another party can verify independently.
// § 05 · model evidence
AI makes things up. Prove yours doesn’t.
The method was built here, on the hardest case: holding a language model to what its evidence supports. Frozen instruments it cannot game, thresholds set before the run, and results anyone can recompute on their own machine. It remains the deepest instrument and the public research programme behind the rest.
// § 06 · proof, not persuasion
Watch certainty get earned.
The Oracle is the method running live: many admissible worlds, an unresolved claim, the one fact that settles it, and a count you can reproduce. Every instrument ends in the same place, a source-bound record and an independent verifier, because distrust is the intended first response.
// § 07 · start
Start with one system and one claim.
For Arcifact Gate that means a private read of one repository and its merge policy, returned as a source-bound report with a verifier you can run yourself. For a model or agent release it means one instrument, thresholds agreed in writing first. Either way, nothing is published without your approval.