@erclx/canon 5.31.0 → 5.33.0

package/standards/wireframes.md

@@ -1,143 +0,0 @@
----
-title: Wireframe reference
-description: Shape and content rules for canon/wireframes/<surface>.md files
-paths:
-  - 'canon/wireframes/**'
-rule:
-  - 'Read it before adding or revising a surface.'
----
-
-# Wireframe reference
-
-Applies to per-surface entries under `canon/wireframes/`. Skip for `index.md`, which is regenerated by `canon indexes regen`.
-
-A wireframe file captures the spatial layout and interaction intent of one UI surface. It is not an implementation log. The check for any single line: would it still be true if the surface were rebuilt in a different framework? If not, it belongs in `canon/context/`.
-
-## Scope
-
-Governs per-surface wireframe entries under `canon/wireframes/`: layout, variants, on-screen copy, and interaction intent.
-
-Does not govern:
-
-- Tokens, typography, spacing, and the rest of the visual system: `design.md`
-- The mechanism behind a surface: `context.md`
-- Voice, rhythm, and sentence construction in wireframe prose: the `write-human` skill
-- Punctuation, formatting, and word choice in wireframe prose: `markdown.md`
-
-## What a working wireframe looks like
-
-A wireframe works when someone can rebuild the surface from it without opening the components:
-
-- What regions are on screen, by name, and where does each sit relative to the others?
-- Which states can a visitor reach, what triggers each, and where is its captured evidence?
-- What does its structural copy say, word for word, and where does its long-form content come from?
-- What was deliberately left off the surface?
-
-A wireframe that fails these is non-conforming regardless of whether it satisfies every section rule below. The sections are the means. These four questions are the test.
-
-## Transcription wireframes
-
-A wireframe regenerated from an already-built surface's own render code may carry what the sections below forbid: the source file and function, the class or token names driving each region, and pixel-exact geometry. Open the file by naming that source: the render function, the stylesheet rule, or the built file the block was read off. The citation is what separates a transcription wireframe from one that merely broke the rules below, since a role label with nothing behind it is unchecked and a class name traced to a real file and line is not.
-
-A drafted-ahead wireframe states intent in role terms because nothing exists yet to check it against. A regenerated one is checkable against the code it mirrors, and a role label standing in for the real class name would throw that check away. The two documents answer different questions, so one set of rules cannot govern both.
-
-Route detail the source citation does not already carry to `canon/context/` as usual: algorithms, event-handler code, workarounds, and rejected approaches stay out of the wireframe regardless of which mode it is written in.
-
-## Frontmatter
-
-- `title` (required): sentence case, names the surface (`Header`, `Section nav`, `Footer`).
-- `description` (required): one line on when and where the surface appears.
-
-Both fields feed `canon/wireframes/index.md` when regenerated.
-
-## Regions
-
-- Name every region the surface holds, in a bullet list ordered as a reader scans the page, each with where it sits relative to the others: `- Act pane: right of the answer from 1024 up, an overlay below 1024`. These names are the vocabulary plans, picks, and tests use, and the placement is what a list without a sketch would otherwise lose. Pixel sizes stay in `canon/DESIGN.md`.
-- Draw an ASCII block inside a `plaintext` fence only for a layout that is not built yet. Label regions with `←` annotations, show a region's role rather than its styling, and keep the proportions honest.
-- Remove the fence in the change that first captures evidence for the layout. The capture is the exact picture, and a sketch kept beside it drifts from it. A wireframe carrying both a sketch and an evidence folder for the same layout is non-conforming.
-- Give a layout that changes across a breakpoint its own entry under the list, named by what triggers it (`At 1024 and wider`), not by an arbitrary label. A wider gutter alone is not a new layout.
-- Keep one surface per file, indexed by `index.md`.
-
-## States
-
-- List every state a visitor can reach in one table: the state name, what reaches it, what it shows in words, and its evidence folder.
-- Name a state in plain kebab case (`answered`, `refused`) and name its evidence folder the same way, with no ordinal prefix. The table carries the reading order, so a state added in the middle renames nothing.
-- Keep the table and the evidence folders one-to-one. A state with no capture yet reads `not captured` in its evidence cell, which is the one exception, and it stays visible until the capture lands.
-- Add an H3 below the table only for a state that needs more than its row: what differs from the regions in words, and its own copy or behavior.
-
-## Copy
-
-- Carry short structural text verbatim, in the ASCII block or a short list below it: labels, headings, empty-state strings, and nav or footer copy. The wireframe is the source of truth for this text.
-- Cite the source file for long-form or article-body content instead of duplicating it. A lede sentence or a body paragraph pulled into an ASCII figure drifts the moment its source changes, and nothing checks a fenced block against prose elsewhere. A citation elsewhere in the file does not excuse the block itself from still carrying the duplicate. Trim the block once the citation exists.
-- Mark copy that is dynamic or templated so a reader does not treat a placeholder as final text.
-
-## Behavior
-
-- Describe interaction intent: what the visitor does and what changes on screen.
-- State the rule, not the mechanism. `The rail tracks the active section as the visitor scrolls` is intent. The scroll handler, throttle, and observer margins are not.
-- Keep it to a short list. A Behavior section longer than the regions and states is a sign implementation detail has leaked in.
-
-## Not on this surface
-
-- State what was deliberately left off, one bullet per exclusion, as a present-tense rule: `- No navigation rail`. This is the section that stops a draft from proposing what was already ruled out.
-- Keep the reason to a clause where one is needed. Cut the rounds that ruled it out.
-
-## What moves out
-
-- Which candidate beat which, and when: nowhere. Cut it, since git keeps the old text
-- Measurements such as contrast ratios and timings: `canon/DESIGN.md` for tokens and floors, the surface's context entry for the rest
-
-## What moves to canon/context/
-
-This section does not govern a transcription wireframe's citation of its own source. See `## Transcription wireframes`. Implementation detail that answers how the surface is built belongs in a `canon/context/` entry, not the wireframe:
-
-- Algorithms, event-handler code, and lifecycle ordering
-- Framework component names, props, and CSS class or token names
-- Pixel-exact spacing, timing constants, and observer thresholds
-- Workarounds and rejected approaches
-
-Reference the context entry from the wireframe by path when a reader needs the mechanism. The wireframe stays answerable on its own for layout and intent.
-
-## Maintenance
-
-- When a surface's layout or interaction changes, update its wireframe file in the same PR. A wireframe showing a defunct layout is worse than none.
-- When a state is added, removed, or renamed, update its row and its evidence folder in the same PR.
-- The Behavior and Copy prose around an ASCII block is prose and follows `markdown.md` and the `write-human` skill. The fenced block itself is not, so a check scoped to prose is the wrong thing to rely on for what sits inside it.
-
-## Template
-
-```markdown
----
-title: <Surface name>
-description: <when and where the surface appears>
----
-
-# <Surface name>
-
-<One paragraph: what the surface is for and what it covers.>
-
-## Regions
-
-- <Region>: <what it holds>, <where it sits relative to the others>
-- <Region>: <what it holds>, <where it sits relative to the others>
-
-## States
-
-| State   | Reached when | Shows      | Evidence                   |
-| ------- | ------------ | ---------- | -------------------------- |
-| <state> | <trigger>    | <in words> | `<evidence-root>/<state>/` |
-
-## Copy
-
-- <on-screen text, word for word>
-- <text the surface templates>: <marked so a reader does not read it as final>
-- <long-form content>: cited at <its source file>, not duplicated here
-
-## Behavior
-
-- <what the visitor does, and what changes on screen>
-
-## Not on this surface
-
-- <what was deliberately left out, as a present-tense rule>
-```

package/tooling/claude/seeds/.claude/memory/index.md

@@ -1,8 +0,0 @@
----
-title: Memory
-subtitle: Session facts with no owning surface, grouped by kind. Feedback is the working set.
----
-
-# Memory
-
-Session facts with no owning surface, grouped by kind. Feedback is the working set.

package/tooling/claude/seeds/canon/ARCHITECTURE.md

@@ -1,23 +0,0 @@
-# Architecture
-
-Authoring guidance: the architecture standard.
-
-## Overview
-
-This record holds at most 12 decisions, at most 150 words a decision, and at most 6 risk bullets.
-
-## Key technical decisions
-
-### Stack and runtime
-
-What was chosen, the alternative that lost, and why.
-
-### Delivery
-
-### Enforced boundaries
-
-### Layout
-
-### Build principles
-
-## Risks / open questions

package/tooling/claude/seeds/canon/wireframes/index.md

@@ -1,8 +0,0 @@
----
-title: Wireframes
-subtitle: Per-surface regions and states loaded on demand
----
-
-# Wireframes
-
-Per-surface regions and states loaded on demand