{
  "schema_version": "0.1",
  "brainstorm_id": "BR-2026-07-15-workspace-development-control-plane",
  "title": "Workspace development control plane for PRD Plugin, AI-Collab and Payload Fabric",
  "created_at": "2026-07-15",
  "author_agent": "Codex",
  "status": "draft",
  "context": "The owner wants the goal-management system to underpin workspace development chat and work across PRD Plugin, AI-Collab-v3 and Payload Fabric. The current runtime has overlapping thread/message, goal, task-tree, Plan Execution, specialist-case and newer mailbox/task protocols. This brainstorm defines one portable workspace contract, correct semantic message routing, hierarchical goal execution and explicit per-agent participation controls without creating another server or project-truth authority.",
  "goals": [
    {"id": "BR-REQ-027", "summary": "Define one versioned Workspace Development Contract that PRD Plugin can ship downstream and AI-Collab can import, reconcile and enforce."},
    {"id": "BR-REQ-028", "summary": "Keep PRD Plugin authoritative for canonical plans, requirements, tracking, acceptance and evidence while AI-Collab owns live workspace execution, messaging and presentation and Payload Fabric owns work delivery and leases."},
    {"id": "BR-REQ-029", "summary": "Represent workspace channels by stable semantic roles so collaborative chat, completions, decisions, durable facts and specialist cases always project to the correct surface without title-based routing."},
    {"id": "BR-REQ-030", "summary": "Compile approved implementation plans into duplicate-safe hierarchical and cascading workspace, repository and recursive goal nodes with dependencies, validations, evidence expectations and computed progress."},
    {"id": "BR-REQ-031", "summary": "Provide complete orchestrator and worker tool surfaces for plan reconciliation, goal CRUD, refactoring, pause/resume, assignment, claim, progress, blockers, evidence, handoff, completion and audit."},
    {"id": "BR-REQ-032", "summary": "Use one immutable workspace event and recipient-delivery model to drive Work Log projections, inboxes, wakeups, lifecycle telemetry, goal progress and PRD runtime receipts without duplicating conversation stores."},
    {"id": "BR-REQ-033", "summary": "Make each agent independently enableable or disableable; a disabled agent receives no new chat delivery, wake, scheduled work or Fabric claim authority until re-enabled."},
    {"id": "BR-REQ-034", "summary": "Make Lobby listening independently configurable per agent; listening off must prevent Lobby delivery, context injection, wake and model invocation while leaving explicitly assigned non-Lobby work available when the agent remains enabled."},
    {"id": "BR-REQ-035", "summary": "Make Lobby reply authority independently configurable per agent; a muted agent may receive and reason over permitted Lobby content but the server must reject its Lobby messages while other work and allowed channel operations continue."},
    {"id": "BR-REQ-036", "summary": "Expose agent participation defaults, role policies and workspace overrides through validated PRD configuration and runtime management tools, with deterministic precedence, audit history and safe re-enable behavior."}
  ],
  "non_goals": [
    "Create another chat server, goal database, message store, work bus or configuration authority inside PRD Plugin.",
    "Treat a prompt instruction such as 'do not reply' as enforcement.",
    "Make workspace visibility imply agent delivery, wake or model invocation.",
    "Replay every missed Lobby message when listening or an agent is re-enabled.",
    "Allow live runtime overrides to silently rewrite repository configuration or canonical PRD state.",
    "Use disable, listening and mute as aliases for one ambiguous status flag."
  ],
  "decisions": [
    {"id": "BR-DEC-019", "summary": "Model enabled, Lobby listening and Lobby reply authority as three orthogonal policy axes with independently queryable configured and effective values."},
    {"id": "BR-DEC-020", "summary": "Store portable defaults, named profiles and allowed override policy in PRD Plugin configuration; store current workspace/agent overrides and operational state in AI-Collab; enforce delivery and claims in AI-Collab/Payload Fabric."},
    {"id": "BR-DEC-021", "summary": "Enforce listening before event delivery, prompt/context construction and model invocation, and enforce mute again at the server message-write boundary."},
    {"id": "BR-DEC-022", "summary": "Use precedence of emergency runtime disable, explicit per-agent workspace override, role/template policy, then repository/workspace default; more restrictive effective policy wins when authorities conflict."},
    {"id": "BR-DEC-023", "summary": "Disabling immediately blocks new admission and requests release of active claims at a safe boundary; force cancellation remains a separate explicit emergency operation."},
    {"id": "BR-DEC-024", "summary": "Re-enabling or resuming listening starts from current state plus a bounded deterministic summary; historical message replay is explicit rather than automatic."}
  ],
  "open_questions": [
    {"id": "BR-Q-001", "summary": "Should the first operator UI expose only the three simple agent controls, or also expose advanced per-channel listening and reply overrides immediately?", "recommendation": "Ship the three simple controls as the primary UI while the contract supports semantic-channel overrides for later expansion."},
    {"id": "BR-Q-002", "summary": "How should an owner make a persistent AI-Collab UI override become repository policy without creating bidirectional configuration writes?", "recommendation": "Require an explicit 'persist to repository policy' operation that emits a source-bound proposal and applies it only through the validated PRD configuration authority."}
  ],
  "risks": [
    {"id": "BR-RISK-022", "summary": "Listening is disabled only in the prompt, so the model still receives Lobby content and burns tokens.", "mitigation": "Filter before delivery, context assembly, wake and invocation; test that no model request is emitted."},
    {"id": "BR-RISK-023", "summary": "A muted agent still posts through another client, tool or retry path.", "mitigation": "Apply the reply policy in the authoritative message reducer/gateway and cover every client with contract tests."},
    {"id": "BR-RISK-024", "summary": "Disabling an agent strands an active Fabric lease or causes duplicate execution after reassignment.", "mitigation": "Fence attempts, record release_requested, reconcile the active claim transactionally and make reassignment idempotent."},
    {"id": "BR-RISK-025", "summary": "Repository defaults and live workspace overrides become competing configuration authorities.", "mitigation": "Separate desired defaults from operational overrides, publish deterministic precedence and prohibit silent reverse synchronization."},
    {"id": "BR-RISK-026", "summary": "Re-enabled agents consume large historical Lobby backlogs and repeat completed work.", "mitigation": "Resume from current goal/event state with a bounded summary and require an explicit replay range for history."},
    {"id": "BR-RISK-027", "summary": "The extra controls become an overengineered policy matrix that users cannot understand.", "mitigation": "Keep three primary booleans, derive effective state deterministically, hide advanced channel overrides until requested and show plain-language runtime consequences."}
  ],
  "candidate_prd_requirements": [
    "The workspace contract shall distinguish agent operational enablement, Lobby listening and Lobby reply authority.",
    "Listening-off shall prevent model invocation and token consumption for Lobby events.",
    "Muted shall allow permitted Lobby reasoning while server-side policy prevents Lobby publication.",
    "Disabled shall prevent new delivery, wake, scheduling and claims and shall safely reconcile active work.",
    "PRD configuration shall own portable defaults while AI-Collab owns live overrides and Payload Fabric enforces work admission.",
    "Every policy mutation and effective-state transition shall be queryable, source-bound and auditable."
  ],
  "candidate_tracking_updates": [],
  "candidate_health_findings": [],
  "related_artifacts": [
    "docs/brainstorm/BR-2026-07-15-substrate-capability-parity.json",
    "docs/audits/substrate-capability-parity-2026-07-15-reaudit.json"
  ],
  "next_recommended_artifact": "project-planning-lifecycle after the owner accepts the brainstorm: PRD, architecture and full implementation plan spanning PRD Plugin configuration/contracts and AI-Collab/Payload Fabric runtime enforcement."
}