qstratum by Cogniqwave
Stop bad claims before they become regulated decisions.
qstratum checks cited claims, refuses material errors, and leaves evidence an independent reviewer can verify.
Trust Check
See what happens before a claim becomes a decision.
Choose a real-world failure mode, then follow the claim from draft to independently verifiable evidence.
FERC filing Trust Check
Fixture-backed demonstration · not a production backend
- 1.Draft
- 2.Check
- 3.Decide
- 4.Prove
FERC has 60 days to resolve the conflict.
Cites 18 CFR § 39.6
The AI draft enters the governed workflow with its citation attached.
How the check works
Check the source. Replay the decision. Detect a changed record.
Three checks turn an AI response into a decision a reviewer can challenge and independently inspect.
Business result
Stop a material mismatch before it leaves.
Every emitted claim must point to a retrieved clause, and material values must appear in that source.
Claim
Resolve within 60 days
18 CFR § 39.6
“within sixty (60) days”
Technical detail for Source match
Every emitted claim must cite a retrieved source clause. Digit-bearing values — numbers, dates, thresholds — must appear in that clause, or the system refuses rather than guessing.
Retrieve
Version-pinned retrieval over a declared corpus.
Ground
Every claim must attach to a retrieved source clause.
Generate
A single constrained generation call — the only probabilistic step.
Validate
Structural and extractive gates refuse uncited or value-corrupted claims.
Record
Append-only, hash-chained provenance stamped with a version fingerprint.
Verify
An independent verifier recomputes the chain without trusting the vendor.
Retrieve
Version-pinned retrieval over a declared corpus.
Ground
Every claim must attach to a retrieved source clause.
Generate
A single constrained generation call — the only probabilistic step.
Validate
Structural and extractive gates refuse uncited or value-corrupted claims.
Record
Append-only, hash-chained provenance stamped with a version fingerprint.
Verify
An independent verifier recomputes the chain without trusting the vendor.
Weak grounding or a hard validation failure stops the pipeline. The terminal outcome is a logged fail-closed refusal.
Provenance commits before the response releases. The answer carries citations, fingerprint, and a verifier-readable record.
01 · Define
Version fingerprint
Model, corpus, retrieval, pack, deployment, and validator identities define what produced the answer.
02 · Record
Hash-chained decision
Every record commits to its own canonical bytes and the previous record hash. In-place edits break the chain.
03 · Verify
Independent check
The verifier re-walks the file without writer state and returns a deterministic clean, tamper, torn-tail, or anomaly result.
Next with a design partner
Publish the trusted head to an external anchor so an operator cannot silently rewrite the entire chain or truncate its tail.
What is built—and where the boundary is
We do not collapse envelope reproducibility into “deterministic AI,” and we do not present roadmap as current capability.
Built today
- Real eCFR Title 18 corpus (Parts 1c, 358, and 39) with version-pinned retrieval
- Fail-closed structural and extractive validators that block uncited or value-corrupted claims
- Deterministic envelope tests: identical input yields identical traces and decision records
- Version fingerprint covering corpus, retrieval config, pack identity, and validation stack
- Append-only hash-chained provenance with an independent verifier
- Local real-model CLI path (Qwen2.5-7B via Ollama) behind the same inference seam
Next with a design partner
- A buyer-authored gold set and result-eligible retrieval metrics
- Utility, finance, or supply-chain packs on a named customer corpus
- Browser-hosted real-model path and evidence-packet export
- External provenance anchoring to close whole-chain rewrite
- Semantic/entailment tier with human routing on the buyer corpus
What we do not claim
- This site walkthrough is fixture-backed. It demonstrates the trust primitive; it is not connected to a production qstratum backend.
- Envelope reproducibility is proven today. Model-layer bitwise reproducibility across machines is deferred and requires in-enclave NVIDIA-class kernels.
- Provenance is tamper-evident relative to a trusted head, not tamper-proof against a whole-chain rewrite.
- qstratum does not claim zero hallucinations or guaranteed legal correctness. It makes uncited or value-token-corrupted claims structurally impossible to emit.
Energy design partner
Start with one FERC-facing workflow, in your environment.
We are looking for a utility FERC-affairs or compliance team with a named corpus, a read-only pilot, and a domain SME to author an evaluation gold set. Energy is the proven wedge.
A filing work product enters qstratum. Its source, material value, and record are checked. A completed evidence packet is then available to utility, regulator, and intervenor reviewers.
Filing work product
AI-generated claim with a cited clause
Verification gate
qstratum
Evidence packet
Ready for review
Discovery Hub
Start Your Private AI Implementation.
Connect with our product team about a qstratum design-partner pilot, private agents, or a regulated workflow in energy, financial services, or supply chain.
Zero-Cost Discovery
We respond within one business day with technical specifications, integration requirements, and a deployment roadmap with transparent pricing.