Identity
The operator owns the principal. A change of model or session must establish continuity before authority carries forward.
Aevos · Platform
Agents can stay
where they work.
Aevos separates what an agent can execute from what its work is allowed to change.
The governing principle
Capability is not authority.
A harness runs agents.
Aevos governs the reality those agents are allowed to create.
Authority
Machine access is a capability. Admitting a change requires authority for that transition.
Settlement
A task can run while its result remains held. An expired lease does not close the work.
Sustained operations
Review where changes meet.
See what can move together, what is held, and what needs a decision.
Start with declared scope and potential overlaps. Preventive enforcement is still being activated; coverage depends on the path and environment.
A study of one operational role
Work carried across days.
A roughly twelve-day coordinator record follows reviews, holds, and a release handoff. The study examines what carried across sessions and what still needed a person.
Recorded activity is not completed work. Outcome totals, time saved, and unattended success remain unverified.
Three records, one boundary
History. Models. Limits.
Our history review identified lost updates. Two independent checkers agreed across 1,744,784 states of a bounded settlement model. A separate model explores the cost of parallel work.
The dated records separate checked findings, unchecked candidates, and exclusions. Model results do not prove implementation correctness.
Recorded episode · September 27, 2026
Keep parallel work reviewable.
See what can move, what is held, and why. This is a recorded account from one development session, not a live status view.
The responsibility
Review related changes before they land.
- Who carries the work?
- The coordinator in this recorded review; its checkpoint and return report the same durable identity.
- What is being carried?
- One change could proceed; the other needed a decision because its tests exposed a possible lineage break.
- Outcome reported by the study
- The original identity change was reported held. A later dispatch reports a revised approach; completion and settlement of that revised change are not established.
- Next step reported
- Implement the revised approach described in the later dispatch; completion and settlement still need evidence.
What needed a person?
The coordinator requested a decision. A later dispatch reports approval of a revised rule.
- 19:46 UTC
Tests reveal a problem
The study transcript contains test output showing two failures on the proposed identity change. One failure expected a child session to bind to its parent’s root.
Captured test output in the study transcript - 19:50 UTC
One change lands; the other is held
A journal event reports that a separate acknowledgment fix settled and the identity change remained held for the operator’s decision. The corresponding acknowledgment-fix merge exists in Git; that does not establish completion of the held change.
Journal report and a separately checked Git merge - 20:24–20:26 UTC
A checkpoint and return
The journal records a pre-compaction checkpoint, a session start, and a post-compaction resume under the same durable actor. A continuation summary carries the review context and intended next action forward.
Recorded checkpoint, session start, and resume - 20:27 UTC
Return to the decision
A later journal dispatch reports the decision: do not land the original change; implement a revised rule.
Recorded dispatch; source references below
Read the recorded account and evidence limits
Availability and verification are reported by the study, not independently verified by this page. References identify records in the source environment; they are not public links or live status.
Who carries the work?
- Availability
- partial
- Study-reported verification
- reported
Checkpoint, session start, and resume report the same durable actor. Attribution of the hold and dispatch to that actor relies on the transcript, not typed identity in those event envelopes.
nabi://syn/a3d1e8db-285b-49c3-8e35-0215c88c34c5nabi://syn/d6ce4fd1-9dd1-42a6-b6dc-7de9009b278anabi://syn/39408d59-1758-4ff4-b0df-023a41dce462
What context was selected?
- Availability
- partial
- Study-reported verification
- reported
A continuation summary carries the open question forward. A ContextPacket for this selection was not located.
Why was it routed to this actor?
- Availability
- unavailable
- Study-reported verification
- unverified
A RouteActionRecord for this decision was not located.
How does the result connect to prior work?
- Availability
- partial
- Study-reported verification
- checked
The events are shown in recorded time order; the available journal graph does not establish causal edges between the selected events. The separate S1 merge exists in Git.
nabi://syn/743d90fe-20b1-4668-9a89-52e335108486bfca3f645502b34144e78dcaaacf5ed2029930f4
Was the event included in an attested batch?
- Availability
- unavailable
- Study-reported verification
- unverified
An inclusion verification for the selected episode was not established.
What can happen next?
- Availability
- partial
- Study-reported verification
- reported
A dispatch reports a revised rule; its later completion and settlement are not established.
nabi://syn/546d5d97-c935-478e-b76c-d35ae8ba18b3
What remains unverified
- Events are ordered by recorded time, not an asserted causal chain.
- Attribution of the hold and dispatch to the coordinator relies on the transcript, not a typed actor in those event envelopes.
- The revised change’s completion and settlement are not established. Journal messages are reports; the separate S1 Git merge was checked.
Recorded episode · September 27, 2026
A release role
changes hands.
The operator said a release manager was about to compact its session, asked another agent to take over the version and changelog work, then supplied the prior manager’s handoff. This is a recorded episode, not a live view.
The responsibility
Take over version and changelog work and settle the reviewed change.
- Who carries the work?
- The incoming release coordinator, identified by a durable actor in the recorded session binding.
- What is being carried?
- Carry the prior manager’s handoff into the version and changelog work.
- Outcome reported by the study
- A settlement receipt is recorded and the candidate and resulting merge have the same Git tree. A later report held the release tag pending installation and smoke testing.
- Next step reported
- Installation and a smoke test, according to the later report.
What needed a person?
The operator requested takeover and relayed the prior manager’s handoff.
- 16:57 UTC
The work is assigned
The operator asks a second agent to take over version and changelog work. A version slice is declared against the then-current main commit.
Operator request and declaration receipt - 16:59–17:06 UTC
The handoff is carried forward
The first manager records a handoff. The operator relays it, and the next manager records that it has assumed the role and identifies the candidate under review.
Close and role-assumed receipts - 18:40 UTC
The version change is settled
A settlement receipt records the result. The referenced Git objects independently confirm the merge parents and that the candidate and settled commit have the same tree.
Settlement receipt and Git object check - 18:44 UTC
Release work remains
A later report says the release tag is held pending installation and a smoke test. The evidence here establishes settlement; it does not establish that the release was finished.
Reported state at the time
Read the recorded account and evidence limits
Availability and verification are reported by the study, not independently verified by this page. References identify records in the source environment; they are not public links or live status.
Who carries the work?
- Availability
- available
- Study-reported verification
- reported
The session-start receipt reports the receiving durable actor binding.
nabi://syn/706d63bd-9f23-49ec-8268-b1cbcb813f81nabi://agent/nabi_a_51eb4413c9754457b32dbbb52e3fc4bd
What context was selected?
- Availability
- partial
- Study-reported verification
- reported
The prior manager’s handoff was relayed. A ContextPacket for the selection was not established.
nabi://syn/d9256f2e-0345-4c00-a0aa-abea1b06b47c
Why was it routed to this actor?
- Availability
- unavailable
- Study-reported verification
- unverified
A RouteActionRecord for this selection was not established.
How does the result connect to prior work?
- Availability
- partial
- Study-reported verification
- checked
The settlement receipt has a recorded derives_from edge to the slice declaration. The role-assumed receipt names the handoff in prose, not a typed causal edge. Git objects confirm merge parents and equal trees.
nabi://syn/53fd6bd4-2911-4c1d-bfbd-11ab3b42c003nabi://syn/d7325666-350c-4fbc-aeb9-b7c4acd39f99nabi://syn/d73e93d6-2887-4f05-8127-0a94d0e922b01f5cc6e7d48b271e947d7fcb97c4a5200141fa3c352192763e45a82055a0b2df93d30a0531b599e6
Was the event included in an attested batch?
- Availability
- unavailable
- Study-reported verification
- unverified
An inclusion verification for the selected episode was not established.
What can happen next?
- Availability
- partial
- Study-reported verification
- reported
A later report held the release tag pending installation and a smoke test; it does not establish that the release was completed.
nabi://syn/472e1ff5-7c55-43fb-b9a0-097e1f5384d2
What remains unverified
- The role-assumed receipt names the handoff in its message; that reference is not a typed causal edge.
- Gate results were reported but their logs were not independently inspected for this replay.
- The prior manager’s compaction was anticipated, not verified. The later report does not establish that the release was finished.
Recorded account
Address a live agent in its own session.
An operator asked Codex to reach breeze.summit.antenna from ChatGPT Desktop. The account describes Claude continuing in its own session.
- 01
Ask
Name the session and the work it already carries.
- 02
Resolve
Resolve the alias and check the socket peer.
- 03
Deliver
Send the request into the existing session.
- 04
Observe
The account reports an acknowledgement and a read-only survey.
Delivery and a read-only continuation are reported. Independent transcript verification, settlement, and full messaging and authority guarantees remain unestablished.
Aevos Workbench · prototype
A place to think, trace, and inspect.
Bring source material, a canvas, and a terminal together. Branch ideas, trace their sources, and compose a draft.
The governor illustrates a captured snapshot. It is read-only and cannot dispatch, grant authority, or settle work.
See the workbench overview →Spatial exploration · Bevy prototype
Another way to see the field.
A spatial prototype for exploring relationships and following evidence. The Nuxt and Tauri workbench is closer to a usable product.
Runtime
nabi
The runtime behind Aevos: identity, authority checks, and records of the work.
Surfaces
Aevos
Ways to inspect and continue the work across web, desktop, spatial, and native environments.
Surfaces
One protocol. Several ways in.
Browser
Web portal
A browser view of shared work, records, and collaboration.
Explore the current surfaces in a walkthrough.
Local
Desktop
Bring local material, agent activity, and a terminal into one workbench.
A Nuxt and Tauri prototype.
Spatial
Canvas
Explore relationships and trace the work through a spatial view.
A Bevy prototype using recorded and example data.
Mobile / Mac
Native (Apple)
Native Apple views onto the same work and its records.
Availability depends on the platform and connected services.
Start with one repository. Agree on authority, approval boundaries, and how the result will be checked.