Security model

What the cryptography controls — and what it does not.

Verification establishes integrity and policy satisfaction against supplied trust material. Everything it cannot establish is stated here, on purpose.

Implemented controls

What the build enforces.

  • Signed metadata binding prevents undetected substitution of key ID, authority ID and creation time.
  • Record context, policy, purpose, record ID, nonce and predecessor are included in the protected signing input.
  • Encrypted-envelope recipient identifiers, key fingerprints, suite parameters and application context are authenticated as additional data.
  • Verification fails closed for malformed records, unknown formats and algorithms, unavailable keys, resolver failures, untrusted authorities, revoked or unusable keys, unsatisfied policy and replay-check errors.
  • Resource limits constrain nesting, canonical size, object keys and signature count.
  • Forbidden prototype-related keys are rejected.
  • Strict schemas reject additional properties in frozen protocol structures.
  • Deterministic fuzz cases confirm malformed input is rejected without verifier exceptions.
Required limitation

Cryptographic verification establishes integrity and policy satisfaction against supplied trust material. It does not establish that the originating workload was authorised, that every relevant event was captured, that a private key was never compromised, or that declared time is independently trustworthy.

  • No durable replay database ships in the SDK. RC3 defines the replay-store boundary; a deployment must supply atomic, persistent replay claiming.
  • No vendor-specific KMS, key registry or trusted-time integration ships in RC3.
  • The default Node provider is not a substitute for managed production key custody.
  • No second-language verifier has yet demonstrated portability independently of JavaScript.
  • No independent cryptographic audit or production-system penetration test is claimed.
  • FIPS validation, Common Criteria certification and formal verification are not claimed.
  • The website is informational; it does not currently receive or retain evidence submissions.