Measured
A bounded detector or command produced evidence for the inspected scope.
Evidence
See what changed, what is missing, and what needs attention next.
Strata19 records what was checked, the evidence behind the result, and what remains uncertain. A successful bounded check is evidence for that check, not a general proof of correctness or security.
The Verification Pipeline
Seven stages. One recursive loop.
When an agent finishes work, the evidence pipeline picks up — verifying claims against explicit criteria, reanalyzing impact, collecting evidence, measuring convergence, and deciding whether to accept or reopen. The loop runs until the numbers agree.
STAGE 01Completion Claim
Did the agent actually do what it says?
An agent finishes work and submits a claim — not a completed status. It declares what it did, what files changed, and what evidence it believes it produced.
Data flow
Agent claim
Str19 reads
Structured assertion
- Claims include: what was changed, which files, which tests passed
- The claim references the acceptance criteria defined in the spec
- Without a spec, acceptance criteria are inferred from test names and type coverage
How this is different: Before: you trust the agent's prose. After: the claim is a structured assertion that can be verified.
Measured, partial, and unmeasured are different results.
Partial
Some evidence exists, but unresolved edges, missing inputs, or limits remain visible.
Unmeasured
Strata19 has no evidence for the claim and does not turn absence into a pass.
Try it on an actual project.
No source code upload required for local verification. The pipeline runs on your machine against your repository.
Run local verification