AEGISCONTROL

WORM transparency and SCITT profile

AEGIS can wrap an execution, restoration, observer or audit artifact in a signed transparency statement and receive a signed, hash-chained receipt. A WORM sink may then retain both the statement and the receipt as immutable S3 object versions.

Implemented format

src/transparency.ts implements the versioned JSON schemas aegis.scitt-statement.v1 and aegis.scitt-receipt.v1. The receipt commits to the statement hash, log sequence, previous receipt hash, issuer, issue time and retention endpoint. Local append operations reject a conflicting existing record instead of overwriting it.

This is a SCITT-inspired signed-statement and receipt model. It is deliberately not described as wire-compatible IETF SCITT: the lab does not implement the COSE envelope, registration policy or interoperable transparency service protocol. That claim requires conformance vectors and an independent implementation.

S3 Object Lock sink

src/s3-worm-sink.ts writes a unique object version with:

Governance mode is intentionally not used because a privileged operator can bypass it. Bucket versioning and Object Lock must exist before the first write. Keys, credentials and the storage administrator must be outside the control plane's administrative domain in production.

Reproducible local campaign

Run npm run sota:worm:qualify. The bounded lab starts a digest-pinned RustFS service on localhost, creates an Object-Lock-enabled bucket, archives a signed statement and its receipt, confirms that deletion of the exact version is rejected, restarts the service, and confirms the retained version and COMPLIANCE date. Docker is stopped in finally.

The final 2026-08-29 run used RustFS 1.0.0-rc.1, confirmed the exact-body SHA-256 through HEAD, produced statement hash f4efb08f..., transparency receipt 5ef827ce..., archived receipt 78529a74..., rejected exact-version deletion and preserved COMPLIANCE retention through restart until 2026-08-30T21:16:44.252Z. Its machine-readable result is retained under .aegis-lab/reports/.

This proves local API and retention behaviour, not that the same host cannot be destroyed by its administrator. A production evidence anchor must be an external account or provider with legal retention, dual control, independent billing and tested export/recovery.