# 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/

## Generated work-record index

This repository opts into staged-source WORK-RECORDS.md generation through
`.generated-work-records.json` and the isolated `.generated-work-records.mk`
recipe. `make generated-work-records` reuses the State Hub renderer through
the Custodian adapter; `make generated-work-records-check` verifies byte-exact
agreement with staged Markdown. The pre-commit hook uses the isolated recipe,
preserves unstaged index edits by refusing them, and retains the generated-only
commit guard. It does not contact the hub, alter workplan statuses, or grant
deployment authority. This consumes shared tooling; it does not make this
repository the provider of the generator capability.