Open source / umbrella architecture

The Fates

An umbrella architecture for composing capability discovery, memory, orchestration, contracts and governed execution.

Last reviewed 31 August 2026

Provisional integration

Current public integration is an inspection-only Stage-A slice.

What is The Fates?

The Fates is the umbrella name for a set of cooperating runtime projects. The public integration repository is a control and evidence layer, not a runtime and not a copy of each component’s source.

What problem does it solve?

Agent systems need a way to discover capabilities without silently gaining permission to act. The architecture gives discovery, memory, orchestration, contracts and execution distinct responsibilities.

How does it work?

Project Adrasteia defines portable contracts. Horae discovers and composes admitted capabilities. Mnemosyne governs memory and provenance. Ananke governs policy, approval and execution. Moirae Code and Moirae Console provide host and human-facing surfaces.

Current status and limits

The public integration README describes a provisional compatibility set and inspection-only integration. Governed execution, qualified memory handoff, durable recovery and content preflight are not claimed as available in that slice.

Architecture in one view

Agent / hostRequests work
HoraeDiscovery and composition
AdrasteiaContracts and compatibility
MnemosyneMemory and provenance
AnankePolicy, approval and execution
ConsoleHuman-visible evidence
Capability discovery is not authority to execute.

A discovered tool can be described, inspected or planned without being authorised to disclose information or change the world.

Components

Follow each boundary.

Horae

Discovery and supervision.

Source and evidence

FAQ

Does The Fates guarantee secure AI execution?

No. It is an evolving architecture with explicit boundaries and current limitations. The public status is provisional and does not claim perfect security.

Does finding a capability authorise an action?

No. Discovery and authority are deliberately separate. Policy, approval and execution belong to the governed execution boundary.