Repository navigation
Description
Outcome
Profiles memory and artifacts.
Execution policy
Difficulty-first delivery. Track every issue assigned to P3, including children of cross-phase epics. Dependencies remain authoritative; no deadlines or implementation claims.
Acceptance
- Each issue meets its own observable acceptance and safety/data-preservation requirements.
- Integration and failure-path evidence is linked before closing.
Phase work checklist
- [P3][Epic] Artifacts: library and revision-safe editing
- [P3][Artifacts] Define artifact identity, storage and sync contract
- [P3][Artifacts] Index approved outputs as artifacts
- [P3][Artifacts] Open artifacts on paired Devices
- [P3][Artifacts] Revision-safe editing with stale-hash rejection
- [P3][Artifacts] Artifact library views on macOS, desktop and phone
- [P3][Artifacts] Artifact deletion and retention
- [P3][Epic] Memory retrieval: evidence on top of the existing foundation
- [P3][Memory-Retrieval] Measure current retrieval quality on synthetic fixtures
- [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline
- [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory
- [P3][Memory-Retrieval] Show source and age of recalled evidence
- [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior
- [P3][Memory-Retrieval] Explicit shared memory between bots
- [P3][Memory-Retrieval] Attach memory-service controls in the macOS app
- [P3][Memory-Retrieval] Attach memory-service controls in the Windows/Linux desktop app
- [P3][Memory-Retrieval] Assess phone memory pages against the shared fixture and close gaps
- [P3][Memory-Retrieval] Implement explicitly shared memory scopes
- [P3][Integrations] Multi-account grants and catalog provenance
- [P3][Integrations] Assess per-account and per-tool grant gaps
- [P3][Integrations] Account-distinguished and per-tool grants for MCP plugins
- [P3][Integrations] Catalog and update provenance and integrity
- [P3][Integrations] Guided local and self-hosted model setup
- [P3][Reliability] OS keychain storage for master secret and credentials
- [P3][Reliability] Secret rotation and device revocation review
- [P3][Reliability] Backup and restore of Runner-local state
- [P3][Reliability] Data retention and deletion controls
- [P3] Epic: Personal, Work and Hobby profiles with multiple authenticated connections
- [P3][Profiles] Analyze current credential, plugin and memory ownership and migration risks
- [P3][Profiles] Define profile, connection-instance and grant contract
- [P3][Profiles] Multiple OAuth/API-key connection instances per plugin
- [P3][Profiles] Account labels and reconnect / revoke flows
- [P3][Profiles] Per-bean and per-profile grants enforced at execution
- [P3][Profiles] Profile-scoped memory and retrieval
- [P3][Profiles] Profile defaults for model, skills and plugins
- [P3][Profiles] Explicit, visible and revocable cross-profile grants
- [P3][Profiles] Native profile and connection management on all clients
- [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation
- [P3][Profiles] Migrate existing setups to one default profile without re-authentication
- [P3][Profiles] Integration acceptance: two Gmail accounts, Personal and Work beans
- [P3][Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources
- [P3][Skills] Native skill catalog and diagnostics on all clients
- [P3][Skills] Integration acceptance: four-host fixtures end to end
- [P3][Plugins] App defaults with profile and per-bean overrides
- [P3][Plugins] Generic schema-driven plugin configuration UI on all clients
- [P3][Skills] Skill authoring, review and rollback without executing installs
- [P3][Setup] Preview and transactionally import setup with account reconnection
- [P3][Setup] Native Pair or Import setup flow across clients
- [P3][Memory] Discover explicit group memory and compaction settings gaps
- [P3][Composer] Dollar-trigger skill picker and explicit invocation
- [P3][Composer] Native plus slash and skill picker parity across clients
Managed roadmap links
Parent: [Roadmap] Beans capability roadmap and personal computers
Blocked by: None.
Children:
- [P3][Epic] Artifacts: library and revision-safe editing
- [P3][Epic] Memory retrieval: evidence on top of the existing foundation
- [P3][Integrations] Multi-account grants and catalog provenance
- [P3] Epic: Personal, Work and Hobby profiles with multiple authenticated connections
Delivery cycles and AI handoff
Use this phase runbook with the global dispatch rules and verification-command catalog in #1. Strategic phase, urgency, lifecycle status, cycle membership and AI readiness are distinct. Each issue retains its own acceptance and explicit direct prerequisites.
P3.01 — Artifacts: identity, access and safe revisions
Canonical issues: #92, #93, #94, #95, #97, #96.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Shared, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.01.W1 Freeze artifact identity and access: [P3][Artifacts] Define artifact identity, storage and sync contract #92, [P3][Artifacts] Index approved outputs as artifacts #93, [P3][Artifacts] Open artifacts on paired Devices #94.
-
Outcome: Reconcile existing ArtifactRevision/ArtifactEnvelope source and prior increments. Select the contract, index only approved outputs, then expose paired-Device fetch; do not rebuild shipped partial foundations.
-
Step 1: [P3][Artifacts] Define artifact identity, storage and sync contract #92 — [Artifacts] Define artifact identity, storage and sync contract
-
Step 2: [P3][Artifacts] Index approved outputs as artifacts #93 — [Artifacts] Index approved outputs as artifacts
-
Step 3: [P3][Artifacts] Open artifacts on paired Devices #94 — [Artifacts] Open artifacts on paired Devices
-
Wave exit: Reviewed record fields, sync kind, capability gating and chat-deletion rule; absent-only publication is not revision replacement.; Approved output yields one durable index row; refusal yields none; record failure does not delete saved workspace file.; Phone fetch from a paired desktop Runner is hash-matched; offline, quota and unpaired failures are readable.
-
-
P3.01.W2 Protect artifact revisions and retention: [P3][Artifacts] Revision-safe editing with stale-hash rejection #95, [P3][Artifacts] Artifact deletion and retention #97, [P3][Artifacts] Artifact library views on macOS, desktop and phone #96.
-
Outcome: Use accepted [P3][Artifacts] Index approved outputs as artifacts #93/[P3][Artifacts] Open artifacts on paired Devices #94 APIs to implement stale-hash protection and deletion semantics, then complete all-client library views. Preserve drafts and user-owned workspace files.
-
Step 1: [P3][Artifacts] Revision-safe editing with stale-hash rejection #95 — [Artifacts] Revision-safe editing with stale-hash rejection
-
Step 2: [P3][Artifacts] Artifact deletion and retention #97 — [Artifacts] Artifact deletion and retention
-
Step 3: [P3][Artifacts] Artifact library views on macOS, desktop and phone #96 — [Artifacts] Artifact library views on macOS, desktop and phone
-
Wave exit: Two-writer stale save returns current hash, retains draft and writes nothing; fresh save creates parent-linked revision.; Binary conflict never auto-merges; bot edit requires approval. Relay deletion failure remains visible/retriable without deleting user workspace files.; All client library views, accessibility and offline state accepted on actual platforms.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
issues: 94; 95; 97; condition: After [P3][Artifacts] Index approved outputs as artifacts #93 acceptance, independent reviews/fixture preparation can overlap, but artifact/file/store mutation paths are single-writer. [P3][Artifacts] Artifact library views on macOS, desktop and phone #96 clients follow [P3][Artifacts] Open artifacts on paired Devices #94 and a stable API.
-
Single-writer constraint: Single core artifact/storage writer with serial contract→index→fetch handoffs. [P3][Artifacts] Define artifact identity, storage and sync contract #92 contract can be scheduled as a narrow prerequisite for P2 [P2][Documents] Propose and save DOCX deliverables through the approval card #88; [P3][Artifacts] Index approved outputs as artifacts #93/[P3][Artifacts] Open artifacts on paired Devices #94 remain P3. docs: define artifact identity storage and sync contract #354 is a zero-diff reservation requiring owner/patch reconciliation.
-
Single-writer constraint: Serialize revision and deletion mutations in the artifact/store paths. After API freeze, platform library views can proceed on disjoint client paths with a single docs owner.
Existing canonical draft work: #354. Resolve current head/base and ownership before creating any branch; a draft or contract-only diff is not feature acceptance.
P3.02 — Profiles: connection authority and migration
Canonical issues: #106, #107, #144, #307, #187, #188, #189, #145, #195.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Shared, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.02.W1 Choose profile security contracts: [P3][Profiles] Analyze current credential, plugin and memory ownership and migration risks #106, [P3][Profiles] Define profile, connection-instance and grant contract #107, [P3][Integrations] Assess per-account and per-tool grant gaps #144, [P3][Integrations] Define purpose-bound secret request security #307.
-
Outcome: Inventory actual credential/plugin/memory ownership once, settle one profile/connection/grant contract, then derive per-tool gap inventory and purpose-bound secret-request design. [P3][Integrations] Define purpose-bound secret request security #307 remains design-only.
-
Step 1: [P3][Profiles] Analyze current credential, plugin and memory ownership and migration risks #106 — [Profiles] Analyze current credential, plugin and memory ownership and migration risks
-
Step 2: [P3][Profiles] Define profile, connection-instance and grant contract #107 — [Profiles] Define profile, connection-instance and grant contract
-
Step 3: [P3][Integrations] Assess per-account and per-tool grant gaps #144, [P3][Integrations] Define purpose-bound secret request security #307 — [Integrations] Assess per-account and per-tool grant gaps / [Integrations] Define purpose-bound secret request security
-
Wave exit: Reviewer spot-checks ownership rows and migration invariants. Contract preserves existing IDs/tokens without reauthentication or states exact upstream exception.; Purpose-bound synthetic canary walkthrough covers stale reply, grant/destination change and every plaintext sink; no real secrets, cards, transport, storage or command injection is implemented.
-
-
P3.02.W2 Enforce connection-instance grants: [P3][Profiles] Multiple OAuth/API-key connection instances per plugin #187, [P3][Profiles] Account labels and reconnect / revoke flows #188, [P3][Profiles] Per-bean and per-profile grants enforced at execution #189, [P3][Integrations] Per-tool MCP grant controls #145, [P3][Profiles] Migrate existing setups to one default profile without re-authentication #195.
-
Outcome: Create multiple instances, implement account labels/revoke/reconnect, then canonical execution-time authorization ([P3][Profiles] Per-bean and per-profile grants enforced at execution #189), per-tool controls ([P3][Integrations] Per-tool MCP grant controls #145) and default-profile migration ([P3][Profiles] Migrate existing setups to one default profile without re-authentication #195). Keep separate acceptance for every issue.
-
Step 1: [P3][Profiles] Multiple OAuth/API-key connection instances per plugin #187 — [Profiles] Multiple OAuth/API-key connection instances per plugin
-
Step 2: [P3][Profiles] Account labels and reconnect / revoke flows #188 — [Profiles] Account labels and reconnect / revoke flows
-
Step 3: [P3][Profiles] Per-bean and per-profile grants enforced at execution #189 — [Profiles] Per-bean and per-profile grants enforced at execution
-
Step 4: [P3][Integrations] Per-tool MCP grant controls #145 — [Integrations] Account-distinguished and per-tool grants for MCP plugins
-
Step 5: [P3][Profiles] Migrate existing setups to one default profile without re-authentication #195 — [Profiles] Migrate existing setups to one default profile without re-authentication
-
Wave exit: Two test account instances stay distinct; reconnect one preserves the other. Revoke while awaiting approval fails closed and identifies the account.; Grant denial survives scripted calls/routines and account Pause; unavailable instance never falls back to another account.; Interrupted migration leaves only old or new state; IDs/tokens/references unchanged; rollback byte-equal. No production migration in this planning task.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
stage: 3; issues: 144; 307; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Read-only research may parallelize after [P3][Profiles] Define profile, connection-instance and grant contract #107. Keep [P3][Profiles] Analyze current credential, plugin and memory ownership and migration risks #106 inventory canonical for [P3][Integrations] Assess per-account and per-tool grant gaps #144; no second ownership model. Exact security contract review is required before any [P3][Integrations] Define purpose-bound secret request security #307 implementation lease.
-
Single-writer constraint: Read-only research may parallelize after [P3][Profiles] Define profile, connection-instance and grant contract #107. Keep [P3][Profiles] Analyze current credential, plugin and memory ownership and migration risks #106 inventory canonical for [P3][Integrations] Assess per-account and per-tool grant gaps #144; no second ownership model. Exact security contract review is required before any [P3][Integrations] Define purpose-bound secret request security #307 implementation lease.
-
Single-writer constraint: One credential/grant schema owner. [P3][Profiles] Per-bean and per-profile grants enforced at execution #189 owns connection/profile resolution and post-approval rechecks; [P3][Integrations] Per-tool MCP grant controls #145 only per-tool policy/UI on that boundary. Serialize roster/schema/migration edits and hand off API fields before client work.
P3.03 — Profiles: isolation, sharing and setup journeys
Canonical issues: #190, #191, #194, #108, #122, #192, #222, #193, #223, #196.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Shared, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.03.W1 Isolate profile state and defaults: [P3][Profiles] Profile-scoped memory and retrieval #190, [P3][Profiles] Profile defaults for model, skills and plugins #191, [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation #194.
-
Outcome: Implement scoped memory and inheritable defaults from [P3][Profiles] Define profile, connection-instance and grant contract #107, then prove encrypted sync and deterministic revoke/conflict behavior. Shared schema must be frozen before parallel implementation.
-
Step 1: [P3][Profiles] Profile-scoped memory and retrieval #190, [P3][Profiles] Profile defaults for model, skills and plugins #191 — [Profiles] Profile-scoped memory and retrieval / [Profiles] Profile defaults for model, skills and plugins
-
Step 2: [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation #194 — [Profiles] Encrypted sync, offline conflicts and revocation propagation
-
Wave exit: Same fact text in Personal/Work remains isolated and separately deletable; unscopable backend disables rather than mixes.; Explicit bean settings win; unavailable default warns and falls back to app default.; Two offline Devices converge; revocation blocks next call after sync; equal-version conflicting known values fail closed.
-
-
P3.03.W2 Make memory sharing explicit: [P3][Memory-Retrieval] Define explicit shared memory scope contract #108, [P3][Memory-Retrieval] Implement explicitly shared memory scopes #122, [P3][Profiles] Explicit, visible and revocable cross-profile grants #192.
-
Outcome: Choose one shared-scope grant API under [P3][Profiles] Define profile, connection-instance and grant contract #107, implement shared memory [P3][Memory-Retrieval] Implement explicitly shared memory scopes #122, then expose cross-profile visibility/revocation [P3][Profiles] Explicit, visible and revocable cross-profile grants #192 over accepted [P3][Profiles] Per-bean and per-profile grants enforced at execution #189/[P3][Profiles] Profile-scoped memory and retrieval #190 boundaries.
-
Step 1: [P3][Memory-Retrieval] Define explicit shared memory scope contract #108 — [Memory-Retrieval] Explicit shared memory between bots
-
Step 2: [P3][Memory-Retrieval] Implement explicitly shared memory scopes #122 — [Memory-Retrieval] Implement explicitly shared memory scopes
-
Step 3: [P3][Profiles] Explicit, visible and revocable cross-profile grants #192 — [Profiles] Explicit, visible and revocable cross-profile grants
-
Wave exit: A→B read does not permit write; foreign C sees nothing. Current authorization blocks queued and approval-resumed work after revoke.; Scope deletion follows existing fences; disabling memory preserves MEMORY.md; profile deletion leaves no orphan shares.
-
-
P3.03.W3 Finish profile and setup journeys: [P3][Setup] Preview and transactionally import setup with account reconnection #222, [P3][Profiles] Native profile and connection management on all clients #193, [P3][Setup] Native Pair or Import setup flow across clients #223, [P3][Profiles] Integration acceptance: two Gmail accounts, Personal and Work beans #196.
-
Outcome: Implement transactional account-aware setup import, expose accepted profile/connection controls, add clear Pair-versus-Import UX, then run cross-profile integration acceptance.
-
Step 1: [P3][Setup] Preview and transactionally import setup with account reconnection #222 — [Setup] Preview and transactionally import setup with account reconnection
-
Step 2: [P3][Profiles] Native profile and connection management on all clients #193 — [Profiles] Native profile and connection management on all clients
-
Step 3: [P3][Setup] Native Pair or Import setup flow across clients #223 — [Setup] Native Pair or Import setup flow across clients
-
Step 4: [P3][Profiles] Integration acceptance: two Gmail accounts, Personal and Work beans #196 — [Profiles] Integration acceptance: two Gmail accounts, Personal and Work beans
-
Wave exit: Corrupt/cancelled/unsafe-path import writes nothing and executes nothing; repeated import is idempotent; foreign-account connections stay disconnected.; All client families can create/connect/grant/revoke; offline age and accessibility evidence provided; Pair and one-time Import are explicit.; Two throwaway Gmail accounts with Personal/Work beans prove provider-side separation, routine grants and revocation; authenticated live actions require separate user authorization.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
stage: 1; issues: 190; 191; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Memory dispatch and default-resolution lanes may write disjoint files only after the model/roster schema handoff. One owner holds model.rs, sync.rs and protocol docs; [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation #194 integration is serial.
-
issues: 190; 191; condition: After [P3][Profiles] Define profile, connection-instance and grant contract #107 selected contract, memory-specific and defaults-specific files can be disjoint; shared model.rs/protocol definitions are integrated first. [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation #194 can start after [P3][Profiles] Define profile, connection-instance and grant contract #107 handoff without waiting for all of P3-B, but must integrate with accepted shared fields.
-
Single-writer constraint: Memory dispatch and default-resolution lanes may write disjoint files only after the model/roster schema handoff. One owner holds model.rs, sync.rs and protocol docs; [P3][Profiles] Encrypted sync, offline conflicts and revocation propagation #194 integration is serial.
-
Single-writer constraint: Single scope/grant schema writer. [P3][Memory-Retrieval] Define explicit shared memory scope contract #108 is contract only; [P3][Memory-Retrieval] Implement explicitly shared memory scopes #122 owns storage/dispatch; [P3][Profiles] Profile-scoped memory and retrieval #190 remains isolation owner and [P3][Profiles] Explicit, visible and revocable cross-profile grants #192 owns explicit review/visibility/revocation. No parallel sharing implementation.
-
Single-writer constraint: Allocate per-client files before launch; same client settings/onboarding owners serialize [P3][Profiles] Native profile and connection management on all clients #193/[P3][Setup] Native Pair or Import setup flow across clients #223. Import core may proceed only with frozen [P3][Profiles] Define profile, connection-instance and grant contract #107/[P2][Setup] Export a bounded secret-free setup recipe #221 schema. [P3][Profiles] Integration acceptance: two Gmail accounts, Personal and Work beans #196 is verification, never an implementation catch-all.
P3.04 — Memory: client parity and evidence lifecycle
Canonical issues: #101, #102, #329, #330, #103, #99, #235, #100, #105, #104.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.04.W1 Finish native memory parity: [P3][Memory-Retrieval] Complete macOS memory controls and acceptance #101, [P3][Memory-Retrieval] Complete desktop memory controls and acceptance #102, [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329, [P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330, [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103.
-
Outcome: Finish existing memory-control increments instead of rebuilding UI. Mac fix(macos): keep unsupported memory controls visible and localize memory forms #344 and desktop test(desktop): preserve localized memory status and delivery semantics #346 remain distinct; shared phone forms [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329 and phone localization [P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 feed [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103 reconciliation/device acceptance.
-
Step 1: [P3][Memory-Retrieval] Complete macOS memory controls and acceptance #101, [P3][Memory-Retrieval] Complete desktop memory controls and acceptance #102, [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329 — [Memory-Retrieval] Attach memory-service controls in the macOS app / [Memory-Retrieval] Attach memory-service controls in the Windows/Linux desktop app / [Memory-Retrieval] Name phone switches and text fields for screen readers
-
Step 2: [P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 — [Memory-Retrieval] Localize phone memory pages (Simplified Chinese)
-
Step 3: [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103 — [Memory-Retrieval] Assess phone memory pages against the shared fixture and close gaps
-
Wave exit: fix(macos): keep unsupported memory controls visible and localize memory forms #344 installed-app VoiceOver/keyboard/EN-zh/local-CLI scenario remains required despite historical fixture pass.; Resolve or explicitly disposition test(desktop): preserve localized memory status and delivery semantics #346 l10n scanner limitation; verify runtime Chinese labels plus actual Windows/Linux keyboard/screen-reader use.; Phone device assessment names every control, consent action and source of unavailable state; English and Simplified Chinese wording reviewed; [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329/[P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 source results alone do not close device acceptance.
-
-
P3.04.W2 Prove memory evidence and lifecycle: [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline #99, [P3][Memory] Discover explicit group memory and compaction settings gaps #235, [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory #100, [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior #105, [P3][Memory-Retrieval] Show source and age of recalled evidence #104.
-
Outcome: Evaluate TinyCortex against closed baseline [P3][Memory-Retrieval] Measure current retrieval quality on synthetic fixtures #98 and discover group-memory gaps independently. Add opt-in PDF ingestion, prove deletion/rebuild, and expose source/age using accepted memory controls.
-
Step 1: [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline #99, [P3][Memory] Discover explicit group memory and compaction settings gaps #235 — [Memory-Retrieval] Evaluate TinyCortex indexes against the baseline / [Memory] Discover explicit group memory and compaction settings gaps
-
Step 2: [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory #100 — [Memory-Retrieval] Opt-in ingestion of approved documents into memory
-
Step 3: [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior #105 — [Memory-Retrieval] Prove delete and derived-index rebuild behavior
-
Step 4: [P3][Memory-Retrieval] Show source and age of recalled evidence #104 — [Memory-Retrieval] Show source and age of recalled evidence
-
Wave exit: [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline #99 measured baseline/license/default-feature/binary/dependency deltas and exactly adopt/adopt-part/do-not-import; zero-diff docs(memory): evaluate TinyCortex and reject direct import #355 is not a result.; [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory #100 accepted PDF [P2][Documents] Read PDFs with page-cited text #86; explicit ingestion retains page provenance, foreign bot denied, delete fencing verified.; test(memory): prove deletion and derived-index behavior #334 final-head isolated serial tests require resource lease; earlier-SHA passes are not current evidence. Canonical notes survive rebuild; residual provider/Lance history disclosed.; [P3][Memory-Retrieval] Show source and age of recalled evidence #104 sources unavailable are labelled honestly; untrusted recalled text stays plain; inspector deletion uses fenced flow; [P3][Memory] Discover explicit group memory and compaction settings gaps #235 never implicitly shares private memory.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
stage: 1; issues: 101; 102; 329; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Mac, desktop and phone shared-form lanes are file-disjoint; memory-ui.md has one integrator. [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329 owns forms.tsx; [P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 owns page string conversion and i18n; [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103 assesses/reconciles and must not rewrite either. Preserve unpushed patches behind zero-diff test(mobile): assess existing phone memory controls and transport #356/chore: start roadmap issue 329 #362/chore: start phone memory localization #365.
-
stage: 1; issues: 99; 235; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Read-only [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline #99/[P3][Memory] Discover explicit group memory and compaction settings gaps #235 research may parallelize with separate evidence; only one memory dispatch/schema writer. [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory #100 implementation hands off to [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior #105 exact-head tests, then [P3][Memory-Retrieval] Show source and age of recalled evidence #104 API/UI provenance. Coordinate docs and Cargo allocation with [P3][Profiles] Profile-scoped memory and retrieval #190/[P3][Memory-Retrieval] Implement explicitly shared memory scopes #122.
-
issues: 101; 102; 329; 330; condition: Distinct macOS, desktop, mobile forms and mobile localization files may be leased separately; [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329/[P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 never concurrently change same forms or i18n file. [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103 can assess read-only concurrently, but its closeout must reconcile child/device evidence.
-
issues: 99; 235; condition: Separate read-only discovery records do not need to wait for native UI closeout. Heavy benchmarks and shared memory docs require resource/document owner coordination.
-
Single-writer constraint: Mac, desktop and phone shared-form lanes are file-disjoint; memory-ui.md has one integrator. [P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329 owns forms.tsx; [P3][Memory-Retrieval] Localize phone memory pages (Simplified Chinese) #330 owns page string conversion and i18n; [P3][Memory-Retrieval] Complete phone memory gap assessment and acceptance #103 assesses/reconciles and must not rewrite either. Preserve unpushed patches behind zero-diff test(mobile): assess existing phone memory controls and transport #356/chore: start roadmap issue 329 #362/chore: start phone memory localization #365.
-
Single-writer constraint: Read-only [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline #99/[P3][Memory] Discover explicit group memory and compaction settings gaps #235 research may parallelize with separate evidence; only one memory dispatch/schema writer. [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory #100 implementation hands off to [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior #105 exact-head tests, then [P3][Memory-Retrieval] Show source and age of recalled evidence #104 API/UI provenance. Coordinate docs and Cargo allocation with [P3][Profiles] Profile-scoped memory and retrieval #190/[P3][Memory-Retrieval] Implement explicitly shared memory scopes #122.
Existing canonical draft work: #334, #344, #346, #355, #356, #361, #362, #365. Resolve current head/base and ownership before creating any branch; a draft or contract-only diff is not feature acceptance.
P3.05 — Skills and plugins: scoped defaults and native UX
Canonical issues: #146, #208, #202, #215, #205, #204, #240, #206, #241.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Shared, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.05.W1 Resolve scoped plugin and skill defaults: [P3][Integrations] Catalog and update provenance and integrity #146, [P3][Plugins] App defaults with profile and per-bean overrides #208, [P3][Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources #202, [P3][Plugins] Generic schema-driven plugin configuration UI on all clients #215.
-
Outcome: Verify plugin/catalog provenance and then wire plugin overrides and skill enablement to [P3][Profiles] Profile defaults for model, skills and plugins #191 defaults. Finish schema-driven configuration UI after effective-state contracts are stable.
-
Step 1: [P3][Integrations] Catalog and update provenance and integrity #146 — [Integrations] Catalog and update provenance and integrity
-
Step 2: [P3][Plugins] App defaults with profile and per-bean overrides #208, [P3][Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources #202 — [Plugins] App defaults with profile and per-bean overrides / [Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources
-
Step 3: [P3][Plugins] Generic schema-driven plugin configuration UI on all clients #215 — [Plugins] Generic schema-driven plugin configuration UI on all clients
-
Wave exit: Digest mismatch refuses install/update and preserves pinned installed version; permission diff needs approval; offline bundled catalog is labelled.; Bean→profile→app→plugin precedence and explicit disabled behavior tested; missing Runner install is unavailable, never fallback execution.; Disabled/ungranted skills stay out of context, over-budget lists give notice, allowed-tools grants nothing; effective state/source shown on all clients.
-
-
P3.05.W2 Complete skill authoring and discovery UX: [P3][Skills] Skill authoring, review and rollback without executing installs #205, [P3][Skills] Native skill catalog and diagnostics on all clients #204, [P3][Composer] Dollar-trigger skill picker and explicit invocation #240, [P3][Skills] Integration acceptance: four-host fixtures end to end #206, [P3][Composer] Native plus slash and skill picker parity across clients #241.
-
Outcome: Build exact-byte reviewed skill revisions, expose four-host catalog, add dollar-trigger invocation, then run skill and composer parity acceptance as separate verification tickets.
-
Step 1: [P3][Skills] Skill authoring, review and rollback without executing installs #205 — [Skills] Skill authoring, review and rollback without executing installs
-
Step 2: [P3][Skills] Native skill catalog and diagnostics on all clients #204 — [Skills] Native skill catalog and diagnostics on all clients
-
Step 3: [P3][Composer] Dollar-trigger skill picker and explicit invocation #240 — [Composer] Dollar-trigger skill picker and explicit invocation
-
Step 4: [P3][Skills] Integration acceptance: four-host fixtures end to end #206, [P3][Composer] Native plus slash and skill picker parity across clients #241 — [Skills] Integration acceptance: four-host fixtures end to end / [Composer] Native plus slash and skill picker parity across clients
-
Wave exit: Declined edit changes no bytes; rollback restores exact revision while retaining history; imported source stays untouched and bot-authored skills remain disabled.; Four-host provenance, duplicate-name disambiguation and pinned source retention proven; discovery causes no external process/file writes.; Caret filtering, Escape, Enter, literal slash/dollar text, revoked selection and retained draft verified with keyboard/touch/screen reader on every client.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
stage: 2; issues: 208; 202; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: After schema freeze, [P3][Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources #202 skill code and [P3][Plugins] App defaults with profile and per-bean overrides #208 plugin configuration may own disjoint paths; shared model/turns/API and docs require one integrator. [P3][Plugins] Generic schema-driven plugin configuration UI on all clients #215 consumes the effective values rather than defining a second inheritance algorithm.
-
stage: 4; issues: 206; 241; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Serialize skill library revisions and common client catalog/composer integration. Platform UI lanes may run in disjoint files after reference schema freeze. [P3][Skills] Integration acceptance: four-host fixtures end to end #206/[P3][Composer] Native plus slash and skill picker parity across clients #241 can run read-only acceptance in parallel after all their own prerequisites; do not assign mobile PR fix(mobile): publish no composer inset before first layout #326/fix(mobile): let the phone transcript be scrolled up while a reply comes in #333 to these skills tickets.
-
issues: 202; 208; condition: After [P3][Profiles] Profile defaults for model, skills and plugins #191 and all individual P1 prerequisites, skill-loader and plugin-config paths can be separate; turns.rs/model.rs and effective-state schemas have one owner.
-
issues: 206; 241; condition: Read-only acceptance can use separate synthetic/native environments after their distinct prerequisite sets pass; this never grants two writers to the same composer file.
-
Single-writer constraint: After schema freeze, [P3][Skills] Per-bean and per-profile enablement, prompt listing and on-demand resources #202 skill code and [P3][Plugins] App defaults with profile and per-bean overrides #208 plugin configuration may own disjoint paths; shared model/turns/API and docs require one integrator. [P3][Plugins] Generic schema-driven plugin configuration UI on all clients #215 consumes the effective values rather than defining a second inheritance algorithm.
-
Single-writer constraint: Serialize skill library revisions and common client catalog/composer integration. Platform UI lanes may run in disjoint files after reference schema freeze. [P3][Skills] Integration acceptance: four-host fixtures end to end #206/[P3][Composer] Native plus slash and skill picker parity across clients #241 can run read-only acceptance in parallel after all their own prerequisites; do not assign mobile PR fix(mobile): publish no composer inset before first layout #326/fix(mobile): let the phone transcript be scrolled up while a reply comes in #333 to these skills tickets.
P3.06 — Local providers, secret storage and recovery
Canonical issues: #153, #152, #147, #154, #155.
Targets or regression scope: Android, CLI/Server, iOS, Linux, macOS, Shared, Windows. See each issue/PR platform labels and actual file scope before allocating writers.
Entry: User/lead explicitly selects this cycle and bounded wave within P0–P10 strategy; no blanket all-earlier-issues-closed condition is invented.; Refresh Project Status, native prerequisite states and canonical PR heads/bases/owner. A phase label or Project Ready is not dispatch permission.; Every direct prerequisite for the selected issue is accepted; apply its wave contract/integration gates without inventing native edges.; Read AGENTS.md, ARCHITECTURE.md and affected current subject docs, then choose exact file ownership and handoff boundaries.; Check current package/script names; run only sourced commands applicable to allocated surface, record exact head, host, environment and result.; Distinguish source review, synthetic fixtures, installed-app, live provider and crash/power-loss evidence; no skipped/queued checks count as pass.; Maintain existing issue and PR identity. No duplicate branch, container issue, mass body rewrite, merge, publish, credential/service action or rollout is authorized by this plan.
Ordered waves (the direct blocked-by contract takes precedence):
-
P3.06.W1 Protect local setup and recovery: [P3][Reliability] Secret rotation and device revocation review #153, [P3][Reliability] OS keychain storage for master secret and credentials #152, [P3][Integrations] Guided local and self-hosted model setup #147, [P3][Reliability] Backup and restore of Runner-local state #154, [P3][Reliability] Data retention and deletion controls #155.
-
Outcome: Reconcile landed revocation controls and discovery docs: describe lost-device revocation boundaries and proposed containment #359; implement keychain storage while separately completing existing local-provider UX fix(macos): show connection-check failures in basic provider setup #357; then restore/retention only under selected replay-fence semantics.
-
Step 1: [P3][Reliability] Secret rotation and device revocation review #153 — [Reliability] Secret rotation and device revocation review
-
Step 2: [P3][Reliability] OS keychain storage for master secret and credentials #152, [P3][Integrations] Guided local and self-hosted model setup #147 — [Reliability] OS keychain storage for master secret and credentials / [Integrations] Guided local and self-hosted model setup
-
Step 3: [P3][Reliability] Backup and restore of Runner-local state #154 — [Reliability] Backup and restore of Runner-local state
-
Step 4: [P3][Reliability] Data retention and deletion controls #155 — [Reliability] Data retention and deletion controls
-
Wave exit: [P3][Reliability] Secret rotation and device revocation review #153 reviewer repeats lost-device, queued/approved work and cached-plaintext trace; confirmed gaps remain separately tracked.; Keychain upgrade/rollback proven on supported OSes; Linux without secret service has visible safe fallback. Local server up/chat/down yields actionable errors on actual clients.; [P3][Reliability] Backup and restore of Runner-local state #154 clean-home/corrupt/wrong-passphrase/non-empty-home restore preserves data and excludes plaintext secrets; [P4][Tasks] Define the durable task state and effect-receipt contract #109 replay fences prevent stale routine/unknown-effect resurrection.; [P3][Reliability] Data retention and deletion controls #155 dry-run inventory and expiry preserve unresolved receipts/account-lifetime minimal tombstones; no secure-erasure claim.
-
Cycle exit: Every included ticket has its own accepted evidence/disposition; tracking parent remains open until all its cross-cycle/cross-phase children are actually complete.; All chosen wave exit gates recorded; skipped platform checks are gaps, not success.
Parallel boundaries:
-
stage: 2; issues: 152; 147; condition: Only after current prerequisites and explicit per-file leases; shared schemas, source files and architecture docs remain single-writer. Read-only inspection/acceptance can parallelize.; ownership: Keychain and local-provider UI may use disjoint exact files, but identity/providers docs have single owners. Serialize backup/restore and retention mutations on local_store.rs and safety tombstones; coordinate [P4][Tasks] Persist task records and history on the Runner #110/[P4][Tasks] Record external-effect receipts around tool calls #111 ownership. Define secret-store contract and conservative verified copying #358/Add conservative backend retention dry-run planner #360 zero-diff reservations are not implementation.
-
issues: 147; 152; condition: Local-provider UI and keychain internals may be disjoint, but provider/identity docs and any credential/API seam need explicit single-writer boundaries.
-
Single-writer constraint: Keychain and local-provider UI may use disjoint exact files, but identity/providers docs have single owners. Serialize backup/restore and retention mutations on local_store.rs and safety tombstones; coordinate [P4][Tasks] Persist task records and history on the Runner #110/[P4][Tasks] Record external-effect receipts around tool calls #111 ownership. Define secret-store contract and conservative verified copying #358/Add conservative backend retention dry-run planner #360 zero-diff reservations are not implementation.
Existing canonical draft work: #357, #358, #359, #360. Resolve current head/base and ownership before creating any branch; a draft or contract-only diff is not feature acceptance.
Activity
[-][P3] Computer operations and optional Camofox[/-][+][P3] Profiles memory and artifacts[/+]bloodf commentedon Oct 13, 2026
Task contract — 2026-10-13
-R bloodf/beans, merge by the publishing authority, post-merge check. Source PASS is not installed-app or live-service acceptance.