cleanup before we spcify and implement more clearly

.custodian-brief.md

@@ -2,16 +2,12 @@
 # Custodian Brief — whynot-control
 
 **Domain:** consumer  
-**Last synced:** 2026-07-03 16:26 UTC  
+**Last synced:** 2026-07-03 18:41 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### Beta signal intake pipeline
-Progress: 0/1 done  |  workstream_id: `f0b119be-93f7-4115-a83c-1c54060d1ce3`
-
-**Open tasks:**
-- · Beta intake pipeline  `cbe32490`
+*(none — repo may need first-session setup)*
 
 ---
 ## MCP Orientation (when available)

BETA_SIGNAL_INTAKE.md

@@ -0,0 +1,59 @@
+# Beta Signal Intake
+
+## Purpose
+
+This playbook defines how a `whynot` idea moves from prototype intake through beta, signal review, and promotion decision.
+
+## Flow
+
+### 1. Intake and Triage
+
+- Capture loose ideas in `inbox/`.
+- Use `PROTOTYPE_PIPELINE.md` Stage 0 and Stage 1 to decide whether to park, reject, merge, or create a prototype card.
+- If the idea deserves structured work, create a prototype card from `templates/prototype-card.md` in `prototypes/`.
+
+### 2. Prototype Readiness
+
+A prototype is ready for beta planning when it has:
+
+- a named audience;
+- a learning question;
+- a smallest useful test;
+- an expected signal;
+- a plausible promotion target if the signal is positive.
+
+### 3. Beta Planning
+
+- Use `BETA_MODEL.md` to choose the beta type and confirm entry criteria.
+- Create a beta plan from `templates/beta-plan.md` in `betas/`.
+- Keep the beta small, explicit, and reversible.
+
+### 4. Signal Capture
+
+- Record feedback and market evidence in `signals/`.
+- Use `MARKET_SIGNAL.md` and `templates/signal-record.md`.
+- Preserve null, weak, and contradictory signals rather than rewriting history.
+
+### 5. Promotion Decision
+
+- Review prototype state, beta notes, and signal strength together.
+- Draft a decision from `templates/promotion-decision.md`.
+- Record the final promotion or non-promotion outcome in `DECISIONS.md`.
+
+## Required Artifacts
+
+| Stage | Required artifact | Location |
+|---|---|---|
+| Intake | raw note or captured idea | `inbox/` |
+| Prototype | prototype card | `prototypes/` |
+| Beta | beta plan | `betas/` |
+| Signal | signal record | `signals/` |
+| Decision | promotion decision record | `DECISIONS.md` and optionally a filled copy of `templates/promotion-decision.md` |
+
+## Seeded Agent Tasks
+
+- `agent-tasks/triage-prototype-intake.md`
+- `agent-tasks/prepare-beta-plan.md`
+- `agent-tasks/review-signals-and-draft-decision.md`
+
+Use these when the repo needs a repeatable agent prompt instead of ad hoc instructions.

README.md

@@ -9,9 +9,10 @@ Control repository for the `whynot` organization.
 1. Read `INTENT.md`.
 2. Review `SCOPE.md`.
 3. Use `PROTOTYPE_PIPELINE.md` to classify ideas.
-4. Capture loose ideas in `inbox/`.
-5. Create prototype cards only for ideas that deserve structured exploration.
-6. Promote only validated candidates toward Helix, Coulomb, Sloppers, Plenitude, or Binky.
+4. Use `BETA_SIGNAL_INTAKE.md` for the prototype -> beta -> signal -> decision flow.
+5. Capture loose ideas in `inbox/`.
+6. Create prototype cards only for ideas that deserve structured exploration.
+7. Promote only validated candidates toward Helix, Coulomb, Sloppers, Plenitude, or Binky.
 
 ## Core Principle
 

agent-tasks/prepare-beta-plan.md

@@ -0,0 +1,35 @@
+# Agent Task: Prepare Beta Plan
+
+## Goal
+Draft a small, controlled beta plan for a named prototype.
+
+## Context
+`whynot` uses closed betas to learn quickly without implying production maturity. Beta rules are defined in `BETA_MODEL.md`.
+
+## Inputs
+- A prototype card from `prototypes/`
+- `BETA_MODEL.md`
+- `templates/beta-plan.md`
+
+## Allowed Changes
+- Create or refine a beta plan in `betas/`.
+- Clarify the learning question, target audience, entry criteria, and feedback method.
+- Recommend the most appropriate beta type.
+
+## Forbidden Changes
+- Do not announce a public beta.
+- Do not promise production readiness.
+- Do not add payment or investment mechanics unless explicitly approved.
+
+## Expected Output
+- One beta plan with a clear learning question, beta type, entry criteria, feedback method, and end condition.
+
+## Acceptance Criteria
+- The plan names the prototype and audience.
+- The plan explains how feedback will be captured.
+- The beta is small and reversible.
+
+## Human Approval Required For
+- Public launch language.
+- Paid beta mechanics.
+- Cross-repo implementation commitments.

