Skip to content

[P3] Profiles memory and artifacts #5

Open

Description

@bloodf

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

Managed roadmap links

Parent: [Roadmap] Beans capability roadmap and personal computers
Blocked by: None.
Children:

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):

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:

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):

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:

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):

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:

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):

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:

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):

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:

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):

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:

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

  1. added
    roadmapManaged Beans capability roadmap
    phase:P3Roadmap phase P3; not a blanket dependency
    on Oct 7, 2026
  2. changed the title [-][P3] Computer operations and optional Camofox[/-] [+][P3] Profiles memory and artifacts[/+] on Oct 7, 2026
  3. added
    blockedBlocked: first unmet prerequisite named in the latest comment
    on Oct 13, 2026
  4. bloodf commented on Oct 13, 2026

    @bloodf
    OwnerAuthor

    Task contract — 2026-10-13

  5. added
    priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.
    platform:androidScope: Android; implementation and acceptance require target-specific evidence.
    platform:cli-serverScope: CLI/Server; implementation and acceptance require target-specific evidence.
    platform:iosScope: iOS; implementation and acceptance require target-specific evidence.
    platform:linuxScope: Linux; implementation and acceptance require target-specific evidence.
    platform:macosTarget scope: macOS. Does not imply implementation or acceptance; require target-specific evidence.
    platform:sharedShared implementation scope; target-platform support and acceptance require separate evidence.
    platform:windowsScope: Windows; implementation and acceptance require target-specific evidence.
    and removed
    blockedBlocked: first unmet prerequisite named in the latest comment
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase:P3Roadmap phase P3; not a blanket dependencyplatform:androidScope: Android; implementation and acceptance require target-specific evidence.platform:cli-serverScope: CLI/Server; implementation and acceptance require target-specific evidence.platform:iosScope: iOS; implementation and acceptance require target-specific evidence.platform:linuxScope: Linux; implementation and acceptance require target-specific evidence.platform:macosTarget scope: macOS. Does not imply implementation or acceptance; require target-specific evidence.platform:sharedShared implementation scope; target-platform support and acceptance require separate evidence.platform:windowsScope: Windows; implementation and acceptance require target-specific evidence.priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.roadmapManaged Beans capability roadmaptype:phaseRoadmap phase

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions