What is Horae?
Horae owns discovery, admission, capability reduction, composition planning, session identity and local lifecycle and freshness supervision in The Fates.
Open source / discovery and supervision
Project Horae
A composition and supervision runtime for discovering, admitting and coordinating approved capabilities.
Last reviewed 31 August 2026
Active development
Public TypeScript repository; licence not identified in the reviewed metadata.
What problem does it solve?
Runtime systems need to know which capabilities are available and compatible without allowing discovery metadata to become action authority.
How does it work?
The public README describes canonical parsing, peer registration, readiness and exposure-aware capability planning, deterministic conflict rejection, bounded session identity and inspection commands.
What does it not own?
Horae does not own policy, approval, governed execution, memory truth, provenance, provider routing or credentials. Those responsibilities remain with other boundaries.
Discovery reduces uncertainty; it does not grant permission.
Capability planning may reduce availability, but it must not silently expand what a runtime is allowed to do.
Source and evidence
Inspect the discovery boundary.
- View source repositoryPublic repository
- Read documentationVerified docs directory
FAQ
Does Horae authorise tool calls?
No. Its stated responsibility is discovery, admission, composition and supervision. Ananke remains the action-policy and execution authority.
Can a healthy peer be trusted automatically?
No. Peer health and readiness remain peer-reported; Horae’s lifecycle and freshness facts are local facts.