whynot-control/WORKPLAN.md

Workplan

Goal

Establish whynot-control as the control repository for prototype exploration, market-signal capture, and early validation.

Phase 0 — Create the Repository

Objective

Create the initial repo structure and seed the core documents.

Tasks

• Create whynot-control in the whynot Gitea organization.
• Add core documents.
• Create inbox/, prototypes/, signals/, betas/, offers/, templates/, and agent-tasks/.

Done When

The repository exists and provides a first usable control surface for prototype exploration.

Phase 1 — Establish Intake

Create a reliable way to capture and triage ideas.

Tasks:

• Define intake rules.
• Add the prototype card template.
• Add the signal record template.
• Add the experiment record template.
• Add the beta plan template.
• Define when an idea becomes a prototype candidate.

Phase 2 — Seed Initial Prototype Candidates

Create the first small set of prototype cards.

Tasks:

• Identify 3–7 candidate ideas.
• Write a prototype card for each.
• Assign lifecycle stage.
• Assign likely promotion target.
• Define smallest useful test.

Phase 3 — Define Signal Capture

Make feedback and market signal visible.

Tasks:

• Define signal strength scale.
• Create first signal records.
• Connect signals to prototype cards.
• Identify weak vs strong evidence.

Phase 4 — Prepare Closed Beta Model

Create a controlled path for early users and feedback.

Tasks:

• Define beta types.
• Define beta entry criteria.
• Define beta exit outcomes.
• Create a first beta plan template.

Phase 5 — Define Promotion Criteria

Prevent premature productization while enabling strong ideas to move forward.

Tasks:

• Define promotion criteria for Helix.
• Define promotion criteria for Coulomb.
• Define promotion criteria for Sloppers.
• Define promotion criteria for Plenitude.
• Define when Binky must be involved.

Phase 6 — Connect to Tegwick Landscape

Ensure whynot remains aligned with the broader project landscape.

Tasks:

• Add a reference from tegwick-control.
• Confirm activation level.
• Document dependencies.
• Create initial review rhythm.