Kijestic Acceptance 0.2.1. In private validation.
Don't trust done. Check it.
Say what done means before the work starts. Kijestic Acceptance checks the work against it and shows you what passed, what failed and what still needs proof.
In private validation.
Designed to run on your own Windows machine, alongside the AI coding tools you already use.
good -> ACCEPTED passed: revenue_reproduces, note_sections, note_figure_matches, no_guarantees clearly_written: MISSING; no evidence: add a probe, or (judgment checks only) a review claim supported: The revenue figure reproduces from the model inputs. claim withheld: The note is clearly written. bad -> REJECTED revenue_reproduces: FAIL; computed 3000 != claimed 3200 note_sections: FAIL; heading_missing:'Assumptions' no_guarantees: FAIL; forbidden_present:'guarantee'
The rule that matters
An agent saying its work passed is a claim, not evidence.
AI agents report that the tests pass, the page is live and the source says what they quoted. Sometimes that is true. For factual checks, Kijestic Acceptance does not take the report. It runs the checks itself and records what it could show.
If an agent hands in "tests: pass", that is recorded as the agent's claim, and the check stays open until the evidence is there.
What a run does
Contract, evidence, verdict, receipt.
-
Contract
Before the work, write what done means as checks that could fail, each tied to a deliverable: a file, a folder, a URL or a piece of text.
-
Evidence
The evaluator runs each check itself: a command you allow, an HTTP request, or an inspection of the file. The work can be done anywhere, by an agent, a script or a person.
-
Verdict
Accepted, staged, rejected, waiting on owner, or contract invalid. Staged means the evidence is missing or inconclusive.
-
Receipt
A JSON record of every check, every piece of evidence and where it came from, and which claims are supported and which must be withheld. Anyone holding the receipt can check it again.
Reading a verdict
Accepted is not released.
Accepted means every blocking check in the contract passed, for this exact version of the deliverable, on evidence the evaluator could admit. It does not mean:
- The contract asked the right questions. A weak contract gives a weak acceptance.
- The work was released. Every receipt says release: UNRELEASED.
- The intended outcome happened. Every receipt says realized_outcome: UNMEASURED.
- Anyone is authorized to act on it. Every receipt says grants_authority: false.
- The receipt came from who it says. Receipts carry SHA-256 digests, not signatures.
{
"format": "kijestic.acceptance-receipt/2",
...,
"verdict": "REJECTED",
"states": {
"acceptance": "REJECTED",
"release": {
"status": "UNRELEASED",
...
},
"realized_outcome": {
"status": "UNMEASURED",
...
}
},
"grants_authority": false,
...
"integrity": {
"method": "sha256-canonical-json",
"signature": null
}
}
Evidence
Tested.
| Automated tests | The full suite passes on Windows with Python 3.12. |
|---|---|
| Security review | Four rounds of adversarial review by a separate AI session from the same vendor; round four left nothing open at critical or high. Our own review, not a third-party audit. |
Why we built it
Agents told us work was done when it was not.
False "done" reports from AI agents are a recurring, documented problem in our own work. A result handed in by the thing being checked is a claim, not evidence.
So in Kijestic Acceptance the evaluator collects its own evidence for factual checks, and anything the caller supplies is labelled asserted.
Your control
Built to stay in your hands.
- Runs on your own Windows machine. No telemetry and no hosted service.
- Command checks stay off until you turn them on.
- Anyone holding a receipt can check it again.
- Commands you allow run with your own account's permissions, so you decide what a contract may run.
Want AI systems built and run for your business? That is Kijestic AI.
Questions: kelvin@doorstopper.io
Kijestic Acceptance is a product of Kijestic.