EVENT HORIZON // SECURITY BOUNDARY

EACH SUCCESSFULLY SEALED CAPSULE CARRIES
ITS INTEGRITY RECORD.

Security is enforced through verified identity, least privilege, ciphertext storage, integrity-gated egress and Company-controlled promotion.
01

Authenticated passage

Identity is derived server-side from the hosting authentication boundary and HMAC-bound to a protected secret.

02

Recipient-bound matter

Vault capsules use fresh-nonce AES-256-GCM and bind ciphertext to the intended recipient scope.

03

Integrity-gated save

Before a hosted answer returns, AVORBYSS commits event and usage evidence. When recipient sealing succeeds, authenticated encryption and an exact digest bind the saved capsule to its recipient scope.

PRIVATE CORE

A client surface is not the Singularity Core

Customers receive only the interface and bounded capabilities needed for their chosen passage. Commerce secrets, identity keys, policy authority and private operational records remain behind the server-side control plane.

NODE CONTROL

Versioned, pinned, integrity-bound

Runtime manifests bind approved revisions and exact integrity metadata. Server-side authorisation, rate limits and Company-controlled gates govern access to protected capabilities.

INCIDENTS

Contain, preserve, report lawfully

Protective controls isolate, rate-limit and record suspected attacks. Security concerns can be submitted through the protected support route for review.