coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
whynot-design/SCOPE.md
tegwick 5b7985f853
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Refresh SCOPE.md and generate WORK-RECORDS.md after WP-0003 close. 
Current State now reflects finished workplans plus residual
WHYNOT-IN-0001. The generated index lists live workplans and the open
intake; archived WP-0003 is omitted.

Assistant: grok
Assistant-Session: 01a04d7c-846d-77e3-af8d-020019e4eb61
2026-08-29 14:48:01 +02:00

953 B
Raw Permalink Blame History

SCOPE

This file was generated by statehub register. Refine it as the repository boundaries become clearer.

One-liner

The neutral, mostly-black-and-white visual language for whynot — Tegwick's prototype and market-signal organisation.

Core Idea

whynot-design exists to provide the capability described in INTENT.md.

In Scope

  • Maintain the repository's primary implementation.
  • Keep docs, tests, and operational metadata current.

Out of Scope

  • Own unrelated adjacent systems.
  • Make irreversible operational decisions without human approval.

Current State

  • Status: the visual language is published as @whynot/design. Bootstrap (WHYNOT-WP-0001), the IR/adapter pipeline (WHYNOT-WP-0002), and downstream consumption (WHYNOT-WP-0003) are finished.
  • Open residual: WHYNOT-IN-0001 (consumer npm-read lane).

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/