agent-tasks/review-signals-and-draft-decision.md

@@ -0,0 +1,38 @@
+# Agent Task: Review Signals And Draft Decision
+
+## Goal
+Turn prototype and beta evidence into a clear signal review and draft promotion decision.
+
+## Context
+Signals are evidence, not enthusiasm. `MARKET_SIGNAL.md` defines strength levels, and `PROTOTYPE_PIPELINE.md` requires an explicit decision before promotion.
+
+## Inputs
+- A prototype card
+- Any related beta notes or beta plan
+- Signal notes or records
+- `MARKET_SIGNAL.md`
+- `templates/signal-record.md`
+- `templates/promotion-decision.md`
+
+## Allowed Changes
+- Create or refine signal records in `signals/`.
+- Summarize beta feedback faithfully.
+- Draft a promotion decision for later human review.
+
+## Forbidden Changes
+- Do not upgrade weak evidence into strong signal.
+- Do not hide contradictory evidence.
+- Do not mark promotion as final without explicit approval.
+
+## Expected Output
+- A signal summary with strength assessment.
+- A draft decision: promote, iterate, park, reject, or merge.
+
+## Acceptance Criteria
+- Evidence and counter-evidence are both represented.
+- The recommendation matches the recorded signal strength.
+- The proposed next step is explicit.
+
+## Human Approval Required For
+- Final promotion into another initiative.
+- Any external-facing launch or commercial claim.

agent-tasks/triage-prototype-intake.md

@@ -0,0 +1,34 @@
+# Agent Task: Triage Prototype Intake
+
+## Goal
+Turn a rough idea into a clear triage outcome: prototype card, merge, park, or reject.
+
+## Context
+`whynot-control` uses `PROTOTYPE_PIPELINE.md` to move ideas from raw capture into structured prototype exploration.
+
+## Inputs
+- One item from `inbox/` or an equivalent rough note.
+- `PROTOTYPE_PIPELINE.md`
+- `templates/prototype-card.md`
+
+## Allowed Changes
+- Create or refine a prototype card in `prototypes/`.
+- Improve wording and structure of the input note.
+- Recommend park, merge, or reject when a prototype card is not justified.
+
+## Forbidden Changes
+- Do not treat the idea as a committed product.
+- Do not invent signal evidence that does not exist.
+- Do not create beta, pricing, or public launch commitments.
+
+## Expected Output
+- One explicit triage outcome.
+- If promoted to prototype, one draft prototype card with learning question, test, and expected signal.
+
+## Acceptance Criteria
+- The output states who might care, what is being tested, and the smallest useful next step.
+- The outcome is one of: prototype card, merge, park, or reject.
+
+## Human Approval Required For
+- Promoting the idea beyond prototype exploration.
+- Making external commitments.

workplans/WHYNOT-WP-0002-beta-signal-intake.md

@@ -4,11 +4,12 @@ type: workplan
 title: "Beta signal intake pipeline"
 domain: consumer
 repo: whynot-control
-status: ready
+status: finished
 owner: codex
 topic_slug: consumer
 created: "2026-06-22"
-updated: "2026-06-22"
+updated: "2026-07-03"
+state_hub_workstream_id: "f0b119be-93f7-4115-a83c-1c54060d1ce3"
 ---
 
 # Beta signal intake pipeline
@@ -19,8 +20,11 @@ Structure how prototype signals, betas, and feedback enter the whynot organizati
 
 ```task
 id: WHYNOT-WP-0002-T01
-status: todo
+status: done
 priority: high
+state_hub_task_id: "cbe32490-2bc3-4a87-a9b3-faf6fe9d3723"
 ```
 
+Result 2026-07-03: Added `BETA_SIGNAL_INTAKE.md`, linked it from `README.md`, and seeded intake-specific prompts in `agent-tasks/`.
+
 Document intake stages from prototype → beta → signal → promotion decision; seed first agent-tasks/ entries.