Identity, evidence, and coordination across tools.
The concepts behind Aevos
Events and causal references can help make the history of work inspectable.
Routing and policy help express who can act, under which conditions, and what evidence is needed.
Signals from workspaces and other sources can provide context for coordination and review.
CLI, adapters, and app surfaces offer different ways to interact with the system; capability and maturity vary by surface.
Aevos separates evidence, delivery, execution, and authority so that a visible result is not mistaken for permission or completion. Consult each component’s license and documentation for its terms and current capabilities.