@erclx/canon 5.52.0 → 5.54.0

package/claude/skills/teach-workspace/references/promotion.md

@@ -1,116 +0,0 @@
-# Promotion routing
-
-Which surface a durable page from a learning workspace belongs to, and what to do when the destination does not exist yet.
-
-## What may be promoted
-
-Only the durable half. A reference page under `reference/` and `GLOSSARY.md` carry no learner and are ordinary reference prose about a subject, so they sort under the routing test like anything else.
-
-A lesson is never promoted, at any age and on any request. It is generated markup worked through once, carrying a quiz and a second person, and nothing downstream cites it.
-
-- Promoting one puts ungated markup into a corpus every other page passed a gate to enter
-- A reference page carrying a quiz, a second person, or an instruction to the learner is a lesson wearing the wrong extension
-- Say so, and propose rewriting that page in place before promotion rather than repairing it at the destination
-
-## The routing test
-
-Sort by who owns the subject, which is the test the wiki already runs. The reader's activity decided the workspace and decides nothing here.
-
-| The page's subject                                                                                                   | Destination                                                                                               |
-| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
-| Owned by Anthropic                                                                                                   | the project's wiki                                                                                        |
-| Owned by another tool or vendor, owned by no single vendor, or written for someone consuming what this project ships | the project's public docs                                                                                 |
-| How this project itself works, for the people who build it                                                           | `canon/context/<domain>.md`, or the domain's own nested `index.md` when it is already split into a folder |
-
-A page a reader cannot sort by that question is a page whose subject has not been settled. Say which two destinations it sits between and let the operator choose, rather than picking the nearer one.
-
-## Where the wiki sits
-
-The folder has two spellings and a project carries whichever the project created:
-
-- `.claude/wiki/`, the folder inside the Claude setup
-- A folder named `wiki` at the project root
-
-Read which one exists rather than composing either. A project carrying both keeps its pages at the root, so propose the root spelling and say the other folder is there.
-
-### Neither spelling
-
-A project carrying neither gets a refusal rather than a scaffold:
-
-```plaintext
-❌ No wiki folder. Create `.claude/wiki/` with an `index.md`, then promote again.
-```
-
-Creating the folder as a side effect of promoting one page hands the project a surface it never chose, and the refusal is one step from resolved.
-
-## What a promoted page owes its destination
-
-Each destination gates prose the workspace does not, so name what the page still needs rather than proposing a move that fails at the gate.
-
-- A wiki page closes its intro paragraph with a sentence naming who owns the subject, and links the canonical page when one exists. A page carrying no such sentence is not ready to move.
-- A context entry is internal narrative about one domain, so a page landing there merges into an existing entry rather than arriving as a new one.
-- A glossary keeps the shape `glossary.md` fixes wherever it lands, and a promoted one has to state any rule it departs from.
-
-## Anti-patterns
-
-- **The page promoted into a new context entry.** Entries are created deliberately, so a promotion proposing one is proposing a domain rather than moving a page.
-- **The glossary split across destinations.** Terms drawn from one subject move together or not at all, since an entry defining a term the other half uses strands both.
-- **The workspace emptied on promotion.** Promotion copies rather than moves. The workspace stays readable to the learner who built it, and the page's later life belongs to its destination.
-
-## Proposing and handing off
-
-Step 6 of `teach-workspace` reads this section once the routing above has placed each page. Propose and wait. A promoted page is public prose that needs a line naming who owns its subject, which is a judgment about ownership rather than a move a session makes on its own reading. Present one block per candidate page:
-
-```plaintext
-reference/<slug>.md → <destination path>
-Subject owner: <who owns it, in a few words>
-Still owed:    <what the destination expects that the page does not carry yet>
-```
-
-Then stop and let the operator strike, redirect, or confirm each block.
-
-### Record the handoff
-
-Write nothing to a destination here. One skill owns the durable writes, and two skills editing one file at one step is the failure that rule exists against.
-
-Record each confirmed block in `.canon/tmp/handoff/teach-promotion/<slug>.md` at the main worktree root instead, appending when the file exists. Each destination takes one H2 naming its path, the source page beneath it, and the page body fenced:
-
-````markdown
-## <destination path>
-
-Source: .canon/teach/<nn>-<topic>/reference/<slug>.md
-
-```markdown
-<the page body as it should land, with the source line the destination expects>
-```
-````
-
-Derive `<slug>` per `${CLAUDE_SKILL_DIR}/../git-branch/references/slug.md`. Fall back to `latest` on an empty result.
-
-### Why the fence
-
-A reference page carries headings of its own, and the reader splits this file on its H2 lines. An unfenced body turns every section heading in the page into a destination naming no path.
-
-- Open the body fence with four backticks, so a page carrying a fenced code block still closes where it should
-- Widen both fences together if the page carries a four-backtick fence
-
-### Why a file of its own
-
-The routed-facts file another skill writes is deleted by whichever pass folds it, so a second producer's unread work would go with it. A sibling path costs the folding skill one more read and removes the interaction.
-
-### Sending and reporting
-
-An append is a whole-file operation, so send it as a heredoc, per the skill's Step 0. Then tell the operator that `/teach-workspace fold` folds the file in from a branch.
-
-The proposal costs nothing tracked and runs anywhere. The page it describes is a tracked file, so the fold is a worktree operation and the workspace it came from is not.
-
-### Output
-
-A promotion pass reports this shape in place of the skill's Output block, one line per page the operator confirmed and one naming the handoff:
-
-```plaintext
-➡️ Promoting: .canon/teach/<nn>-<topic>/reference/<slug>.md → <destination path>
-→ Confirmed pages wait at .canon/tmp/handoff/teach-promotion/<slug>.md. Run /teach-workspace fold from a branch to fold them in.
-```
-
-A pass where the operator confirmed nothing writes no handoff file and reports that alone.

