coulomb/whynot-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
whynot-control/workplans/WNCTL-WP-0002-beta-signal-intake.md
tegwick cadbe22d9e
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
fix(workplans): re-key WHYNOT-WP strays onto WNCTL-WP 
WHYNOT-WP belongs to whynot-design (26 ids vs 6 here), ruled by Bernd. The two
repos were cross-blocking in the hub: whynot-design could not claim
whynot-wp-0001 because this repo held it, and this repo could not claim
whynot-wp-0002 because whynot-design held that.

WNCTL-WP is newly registered to this repository. Numbers carry over unchanged
since nothing here used the new prefix. Both files declare repo: whynot-control,
so this is the repo's own work, not inherited template residue.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 14:15:09 +02:00

786 B
Raw Permalink Blame History

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
WNCTL-WP-0002 workplan Beta signal intake pipeline consumer whynot-control finished codex consumer 2026-06-22 2026-07-03 f0b119be-93f7-4115-a83c-1c54060d1ce3

Beta signal intake pipeline

Structure how prototype signals, betas, and feedback enter the whynot organization.

Beta intake pipeline

id: WNCTL-WP-0002-T01
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.