ALFRED — defense
Described role: observe security signals, assess anomalies and propose defensive measures. Performance and limitations must be documented.

Accueil›trinity
Architecture — limits to document
TRINITY organizes defense, governance and coordination functions. This description presents their architectural roles; it does not certify the operational status of hubs or functions.
Described role: observe security signals, assess anomalies and propose defensive measures. Performance and limitations must be documented.
Described role: assess proposed actions against governance rules and provide for a human veto. TEE/HSM hardware anchoring remains in integration.
Described role: coordinate authorized responses and study operation under degraded conditions. Distribution across jurisdictions belongs to the roadmap.
ATHENA is presented as an automated conversational interface. Its responses may contain errors and are not technical or legal validation.
METATRON aims to produce and verify records. The J3 demonstration remains to be validated; no operational proof registry or completed audit is established here.
View limitations and evidence on the Foundation websiteASVPRET connects seven architecture genes to rules, protocols and tests. Authority remains human. Architecture framework. Series 8 is under construction, demonstrated in a staging environment as milestones are reached.
Read the ASVPRET doctrineInternal conversational reception prototype, presented with fictional data. No service available for sale or release schedule is announced.
White paper · ALPHA specification
The Series 8 white paper describes a traceable processing chain: classify, decide, produce evidence, then prepare it for examination. The steps below present this ALPHA specification.
A versioned reference classifies cases into ST, SN, CR, CS and INT categories. Each revision receives its own hash.
The engine describes three decisions: ALLOW, DENY or ESCALATE, with structured reasoning and contradiction detection. In ambiguous cases, the specified rule is DENY.
The integrity proof uses SHA3-512 in tests. An append-only log links entries by hashes and aggregates them into a deterministic Merkle root.
Reports tailored to auditors, courts or regulators redact sensitive data. An independent Rust verifier is compared with the Python reference.
SVP-X describes an Evidence/Audit sandbox using OpenAPI 3.1 with separate permissions. Némésis provides for supervised Tier 2 forensic compilation; its dependencies remain simulated in this publication.