◉ Indra ORIGO LABSSource & releases ↗
INDRA / USER & DEVELOPER GUIDE

Audit, provenance and analytics

Use Audit to inspect event records, model/provider attribution and available verification results. The workbench surfaces hash-chain/signature evidence to make later changes detectable within the recorded sequence. Exported verification should include the relevant public key/check information; keep private signing material out of Git and shared screenshots.

Cryptographic verification is not proof that a model's statement is true. It does not guarantee that every external action was logged, that a compromised host was honest, or that a local clock is correct. A local signing key is controlled by its host. Treat the ledger as inspectable provenance, not irreversible truth.

Analytics are local observations. Compression, auxiliary vision calls, retries and provider-side billing can differ from local token counts. Use provider billing as authoritative for spend. A selected model in settings is weaker evidence than the actual recorded call attribution plus observed output; inspect both.

Do not publish complete personal logs or conversation databases as "proof." The gallery shows a reviewed view of the demo ledger. A real provider key, phone session or signing key is never required for a judge to inspect the public example.