cleanup before we spcify and implement more clearly

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.