package/claude/skills/teach-workspace/references/revisit.md

@@ -1,28 +0,0 @@
----
-title: Revisit schedule
-description: How teach-workspace Step 5 writes a learning record's Revisit section, being the bullet shape, where each date and rung is copied from, the first schedule for a new item, and how a later record revises one
----
-
-# Write the Revisit section
-
-Part of Step 5 of `teach-workspace`. The session reads this file once the record's lessons, retrievals, and wrong answers are written, before restating the mission's success lines.
-
-Then write `## Revisit`, one bullet per item, in the shape `${CLAUDE_SKILL_DIR}/references/teach.md` fixes:
-
-```markdown
-## Revisit
-
-- **<what comes back up>**: due <YYYY-MM-DD>, rung <n>
-```
-
-## Where the date comes from
-
-Take both the date and the rung from the `due` entry Step 1 already read. Copy `hit` for an item the learner retrieved unaided and `miss` for one they did not, with the rung stepped the same way.
-
-- Do not compute a date from the ladder. A session told to widen a gap still picks the number by judgment, which is why the verb reports both dates.
-- An item never scheduled has no `due` entry. Open it at rung 1, dated the day after this session, the ladder's floor and the one number this body states.
-- Every later date for that item comes from the verb
-
-## Writing the shape exactly
-
-An entry outside this shape schedules nothing and nothing reports that it was skipped, so write the shape exactly. A later record naming the same item supersedes an earlier entry, so revise a schedule by writing the new bullet rather than editing the record it was set in.

package/claude/skills/teach-workspace/references/teach.md

