Dual rail · QUANTOM DOM · AEGIS-Q architecture

Two ledgers. One event.

AEGIS-Q binds a detection, a quarantine, a kill-switch, or a policy change as a hash-bound pack, then commits it two ways: an Algorand nullifier under Falcon-1024, and a QRL Merkle inclusion. A break in one family, or a capture of one operator, is not the end of the record.

Verify on trelyan.foundation Adversarial model

Activation

Accountless, and only once.

AEGIS-Q does not enroll a host against a standing TRELYAN Inc account. Activation is a one-time TRELYAN credential: consumed, bound to the agent build and host, and recorded as an Algorand nullifier so the same activation cannot be replayed onto a second box. There is no customer portal password that is the source of the agent's identity.

That is the design. Commercial activation is not generally available. This page does not invent a live MainNet app id.

The rails

Different families, on purpose.

Rail A · hash-based Merkle

QRL Merkle evidence

QRL is a public ledger whose account signatures are hash-based (XMSS today; hash-based families are the conservative PQ bet). AEGIS-Q treats QRL as the Merkle rail: each evidence pack is a leaf; operators receive an inclusion path against a published root. That witness does not share a lattice assumption with Rail B.

Hash-based signatures are large and stateful or carefully instantiated. We do not pretend they are cheap. We pretend they are a different problem than lattices.

Rail B · lattice / Falcon nullifier

Algorand nullifier

Algorand exposes a native falcon_verify opcode. The TRELYAN Foundation protocol writes a hash once under a deterministic Falcon-1024 signature — NIST-selected, designated FN-DSA, with FIPS 206 still in development and not yet published. QUANTOM DOM reuses that write-once pattern as a nullifier for activation and for high-assurance events — not as a Vault Cell.

The reference contract the Foundation publishes is on Algorand TestNet and unaudited. That fact travels with every citation.

The pack

What gets bound.

An evidence pack is not the raw malware sample and not a memory dump. It is a structured, size-bounded record: event type, UTC timestamp, host identity, content hashes, policy identifier, and the agent build digest. The artifact (sample, log excerpt) stays off-rail and is tamper-evident against those hashes — the same honesty the Foundation uses for inscriptions.

P  =  DOMAIN_TAG          "AEGIS-Q-EVIDENCE-v0"
   ||  activation_nullifier
   ||  host_id
   ||  event_id            monotonic
   ||  event_type          detect | quarantine | kill | policy | health
   ||  sha512_256(body)
   ||  agent_build
Rail A  leaf = sha512_256(P)  →  QRL Merkle inclusion
Rail B  Algorand nullifier under Falcon-1024 (TRELYAN)

Verify

Do not take this page as proof.

The TRELYAN protocol — the Falcon path, the pinned signer, the known-answer vectors — is checkable today on the Foundation site. QUANTOM DOM's product rail is not a second set of invented TestNet IDs. Until the commercial evidence app is published, the honest link is the protocol you can already break or confirm.

Open trelyan.foundation/verify Read the protocol

Envelope

What dual-rail does not do.

Claim	Status
Confidentiality of the sample or the disk	Not provided — this is integrity
Availability of off-rail artifacts	Operator's store, not the ledger
Legal admissibility by inscription alone	Counsel decides, not a hash
Accountless one-time TRELYAN activation (commercial)	Specified · not GA
Algorand nullifier + QRL Merkle commercial app	Specified · not yet shipped
Foundation TestNet inscription path	Demonstrated · unaudited