History and relationships
Events and causal references can make the history and relationships of work inspectable.
Architecture
Many surfaces.
A connected foundation.
Aevos brings identity, communication, and evidence into a shared operational context. The interfaces are different ways to see and work with that context.
How the pieces fit
A structure for work.
These layers describe the architecture. A surface can show evidence without granting authority to act.
Work across boundaries
Routing and policy help work move across environments with scope and ownership visible.
Meet the work where it is
Web, desktop, command line, and native surfaces provide different ways to interact with the system.
Explore surfacesKnow who and where
Identity and session bindings help distinguish an actor from the surface where it is currently reachable.
Keep action explicit
A view or a delivered message does not by itself grant permission or establish completion.
Explore boundariesSee what is known
Health, signals, and receipts can support investigation, with freshness and missing evidence made visible.
See it in practice
Follow a real interaction.
See how Codex reached an existing Claude session and what the observed interaction actually established.