hermes/steev
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: define personal-agent desktop exposure contract

Browse Source
This commit is contained in:
Svrnty
2026-06-14 08:46:33 -04:00
parent 8274edffeb
commit 0944fc7fd0
6 changed files with 346 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/supersession/2026-06-14-personal-agent-context-runtime-supersession-register.md
+3 -1
View File
@@ -41,7 +41,8 @@ desktop exposure must be treated as one of:
| Personal-agent Conductor/Curator service handoff | active-authority | `docs/contracts/personal-agent-conductor-curator-service-handoff.json` gives route and hygiene lanes a redacted service map |
| Conductor/curator adoption | blocked-follow-up | Owning lanes must explicitly pick up the handoff; this profile does not mutate them |
| Personal-agent runtime readiness snapshot | active-authority | `docs/contracts/personal-agent-runtime-readiness-snapshot.json` names per-surface states and runtime gaps without aggregate readiness claim |
| Desktop app exposure | blocked-follow-up | `PACR-008`, after adapter lane release |
| Personal-agent desktop exposure contract | active-authority | `docs/contracts/personal-agent-desktop-exposure-contract.json` defines adapter-visible rows without UI wiring |
| Desktop app exposure wiring | blocked-follow-up | Owning adapter lane must pick up the contract and wire UI after approval |
| Browser/Webwright host control | blocked-follow-up | `PACR-009`, explicit approval only |
## Known Artifacts And Supersession State
@@ -80,6 +81,7 @@ desktop exposure must be treated as one of:
- Graph context should expose the personal-agent Secondbrain proposal route as active while keeping durable apply blocked to Secondbrain/curator.
- Graph context should expose the personal-agent Conductor/Curator service handoff as active, while adoption remains blocked to owning lanes.
- Graph context should expose the personal-agent runtime snapshot as degraded until the named runtime gaps close.
- Graph context should expose the personal-agent desktop exposure contract as active, while adapter UI wiring remains blocked to the adapter lane.
- Graph context should not treat legacy Cortex Proton/rclone repositories as active authority.
- Graph context should not treat duplicate Proton skills as separate current product surfaces.
- Graph context should mark browser/Webwright host control as separate HITL runtime authority.