docs: capture personal-agent runtime readiness snapshot

2026-06-14 08:40:58 -04:00
parent 412f669b93
commit 8274edffeb
6 changed files with 315 additions and 1 deletions
@@ -40,6 +40,7 @@ desktop exposure must be treated as one of:
 | Personal memory durable apply | blocked-follow-up | Owning Secondbrain/curator route must approve and apply; profile/capability packages do not write durable memory |
 | 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 |
 | Browser/Webwright host control | blocked-follow-up | `PACR-009`, explicit approval only |

@@ -78,6 +79,7 @@ desktop exposure must be treated as one of:
 - 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 expose the personal-agent runtime snapshot as degraded until the named runtime gaps close.
 - 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.