AUD-PUB-DEPLOY-001Published version integrity
Both checksum sets are valid.
View structured evidence
{
"manifest": {
"ok": 563,
"total": 563
},
"delivery": {
"ok": 564,
"total": 564
}
}ClarioDB does not ask for blind trust: each public assurance states its status, evidence, date and assurance level.
No external certification is currently claimed. The roadmap and permitted wording are permanently documented.
Open the reference documentAUD-PUB-DEPLOY-001Both checksum sets are valid.
{
"manifest": {
"ok": 563,
"total": 563
},
"delivery": {
"ok": 564,
"total": 564
}
}AUD-PUB-AGENT-001The shipped protocol supports pinned identity, anti-replay and signed attestations.
AUD-PUB-RETRY-001Mutation paths classify ambiguous outcomes and prevent automatic replay.
AUD-PUB-ATTEST-001Public Ed25519 signing is not configured yet; the report exposes only its SHA-256.
{
"state": "not_configured",
"public_key_base64": null
}AUD-PUB-CERT-001No CSA STAR, ISO/IEC 27001, SOC 2/SOC 3 or OWASP certification is currently claimed.
AUD-PUB-SESSION-001The browser receives only an opaque session identifier and the PHP session retains only an opaque handle. Derived keys and active credentials are encrypted separately in private runtime storage, time-bounded, and removed on logout.
{
"browser_cookie_contains": "opaque_session_id_only",
"php_session_contains": "opaque_secret_state_handle_only",
"encrypted_runtime_contains": [
"derived_vault_key",
"active_connection_credentials"
],
"encryption": "libsodium_secretbox"
}AUD-PUB-RESTORE-001ClarioDB provides asynchronous additive restoration with terminal verification. For Direct connections, recent protected archives can resume from an atomic checkpoint; ambiguous Agent outcomes are never replayed. Destructive replacement and automatic periodic restore tests remain uncovered.
{
"coverage": "additive_async_checkpointed"
}