@@ -1,211 +0,0 @@
----
-title: Teach reference
-description: Workspace layout, ordinal naming, frontmatter, and the mission and learning-record formats for a learning workspace
----
-
-# Teach reference
-
-Applies to a learning workspace at `.canon/teach/<nn>-<topic>/`. One workspace holds one subject studied across sessions, and it carries both halves of what studying produces: the durable reference material a reader consults later, and the disposable lessons a learner works through once.
-
-The folder is gitignored. Its markdown half is written in a format the authoring gates read, so a page promoted out of it later needs no conversion.
-
-## Contents
-
-- [Scope](#scope)
-- [What a working workspace looks like](#what-a-working-workspace-looks-like)
-- [Folder name](#folder-name)
-- [Layout](#layout)
-- [Frontmatter](#frontmatter)
-- [File naming](#file-naming)
-- [MISSION.md](#missionmd)
-- [Learning records](#learning-records)
-- [Revisit](#revisit)
-- [GLOSSARY.md](#glossarymd)
-- [RESOURCES.md](#resourcesmd)
-- [Conventions](#conventions)
-- [Anti-patterns](#anti-patterns)
-- [Template](#template)
-
-## Scope
-
-Governs a learning workspace under `.canon/teach/<nn>-<topic>/`: folder layout, ordinal naming, frontmatter, and the mission and learning-record formats.
-
-Does not govern:
-
-- **the `teach-workspace` skill**: the frontmatter, entry shape, and ordering of the glossary the workspace holds, which that skill's reference carries
-- **the surface driving the workspace**: what a lesson teaches, how it sequences difficulty, and what makes one worth returning to
-- **the routing test the destination surface states**: where a durable page goes once it leaves the workspace
-- **`groundwork.md`**: one question measured in depth before anyone can plan against it
-- **`intake.md`**: A dump of many findings filed by domain, each carrying its own verdict
-- **the `write-human` skill**: voice, rhythm, and sentence construction
-- **`markdown.md`**: headings, punctuation, word choice, and file references
-- **the surface driving it**: when a workspace opens at all, and the procedure that runs one
-
-## What a working workspace looks like
-
-A workspace works when a session returning after weeks can resume from the folder alone:
-
-- Which subject is being learned, and what will the learner be able to do when the mission is finished?
-- Which sources stand behind the material, and which were found and never opened?
-- What has the learner already been through, and what did they get wrong?
-- Which pages here are durable reference material, and which are disposable?
-
-A workspace failing these is non-conforming even when it satisfies every shape rule below.
-
-## Folder name
-
-- Name the folder `<nn>-<topic>`, a two-digit zero-padded ordinal followed by a kebab-case topic slug.
-- Take the ordinal from the highest one already present, incremented. A listing then sorts by when each workspace opened rather than alphabetically.
-- Use two digits on the folder and four inside it. A person opens far fewer workspaces than one workspace holds lessons.
-- Never renumber an existing folder. The ordinal is the order it opened, and a later reader cites it by that name.
-
-## Layout
-
-| Path                    | Holds                                                                   | Required |
-| ----------------------- | ----------------------------------------------------------------------- | -------- |
-| `MISSION.md`            | The subject, the learner's starting point, and success                  | Always   |
-| `RESOURCES.md`          | Sources read and sources found but not opened                           | Always   |
-| `GLOSSARY.md`           | Terms the subject defines, one entry each                               | Always   |
-| `NOTES.md`              | Session scratch that belongs to no other file                           | Optional |
-| `reference/<slug>.md`   | Durable reference pages, the promotable half                            | Optional |
-| `reference/<slug>.html` | Each reference page rendered by `canon teach nav`, never edited by hand | Optional |
-| `learning-records/`     | Numbered records of what the learner was taken through                  | Optional |
-| `lessons/`              | Numbered lessons, generated and disposable                              | Optional |
-| `assets/`               | Files several lessons share, including the stylesheet                   | Optional |
-
-Only the markdown half answers to a conformance check: `MISSION.md`, `RESOURCES.md`, `GLOSSARY.md`, `NOTES.md`, the markdown under `reference/`, and `learning-records/`.
-
-- A lesson is generated markup nothing downstream cites, so this standard fixes its filename and location and nothing about its contents
-- A rendered reference page is the same kind of output, rewritten from its markdown on every `nav` run
-
-## Frontmatter
-
-Every markdown file carries `title` and `description`. `MISSION.md` carries one field the others do not.
-
-- `title` (required): what the file covers, in sentence case
-- `description` (required): one line naming what a reader gets from it
-- `date` (required, `MISSION.md` only): the day the workspace opened, as `YYYY-MM-DD`
-
-Date the workspace once rather than every file. A per-file date leaves every other file stale the first time one is edited, and the opening date never rots.
-
-## File naming
-
-- Number a lesson and a learning record `0001` upward, as `<nnnn>-<slug>.html` and `<nnnn>-<slug>.md`. The number is read order and never changes.
-- Name a reference page for its subject alone, with no number. A reference page is looked up rather than worked through, so an ordinal on one implies an order no reader follows.
-- Keep one shared stylesheet under `assets/` and embed it in every lesson. A lesson restating its own styles makes a workspace read as a pile of one-offs rather than as one course.
-
-## MISSION.md
-
-Fixes what the workspace is for. Everything else in the folder answers to it.
-
-- A one-line statement of the subject
-- A `## Starting point` section stating what the learner already knows, so difficulty has a floor to sit above
-- A `## Success looks like` section listing specific observable things the learner will be able to do
-- A `## Out of scope` section naming what this workspace deliberately does not cover
-
-Write each success line as something a learner can be asked to do rather than something they will understand. A line nobody can test is a line nothing can report progress against.
-
-## Learning records
-
-One record per session the learner worked through, holding what happened rather than what was taught.
-
-- The lessons covered, by number
-- What the learner retrieved correctly without help
-- What they got wrong, and what the wrong answer was, including what an explanation the learner produced left out
-- A `## Revisit` section scheduling what comes back up
-
-Record the wrong answer rather than the fact of an error. A wrong answer names the misconception, and the count alone names nothing.
-
-A produced explanation and a selected option are both retrieval, so a gap in an explanation goes under what the learner got wrong rather than under a heading of its own. Name the concept and where the explanation broke. Splitting the two puts one input to the next session's placement across two sections, and the placement reads both or neither.
-
-### The revisit section
-
-Write one bullet per item, in this shape and no other:
-
-```markdown
-## Revisit
-
-- **<what comes back up>**: due <YYYY-MM-DD>, rung <n>
-```
-
-The rung is the item's place on the spacing ladder. It travels in the record rather than being counted from records naming the item, since a miss drops it back and a count only climbs.
-
-- A later record naming the item supersedes an earlier one, so revise by writing a new entry rather than editing the old record
-- Take the date and rung from what the driving surface reports. An entry outside this shape schedules nothing, silently.
-
-## GLOSSARY.md
-
-Required at the root of every workspace, one entry per term the subject defines. The glossary reference the `canon:teach-workspace` skill carries fixes the entry shape, order, grouping, and which terms it holds.
-
-- That reference ships with the plugin rather than installing here, since a promoted glossary keeps its shape wherever it lands
-- With no plugin to read it from, say so and stop rather than working the shape from memory
-- Name the lesson or reference page a term first appears in, which a workspace always has
-
-## RESOURCES.md
-
-Splits what was read from what was found.
-
-- List every source that stands behind the material, each with a link
-- List under a leads heading any source found and not opened, and never cite one
-- Say which claims in the workspace rest on which source
-
-An unread source is a lead because a link to a page nobody opened is worse than none. Listing it stops a later session searching again.
-
-### Choosing sources
-
-Rest each general claim on the highest rung that covers it:
-
-1. Documentation or a specification published by whoever owns the subject
-2. A canonical work on the subject, such as the standard text, a reference book, or a primary paper
-3. Other material, such as a tutorial, a course, or a post, and only for a claim the first two rungs do not cover
-
-A subject nobody owns, such as a mathematical topic or a craft, has no first rung, so its list starts at the second and is not missing anything. Record a third-rung source with the claim it covers and why no higher rung does, since that reason is what a later session checks the choice against.
-
-### What never counts
-
-The learner's own projects and material specific to one employer or organization are never a source for a general claim. Either may appear in the workspace as a worked application labeled with whose it is, and neither stands in `RESOURCES.md` as proof of what the subject says.
-
-A source reachable only through a paywall or a summary stays a lead until it is opened. A review or summary of a book is a different source from the book, so list the summary as read on its own rung and the book as a lead.
-
-## Conventions
-
-- Write the markdown half in the format the authoring gates read, so a page promoted later needs no conversion.
-- Keep a reference page free of the learner. A page carrying a second person or a quiz is a lesson wearing the wrong extension, and it cannot be promoted.
-- Revise a file the subject has moved under rather than appending a second version narrating the change.
-
-## Anti-patterns
-
-- **The mission with no test.** Success stated as understanding rather than as a task leaves nothing able to say the mission is finished.
-- **The lesson filed as reference.** A page written to be worked through once sits in `lessons/`, and putting it in `reference/` puts disposable output in the half that gets promoted.
-- **The record that counts errors.** A tally of how many were missed carries none of the misconception, which is the only part a later session can act on.
-- **The revisit note with no date.** A line naming what to come back to and not when schedules nothing, so the next session picks from the last record alone, the state the section exists to end.
-- **The date left in the body.** A frontmatter field and a sentence both claiming the opening date resolve to whichever a reader hits, and a walker reads only one.
-- **The first search result as the source list.** A workspace resting on the first search hit teaches the weakest account of the subject, and nothing in the folder says a stronger one went unsought.
-- **The renumbered folder.** Closing a gap in the ordinals moves every name a reader or a record already cited.
-
-## Template
-
-```markdown
----
-title: <Subject>
-description: <one line naming what a learner gets from this workspace>
-date: <YYYY-MM-DD>
----
-
-# <Subject>
-
-<One line stating the subject.>
-
-## Starting point
-
-<What the learner already knows.>
-
-## Success looks like
-
-- <a specific thing the learner will be able to do>
-- <a specific thing the learner will be able to do>
-
-## Out of scope
-
-- <what this workspace deliberately does not cover>
-```

package/claude/skills/video-craft/REQUIREMENT.md

@@ -1,35 +0,0 @@
----
-name: video-craft
-description: Why a session composing a video of software needs sourced judgment on captions, zoom, pointer, and audio beyond what HyperFrames' own skills carry, and why every number in it has to trace to a source
----
-
-# Video craft requirement
-
-## Gap
-
-Without this skill, a composed video of software gets general motion craft from HyperFrames and nothing on top. Nothing says what a caption says, which moment earns a zoom, how a recorded pointer behaves, or how far music sits under a voice. A render pushes in slowly, narrates the whole flow in one caption, and opens on a slogan card.
-
-Numbers from recall are the second gap. HyperFrames states its zoom duration with no source, and its default music bed sits closer under a voice than the accessibility guideline asks. A session taking either as given reproduces the defaults that read generic.
-
-## Must
-
-- A caption names only what its frame shows, with its timing, line count, line length, and reading rate traced to published subtitle guidelines
-- A zoom lands on an action, aimed from the take's timeline with a sourced push duration, and one pointer clicks inside each recorded target
-- The choice of music or silence, the music's level under a voice, and a voiceover's pace each carry a sourced number
-- A checker finding is dismissed only after the frame it names is read
-- Every number traces to a source in `references/adopted.md`, a conflict between sources names its pick, and the body closes with the practice skill's three closing sections
-
-## Must not
-
-- Restate a rule HyperFrames' own skills carry, such as ease variety, anchoring, click timing, a zoom's scale and dwell, safe margins, or the carve under a voice
-- State a number `references/adopted.md` does not trace to a source, or claim loading the skill improves a render before a with-and-without comparison
-- Fetch, generate, or install a media file or HyperFrames itself
-- Name this repository's demos, branches, or render files, since the body ships to targets holding none of them
-- Set pointer smoothing or hiding, which are recorder settings a composition cannot change
-
-## Out of scope
-
-- General motion and composition rules, which `hyperframes-animation` and `hyperframes-creative` own
-- Sourcing media, which `media-use` owns
-- Recording the take, and loading this skill before it composes, which `record-screencast` owns
-- Vertical 9:16 framing, which no skill owns until a project asks for it

package/claude/skills/video-craft/SKILL.md

@@ -1,96 +0,0 @@
----
-name: video-craft
-description: Carries what makes a composed video of software read as designed rather than generic, being captions that name only what the frame shows, which moment earns a zoom and how fast it lands, how a real pointer behaves on a real interface, music or silence and how far under a voice the music sits, and reading a frame before dismissing a checker finding. Every number traces to a source. Use before composing or judging any video, whether a product demo, an explainer, a pull request walkthrough, or a launch clip, when a render reads generic or slow, or when asked "make this video look designed", "is this zoom too slow", "what should this caption say", "should this have music", or "the checker flagged a frame, is it real". Do NOT use for general motion such as easing, speed variety, and click timing, which HyperFrames' `hyperframes-animation` and `hyperframes-creative` carry, to fetch or generate a media file, which is `media-use`, or to record the take, which is `record-screencast`.
-metadata:
-  family: build
----
-
-# Video craft
-
-A session composing a video with no stated direction reaches for defaults, such as a slow push-in, one ease on every move, a centered caption pill, and a slogan intro card. Together they read as generic. This skill carries the judgment specific to a video of software, which HyperFrames' own skills leave out.
-
-Load `hyperframes-creative` and `hyperframes-animation` first. They own general motion, being ease and speed variety, anchoring, and click timing, and this body names none of their rules.
-
-## Scope and sources
-
-The guidance covers landscape 16:9 video, and vertical 9:16 framing is not covered yet. Read `${CLAUDE_SKILL_DIR}/references/adopted.md` for the source behind every number below, only when extending this guidance or arguing against a rule in it.
-
-## Captions name what the frame shows
-
-- Write each caption about the frame on screen while it shows, never about the step before or the one after. A caption narrating the whole flow describes a frame the viewer is not looking at.
-- Name the visible change, such as the card landing or the field filling, rather than the feature's pitch. The pitch belongs in an intro card or the voiceover.
-- Start a caption on the first frame of the action it names, and keep it on screen for at least 5/6 of a second and at most 7 seconds.
-- Hold a caption to two lines of at most 42 characters, read at no more than 20 characters per second, or 17 for an audience of children. Cut words rather than shorten the hold.
-- Place a caption where it covers nothing the frame is about. Move it off the element the step acts on, rather than centering it by default. HyperFrames' studio skill owns the title-safe margins.
-
-## A zoom is earned by an action
-
-- Zoom only on a click, fill, or hover whose result is too small to read at full frame. A navigate, a wait, or a hold has nothing to aim at.
-- Aim the zoom at the action's own place and moment. `canon demo run` writes a timeline beside the take with each step's start, end, and target box, so read the zoom off it, never summing holds.
-- Run a push that lands on an action no faster than the floor HyperFrames' `viewport-change` rule states, and never past 1 second
-- That rule's own range suits an ambient reveal with no action to land on, and reads slow on a push onto a click
-- Leave the scale and the dwell after a zoom settles to the `viewport-change` rule, which states both.
-
-## A real pointer on a real interface
-
-- Keep the pointer the take recorded. Never draw a second, synthetic cursor over a real interface, since two pointers on one frame leave the viewer guessing which one acted.
-- Check that each click lands inside the target box the timeline records for it. A pointer arriving beside the button it claims to press reads as a fake.
-
-## Music, silence, and a voice
-
-- Choose silence over a music bed that competes with a voiceover. A bed earns its place on a video with no voice, where it carries the pacing between beats.
-- Sit music at least 20 dB under the voice. Check `media-use`'s narrated bed default against that floor, since it has sat short of it.
-- The mechanism, a carve rather than a flat duck, is `hyperframes-audio`'s
-- Keep a captioned voiceover at or under 160 words a minute, since a faster voice forces captions past their reading limit. `hyperframes-creative`'s narration pace sits under that ceiling.
-
-## Read the frame before dismissing a finding
-
-- Open the frame at the timestamp a checker names before calling its finding a false positive, whether the checker is `hyperframes check`, `canon demo frames`, or `read-frames`.
-- Report what the frame shows beside the dismissal. A dismissal with no frame read is a guess about the render, and the viewer sees the render.
-
-## Excuses and rebuttals
-
-| Excuse                                                       | Rebuttal                                                                                                                     |
-| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
-| A slow zoom feels cinematic                                  | A push onto an action is interface motion. Past 1 second the viewer waits on the camera instead of watching the action land. |
-| The caption explains the whole feature, so it is more useful | A caption about anything but the frame on screen makes the viewer read one thing and watch another.                          |
-| The checker flagged a frame I already know is fine           | Knowing is a memory of the composition, not of the render. Open the frame.                                                   |
-| Music makes it feel finished                                 | Music under a voice that is not 20 dB down masks the words, and the words carry the explanation.                             |
-| A drawn cursor looks cleaner than the recorded one           | The recorded pointer is the one that pressed the button. A drawn one is a claim about an action the take already shows.      |
-
-## Red flags
-
-- A push onto a click runs longer than 1 second.
-- Every move in the composition shares one duration.
-- A caption is centered on screen and covers the element the step acts on.
-- A caption names a step the frame is not showing.
-
-### Timing and checks
-
-These flags catch a composition built from memory rather than from the take.
-
-- The zoom's start time was added up by hand while a timeline file sits beside the take.
-- Two pointers appear on one frame.
-- A checker finding was dismissed and no frame was opened.
-
-## Before handing over
-
-- Every caption names what its frame shows, starts on its action's first frame, and holds within its time and length limits.
-- Every zoom aims at a click, fill, or hover read from the timeline, and lands within its duration.
-- One pointer is on screen, and each click lands inside its recorded box.
-- Music, when present, sits at least 20 dB under any voice, and a captioned voice stays at or under 160 words a minute.
-- Every checker finding was either fixed or dismissed with the frame it names read and reported.
-
-## What this delegates
-
-- Easing, speed variety, anchoring, click timing, and every other general motion rule: `hyperframes-animation` and `hyperframes-creative`
-- Title-safe margins and timeline layout: `hyperframes-studio`
-- The carve that sits music under a voice: `hyperframes-audio`
-
-### Media, capture, and reading
-
-The assets around the composition belong to other skills too.
-
-- Fetching or generating music, effects, voice, and imagery: `media-use`
-- Recording the take and writing its timeline: `record-screencast` through `canon demo run`
-- Reading a render frame by frame: `read-frames`

package/claude/skills/video-craft/references/adopted.md

@@ -1,110 +0,0 @@
----
-title: Adopted and declined
-description: The source behind every number in the video-craft body, by field, which conflicts between sources were picked and why, and what was declined
----
-
-# Adopted and declined
-
-Each number in the body traces to a source here, read through the `search-craft` method: the field named first, its authorities derived from the kind of body it trusts, and each question searched scoped to those authorities and open beside it. A later session extending the skill adds to this file rather than re-arguing an item settled here.
-
-## Captions
-
-Field: subtitling and captioning. Authorities: broadcasters' and streamers' published subtitle guidelines, and the captioning program that sets educational practice.
-
-| Rule                                       | Source                                                                                                                                                                                                     |
-| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| On screen for 5/6 of a second to 7 seconds | Netflix's [Timed Text Style Guide: General Requirements](https://partnerhelp.netflixstudios.com/hc/en-us/articles/215758617-Timed-Text-Style-Guide-General-Requirements), a minimum of 20 frames at 24 fps |
-| Two lines, 42 characters a line            | Netflix's [English (USA) guide](https://partnerhelp.netflixstudios.com/hc/en-us/articles/217350977-English-USA-Timed-Text-Style-Guide)                                                                     |
-| 20 characters per second, 17 for children  | The same English (USA) guide, adult and children's programs respectively                                                                                                                                   |
-| Never over what the frame is about         | The DCMP [Captioning Tip Sheet](https://dcmp.org/learn/225-captioning-tip-sheet): "Placement must not interfere with existing visuals/graphics."                                                           |
-
-### Start on the first frame of the action
-
-Netflix's [Subtitle Timing Guidelines](https://partnerhelp.netflixstudios.com/hc/en-us/articles/360051554394-Timed-Text-Style-Guide-Subtitle-Timing-Guidelines) put a subtitle's in-time on the first frame of its audio. A software video's caption names an action rather than a line of speech, so the body keys the in-time on the action's first frame.
-
-### Captions name what the frame shows
-
-No source states this for a software video. It is the operator's read of an unguided render whose caption narrated the whole flow, kept because the timing rules above already assume a caption tied to one moment.
-
-## Zoom
-
-Fields: interface motion design, and screen recording practice. Authorities: design systems that publish motion specs, and the reference documentation of a screen recording tool.
-
-### A push onto an action stays under 1 second
-
-The floor is HyperFrames'. Its `viewport-change` rule states a zoom of 1.0 to 2.0 seconds with the reason beside it, "under 0.8s teleports, over 2.5s drags", and the body points at the rule rather than restating it.
-
-- Measured: an unguided render pushed in over 2.2 seconds and a second over 1.4 seconds, and the operator judged both slow, so the range's lower half already reads slow on a push onto a click
-- Published: Material Design 3's [easing and duration tokens](https://m3.material.io/styles/motion/easing-and-duration/tokens-specs) end at 1000 ms, the top of a band reserved for ambient transitions, so no input-driven transition there runs longer
-
-### Zoom on a click
-
-Screen Studio's [auto zoom guide](https://screen.studio/guide/auto-zoom) keys its zoom on click positions and zooms nowhere a click did not occur.
-
-### Conflict, and the pick
-
-HyperFrames' range and the measured renders disagree on the push onto an action. The body takes the overlap, HyperFrames' teleport floor below and 1 second above, which sits inside HyperFrames' range at its fast end.
-
-- HyperFrames' full range stays with an ambient reveal, matching Material's own split between input-driven and ambient motion
-- A tighter band was declined. Material puts large expressive transitions at 450 to 600 ms, and Nielsen Norman Group's [animation duration article](https://www.nngroup.com/articles/animation-duration/) calls 400 ms "very slow".
-- Both write for an interface a user waits on, which a video viewer is not, and that band sits below HyperFrames' teleport floor with nothing measured to show it reads right
-
-Narrow the band once a composed demo is compared against the unguided renders.
-
-## Pointer
-
-The two pointer rules in the body carry no number. One pointer on a frame and a click landing inside its recorded box both follow from the take recording the real pointer and the timeline recording each target's box.
-
-## Audio
-
-Fields: web accessibility, and audio post-production. Authorities: the W3C's accessibility guidelines, and the audio engineering society's streaming recommendation.
-
-### Music at least 20 dB under the voice
-
-WCAG 2.1 [Success Criterion 1.4.7](https://www.w3.org/WAI/WCAG21/Understanding/low-or-no-background-audio.html) is the source, reading "The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds."
-
-HyperFrames' `media-use` sets its narrated bed at a volume of 0.12, about 18 dB under a voice at full scale. The body takes WCAG's 20 dB, since it is the published floor and the bed default sits 2 dB short of it.
-
-### Overall loudness is delegated
-
-The AES [TD1008](https://aes.org/wp-content/uploads/2024/01/20210924_TD1008_v3.13.pdf) streaming recommendation normalizes speech to -18 LUFS with a true peak no higher than -1 dBTP. `media-use` ships -14 and -16 LUFS targets for social and podcast delivery.
-
-The body states no overall target, since the right one depends on where the video is published and `media-use` owns that operation.
-
-## Voiceover
-
-Field: captioning, for the reading ceiling a voiceover's captions inherit. Authority: the captioning program's presentation rate guidance.
-
-### At or under 160 words a minute when captioned
-
-The DCMP [Captioning Key: Presentation Rate](https://dcmp.org/learn/601-captioning-key---presentation-rate) caps upper-level captions at 160 words a minute.
-
-- `hyperframes-creative`'s narration reference states 2.5 words a second, 150 a minute, under the ceiling, so the two do not conflict
-- An open search of voiceover practitioners put explainers at 140 to 160 words a minute, which agrees
-- Narration has no standards body for pace, and the scoped search found none, so the body sets only the ceiling and points at HyperFrames for pace
-
-## Declined
-
-Each item below stays out of the body for the reason given.
-
-### Restating HyperFrames' motion rules
-
-Ease variety, anchoring, click timing, the scale and dwell of a zoom, and title-safe margins are stated in HyperFrames' own skills, which update on their own cadence. A copy here goes stale on theirs.
-
-### A loudness target in the body
-
-See Audio above.
-
-### Pointer smoothing and hiding at rest
-
-Screen Studio's [cursor guide](https://screen.studio/guide/cursor) smooths the pointer and hides it when idle, and its [guide to disabling smooth movement](https://screen.studio/guide/disable-smooth-mouse-movement) turns smoothing off for a dropdown menu.
-
-Both are recorder settings. A take is composed with its pointer baked into the frames, so a session composing from it cannot change either, and they belong to whatever records the take.
-
-### Zoom out before a cut, and a sound effect only on a meaningful click
-
-Neither has a source, and no operator read stands behind either, so both stay out until one does.
-
-### Vertical 9:16 framing
-
-Every video measured when this skill was written was landscape. Add it when a project asks for vertical video, with its safe areas sourced from the platform's own creator documentation.

package/governance/rules/ui/canvas.md

@@ -1,13 +0,0 @@
----
-description: Route edits to canvas frames under .canon/canvas/ to the canvas-board skill for the house style, and keep frame text and box height readable
-paths:
-  - '.canon/canvas/**'
----
-
-# Canvas standards
-
-## Frames
-
-- Load the `canon:canvas-board` skill before drawing or editing a frame. It carries the house style for an explanation frame and the content format. Report it rather than proceeding silently when the skill does not resolve.
-- Write explanation frame text in sentence case. A mockup of the project's interface follows its design document instead.
-- Size each explanation frame's box to show all its content with no scrollbar.