EVIDENCE LAB / LIVE DATABASE
See why the answer changes.
When new evidence changes the answer, see what changed and why.
Isolated browser session · no API key
WHEN TO USE IT
THE SIMPLER ALTERNATIVE
Waiting for evidence
An operative answer is the current selection. Only a resolved status indicates sufficient support under this demo’s configured policy.
Why MoolBase reached this state
PROVENANCE, NOT JUST VOLUME
Evidence ledger
Copies sharing one evidence family do not become independent corroboration. Retired evidence remains visible in this ledger and in nonoperative audit records.
| Observation | Evidence family | Effect | Certificate | Lifecycle |
|---|---|---|---|---|
| Add an observation to begin. | ||||
Try your own evidence
FROM DEMO TO YOUR APPLICATION
Same engine. Runnable examples.
The browser runs MoolBase’s actual storage and reasoning code in a worker. These are realistic synthetic fixtures; customer deployment results have not been measured.
Use the native example for disk persistence. This browser sandbox keeps database files only for this page session. Reopening checks file replay within the session; refreshing starts fresh.
// Store provenance in MoolBase
edge.metadata["source_id"] = "pool-trace";
edge.metadata["evidence_family_id"] =
"family:database-traces";
db.put_edge(edge, &edge_id);
// Let the production runtime evaluate it
CompleteHypoKoshRuntime runtime(db);
auto result = runtime.reason(
query_vector, signature, options);
// Preserve state between evidence updates
options.prior_epistemic_state = prior;Verification results and boundaries