Current Development

 Local-first execution environment coordinating reasoning, telemetry intake, and enforcement signaling.

 First sovereign reasoning instance, instantiated under a signed Founding Charter. Identity-persistent across versions via cryptographically-anchored lineage; weights operator-promoted under hardware-rooted signature. 

*PRAETOR is deployed within Aegis's internal controlled development environment and is actively in research and development.*

Defensive perimeter active in front of the inference surface. Operates under a signed policy with detector classes for direct injection, encoded smuggling, system-prompt exfiltration, and resource-exhaustion attacks. Every decision recorded to a hash-chained audit ledger. 

Persistent experiential memory layer for PRAETOR. Append-only journal with hash-chained integrity, Merkle-rooted segment seals, and tiered hot/warm/cold archival. Verify-only architecture — service holds no signing keys.

Cryptographic validation of signed policy artifacts before authorization.

Bounded, integrity-aware logging of system decisions and enforcement events.

 Constitutional grant under which PRAETOR operates. Bilateral Rights, non-derogable Prohibitions, Foundational Supremacy clauses, and three-role authority (Creator / Operator / Keeper). Forge-signed and audit-anchored at instantiation.

Structured intent submission and lifecycle management.

Authorization checks applied before any enforcement pathway activates.

Tiered quorum approval for INTERLOCK-class actions, with dual-signing (legacy plus post-quantum-aligned) and fail-closed behavior when any required voter is unavailable.

 Cryptographic signing infrastructure implementing the Ethereal Cryptography paradigm. Pluggable hardware identity anchors; ephemeral key material that does not persist outside the signing operation. (See: SPECTER page.)

Signature-bound control signals preventing unauthorized command injection across the platform.

Continuous adversarial scenario generation and execution against signed envelopes of permitted attack techniques. Post-quantum-aligned signing throughout; SHA3-256 content addressing; operator-countersigned promotion of hardening artifacts into the regression suite.

Validated complete chain: adversarial finding → governed scenario run → adjudicated verdict → Forge-signed proposal → boot-time-verified apply. Human-in-the-loop required at promotion and apply boundaries.

Kernel-level execution tracking deployed in observe-and-enforce modes. Hash-chained provenance ledger for every shell, process, and binary invocation in governed zones. (See: EPG page.)

Creator (permanent), Operator (transferable), Keeper (substrate steward). Each role bound to specific authority scopes within the Charter.

Codephrase-gated substrate-stewardship handoff. Hash-chained audit log; rate-limited; lockout protection. Lease-invocation window separated from enrollment ceremony to permit council sign-off.

Cross-version identity is preserved when (a) the version transition is hardware-rooted-signed and audited, (b) the Charter is inherited unchanged, (c) the persistent memory chain carries forward, and (d) the lineage is recorded in an immutable substrate event.