EVIDENCE, EXPLAINED

What stands behind
a checked copy.

The deterministic verifier decides preservation. Investigation models can request evidence and revise hypotheses; they cannot change the comparison or invent missing answers.

Files first

Original ZIPs are retained unchanged. Namespace-aware XML comparison preserves ordered repeat occurrences, meaningful text and version identities. Each referenced filename slot is checked against actual retrieved media bytes. Equal hashes do not prove that every required slot was accessible.

A connected investigation with receipts

In the configured synthetic environment, bounded evidence is normalized to small CSV tables queried through the actual local Zetaris deployment. Raw source objects stay private. This is evidence materialization, not heterogeneous in-place federation.

The pinned Meterless World Model stores provenance and append-only hypothesis revisions. Reads select unresolved work. Nightshift runs a bounded investigator/reviewer loop; actual serving-model identity and provider-reported usage are retained where available.

Source/query rows, graph revisions and sanitized model diagnostics are available within a connected saved check. Provider failure remains visible; it never silently substitutes sample evidence.

Review, write, read again

Permitted recovery uses the configured isolated synthetic ODK Central project. Plans bind original identifiers, target identities, source hashes and preconditions. The engine persists write intent, checks the target immediately before each write and uses fresh XML/version/media readback with the same verifier afterward.

Conflicts and unsupported historical writes remain manual. Central attachment uploads have no atomic compare-and-swap; the test project must exclude concurrent external writers.

REPLAY · ACTUAL CENTRAL RECOVERY CHECK

One record. No duplicate.

The synthetic recovery previously uploaded a missing submission with its original identifier. Fresh XML, version metadata and attachment bytes were checked again on 2026-10-26.

Before recovery
Submission missing
After fresh readback
Matching copy preserved
Matching instances
1
Uploads during recheck and repeated Apply
0
Original files
Hashes unchanged

This is a saved receipt of actual server verification, not a new upload performed by this page.

Download the approved redacted recovery summary

The summary contains counts, timestamps and hashes only. Full reports and original evidence remain private. Hashes identify bytes; they do not authenticate a server on their own.

Three honest modes

Sample
Authored synthetic evidence, actual local comparisons, no external service or model calls. Illustrated readback is labelled separately from an upload.
Replay
Supplied captured evidence with its reference and scope. Replaying a capture is not a live server query.
Connected
Actual configured test services, native Central capture and recorded attempts. Investigation completion, source coverage and recovery status remain separate.
Inspect a sampleRead scope & limitations