docs: hand off personal-agent services to conductor curator

This commit is contained in:
Svrnty
2026-06-14 08:36:34 -04:00
parent 5807a86b2e
commit 412f669b93
6 changed files with 376 additions and 2 deletions
@@ -38,7 +38,8 @@ desktop exposure must be treated as one of:
| Proton Drive/rclone | blocked-follow-up | rclone read probe is redacted-ok; governed wrapper and write gates remain follow-up work |
| Personal-agent Secondbrain proposal route | active-authority | `docs/contracts/personal-agent-secondbrain-proposal-route.json` defines proposal-only personal memory intake |
| Personal memory durable apply | blocked-follow-up | Owning Secondbrain/curator route must approve and apply; profile/capability packages do not write durable memory |
| Conductor/curator service routing | blocked-follow-up | `PACR-006`, after owning lanes release |
| 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 |
| Desktop app exposure | blocked-follow-up | `PACR-008`, after adapter lane release |
| Browser/Webwright host control | blocked-follow-up | `PACR-009`, explicit approval only |
@@ -76,6 +77,7 @@ desktop exposure must be treated as one of:
- Graph context should expose BlueBubbles as the active iMessage capability package.
- Graph context should expose the Proton/rclone package candidate as the active standardization pickup, not a runtime-ready child package.
- 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 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.