Most databases assume data is correct. Real systems are not like that. Sources are incomplete, facts conflict, knowledge evolves, and mistakes propagate. AttestDB is built for that reality.
A claim is a statement with a source, a timestamp, and a confidence value. That gives you a storage layer that can track where knowledge comes from, detect contradictions, update when facts change, and reason over uncertainty.
If you are building AI agents, RAG systems, knowledge graphs, research pipelines, or long-running reasoning systems, you have already seen the same failure mode: answers without sources and no clean way to retract bad information.
Instead of bolting provenance, correction, and temporal logic onto an existing database, it makes them first-class in the write path and query model.
The point is not just adding information. The point is letting the system know when previously trusted knowledge stopped being safe.
attest add "Company policy requires SOC2" \
--source policy.pdf \
--confidence 0.9
attest retract --source policy.pdf
# dependent claims are flagged,
# invalidated, or updated automatically
Store the reason to believe a statement alongside the statement itself.
Conflicting claims can coexist with evidence and confidence instead of being flattened away.
Invalidate a source and surface what downstream knowledge is now stale or unsafe.
Reason over when a claim was asserted, corroborated, weakened, or superseded.
Model uncertainty directly instead of treating every stored assertion as equally trustworthy.
Single-file database, Rust engine, and no requirement to run a service just to get started.
AttestDB fits systems where sources matter, facts evolve, and you need the system to know when it is no longer safe to trust an answer.
Start with the quickstart if you want a working install, or jump into the docs if you want the API, schema, and implementation details.