Tracking Issue: Development Context and Scope Model

Goal

Track the design and follow-up work needed to define how Project, Workstream, Session, and scope relate across PowerContext.

PowerContext originally used a project-derived scope_id to share context across Sessions. Handoff later used the same scope as the identity of one linear Workstream. This assumption does not cover projects with parallel work or development spanning multiple projects.

RFC required

Implementation requires a new RFC that defines:

• Project, Workstream, Session, and scope semantics;
• their relationships and identity boundaries;
• scope granularity for Memory, Handoff, Statistics, and other Runtime capabilities;
• whether project_id remains a separate identity;
• compatibility expectations for the API, CLI, integrations, and existing data.

The RFC should decide the model and invariants without fixing detailed user-flow orchestration prematurely.

Tracking

• Draft and review the RFC.
• Record the accepted identity and scope model.
• Reconcile affected existing RFCs, including RFC 0019, RFC 0048, and RFC 0082.
• Create follow-up issues for API, CLI, Codex integration, Dashboard, and Handoff Report work.
• Implement changes only after the RFC is accepted.

Constraints

• Preserve shared project context across Sessions.
• Keep independent Workstream histories isolated.
• Do not equate Session with Workstream.
• Do not assume the current project_id model is final.
• Treat migration and detailed orchestration as follow-up work.

Start by reviewing RFC 0019, RFC 0048, and RFC 0082, then map the current Project, Workstream, Session, and scope assumptions described in this issue. Done means a reviewed RFC records the identity and scope model, reconciles affected RFCs, and lists follow-up issues for API, CLI, Codex integration, Dashboard, and Handoff Report work.