docs: standardize Proton rclone package candidate
This commit is contained in:
+7
-5
@@ -33,8 +33,9 @@ desktop exposure must be treated as one of:
|
||||
| Steev display name | active-alias | User-facing name for `personal-agent`, not separate authority |
|
||||
| Personal-agent BlueBubbles binding | active-authority | `docs/contracts/personal-agent-bluebubbles-binding.json` binds `imessage.read` to the package |
|
||||
| BlueBubbles iMessage | active-capability-package | BlueBubbles child completion-readiness package |
|
||||
| Proton Mail/Calendar/Contacts | blocked-follow-up | New Proton/rclone capability package work from `PACR-004` |
|
||||
| Proton Drive/rclone | blocked-follow-up | New Proton/rclone capability package work from `PACR-004` |
|
||||
| Proton/rclone package candidate | active-authority | `docs/contracts/personal-agent-proton-rclone-package.json` standardizes Mail, Calendar, Contacts, and Drive without child/runtime readiness overclaim |
|
||||
| Proton Mail/Calendar/Contacts | blocked-follow-up | Package child registration, degraded gate repair, and runtime proof remain follow-up work |
|
||||
| Proton Drive/rclone | blocked-follow-up | rclone read probe is redacted-ok; governed wrapper and write gates remain follow-up work |
|
||||
| Personal memory route | blocked-follow-up | `PACR-005`, then owning Secondbrain/curator route |
|
||||
| Conductor/curator service routing | blocked-follow-up | `PACR-006`, after owning lanes release |
|
||||
| Desktop app exposure | blocked-follow-up | `PACR-008`, after adapter lane release |
|
||||
@@ -48,7 +49,7 @@ desktop exposure must be treated as one of:
|
||||
| `CONTRACT.md` v1 iMessage-as-v2 wording | superseded | iMessage is now main personal context intake, not a low-priority future messaging item. |
|
||||
| `AGENT.md` reused-skill summary | superseded | It names useful tools but not the new governed surface model. |
|
||||
| `skills/steev-agent` current memory protocol | superseded | It says episodic memory only but does not encode personal Secondbrain proposal/apply routing. |
|
||||
| `skills/proton-tools` | active-source-to-consolidate | It contains live Proton tool knowledge but must be folded into a standardized capability package. |
|
||||
| `skills/proton-tools` | superseded-pending-package-install | It remains tool reference material, but governance now lives in the Proton/rclone package candidate. |
|
||||
| `DISCLOSURE.md` Wave 8/8.5 runtime disclosure | superseded-pending-refresh | It is historical disclosure and must be refreshed after the profile capability contract changes. |
|
||||
| BlueBubbles runtime-readiness PRD | active-capability-package | It remains valid for the iMessage capability package, subordinate to the `personal-agent` profile contract. |
|
||||
| BlueBubbles completion-readiness PRD | active-capability-package | It remains the BlueBubbles package pickup for read-only iMessage readiness. |
|
||||
@@ -59,8 +60,8 @@ desktop exposure must be treated as one of:
|
||||
| Hermes installed `proton-access` skill | superseded-pending-consolidation | It overlaps with Steev `proton-tools` and should not be a separate authority. |
|
||||
| Hermes installed `proton-mail-operations` skill | superseded-pending-consolidation | It overlaps with Steev `proton-tools` and should fold into the canonical Proton package. |
|
||||
| Hermes installed `proton-services` skill | superseded-pending-consolidation | It overlaps with Steev `proton-tools` and should fold into the canonical Proton package. |
|
||||
| Direct rclone CLI proofs | active-evidence-source | Read-only `about` proof is useful, but runtime authority must be packaged. |
|
||||
| Docker Proton Bridge and calendar gate state | active-evidence-source | Current runtime fact, not a profile contract by itself. |
|
||||
| Direct rclone CLI proofs | active-evidence-source | Read-only `about` proof is captured redacted in the package candidate, but runtime authority still needs a governed wrapper. |
|
||||
| Docker Proton Bridge and calendar gate state | active-evidence-source | Current runtime fact is captured redacted in the package candidate, not a readiness claim by itself. |
|
||||
| Broken user `proton-bridge.service` state | active-gap | Must be resolved or explicitly abandoned when one canonical runtime path is chosen. |
|
||||
| Inactive rclone RC/proxy units | active-gap | Must stay disabled or become gated through a governed wrapper before runtime readiness. |
|
||||
| Secondbrain direct-write ideas | superseded | Personal context must begin as proposal/apply, not direct durable writes. |
|
||||
@@ -72,6 +73,7 @@ desktop exposure must be treated as one of:
|
||||
- Graph context should expose this PRD as the `personal-agent` profile-level pickup.
|
||||
- Graph context should treat Steev as display name / distribution alias only.
|
||||
- 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 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.
|
||||
|
||||
Reference in New Issue
Block a user