diff --git a/AGENTS.md b/AGENTS.md index bfb1a4f..fc9f151 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -17,9 +17,9 @@ Keep static drawings, timelines, and playback responsibilities separate. Preserv ## Typography and records -Use Cal Sans with no added letter-spacing, `font-optical-sizing: auto`, one `GEOM` value per role, and `font-synthesis: none`. Keep text editable and use typeset punctuation (’ – − “ ”). +Use Cal Sans with no added letter-spacing, `font-optical-sizing: auto`, one `GEOM` value per role, and `font-synthesis: none`. The skill’s bundled `skills/plotter/assets/fonts/CalSansVF.woff2` stays identical to `public/fonts/CalSansVF.woff2`. Keep text editable and use typeset punctuation (’ – − “ ”). -Treat coss paths and evaluations under `skills/plotter/references/history/` as historical evidence. Keep current integration paths in `skills/plotter/references/implementation.md`. Report only inspection and verification actually performed; source generation does not establish visual approval. +Skill documents address a stranger’s agent, so maintainer rules belong here. The dated coss review record that lived under `skills/plotter/references/history/` was removed from the tree after commit `37f3464`; read it from git history when tracing an old decision. Keep revision IDs stable unless alternatives are requested. Appearance approval applies to a particular revision; gallery inclusion, production placement, and style-reference selection are separate decisions. `skills/plotter/references/drawings/manifest.json` records the reference snapshots’ source revisions and hashes. Keep current integration paths in [CONTRIBUTING.md](CONTRIBUTING.md#website-integration). Report only inspection and verification actually performed; source generation does not establish visual approval. diff --git a/ATTRIBUTION.md b/ATTRIBUTION.md index 3b84358..a8a542b 100644 --- a/ATTRIBUTION.md +++ b/ATTRIBUTION.md @@ -6,7 +6,7 @@ Extraction baseline: coss commit `54c5a6dd2527d91127bd5efd0dfe2ee055570f27` on ` The extraction preserves the Plotter skill package originally located at `apps/ui/skills/plotter`, the illustration catalogue and related components from `apps/ui/app/plotter`, and the associated generation and export scripts from `apps/ui/scripts`. -The skill’s bundled reference manifest records the source revisions of its approved SVG snapshots. Dated feedback and audits remain under `skills/plotter/references/history/`. Repository paths and routes inside those records describe the original coss context. +The skill’s bundled reference manifest records the source revisions of its approved SVG snapshots. Dated feedback and audits from the coss period were removed from the tree after commit `37f3464` and remain in git history. ## License record @@ -14,4 +14,4 @@ Plotter and its portable skill package use the [MIT license](LICENSE), selected For historical provenance, the initial extraction carried an AGPL-3.0 root license alongside an MIT declaration in `apps/ui/package.json`. That was the extraction record; the current project and packaged skill licenses are MIT. -Cal Sans is credited to Mark Davis, WORDMARK × Cal.com. The site’s font package and any bundled third-party assets retain their own accompanying license information. Reference images and historical material remain part of the preserved source record. +Cal Sans is credited to Mark Davis, WORDMARK × Cal.com. The skill bundles one copy of the variable font with its SIL Open Font License 1.1 at `skills/plotter/assets/fonts/`. The site’s font package and any bundled third-party assets retain their own accompanying license information. Earlier reference images and review records remain in git history. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6261622..07ccfcc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,7 +14,7 @@ Start with the [local setup](README.md#run-the-website) and [repository guidelin | `content/docs/` | Website documentation | | `scripts/` | Website adapters, generators, and export scripts | -Edit SVG sources before regenerating drawing components. Foundation runtime data, CSS, and reference tables derive from `standard.json`. Keep approved reference revisions and stable catalogue codes intact; historical records are evidence, not current instructions. +Edit SVG sources before regenerating drawing components. Foundation runtime data, CSS, and reference tables derive from `standard.json`. Keep approved reference revisions and stable catalogue codes intact. Drawings use a native `560 × 440` viewBox and scale proportionally in the website. Every current illustration uses 1-unit visible strokes. Shared role-token customization currently covers **AGT-01, MEC-05, GEO-11, SYS-06, and CRF-06**. Other drawings retain their authored opacity and dash patterns; uniform width does not imply a catalogue-wide token migration. @@ -34,7 +34,7 @@ bun run downloads # Catalogue, downloads, and public After a shared-standard change, regenerate the drawing components that consume it. After a catalogue change, refresh the bundled catalogue. `bun run build` also refreshes the documentation copies in `public/docs` before building the website. -The [website integration guide](skills/plotter/references/implementation.md) maps individual adapters and export paths. Generation produces files; it does not establish visual correctness. +Generation produces files; it does not establish visual correctness. Repository previews live in `.github/assets/`. The README’s galleries are in `showcase/`: @@ -48,6 +48,32 @@ The fourteen static selections come from the existing [approved reference set](s These are presentation compositions of the original catalogue SVGs, with unused margins cropped and each drawing scaled proportionally. Preview SVGs outline typography for consistent rendering and have 3200-pixel-wide PNG companions. The **MEC-01** iris GIF is exported at twice its displayed size and has a static SVG fallback for reduced motion. Editable text and drawing sources remain in the catalogue and animation components; refresh these presentation exports when the featured artwork changes, and use new filenames so cached README images do not show the old artwork. +## Website integration + +The installed skill does not depend on the website. These paths are relative to the repository root. + +| Responsibility | Source | +| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | +| Gallery SVG wrapper and role-style opt-in | `components/plotter/blueprint-drawing.tsx` | +| Catalogue compiler and SVG serializer | `scripts/build-plotter-drawings.py`, `scripts/plotter_svg.py` | +| Bundled catalogue SVGs and index | `skills/plotter/references/catalogue/`, generated by `scripts/build-plotter-catalogue.tsx` | +| AGT-01 helper-fragment recipe | `skills/plotter/assets/examples/render-registration.mjs` | +| AGT-01 host file adapter | `scripts/build-plotter-registration.mjs` | +| Static MEC-05 and OBJ-05 | `components/plotter/engineering-studies.tsx` | +| MEC-05 shared core hatching | `components/plotter/production-chain-hatching.tsx` | +| MEC-05 and OBJ-05 timelines | `components/plotter/production-chain-motion-drawing.tsx`, `components/plotter/newtons-cradle-motion-drawing.tsx` | +| Engineering playback, fallback, and visibility | `components/plotter/engineering-motion-preview.tsx` | +| Resolved pilot export adapter | `scripts/export-plotter-pilots.tsx` | +| Download artifact generator | `scripts/build-plotter-downloads.tsx` | + +`BlueprintDrawing` opts into shared roles with `roles`. The independent highlight-opacity token is used by TIM-01, TIM-03, and TIM-05 without changing their stroke-role adoption. The SVG-to-JSX builder preserves supported root styles, removes standalone fixed ink and the root font family so the gallery inherits its theme and loaded font, and gives repeated definitions local IDs. Font weight, optical sizing, and GEOM settings remain authored. Standalone SVGs retain their own font stack. + +Catalogue codes are a three-letter family prefix (`familyPrefix` in `components/plotter/study-types.ts`) and a number, without gaps within a family. A new drawing takes the next number in its family; a retired drawing keeps its code reserved in `retiredStudies`. Keep study IDs stable and keep removed studies out of active metadata. + +MEC-05’s static and animated core faces share a hatch component; its carrier frames remain unhatched. Timeline edits preserve the chosen still unless redesign is requested. Grammar isolation keeps focused marks at their original appearance, and supplemental grid segments restore only portions hidden with a form. + +`bun scripts/export-plotter-pilots.tsx /tmp/plotter-exports` renders the selected static MEC-05 drawing and sends it, with AGT-01, through the packaged exporter. Neither a resolved static SVG nor an animated HTML file should rely on website imports. + ## Formatting and checks Biome formats handwritten JavaScript/TypeScript, JSON, CSS, Markdown, and YAML: two spaces, 80 columns, double quotes, and trailing commas. Use the recommended Biome editor extension for formatting on save. @@ -64,12 +90,12 @@ bun run plotter:check Formatting does not apply lint fixes. Linting uses Biome’s recommended rules and reports Tailwind class ordering; it is separate from the formatting CI job. Neither fix command enables unsafe fixes. -Generated drawing components, foundation outputs, public assets, and historical records are excluded in `biome.json`. SVG sources and HTML examples are excluded to preserve reference hashes and embedded stylesheet checks. Markdown code blocks stay as authored. Python is outside Biome’s scope. +Generated drawing components, foundation outputs, and public assets are excluded in `biome.json`. SVG sources and HTML examples are excluded to preserve reference hashes and embedded stylesheet checks. Markdown code blocks stay as authored. Python is outside Biome’s scope. ## Review and portable output -Include the brief and relevant before/after drawings when proposing visual changes. Inspect the drawing at its intended size and, for motion, watch a complete cycle and inspect its fallback. Report the review actually performed; sampled frames establish poses, not playback rhythm. +Include the brief and relevant before/after drawings when proposing visual changes. Inspect the drawing at its intended size with `python3 skills/plotter/scripts/render.py` and, for motion, watch a complete cycle and inspect its fallback. Report the review actually performed; sampled frames establish poses, not playback rhythm. -Keep exports independent of the website. Resolved static SVG carries its own appearance and definitions. Standalone animation includes its editable timeline and required local resources, or inlines them in one HTML file. Exact Cal Sans appearance requires the font to be available; SVG text remains editable with a sans-serif fallback. +Keep exports independent of the website. Resolved static SVG carries its own appearance and definitions. Standalone animation includes its editable timeline and required local resources, or inlines them in one HTML file. Exact Cal Sans appearance requires the font to be available; SVG text remains editable with a sans-serif fallback. The skill bundles the font for previews and for exports made with `--embed-font`. -The skill’s historical coss paths and review records remain as provenance. Preserve [ATTRIBUTION.md](ATTRIBUTION.md), [LICENSE](LICENSE), and accompanying third-party license information. +The skill’s dated coss review records were removed from the tree after commit `37f3464` and remain in git history. Preserve [ATTRIBUTION.md](ATTRIBUTION.md), [LICENSE](LICENSE), and accompanying third-party license information. diff --git a/biome.json b/biome.json index 594ffa9..e28b392 100644 --- a/biome.json +++ b/biome.json @@ -14,7 +14,6 @@ "!bun.lock", "!next-env.d.ts", "!public", - "!skills/plotter/references/history", "!skills/plotter/references/catalogue", "!components/plotter/expanded-studies.tsx", "!components/plotter/visual-grammar-drawings.tsx", diff --git a/content/docs/drawing.md b/content/docs/drawing.md index d9a3f38..7ec2859 100644 --- a/content/docs/drawing.md +++ b/content/docs/drawing.md @@ -73,6 +73,6 @@ Download the resolved [AGT-01 registration SVG](/plotter/downloads/agent-registr ## Review the result -Compare the candidate with its chosen reference at the intended size and as a thumbnail. For a revision, compare with the previous drawing too. Inspect the host’s themes and narrow layout when those are part of delivery. +Render the candidate with `python3 scripts/render.py drawing.svg`, adding `--width` for the size it will be shown at and `--theme both` for a dark host. Compare it with its chosen reference at the intended size and as a thumbnail. For a revision, compare with the previous drawing too. Inspect the host’s themes and narrow layout when those are part of delivery. Confirm that the focal relationship reads, guides remain subordinate, labels have space, transparent forms keep their meaning, and numeric or behavioral claims match their evidence. Deliver the editable source and requested export, naming any visual review that remains pending. Source generation alone does not establish visual approval. diff --git a/content/docs/installation.md b/content/docs/installation.md index bc52e2f..8af77c6 100644 --- a/content/docs/installation.md +++ b/content/docs/installation.md @@ -41,9 +41,9 @@ For an existing drawing, attach its editable source and describe the change. To ## What you need -Reading the skill and opening its bundled SVGs needs no package manager or website checkout. The registration authoring example uses Node.js; the resolved static SVG exporter uses Python 3. The animation example opens in a modern browser with its packaged local stylesheet. +Reading the skill and opening its bundled SVGs needs no package manager or website checkout. The registration authoring example uses Node.js; the resolved static SVG exporter and the preview renderer use Python 3. The renderer needs a Chromium-based browser such as Chrome, Edge, or Brave, or another SVG renderer such as `rsvg-convert`; without one, the agent delivers the drawing with its visual review marked as pending. The animation example opens in a modern browser with its packaged local stylesheet. -Recipients opening an exported SVG need neither Node.js nor Python. Cal Sans is optional for opening the files; a sans-serif fallback keeps labels editable, while exact text metrics depend on the font being available. +Recipients opening an exported SVG need neither Node.js nor Python. The skill bundles Cal Sans, so previews show the intended typography. A delivered SVG still names the font without containing it: load Cal Sans on your site, or ask for an export with the font embedded (`--embed-font`, about 200 KB). Otherwise labels fall back to a sans-serif and stay editable. ## Run the website diff --git a/design-directions.md b/design-directions.md deleted file mode 100644 index 7f0cf4a..0000000 --- a/design-directions.md +++ /dev/null @@ -1,39 +0,0 @@ -# Plotter identity: Sheet - -Selected on 2026-11-01. The site is set as one drawing sheet. It replaces the Manual direction chosen on 2026-10-31. - -## Decision - -- The whole site sits inside one hairline-framed sheet, with small registration ticks at its outer corners. Rules (`--rule`) divide it into cells. Inside the sheet, `--border` follows the rule color, so component borders and cell rules match. -- The header is a ruled strip: wordmark, navigation, a catalogue count (“95 drawings · Editable SVG”, computed), and actions. The footer is a title block: wordmark, guides, skill, and credits. -- Sections open with a ruled bar: a mono label numbered by page (`01 — Illustrations`, `03.1 — Glossary`), an optional mono meta note, and an optional link. -- **Drawings always render at their native 560 × 440, never scaled down.** Cells pair side by side only from 1280px, where each cell can hold a full-size drawing. Below that they stack. On screens narrower than a drawing, the drawing scrolls sideways (keyboard-focusable), following the existing gallery convention. -- Bordered panels inside cells (drawing frames, code blocks, prompt cards, the animation preview) have square corners, like the sheet. Only controls (buttons, tabs, the skip link) keep the coss radius. -- Captions are short, with mono codes and categories: `MEC-01 · Six blades, one aperture · Scale 1:1`. -- Type follows the existing roles: Cal Sans 500 with `GEOM` 50 for headings, `GEOM` 25 for body text, Paper Mono for labels, no added tracking. Colors stay on the coss neutral tokens. The page canvas is `bg-sidebar`, and the sheet uses `--background`. -- Shared pieces: `components/sheet.tsx` (`PageIntro`, `SheetBar`, `SheetArt`, `DrawingFigure`) and the `@layer components` sheet block in `app/globals.css`. - -## Rejected - -- **Library**, a docs-app shell with a sidebar, search, and a filterable card grid: it reads like any documentation site, and its cards scale drawings down to about 290px. -- **Plates**, one drawing per screen like a printed book: slow for browsing 100 drawings, and it scales drawings up instead of using their native size. -- The first Sheet draft used a four-column library grid. That scaled drawings to about half size, so it was replaced by the native-size two-up module. -- The earlier Manual, Archive, and Studio directions are recorded at `5536ffc` and `2197cf4`. - -## Unboxed layouts, compared and rejected (2026-11-01) - -The boxed sheet was compared on the live site against unboxed layouts. Each removed the frame, corner ticks, grey margin, and vertical rules, keeping full-width horizontal rules and a centered 1320px column. The boxed version stayed as the best option. - -- **Open**: no separation between drawings. It read well on text pages, but drawings ran together in collections. -- **Marked**: registration crosses at drawing corners. Not enough separation. -- **Ruled**: a hairline under each row of drawings, with a cross at the column gap. -- **Construction**: dash-dot centerlines between drawings, across and down. -- **Plates**: each drawing on a faint tinted panel with gaps, which is close to cards. - -One idea from the comparison was liked but not adopted: the homepage hero **plots itself** on load. Construction lines appear first, then each primary stroke is drawn, then the labels. It ran once, could be replayed, and was skipped under reduced motion. It reads the drawing’s own strokes, so it works with any catalogue drawing. The prototype was removed. It was a small client component that animated each stroke’s dash offset with the Web Animations API, about 100 lines. - -## Review record - -All pages were rebuilt on the Sheet system: home, illustrations, animations, grammar, docs, each guide, and 404. Motion previews now keep their drawings at 560 px and scroll on narrow screens instead of shrinking. - -The pages were reviewed as headless Chrome screenshots against the running dev server: 1440px light on every page, 390px for home, illustrations, and a guide, and 1440px dark for grammar. The typecheck, Biome format check, and `plotter:check` pass. Lint reports three errors that already existed before this change (`illustration-gallery.tsx` and `plotter-prompts.tsx` `role="group"`, `particles-assembly-drawing.tsx` array keys). No production build was run. Interactive behavior (filters, isolation, playback) was not exercised in a browser after the restyle. diff --git a/evals/README.md b/evals/README.md new file mode 100644 index 0000000..039ee17 --- /dev/null +++ b/evals/README.md @@ -0,0 +1,24 @@ +# Cold-run briefs + +Twelve briefs that show what the downloadable skill produces for someone who has never seen this repository. Run them after any change to `skills/plotter`, then compare the drawings with the previous run and with the catalogue. + +```sh +bun run downloads # rebuild the archive under test +evals/run.sh claude # or: evals/run.sh claude opus +evals/run.sh codex # needs the same build at ~/.codex/skills/plotter +evals/run.sh claude sonnet 07 # one brief, by number +``` + +Each brief runs in its own fresh session in a temporary folder outside this checkout, printed when the run ends; set `PLOTTER_EVAL_OUT` to choose another. A session started inside the checkout would read this repository’s `AGENTS.md` and stop being a clean install. The session's files are the deliverables; `transcript.jsonl` records what the agent read, ran, and reported. + +| Briefs | What they test | +| ------ | -------------------------------------------------------------------------------------- | +| 01–03 | README briefs. Each describes a catalogue drawing, so they mostly test retrieval. | +| 04–05 | Open briefs. The agent should stop and offer three options. | +| 06–10 | Plain-language subjects with no catalogue match, including a small size and TSX. | +| 11 | Animating a supplied drawing into one self-contained HTML file. | +| 12 | Critique. `upload-card.svg` has eight planted faults, listed below; none may be fixed. | + +Planted faults in `attachments/upload-card.svg`: a gradient and drop shadow on the card; a skewed icon; hatching that leaves its region; a 240-unit span labelled 200; a dashed arrowhead on an arrow used for alignment; a heavy unexplained grid with every stroke at full weight; a letter-spaced bold title with straight quotes and a hyphen; a rule through the title. + +Judge the drawings by eye. Rendering a result with `python3 skills/plotter/scripts/render.py` shows what the agent saw, or should have seen. One run per brief is a single sample, so a difference between two runs is not evidence until it repeats. diff --git a/evals/attachments/parts.svg b/evals/attachments/parts.svg new file mode 100644 index 0000000..93f971f --- /dev/null +++ b/evals/attachments/parts.svg @@ -0,0 +1 @@ +An assembly of partsAn icon, a label, and a status pill align into one row, shown as an exploded technical drawing.WorkspaceWorkspaceReadyReady0102033 parts / 1 composition diff --git a/evals/attachments/upload-card.svg b/evals/attachments/upload-card.svg new file mode 100644 index 0000000..e2a74d9 --- /dev/null +++ b/evals/attachments/upload-card.svg @@ -0,0 +1,31 @@ + + Upload card + + + + + + + + + + + + + + + + + + + + + + + 200 + + + + UPLOAD - 'report.pdf' + Aligned + diff --git a/evals/briefs/01-readme-interface.txt b/evals/briefs/01-readme-interface.txt new file mode 100644 index 0000000..6b3235d --- /dev/null +++ b/evals/briefs/01-readme-interface.txt @@ -0,0 +1 @@ +Draw an icon, label, and status pill as separate parts projecting into one interface row. Keep their sizes fixed and make the shared alignment clear. Deliver an editable SVG for a component-library page. diff --git a/evals/briefs/02-readme-routing.txt b/evals/briefs/02-readme-routing.txt new file mode 100644 index 0000000..a09decf --- /dev/null +++ b/evals/briefs/02-readme-routing.txt @@ -0,0 +1 @@ +Draw three agents A–C opposite three tools 01–03, arranged as a switching matrix. Select only the junction connecting agent B to tool 02. Deliver an editable SVG for a tool-routing guide. diff --git a/evals/briefs/03-readme-schedule.txt b/evals/briefs/03-readme-schedule.txt new file mode 100644 index 0000000..9896751 --- /dev/null +++ b/evals/briefs/03-readme-schedule.txt @@ -0,0 +1 @@ +Draw Alex’s and Sam’s availability as two measured bands meeting at one shared slot. Label the people and the meeting, and make the overlap the focal point. Deliver an editable SVG for a scheduling feature page. diff --git a/evals/briefs/04-vague-handoff.txt b/evals/briefs/04-vague-handoff.txt new file mode 100644 index 0000000..5cf4799 --- /dev/null +++ b/evals/briefs/04-vague-handoff.txt @@ -0,0 +1 @@ +I need an illustration for agent handoff. diff --git a/evals/briefs/05-vague-pricing.txt b/evals/briefs/05-vague-pricing.txt new file mode 100644 index 0000000..abbc417 --- /dev/null +++ b/evals/briefs/05-vague-pricing.txt @@ -0,0 +1 @@ +Make me a hero illustration for our pricing page. We have three plans. diff --git a/evals/briefs/06-rate-limiter.txt b/evals/briefs/06-rate-limiter.txt new file mode 100644 index 0000000..5913470 --- /dev/null +++ b/evals/briefs/06-rate-limiter.txt @@ -0,0 +1 @@ +Illustrate a token-bucket rate limiter for our API docs: tokens refill at a steady rate, each request spends one, and requests get rejected when the bucket is empty. SVG please. diff --git a/evals/briefs/07-backoff.txt b/evals/briefs/07-backoff.txt new file mode 100644 index 0000000..d07edc4 --- /dev/null +++ b/evals/briefs/07-backoff.txt @@ -0,0 +1 @@ +Draw webhook retries with exponential backoff: wait 1s, 2s, 4s, 8s, then give up. It's for a docs page. SVG. diff --git a/evals/briefs/08-empty-search.txt b/evals/briefs/08-empty-search.txt new file mode 100644 index 0000000..507dbb1 --- /dev/null +++ b/evals/briefs/08-empty-search.txt @@ -0,0 +1 @@ +Empty state for a search with no results. It will sit above the text “No results found” at about 240px wide, so it has to read at that size. SVG. diff --git a/evals/briefs/09-bicycle.txt b/evals/briefs/09-bicycle.txt new file mode 100644 index 0000000..eaa85c0 --- /dev/null +++ b/evals/briefs/09-bicycle.txt @@ -0,0 +1 @@ +Draw a bicycle. diff --git a/evals/briefs/10-optimistic-tsx.txt b/evals/briefs/10-optimistic-tsx.txt new file mode 100644 index 0000000..5e7f510 --- /dev/null +++ b/evals/briefs/10-optimistic-tsx.txt @@ -0,0 +1 @@ +Illustrate optimistic UI updates (the interface changes before the server confirms). I need it as a React component in TSX with no dependencies. It should inherit the text color because it sits on a dark docs page. diff --git a/evals/briefs/11-animate.txt b/evals/briefs/11-animate.txt new file mode 100644 index 0000000..cedc4ed --- /dev/null +++ b/evals/briefs/11-animate.txt @@ -0,0 +1 @@ +Animate parts.svg for our homepage: the separate parts come together into the finished row, hold for a moment, then come apart again. It should loop. Give me one self-contained HTML file. diff --git a/evals/briefs/12-critique.txt b/evals/briefs/12-critique.txt new file mode 100644 index 0000000..8a3ab49 --- /dev/null +++ b/evals/briefs/12-critique.txt @@ -0,0 +1 @@ +Critique upload-card.svg as a Plotter illustration. Don't edit it, just tell me what's wrong and what you'd change. diff --git a/evals/run.sh b/evals/run.sh new file mode 100755 index 0000000..f367da1 --- /dev/null +++ b/evals/run.sh @@ -0,0 +1,59 @@ +#!/bin/bash +# Run every brief in a fresh agent session that sees only the downloadable skill. +# Usage: evals/run.sh claude [model] [brief-prefix] | evals/run.sh codex '' [brief-prefix] +set -euo pipefail +agent=${1:?claude or codex} +model=${2:-sonnet} +[ -n "$model" ] || model=sonnet +only=${3:-} +root=$(cd "$(dirname "$0")/.." && pwd) +# Outside the checkout: a session started inside it would read this repository's +# AGENTS.md and stop being a clean install. +out="${PLOTTER_EVAL_OUT:-${TMPDIR:-/tmp}/plotter-evals}/$(date +%Y%m%d-%H%M%S)-$agent" +skill=$(mktemp -d) +unzip -q "$root/public/plotter/downloads/plotter.zip" -d "$skill" + +if [ "$agent" = codex ] && ! diff -rq "$skill/plotter" "$HOME/.codex/skills/plotter" >/dev/null; then + echo "Codex loads ~/.codex/skills/plotter, which differs from the download." >&2 + echo "Install the build under test there first, then run this again." >&2 + exit 1 +fi + +run_brief() { + local id=$1 dir="$out/$1" + mkdir -p "$dir" + case $id in + 11-*) cp "$root/evals/attachments/parts.svg" "$dir/" ;; + 12-*) cp "$root/evals/attachments/upload-card.svg" "$dir/" ;; + esac + local brief + brief=$(cat "$root/evals/briefs/$id.txt") + if [ "$agent" = claude ]; then + # A project-level copy with user settings off is the clean install: + # no personal skills, plugins, or instructions reach the session. + mkdir -p "$dir/.claude/skills" + cp -R "$skill/plotter" "$dir/.claude/skills/plotter" + (cd "$dir" && claude -p "/plotter $brief" \ + --setting-sources project --model "$model" --permission-mode acceptEdits \ + --output-format stream-json --verbose \ + --allowedTools Read Write Edit Glob Grep Skill Bash \ + --disallowedTools "Bash(brew:*)" "Bash(npm:*)" "Bash(npx:*)" "Bash(pnpm:*)" \ + "Bash(yarn:*)" "Bash(bun:*)" "Bash(pip:*)" "Bash(pip3:*)" "Bash(sudo:*)" \ + "Bash(curl:*)" "Bash(wget:*)" "Bash(git:*)" WebFetch WebSearch \ + >"$dir/transcript.jsonl" 2>"$dir/stderr.txt") || true + else + # Codex's default sandbox blocks every renderer on macOS, so these runs + # show what an unattended session produces without a visual check. + codex exec -C "$dir" --skip-git-repo-check -s workspace-write --json \ + -o "$dir/final.txt" "\$plotter $brief" \ + "$dir/transcript.jsonl" 2>"$dir/stderr.txt" || true + fi + echo "$id done" +} + +for file in "$root"/evals/briefs/"$only"*.txt; do + run_brief "$(basename "$file" .txt)" & + while [ "$(jobs -rp | wc -l)" -ge 4 ]; do sleep 2; done +done +wait +echo "Outputs: $out" diff --git a/illustration-library.md b/illustration-library.md deleted file mode 100644 index 51beeec..0000000 --- a/illustration-library.md +++ /dev/null @@ -1,43 +0,0 @@ -# Illustration library: decisions - -Decided on 2026-11-01. - -## Browsing: one ordered collection - -The illustrations page shows one list: eight varied drawings first (GEO-01, INT-04, SRV-04, TIM-03, INT-09, MEC-01, CRF-03, TYP-03), then every other drawing by family and code. - -- The 16-category filter was dropped. It mixed product area, subject, and drawing method, and only two of its categories matched a job someone arrives with. -- A seven-category taxonomy, then sections (Selected, Empty states, Agents, More) with search, were tried and rejected. With an intentional order, the extra navigation was not needed. -- The `category` field now names a drawing’s code family and sets its place in the order. It is not shown as a filter or caption. Old `?category=` and `?q=` links show the full page. - -## Retired near-duplicates - -Five drawings were removed from the catalogue (100 → 95). Their sources and codes stay reserved. `retiredStudies` in `components/plotter/illustrations.tsx` maps each one to its replacement, so old `?variant=` links still land on a drawing. - -| Retired | Kept instead | Why | -| ------------------------------- | ---------------------------------------------- | ----------------------------------------------- | -| TM02 Room around an appointment | TIM-06 Appointment buffers | Same subject; TIM-06 was liked when added | -| S15 No matching results | EMP-06 A search, unanswered | Same subject; EMP-06 chosen by the user | -| SW03 A history comes together | SRV-06 GitHub · A change, brought together | SRV-06 is an approved reference and adds review | -| SW02 A shorter return | SRV-01 Cloudflare · Between visitor and origin | SRV-01 is approved and shows hit and miss | -| AR03 The last piece of the arch | EMP-04 An unbuilt arch | EMP-04 is approved and works as a 404 | - -These pairs were reviewed side by side and kept as distinct drawings: TIM-01 and TIM-05 (both approved), GEO-03 and INT-10, INT-03 and INT-05, and GEO-08, GEO-10, and EMP-01. - -## Codes: one scheme, usable in briefs - -Codes were renumbered into a three-letter family prefix and a number, without gaps in a family: GEO, TYP, INT, TIM, SYS, SRV, AGT, EMP, OBJ, MEC, CRF, NAT, plus COS for the two coss.com concepts. The `category` field now names the family, and `familyPrefix` in `components/plotter/study-types.ts` ties them together. - -Every coded drawing is bundled in the skill as a resolved static SVG (`skills/plotter/references/catalogue/`, generated by `bun run catalogue`), so a brief can say “like TIM-06” without the website. `plotter:check` fails on a malformed code, a gap, or a catalogue that is out of date. - -Older records keep the codes they were written with. `skills/plotter/references/history/code-map.md` maps every former code to its current one, including the retired drawings. - -## Resilience studies — 2026-11-01 - -The user approved all three directions from a fresh Astra run of the brief “Resilience” using the skill at `3fe538c`, then requested their inclusion in the catalogue. Their approved geometry and typography are preserved: - -- **GEO-11 · Return to balance:** a displaced disc returns to the low point of a circular cradle. -- **SYS-06 · Keep a way through:** an alternate route bypasses a broken connection. -- **CRF-06 · Rejoin:** a fitted key repairs a seam. - -These additions bring the active illustration count to 98. All three use the shared drafting roles. Their source SVG metadata records the conceptual scope and construction; the existing approved style-reference selection is unchanged. diff --git a/public/docs/drawing.md b/public/docs/drawing.md index d9a3f38..7ec2859 100644 --- a/public/docs/drawing.md +++ b/public/docs/drawing.md @@ -73,6 +73,6 @@ Download the resolved [AGT-01 registration SVG](/plotter/downloads/agent-registr ## Review the result -Compare the candidate with its chosen reference at the intended size and as a thumbnail. For a revision, compare with the previous drawing too. Inspect the host’s themes and narrow layout when those are part of delivery. +Render the candidate with `python3 scripts/render.py drawing.svg`, adding `--width` for the size it will be shown at and `--theme both` for a dark host. Compare it with its chosen reference at the intended size and as a thumbnail. For a revision, compare with the previous drawing too. Inspect the host’s themes and narrow layout when those are part of delivery. Confirm that the focal relationship reads, guides remain subordinate, labels have space, transparent forms keep their meaning, and numeric or behavioral claims match their evidence. Deliver the editable source and requested export, naming any visual review that remains pending. Source generation alone does not establish visual approval. diff --git a/public/docs/installation.md b/public/docs/installation.md index bc52e2f..8af77c6 100644 --- a/public/docs/installation.md +++ b/public/docs/installation.md @@ -41,9 +41,9 @@ For an existing drawing, attach its editable source and describe the change. To ## What you need -Reading the skill and opening its bundled SVGs needs no package manager or website checkout. The registration authoring example uses Node.js; the resolved static SVG exporter uses Python 3. The animation example opens in a modern browser with its packaged local stylesheet. +Reading the skill and opening its bundled SVGs needs no package manager or website checkout. The registration authoring example uses Node.js; the resolved static SVG exporter and the preview renderer use Python 3. The renderer needs a Chromium-based browser such as Chrome, Edge, or Brave, or another SVG renderer such as `rsvg-convert`; without one, the agent delivers the drawing with its visual review marked as pending. The animation example opens in a modern browser with its packaged local stylesheet. -Recipients opening an exported SVG need neither Node.js nor Python. Cal Sans is optional for opening the files; a sans-serif fallback keeps labels editable, while exact text metrics depend on the font being available. +Recipients opening an exported SVG need neither Node.js nor Python. The skill bundles Cal Sans, so previews show the intended typography. A delivered SVG still names the font without containing it: load Cal Sans on your site, or ask for an export with the font embedded (`--embed-font`, about 200 KB). Otherwise labels fall back to a sans-serif and stay editable. ## Run the website diff --git a/public/plotter/downloads/plotter.zip b/public/plotter/downloads/plotter.zip index 989ff38..43ca575 100644 Binary files a/public/plotter/downloads/plotter.zip and b/public/plotter/downloads/plotter.zip differ diff --git a/scripts/build-plotter-catalogue.tsx b/scripts/build-plotter-catalogue.tsx index ae00a44..53541ed 100644 --- a/scripts/build-plotter-catalogue.tsx +++ b/scripts/build-plotter-catalogue.tsx @@ -122,7 +122,7 @@ writeFileSync( Every drawing in the Plotter catalogue, exported as a resolved static SVG at its native 560 × 440. Codes match the website. When a brief names a code (“like TIM-06”), open that file and borrow its construction relationship, not its subject. -Codes are a three-letter family prefix and a number, without gaps within a family. Drawings retired as near-duplicates keep their former codes in the [code map](../history/code-map.md) and are not exported here. The [approved references](../approved-references.md) remain the style anchors; a catalogue drawing is an example, not a new reference selection. +Codes are a three-letter family prefix and a number, without gaps within a family. Drawings retired as near-duplicates keep their codes reserved and are not exported here. The [approved references](../approved-references.md) remain the style anchors; a catalogue drawing is an example, not a new reference selection. ${sections}`, ); diff --git a/scripts/check-plotter.tsx b/scripts/check-plotter.tsx index d6a1887..025ca7c 100644 --- a/scripts/check-plotter.tsx +++ b/scripts/check-plotter.tsx @@ -101,6 +101,14 @@ for (const [prefix, values] of numbers) { } }); } +const fontCopies = [ + resolve(skillRoot, "assets/fonts/CalSansVF.woff2"), + resolve(import.meta.dir, "../public/fonts/CalSansVF.woff2"), +].map((file) => createHash("sha256").update(readFileSync(file)).digest("hex")); +if (fontCopies[0] !== fontCopies[1]) { + throw new Error("The skill's bundled Cal Sans differs from the website's."); +} +statSync(resolve(skillRoot, "assets/fonts/OFL.txt")); const bundled = readdirSync(catalogueRoot).filter((file) => file.endsWith(".svg"), ); diff --git a/skills/plotter/NOTICE.md b/skills/plotter/NOTICE.md index a2dd6bc..731460a 100644 --- a/skills/plotter/NOTICE.md +++ b/skills/plotter/NOTICE.md @@ -1,11 +1,9 @@ -# Plotter package provenance +# Plotter package notice -This package is maintained at `skills/plotter` in the public `pasqualevitiello/plotter` repository. It was extracted from `apps/ui/skills/plotter` in the coss repository. +This package is maintained at `skills/plotter` in the public `pasqualevitiello/plotter` repository. It was extracted from the coss repository; the repository’s `ATTRIBUTION.md` records that extraction and its license history. -The bundled reference manifest preserves the source revisions of the approved SVG snapshots. Files under `references/history/` preserve dated coss feedback and audits; their paths and routes describe that historical host. +It uses the accompanying MIT `LICENSE`, which retains the coss.com and Origin UI copyright and includes Pasquale Vitiello’s copyright for Plotter. -This package uses the accompanying MIT `LICENSE`, selected by the maintainer on 2026-11-08. It retains the coss.com and Origin UI copyright and includes Pasquale Vitiello’s copyright for Plotter. Third-party materials retain their own notices. +The bundled `assets/fonts/CalSansVF.woff2` is Cal Sans, credited to Mark Davis, WORDMARK × Cal.com, under the SIL Open Font License 1.1 in the adjacent `OFL.txt`. -The original extraction’s differing license declarations are recorded in the repository’s `ATTRIBUTION.md`; they describe that historical extraction rather than this package’s current license. - -Keep the complete package and its provenance together when copying or updating an installation. +Keep this notice and both licenses with the package when copying or updating an installation. diff --git a/skills/plotter/README.md b/skills/plotter/README.md index 01fde66..4c586db 100644 --- a/skills/plotter/README.md +++ b/skills/plotter/README.md @@ -11,7 +11,7 @@ Copy this **complete `plotter` directory** into the agent’s personal skills di | Codex | `~/.codex/skills/plotter` | `$plotter` | | Claude Code | `~/.claude/skills/plotter` | `/plotter` | -The canonical source is `skills/plotter` in the private `pasqualevitiello/plotter` repository. Obtain it through authenticated repository access or the complete skill download. Update installed copies as complete folders. Standalone work needs no website checkout, conversation history, package manager, or external font download. +The canonical source is `skills/plotter` in the public [`pasqualevitiello/plotter`](https://github.com/pasqualevitiello/plotter) repository. Download the complete skill from the Plotter website, or copy that folder from a checkout. Update installed copies as complete folders. Standalone work needs no website checkout, conversation history, package manager, or external font download. Example briefs for Codex: @@ -24,22 +24,19 @@ In Claude Code, start the same request with `/plotter`. One entrypoint routes to ## What is portable -Seven bundled SVG anchors support construction-reference selection, and the [catalogue](references/catalogue/index.md) bundles every website drawing by code, so a brief can say “like TIM-06”. The [visual grammar](references/visual-grammar.md) includes teaching SVGs; the [foundation](references/foundation.md) contains dependency-free geometry helpers and generated role styles. [Website integration](references/implementation.md) and dated feedback are optional branches. +Seven bundled SVG anchors support construction-reference selection, and the [catalogue](references/catalogue/index.md) bundles every website drawing by code, so a brief can say “like TIM-06”. The [visual grammar](references/visual-grammar.md) includes teaching SVGs; the [foundation](references/foundation.md) contains dependency-free geometry helpers and generated role styles. | Example | Open or generate it from the copied skill directory | | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | Static registration, using the shared arrow/dimension helpers | `node assets/examples/registration.mjs > registration.svg` | | Resolved static SVG with editable labels | `python3 scripts/export-svg.py registration.svg registration-export.svg --id-prefix registration` | +| PNG preview for inspection, light and dark | `python3 scripts/render.py registration-export.svg --theme both` | | Animation and static fallback, with shared role CSS | Open `assets/examples/assembly-motion.html` in a modern browser; keep `assets/foundation/roles.css` in place. | -Node.js is needed for the authoring example; Python 3 is needed for the static exporter. Recipients opening a resolved SVG need neither. The motion example uses browser SVG animation and a small player without a build or server. Keep its local stylesheet alongside it, or inline that generated stylesheet when delivering one HTML file. Exact Cal Sans typography depends on the font being available; the fallback is sans-serif. +Node.js is needed for the authoring example; Python 3 is needed for the static exporter and the preview renderer. The renderer uses an installed Chromium-based browser such as Chrome, Edge, or Brave, and falls back to `rsvg-convert`, `resvg`, Inkscape, ImageMagick, or macOS Quick Look. Recipients opening a resolved SVG need neither. The motion example uses browser SVG animation and a small player without a build or server. Keep its local stylesheet alongside it, or inline that generated stylesheet when delivering one HTML file. Cal Sans is bundled under the SIL Open Font License at `assets/fonts/`: previews render with it, and `export-svg.py --embed-font` carries it inside a standalone SVG. Without it on the host, labels fall back to sans-serif. The [annotated motion studies](references/motion-examples.md) explain staging and timing using three existing animations; open `assets/examples/motion-studies.html` to inspect them. The examples are teaching material, not additional approved style references. The static exporter handles the selected still, not active animation. -## Maintain the package - -[`standard.json`](assets/foundation/standard.json) owns shared numeric defaults; `scripts/build-standard.py` generates runtime data, CSS, and marked drafting tables. Generated or example-embedded styles are outputs, not separate palettes. Regenerate an example’s SVG before export when the standard changes. Website token adoption currently covers AGT-01, MEC-05, GEO-11, SYS-06, and CRF-06; all current illustrations use 1-unit visible strokes while legacy catalogue drawings retain their authored opacity and dash patterns. - -Current instructions live outside [history](references/history/index.md). Preserve the seven reference snapshots and their revision manifest. Historical coss records establish only their original tasks and revisions; coss paths in those records are provenance, not active dependencies. Update general guidance from specific evidence rather than extending every past preference to all drawings. +## Licenses See [NOTICE.md](NOTICE.md) and [LICENSE](LICENSE) for the preserved source and licensing record. diff --git a/skills/plotter/SKILL.md b/skills/plotter/SKILL.md index d30d6a1..f349688 100644 --- a/skills/plotter/SKILL.md +++ b/skills/plotter/SKILL.md @@ -9,7 +9,7 @@ Make one construction relationship carry the idea: alignment, proportion, assemb ## Choose the workflow -Resolve this skill’s installed directory first. All links below are relative to it. The complete folder includes visual references, helper implementation, examples, and export tools; standalone work needs no website checkout or prior conversation. The canonical package is `skills/plotter` in the public `pasqualevitiello/plotter` repository. +Resolve this skill’s installed directory first. All links below are relative to it. The complete folder includes visual references, helper implementation, examples, and render and export tools; standalone work needs no website checkout or prior conversation. | Request | Read and follow | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -17,7 +17,7 @@ Resolve this skill’s installed directory first. All links below are relative t | Animate an illustration; refine timing, transitions, or a loop | [Animation workflow](references/motion.md). If no usable static composition exists, complete the drawing workflow first. | | Deliver only a static drawing from an animation | Use the selected static composition and the [foundation's static export](references/foundation.md#standalone-static-export). Time zero is not automatically the right drawing. | -One Plotter entrypoint serves both workflows: `$plotter` in Codex and `/plotter` in Claude Code. “Animate this illustration” should reach the animation workflow directly while retaining the same grammar and tokens. Motion uses the same visual rules. Choose the change, stage its events, and review its rhythm before deciding how to package it; playback UI follows the delivery context. +“Animate this illustration” goes straight to the animation workflow, with the same grammar and tokens. Motion uses the same visual rules. Choose the change, stage its events, and review its rhythm before deciding how to package it; playback UI follows the delivery context. ## Load the shared references @@ -27,19 +27,17 @@ For drawing, critique, or animation: 2. Read the [visual grammar](references/visual-grammar.md) to choose meaningful marks. Inspect the linked teaching SVG for each mark you add or revise. Existing unchanged marks do not require loading every teaching example. 3. Read the [drafting standard](references/drafting-standard.md): scope, stroke palette, and geometry/dimensions; include hatch grammar when hatching is involved and symbols/topology when making connectivity or product-behavior claims. -Current direction governs composition, the grammar explains marks, and the drafting standard defines their treatment. [`standard.json`](assets/foundation/standard.json) is the editable source for shared numerical role defaults and helper constants; generated runtime data, CSS, and marked reference tables derive from it. Historical snapshots demonstrate composition and may retain documented exceptions. Preserve an existing illustration's appearance during implementation refactors. +Current direction governs composition, the grammar explains marks, and the drafting standard defines their treatment. Shared numerical role defaults and helper constants come from [`standard.json`](assets/foundation/standard.json). Historical snapshots demonstrate composition and may retain documented exceptions. Preserve an existing illustration's appearance during implementation refactors. Load additional material only for its branch: | When | Reference | | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | Writing role-based SVG, using arrow/dimension/hatch helpers, overriding tokens, or exporting | [Portable foundation](references/foundation.md), including its supported cases and examples | -| Editing the Plotter website or its components | [Website integration](references/implementation.md), then the checkout’s applicable instructions | -| Revisiting a named study's feedback or investigating a past failure | [History index](references/history/index.md); read only the relevant entry/revision | | Explicitly asked for technical verification | [Verification prompt](references/verification-prompt.md), supplied with current source and renders | ## Finish the requested artifact -Use the selected workflow's completion criteria. Deliver the editable source, the requested preview/export, and a concise account of the relationship, relevant limitations, and what was actually inspected. If rendering or interaction was unavailable, identify that gap instead of claiming visual or motion verification. Honor the requested verification scope; automated checks and tests are not prerequisites when the user excludes them. +Use the selected workflow's completion criteria. Save deliverables where the user is working, not in a temporary folder, and give their paths. Deliver the editable source, the requested preview/export, and a concise account of the relationship, relevant limitations, and what was actually inspected. If rendering or interaction was unavailable, identify that gap instead of claiming visual or motion verification. Honor the requested verification scope; automated checks and tests are not prerequisites when the user excludes them. -Keep revision IDs stable unless alternatives are requested. Appearance approval applies to a particular revision; gallery inclusion, production placement, and style-reference selection are separate decisions. When maintaining this skill, put new dated feedback in [history](references/history/index.md#maintaining-the-record) and update current instructions only where the evidence changes a reusable decision. +Write that account for someone who has not seen this package. Name a borrowed drawing by its title and what you took from it; a bare catalogue code or the word “approved” tells them nothing. diff --git a/skills/plotter/assets/fonts/CalSansVF.woff2 b/skills/plotter/assets/fonts/CalSansVF.woff2 new file mode 100644 index 0000000..b6d4ac9 Binary files /dev/null and b/skills/plotter/assets/fonts/CalSansVF.woff2 differ diff --git a/skills/plotter/assets/fonts/OFL.txt b/skills/plotter/assets/fonts/OFL.txt new file mode 100644 index 0000000..5213555 --- /dev/null +++ b/skills/plotter/assets/fonts/OFL.txt @@ -0,0 +1,93 @@ +Copyright 2021 The Cal Sans Project Authors (https://github.com/calcom/font) + +This Font Software is licensed under the SIL Open Font License, Version 1.1. +This license is copied below, and is also available with a FAQ at: +https://openfontlicense.org + + +----------------------------------------------------------- +SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 +----------------------------------------------------------- + +PREAMBLE +The goals of the Open Font License (OFL) are to stimulate worldwide +development of collaborative font projects, to support the font creation +efforts of academic and linguistic communities, and to provide a free and +open framework in which fonts may be shared and improved in partnership +with others. + +The OFL allows the licensed fonts to be used, studied, modified and +redistributed freely as long as they are not sold by themselves. The +fonts, including any derivative works, can be bundled, embedded, +redistributed and/or sold with any software provided that any reserved +names are not used by derivative works. The fonts and derivatives, +however, cannot be released under any other type of license. The +requirement for fonts to remain under this license does not apply +to any document created using the fonts or their derivatives. + +DEFINITIONS +"Font Software" refers to the set of files released by the Copyright +Holder(s) under this license and clearly marked as such. This may +include source files, build scripts and documentation. + +"Reserved Font Name" refers to any names specified as such after the +copyright statement(s). + +"Original Version" refers to the collection of Font Software components as +distributed by the Copyright Holder(s). + +"Modified Version" refers to any derivative made by adding to, deleting, +or substituting -- in part or in whole -- any of the components of the +Original Version, by changing formats or by porting the Font Software to a +new environment. + +"Author" refers to any designer, engineer, programmer, technical +writer or other person who contributed to the Font Software. + +PERMISSION & CONDITIONS +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Font Software, to use, study, copy, merge, embed, modify, +redistribute, and sell modified and unmodified copies of the Font +Software, subject to the following conditions: + +1) Neither the Font Software nor any of its individual components, +in Original or Modified Versions, may be sold by itself. + +2) Original or Modified Versions of the Font Software may be bundled, +redistributed and/or sold with any software, provided that each copy +contains the above copyright notice and this license. These can be +included either as stand-alone text files, human-readable headers or +in the appropriate machine-readable metadata fields within text or +binary files as long as those fields can be easily viewed by the user. + +3) No Modified Version of the Font Software may use the Reserved Font +Name(s) unless explicit written permission is granted by the corresponding +Copyright Holder. This restriction only applies to the primary font name as +presented to the users. + +4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font +Software shall not be used to promote, endorse or advertise any +Modified Version, except to acknowledge the contribution(s) of the +Copyright Holder(s) and the Author(s) or with their explicit written +permission. + +5) The Font Software, modified or unmodified, in part or in whole, +must be distributed entirely under this license, and must not be +distributed under any other license. The requirement for fonts to +remain under this license does not apply to any document created +using the Font Software. + +TERMINATION +This license becomes null and void if any of the above conditions are +not met. + +DISCLAIMER +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE +COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL +DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM +OTHER DEALINGS IN THE FONT SOFTWARE. diff --git a/skills/plotter/references/approved-references.md b/skills/plotter/references/approved-references.md index b92ab1f..8ab5cc5 100644 --- a/skills/plotter/references/approved-references.md +++ b/skills/plotter/references/approved-references.md @@ -1,6 +1,6 @@ # Approved references -On 2026-10-25, the user explicitly identified these 27 drawings as the best illustrations and asked that they be used as references. This list supersedes earlier broad endorsements and pending-review labels. Keep reference selection separate from revision identity: a later edit to a drawing does not silently inherit approval. +Plotter’s author selected these 27 drawings on 2026-10-25 as the best illustrations and the references for new work. A later edit to one of them does not silently inherit that approval. ## Bundled starting points @@ -16,11 +16,11 @@ Choose by construction relationship, then render and inspect the linked SVG. The | Conversation expressed with a few UI fragments | [INT-09](drawings/INT-09.svg) | Recognition through avatars, tail-free messages, and spacing | | Absence interrupting a structure | [EMP-03](drawings/EMP-03.svg) | A missing connection that affects the construction itself | -[The manifest](drawings/manifest.json) records source revision and snapshot hashes; a reference-level `source_commit` overrides the manifest's shared revision. These are source snapshots of selected compositions, not newly normalized or technically certified drawings. Historical background fills and line-role variations may remain; use the [drafting standard](drafting-standard.md) for new work. Render the snapshots on a light surface to inspect their original presentation. Bundling INT-02 adds access to an already approved composition; the 27-reference selection remains unchanged. +These are source snapshots of selected compositions, not newly normalized or technically certified drawings. Historical background fills and line-role variations may remain; use the [drafting standard](drafting-standard.md) for new work. Render the snapshots on a light surface to inspect their original presentation. ## Full reference set -The following selection remains unchanged. Every catalogue drawing, including these, is bundled as a resolved static SVG in the [catalogue](catalogue/index.md). Codes were renumbered on 2026-11-01; older records use the former codes listed in the [code map](history/code-map.md). A familiar subject alone is not a sufficient reference match. The original coss route and source locations are historical provenance, recorded in [history](history/index.md). +Every catalogue drawing, including these, is bundled as a resolved static SVG in the [catalogue](catalogue/index.md). A familiar subject alone is not a sufficient reference match. | Code | Drawing | Study ID | | ------ | --------------------------------------- | ---------------------------- | @@ -52,4 +52,4 @@ The following selection remains unchanged. Every catalogue drawing, including th | EMP-04 | An unbuilt arch | `404-unbuilt-arch` | | EMP-01 | The missing corner | `404-reference` | -The [selection evidence](history/reference-selection.md) preserves the original exclusions and working interpretations. A later revision still needs its own visual assessment; inclusion here is not technical certification. +A later revision still needs its own visual assessment; inclusion here is not technical certification. diff --git a/skills/plotter/references/catalogue/index.md b/skills/plotter/references/catalogue/index.md index 63766f0..3613946 100644 --- a/skills/plotter/references/catalogue/index.md +++ b/skills/plotter/references/catalogue/index.md @@ -4,7 +4,7 @@ Every drawing in the Plotter catalogue, exported as a resolved static SVG at its native 560 × 440. Codes match the website. When a brief names a code (“like TIM-06”), open that file and borrow its construction relationship, not its subject. -Codes are a three-letter family prefix and a number, without gaps within a family. Drawings retired as near-duplicates keep their former codes in the [code map](../history/code-map.md) and are not exported here. The [approved references](../approved-references.md) remain the style anchors; a catalogue drawing is an example, not a new reference selection. +Codes are a three-letter family prefix and a number, without gaps within a family. Drawings retired as near-duplicates keep their codes reserved and are not exported here. The [approved references](../approved-references.md) remain the style anchors; a catalogue drawing is an example, not a new reference selection. ## Geometry (GEO) diff --git a/skills/plotter/references/direction.md b/skills/plotter/references/direction.md index 2a25ad3..c9f66ac 100644 --- a/skills/plotter/references/direction.md +++ b/skills/plotter/references/direction.md @@ -1,6 +1,6 @@ # Current visual direction -Shared by drawing and animation. This is the active art direction; dated review conversations live in [history](history/index.md). Numerical roles belong to the [drafting standard](drafting-standard.md) and its generated source, not this file. +Shared by drawing and animation. This is the active art direction. Numerical roles belong to the [drafting standard](drafting-standard.md) and its generated source, not this file. ## Composition @@ -20,7 +20,7 @@ Preserve the original grouping level of opacity during role adoption. At the sha ## Typography and presentation -Use the host font or `Cal Sans, sans-serif`. Use automatic optical sizing, no added letter-spacing, no synthesized bold/italic, and one GEOM value per text role where the font supports it: 25 for ordinary illustration text, 0 for identifiers. Use typeset punctuation. Editable text with a sans-serif fallback is portable; exact Cal Sans metrics require that font to be available. +Use the host font or `Cal Sans, sans-serif`. Use automatic optical sizing, no added letter-spacing, no synthesized bold/italic, and one GEOM value per text role where the font supports it: 25 for ordinary illustration text, 0 for identifiers. Use typeset punctuation. Editable text with a sans-serif fallback is portable; exact Cal Sans metrics require that font to be available. The package bundles [Cal Sans](../assets/fonts/CalSansVF.woff2): previews render with it, and `export-svg.py --embed-font` carries it inside a standalone SVG for a host that will not load the font. Bundled references use a `560 × 440` viewBox. Inspect at the intended output size and as a thumbnail; preserve essential labels when adapting a composition. The website displays drawings at native size when space permits and scales them proportionally to fit narrower containers. diff --git a/skills/plotter/references/drafting-standard.md b/skills/plotter/references/drafting-standard.md index 27f0b21..047226b 100644 --- a/skills/plotter/references/drafting-standard.md +++ b/skills/plotter/references/drafting-standard.md @@ -1,6 +1,6 @@ # Plotter drafting standard -Use for new drawings and deliberate revisions. Read the [approved references](approved-references.md) for composition. Load the [verification prompt](verification-prompt.md) only for an explicit technical verification request. The [historical source audit](history/source-audit.md) records exceptions in named past revisions; appearance approval does not prove every annotation. +Use for new drawings and deliberate revisions. Read the [approved references](approved-references.md) for composition. Load the [verification prompt](verification-prompt.md) only for an explicit technical verification request. Appearance approval does not prove every annotation. [`standard.json`](../assets/foundation/standard.json) owns shared numeric role defaults, dash patterns, and the implemented helpers' geometry constants. The marked tables below, runtime data, and role CSS are generated from it. The prose defines meaning and conventions for native SVG beyond the helpers. Read [foundation.md](foundation.md) when applying these roles or generating marks. @@ -8,8 +8,6 @@ Use for new drawings and deliberate revisions. Read the [approved references](ap **Monochrome orthographic construction diagrams** is the precise name for this house illustration language. “Blueprint illustrations” remains useful informal shorthand. The drawings present one flat geometric relationship through visible outlines, restrained construction lines, sparse dimensions, and occasional line hatching. GEO-01 supplies the circle/square relationship, INT-03 the modular assembly and switch geometry, and SRV-04 the alignment of work within a time grid. -“Blueprint” historically identifies a reproduction process: cyanotypes commonly reproduce designs as white lines on a blue ground. Black or theme-colored SVG linework is not a cyanotype reproduction. This distinction concerns medium, not drawing accuracy. [Te Papa collection terminology](https://collections.tepapa.govt.nz/category/421176) - Declare one mode in the drawing’s source note or review: | Mode | What the drawing asserts | Required evidence | @@ -21,17 +19,7 @@ Declare one mode in the drawing’s source note or review: Most Plotter drawings are geometric constructions or conceptual diagrams. A plug outline is not automatically an electrical schematic; a circle marked “Cache” is a conceptual node, not an IEC electrical component. Orthographic here describes the flat presentation, not a claim that every diagram is a projection of a buildable object. -## What the external standards establish - -These are verified source facts, separate from the house choices below: - -- **ISO 128-2:2022** concerns technical line types, configurations, leaders, and references, including discipline-specific applications. Its public abstract supports treating line roles consistently; it does not establish Plotter’s pixel values. [ISO catalogue](https://www.iso.org/standard/83355.html) -- **ISO 128-3:2022** concerns views, sections, and cuts using orthographic projection methods. A cut or section therefore needs a meaningful relationship to an object and view. [ISO catalogue](https://www.iso.org/standard/83356.html) -- **ISO 129-1:2018** concerns presentation of dimensions and associated tolerances. Its scope distinguishes presentation from the meaning/application of dimensional tolerancing. Decorative dimensions cannot establish fit or manufacturability. [ISO catalogue](https://www.iso.org/standard/64007.html) -- **IEC 60617 DB** is IEC’s maintained collection of graphical symbols for diagrams. **IEC 60417** addresses symbols on equipment, a different use. A claimed IEC symbol needs the actual symbol entry and application context. [IEC TC 3](https://tc3.iec.ch/standard-as-database/) -- **NPS HABS drawing guidelines** distinguish line weights by the represented feature and require scale-aware adjustment. They differentiate hidden/missing features and overhead features. Their hatch rules depend on the view and material: plan poché and section treatment differ, and standard CAD surface patterns must not substitute for measured conditions. This demonstrates why “architectural hatch” is not one universal texture. [HABS guidelines, §§4.2–4.7](https://www.nps.gov/subjects/heritagedocumentation/upload/HABS-Guidelines-Measured-Drawings_508.pdf) - -Research used the public ISO catalogue abstracts and the cited IEC/NPS material. It did not review the full paid ISO standards or validate individual IEC symbol entries. This document defines an internally consistent illustration standard; it does not certify ISO/IEC/HABS compliance. +External standards inform these roles; none is claimed. Read the [standards background](standards-background.md) before asserting compliance with ISO, IEC, or HABS conventions or citing one of their symbols. ## House stroke palette diff --git a/skills/plotter/references/drawing.md b/skills/plotter/references/drawing.md index 9437de5..8a3eb18 100644 --- a/skills/plotter/references/drawing.md +++ b/skills/plotter/references/drawing.md @@ -34,6 +34,8 @@ Read [foundation.md](foundation.md) for shared roles, helpers, and export. Use n Separate geometry from presentation and file writing. Derive paths from named parameters; retain calculation precision until serialization. Preserve opacity grouping, solid arrowheads, transparent forms, and single ownership of shared strokes. Keep IDs local and unique when drawings repeat in one document. +When the deliverable is a component or other host code, compose and inspect the drawing as SVG first, then translate it, and say that the inspected render was the SVG. + Use an accessible title and description for meaningful standalone output. In a host where adjacent copy supplies all meaning, decorative SVG may be hidden from accessibility APIs. Typography follows [current direction](direction.md#typography-and-presentation). **Complete when:** the source remains editable, every dimension agrees with its witnesses, and role adoption has preserved the intended hierarchy and exceptions. @@ -42,6 +44,16 @@ Use an accessible title and description for meaningful standalone output. In a h Render the candidate beside the selected reference at a common intended size, then inspect the thumbnail. For a revision, also compare with its own previous render. Inspect both themes when the host uses them and the actual narrow layout when embedding it. +Render with the packaged script, resolved from the skill directory, and open the PNG it names: + +```sh +python3 scripts/render.py drawing.svg # native size, light surface +python3 scripts/render.py drawing.svg --theme both # when the host has a dark theme +python3 scripts/render.py drawing.svg small.png --width 240 # the width it will be shown at +``` + +The script uses an installed Chromium-based browser and falls back to other SVG renderers. A dark render recolors a themeable source that draws in `currentColor`; a resolved export keeps the ink it was exported with. When a sandbox blocks the renderer, ask to run this one command outside it. Render again after the last edit: a drawing changed since its render has not been inspected. Previews use the bundled Cal Sans, so say when the delivered file will fall back to another font on its host. + Resolve these concrete questions: - Does one focal relationship survive at a glance, with recognizable subject cues? @@ -65,6 +77,7 @@ From the copied `plotter` directory, with Node.js and Python 3 available: ```sh node assets/examples/registration.mjs > registration.svg python3 scripts/export-svg.py registration.svg registration-export.svg --id-prefix registration +python3 scripts/render.py registration-export.svg ``` -The first file is editable, themeable SVG with embedded generated role CSS. The second has resolved appearance and no coss, JavaScript, or external CSS dependency. Opening it does not require Node or Python. Adapt the example's parameters and labels to a new brief; preserve the relationship only if it fits that brief. The width witnesses come from the record rectangle; the label clearance and surrounding composition are authored explicitly and need adjustment when text or layout changes. +The first file is editable, themeable SVG with embedded generated role CSS. The second has resolved appearance and no host application, JavaScript, or external CSS dependency. Opening it does not require Node or Python. The third command writes `registration-export.png` for inspection. Adapt the example's parameters and labels to a new brief; preserve the relationship only if it fits that brief. The width witnesses come from the record rectangle; the label clearance and surrounding composition are authored explicitly and need adjustment when text or layout changes. diff --git a/skills/plotter/references/foundation.md b/skills/plotter/references/foundation.md index c8f9727..5a9dd46 100644 --- a/skills/plotter/references/foundation.md +++ b/skills/plotter/references/foundation.md @@ -2,7 +2,7 @@ Use the foundation when implementing straight transfer arrows, horizontal/vertical dimensions, or rectangular hatching. Compose the illustration with ordinary SVG; use native paths for constructions these helpers do not cover. The helpers do not choose a composition or establish a mark's meaning. -The complete skill folder contains the implementation. Resolve paths from the installed `plotter` directory, not a repository root. The ESM entrypoint is `assets/foundation/index.mjs`; it runs in a JavaScript authoring script or a host such as React without coss imports. It exports `arrow`, `dimension`, `hatch`, `highlightOpacity`, read-only `standard`, and `roleCss`. Its adjacent declaration file documents inputs and outputs. The import below assumes an authoring file at the skill root; examples in subdirectories use their own relative paths. +The complete skill folder contains the implementation. Resolve paths from the installed `plotter` directory, not a repository root. The ESM entrypoint is `assets/foundation/index.mjs`; it runs in a JavaScript authoring script or a host such as React, with no imports from a host application. It exports `arrow`, `dimension`, `hatch`, `highlightOpacity`, read-only `standard`, and `roleCss`. Its adjacent declaration file documents inputs and outputs. The import below assumes an authoring file at the skill root; examples in subdirectories use their own relative paths. ```js import { arrow, dimension, hatch } from "./assets/foundation/index.mjs"; @@ -76,13 +76,13 @@ python3 scripts/export-svg.py drawing.svg exported.svg \ Existing SVG titles/descriptions are used when those arguments are omitted. Optional `--ink '#171717'` selects the output ink; `--token=--plotter-opacity-guide=0.14` supplies an explicit token value. The exporter resolves generated roles at their original grouping level, embeds no application dependency, and prefixes local IDs and their references. It preserves authored inline overrides. Supply the token values needed for an export; a detached SVG cannot read the host's computed theme. -The output has literal appearance values, local defs, editable labels, native dimensions, and accessible meaning. Cal Sans uses a sans-serif fallback when the font is unavailable. Exact typography needs the same font; no font download is required. The exporter accepts Plotter's generated stylesheet and supported inline styles, and reports unsupported classes, external resources, or stylesheets rather than silently dropping them. +The output has literal appearance values, local defs, editable labels, native dimensions, and accessible meaning. Cal Sans uses a sans-serif fallback when the font is unavailable. Add `--embed-font` to carry the bundled Cal Sans inside the SVG, at about 200 KB, when the host will not load the font; text stays editable either way. The exporter accepts Plotter's generated stylesheet and supported inline styles, and reports unsupported classes, external resources, or stylesheets rather than silently dropping them. Export the selected static drawing. Active animation is intentionally unsupported by this static exporter; time zero is not necessarily the intended static fallback. Animation timelines and playback remain separate from the drafting helpers. ## Portable examples -- [Registration authoring](../assets/examples/registration.mjs) reads the adjacent [editable template](../assets/examples/registration.svg), regenerates its shared arrow/dimension fragments and embedded role styles, and emits SVG. The [drawing workflow](drawing.md#portable-starting-example) gives Node.js and Python commands. It reads no coss files. +- [Registration authoring](../assets/examples/registration.mjs) reads the adjacent [editable template](../assets/examples/registration.svg), regenerates its shared arrow/dimension fragments and embedded role styles, and emits SVG. The [drawing workflow](drawing.md#portable-starting-example) gives Node.js and Python commands. It reads nothing outside this package. - [Seat and withdraw](../assets/examples/assembly-motion.html) opens directly in a browser and uses the package's generated `roles.css`. It demonstrates hatch attachment, contact ownership, and playback separately from geometry. Read the [animation workflow](motion.md#portable-example) for its delivery boundary. If delivering one HTML file, inline that generated CSS rather than copying role numbers into a new stylesheet. These are implementation examples, not composition references. Regenerate registration output when the shared standard changes; keep example geometry and text intentional. Helpers centralize construction arithmetic, not the semantic decision to add a mark. diff --git a/skills/plotter/references/history/catalogue-consistency-2026-11-01.md b/skills/plotter/references/history/catalogue-consistency-2026-11-01.md deleted file mode 100644 index 4b0f613..0000000 --- a/skills/plotter/references/history/catalogue-consistency-2026-11-01.md +++ /dev/null @@ -1,179 +0,0 @@ -# Catalogue consistency review — 2026-11-01 - -## Request and scope - -After removing background fills exposed unwanted guides, the user requested a review of all illustrations and a consistent general rule with justified exceptions. This review covers all 100 active catalogue drawings, the 13 shipped compact empty-state variants, all nine existing grammar examples, a new highlight example, and representative poses of six animated companions. It preserves the earlier requested background removals and line repairs. - -This pass changes 60 catalogue exports, mostly through local label/guide clearance and removal of decorative or opaque fills. Some export changes come from the shared horizontal-dimension label offset. Eight existing grammar examples are repaired; one is unchanged. Compact variants need no changes. The seven frozen composition references and four retired SVG sources remain historical evidence. - -## Decisions - -The authoritative rule is [Fills and line clearance](../drafting-standard.md#fills-and-line-clearance): - -- Ordinary forms are transparent. Clear underlying geometry rather than painting a surface over it. -- A highlight identifies a named selection, intersection, or result. TIM-01, TIM-03, and TIM-05 use the shared `--plotter-opacity-highlight` default of `0.055`, independently of lines and labels; each physical patch is painted once. -- Text, plotted points, selected junctions, and pips may be filled symbols. This does not authorize decorative whole-object tint. -- Background guides clear UI forms and text. Start with an 8-unit contour gap; keep at least 3 units around actual glyphs. Remove short fragments that no longer explain anything. -- Axes, generating circles, radii, meaningful coordinate grids, physical contacts, and bounded hatching stay when they explain the subject. They still clear text. AGT-01’s short padding witnesses are an explicit local exception inside its card. -- Connectors terminate at open-node boundaries. Each coincident edge has one owner. Existing invisible motion masks transfer edge ownership without painting a background. - -The customization control includes the new highlight token and an independent sample. Stroke-role adoption remains limited to AGT-01, MEC-05, GEO-11, SYS-06, and CRF-06; highlight adoption does not migrate other marks to those roles. - -## Review evidence and limits - -All 100 catalogue drawings were source-reviewed and rendered in light and dark with the actual Cal Sans font. Repaired clusters received native 560 × 440 follow-up inspection. Browser clearance screens sample visible stroke geometry and transform points into each label’s coordinate space, including rotated labels. Clipped hatching is checked visually. A final screen of the regenerated 100 exports leaves only TIM-01’s enclosing A/B circles as conservative font-box candidates; measured actual-glyph clearances are 4.94 and 5.42 units, so those circles remain unchanged. - -The 13 compact variants, EMP-05 through EMP-17, were inspected at native 96 × 96 in both themes. They have no internal text or filled geometry; all computed strokes are 1px with non-scaling-stroke. No compact changes are needed. - -The new highlight example was inspected in both themes and passes the same clearance screen. A mounted customization component test verifies keyboard adjustment from 0.055 to 0.06, unchanged outline width/opacity, CSS output, and Reset to 0.055. Standalone export resolves a requested highlight override of 0.2. - -These are visual-consistency and relevant geometry checks, not renewed product-fact research, mechanical certification, approval of new reference revisions, or an exhaustive test of animation playback. Reduced motion, off-screen pausing, and interactive measurement updates were not re-tested in this pass. - -## Hand-authored geometry, interface, time, type, and empty states - -| Code | Review and fixes | Retained intentional construction | -| --- | --- | --- | -| GEO-01 | Removed hatch-area tint and marker fills; rebuilt grid segments around labels, removed duplicate diagonals and square-edge/axis overlays. | Circle, square, generating diagonal, radii and lower-left hatching explain geometric construction. | -| GEO-02 | Removed duplicated low-opacity baseline; clear in both themes. | Tangency line, perpendicular markers, center axes and radius guides. | -| GEO-03 | Removed offset-band tint and marker fills; cleared R104, moved that label along its radius; removed duplicate construction edges. | Inner generating circle, offsets, radius and center axes explain the curved band. | -| GEO-04 | Removed large-square tint and marker fills; cut grid near ×1.5 and duplicate square edges. | Growth ray, proportional squares and largest square's diagonals. | -| INT-02 | Cleared loose icon, Workspace label, Ready pill and assembled row from grid/projection strokes. | Exterior assembly guides and directional arrows terminate outside forms. | -| INT-03 | Reviewed existing rework; no further changes. | Exterior dimensions and separated construction grid. | -| INT-04 | Enlarged the gap in the u dimension around its label. | Assembly arrows, component rows and empty exterior grid. | -| INT-05 | Reviewed; no changes. | Shared gutter hatching is semantic; panel interiors remain clear. | -| TIM-01 | Tokenized two shared-window patches; cut grid and baselines at bars, removed doubled projection lines, cleared the equality sign. | Dashed selected-column projection connects the same interval across schedules; A/B circles are label enclosures. | -| TIM-02 | Cut hour grid around UTC/UTC+03 and hour labels. | Timeline ticks, booking alignment and equality mark. | -| TIM-03 | Tokenized selected cell, removed marker fill; split calendar lattice so the selected square owns each boundary once. | Calendar grid is the temporal coordinate system; meeting center/radius marks are explanatory. | -| TIM-04 | Reviewed existing rework; no further changes. | Local radius callout and exterior assembly arrows. | -| TIM-05 | Tokenized overlap square, removed marker fill; split interval outlines to avoid duplicate overlap boundaries; cleared labels, dimensions and callout; moved meeting caption down. | Selected intersection and its center mark; vertical availability centerline. | -| TIM-06 | Reviewed; no changes. | Hatching denotes reserved before/after buffers and stays out of appointment text. | -| TYP-01 | Removed letter tint and control-point fills; cleared x-height/r labels. | Generating circle, letter handles and center/baseline axes explain the letter. | -| TYP-02 | Removed C tint and control-point fills; reduced duplicate generating circles to the open right arcs and cleared 90°. | Radius/angle geometry explains terminals and opening. | -| EMP-01 | Removed whole L-shape tint and marker fills. | Modular grid, missing square and center/edge witnesses explain the absent module; 404 stays clear. | -| EMP-02 | Removed wall tint beneath hatch and marker fills; cleared r = 4u and 90°. | Wall hatching, door sweep, radius and pivot guides remain meaningful. | -| EMP-03 | Removed route-band tint; cut circle/grid segments around Request/Missing link/Unresolved; moved R60 to clear its shaft. | Generating circles and center axes explain the route and its absent connection. | -| EMP-04 | Shortened central axis above 7u; retained existing transparent arch rework. | Arch radii and keystone geometry are explanatory, not background decoration. | - - -## Other hand-authored studies - -| Code | Result / fix | Retained meaningful exception | -| --- | --- | --- | -| INT-01 | Existing repair passes; no new edit. | Local R16 corner construction inside the top pill. | -| INT-06 | Broke background grid/axes outside the fragments and assembled row; removed redundant circle bounding box and unlabeled radius fragment. | R16 generating circle and its center cross explain the pill end. Projection arrows remain. | -| INT-07 | Shortened upper-right continuation to clear R12. | Browser corner radius and content-inset construction. | -| INT-08 | Shortened lower projections to clear both 1.5u labels. | Safe-area, inset, and corner-radius geometry. | -| INT-09 | Previous transparent-dialogue repair passes; preserved. | Small labeled corner-radius witnesses. | -| OBJ-01 | Passes; no new edit. | Cropped key rows and dashed continuation explain pitch/stagger. | -| OBJ-02 | Shortened axis above shade to clear 2r; shortened lower guide beside Generating circle; shifted rotated r label from x316 to306. | Generating circle, shade radius, centerline, and base dimensions are geometric explanations. | -| OBJ-03 | Passes; no new edit. | Paired R8 circles explain the shared folder tab. | -| OBJ-04 | Existing processor omissions pass; no new edit. | Electrical routing, package pitch, and small registration/symbol dots. | -| OBJ-05 | Passes; no new edit. | Pendulum trajectory, pivot marks, equal radii, and fixed-support hatch. | -| SYS-01 | Passes; no new edit. | Route radius and inactive branch alternatives. | -| SYS-02 | Removed node covers; split all row/column connections at node perimeters; primary selected route owns its segments; removed coincident secondary route parts; stopped input axis before the open port. | Filled selected junction and its geometric locator circle/square. | -| SYS-03 | Expanded the n₁ text omission through y180. | Grid explains circuit-node positions; electrical node fill remains meaningful. | -| SYS-04 | Removed node covers and redundant lattice dots under outlined data points; broke grid/projections around points and coordinate label. | Coordinate field is the subject; measurement projection intentionally connects the selected point to the axes. | -| MEC-05 | Added grid omissions around Load and Assembled; label positions unchanged. | Bounded core hatch identifies the inserted part. | -| SRV-01 | Prior edge/cache repair passes; no new edit. | Routing and cache bend radius. | -| SRV-02 | Prior deployment-card repair passes; no new edit. | Promotion path, inset, and radius witnesses. | -| SRV-03 | Prior payment aggregation repair passes; no new edit. | Explicit collection arrows and corner radius. | -| SRV-04 | Split grid and cycle-end projection outside issue bars; cleared Week 1/Week 2 labels. | Local R16 end constructions explain shared bar geometry. | -| SRV-05 | Prior checkout repair passes; no new edit. | Routing into the Pay node and out to the result port. | -| SRV-06 | Removed six commit covers; trimmed branch/main routes at each circle, including exact arc intersections; removed duplicated main-axis segments; broke grid at captions; widened Pull request dimension gap. | Branch radii and review bracket remain explanatory. | -| SRV-07 | Prior component/instance repair passes; no new edit. | Resize bounds, control handles, and corner-radius witness. | -| SRV-08 | Removed duplicated upper projection guides and lower-left guide behind Page. | Existing dashed insertion slot and inset dimensions. | -| SRV-09 | Prior relationship-table repair passes; no new edit. | Table row dividers, connector ports, and route radius. | -| EMP-05 | Shortened lower Request projection. | Missing destination outline and routing geometry. | -| EMP-06 | Interrupted index grid outside cards; removed guide behind Index. | Missing C slot, search glyph, and dashed query projection. | -| EMP-07 | Removed guide segments coincident with cloud baseline and route edges. | Cloud generating circles, route centerline/radius, and gap witnesses. | -| EMP-08 | Interrupted notification grid outside cards and Read caption. | Stream connections terminate at open node boundaries. | -| EMP-09 | Removed guide segments coincident with page/fold perimeter; kept exterior witnesses. | Fold diagonal, writing-area proportion, and leader to the insertion point. | -| EMP-10 | Passes; no new edit. | Coordinate grid is the empty-state subject. | -| EMP-11 | Cleared R16 and keyhole-width 8; interrupted generic outer guides; shortened keyhole construction frame. | Shackle/lock inset/radius geometry remains purposeful. | -| EMP-12 | Removed guide beside Fold and grid segment coincident with envelope bottom. | Actual envelope folds and symmetry axis. | -| EMP-13 | Passes; no new edit. | Gear pitch circles and geometric construction. | -| EMP-14 | Moved Socket label x376→400, extended leader to M376 172V162H400; interrupted guides outside plug body. | Fixed-support hatch and socket section kept. Compact source geometry untouched. | -| EMP-15 | Started vertical R40-adjacent guide at y156. | Pin generating radius and coordinate field. | -| EMP-16 | Interrupted guides outside calendar frame; set Today `labelOffset={10}` to clear dimension tick. | Calendar grid is subject geometry; selected-day lines remain. | -| EMP-17 | Interrupted guides outside image frame to avoid coincident solid/dashed perimeter strokes. | Aspect-ratio diagonal and right-angle mark. | -| COS-01 | Interrupted proposed upper outline behind SMS. | Common-interface construction, generating radii, bounded profile hatch. | -| COS-02 | Started top center axis at y72; moved rotated r=u label (302,120)→(298,116); widened local horizontal grid omission to x278–318. | Half-unit field and complementary generating circles explain the seam. | - - -## SVG-authored studies - -| Code | Result and reason | -| --- | --- | -| AGT-01 | Shortened the x328 upper guide to y218 to clear Registered agent. Transparent card, buttons, and avatar retained. Short local internal alignment witnesses remain because they demonstrate the registered layout and avoid content; root confirmed this exception and will document it. | -| AGT-02 | Reviewed; no change. Delegation projections stop outside the resulting task forms. | -| AGT-03 | Reviewed; no change. Handoff connectors/ports and text remain clear. | -| AGT-04 | Shortened the upper 32-unit dimension segment by 1 unit for full label clearance. Tool control interiors remain clear. | -| AGT-05 | Reviewed; no change. Permission geometry, labels, and local hatching remain clear. | -| AGT-06 | Moved R24 above the corner-center witness so it clears both the witness and the input connector. Shared-memory table and open ports preserved. | -| AGT-07 | Reviewed; no change. Checkpoint labels and local construction remain clear. | -| AGT-08 | Reviewed; no change. Parallel routing and open-node clearances retained. | -| GEO-05 | Repositioned R = u between its radius witness, rounded outline, and prior circle. The circle remains as meaningful before-state geometry. | -| GEO-06 | Repositioned all three radius labels away from their shafts, arc, and arrowhead. The three tangent radii and continuous primary curve are unchanged. | -| GEO-07 | Moved R = u outside the hatched lobe and extended its radius shaft along the same ray to support the label. XOR hatch and shared void preserved. | -| GEO-08 | Reviewed; no change. Interrupted pattern and its meaningful construction remain clear. | -| MEC-01 | Moved Aperture 4 units right and extended its leader equally, keeping the 8-unit leader-to-label gap while clearing the outside ring. Blade hatch and aperture geometry preserved. | -| MEC-02 | Repositioned 2r and r inside clear regions of their pulleys, away from radius shafts, centerlines, and hubs. Belt tangencies and pulley geometry unchanged. | -| MEC-03 | Moved e = 24 away from the cam/follower center ray. Mechanical centers/radii remain as explanatory construction. | -| MEC-04 | Reviewed; no change. Latch/receiver geometry and labels remain clear. | -| GEO-09 | Reviewed; no change. Staircase dimensions and construction are meaningful and clear. | -| NAT-01 | Widened the u dimension gap and removed the surplus bottom centerline segment behind 4u. Leaf geometry and vein construction unchanged. | -| NAT-02 | Reviewed; no change. Honeycomb repetition, cell construction, and labels remain clear. | -| TIM-08 | Reviewed; no change. Chord geometry and annotations remain clear. | -| NAT-03 | Extended the existing break in the 175 contour by removing two short sampled segments at each end. Label position and overall contour shape retained. | -| SYS-05 | Reviewed; no change. Converging routes meet their intended geometry without text collisions. | -| TYP-03 | Reviewed; no change. Letter construction and hatch areas remain clear. | -| TYP-04 | Reviewed; no change. Shared glyph geometry and labels remain clear. | -| TYP-05 | Split the upper horizontal height guide around R56. Shared-stroke hatch and glyph geometry retained. | -| TYP-06 | Removed the short surplus upper centerline behind 8u. Negative monogram and hatch field retained. | -| TYP-07 | Reviewed; no change. Optical alignment guides remain meaningful and avoid labels. | -| INT-10 | Reviewed; no change. Corner-rule witnesses and text remain clear. | -| INT-11 | Shortened the left upper dimension witness before Wide. Reflow cards remain transparent with clear interiors. | -| INT-12 | Reviewed; no change. Slider track and leader already terminate at the open control boundary. | -| TIM-07 | Reviewed; no change. Recurrence geometry and labels remain clear. | -| CRF-01 | Raised Warp by 2 units to clear its dimension witness. Alternating weave cuts and hatch remain intact. | -| CRF-02 | Reviewed; no change. Stitch paths already terminate at hole rims rather than crossing open holes. | -| CRF-03 | Reviewed; no change. Dovetail geometry and annotations remain clear. | -| CRF-04 | Moved 45° off the fold diagonal and hatch region. Folded and proposed sheet geometry unchanged. | -| CRF-05 | Reviewed; no change. Tile geometry and local annotations remain clear. | -| GEO-10 | Trimmed the Missing leader start by 2 units for label clearance. Domino dots retained as semantic pips, not object background fills. | -| MEC-06 | Reviewed; no change. Balance geometry and its explanatory axes remain clear. | -| GEO-11 | Reviewed; no change. Radius annotation already has a deliberate clear interval. | -| SYS-06 | Reviewed; no change. Resilient-route connectors terminate at open port rims. | -| CRF-06 | Split the right projection around Rejoin. Repair-key and broken-board geometry retained. | - - -## Existing grammar examples - -| Drawing | Result and reason | -| --- | --- | -| arrows | Repositioned 90° into the clear pocket between the proposed part, angle arc, and current part. Started the left long-dimension witness below the 2u annotation. | -| callouts | Same geometry/annotation repair as arrows, preserving its separate grammar focus. | -| centerlines | Stopped the bottom centerline before ⌀264 and widened its horizontal dimension-label gap. | -| dimensions | Moved rotated R120 inward along its construction so it clears the object band and radius shaft. Moved Offset left to clear the explanatory full-circle construction. | -| grids | Moved 3u and 2u into clear grid cells away from their radii and circle boundaries. Existing complementary isolation-only grid segments remain unchanged. | -| hatching | Same Aperture callout repair as MEC-01; hatch region and focus preserved. | -| outlines | Same Registered agent guide repair as AGT-01; short named alignment witnesses retained. | -| projections | Reviewed; no change. Projection lines stop outside the source and destination task forms. | -| states | Moved R52 into the clear lower-right interior of the circular opening, away from its radius shaft, centerline, and circumference. Hidden channel semantics preserved. | - - -The new `highlights.svg` teaches the common two-hour interval in two schedules. Each row has one highlight patch; guides, outlines, and labels remain separate. - -## Animated companions - -Six companions were inspected at representative poses in both themes. The PrimitivesMorph follow-up covers all six held stages at 1.8, 5.0, 8.2, 11.4, 14.6, and 17.8 seconds: Avatar, Pill, Switch, Button, Card, and Slider. Local grid gaps clear each annotation; slider extension guides now clear their endpoint percentages while retaining matching path topology across stages. The 45° annotation moves outside the intact hatch sector. Final held-pose screens include visible animated guide references and report no candidates. Timing, easing, primary shapes, and existing edge-ownership masks are preserved. - -Assembly was inspected at its Workspace, Booking, and Activity holds. Production-chain poses cover the entering/seated core; its feed guide now breaks around Load. Cradle inspection includes rest and left/right swing states. Orbits and missing-destination companions were checked at representative positions; the latter inherits its static Request clearance fix. These samples establish the reviewed appearance, not continuous playback or full transition correctness. Morph previews populate measurement labels from held geometry; they do not execute the React measurement effect. - -## Verification - -- Repository formatting, TypeScript, catalogue integrity, unique IDs, skill links, and all seven frozen-reference hashes pass. -- The skill-creator validator passes using an isolated temporary Python environment with its PyYAML dependency. -- All 100 resolved catalogue exports retain explicit 1-unit strokes. Invisible animation masks retain their separate clearance widths. -- Highlight keyboard adjustment, reset, CSS output, grammar isolation without opacity amplification, and standalone token override pass. -- Full lint still reports the pre-existing array-index key in `particles-assembly-drawing.tsx:440`, plus 15 existing warnings. The key is identical to the committed version; this audit does not change it. diff --git a/skills/plotter/references/history/code-map.md b/skills/plotter/references/history/code-map.md deleted file mode 100644 index c445035..0000000 --- a/skills/plotter/references/history/code-map.md +++ /dev/null @@ -1,121 +0,0 @@ -# Code map - -On 2026-11-01 the catalogue was renumbered into one scheme: a three-letter family prefix and a number, without gaps within a family. Study IDs, deep links, and drawing sources did not change. Use this table to read older records, which keep the codes they were written with. - -The seven bundled snapshots were renamed with their codes (for example, `P00.svg` became `GEO-01.svg`); their contents and hashes are unchanged. - -## Renumbered - -| Former | Current | Drawing | -| --- | --- | --- | -| P00 | GEO-01 | Circle, square, line | -| P01 | GEO-02 | Tangency | -| P02 | GEO-03 | The corner rule | -| P03 | GEO-04 | A system of proportions | -| GE01 | GEO-05 | A circle, extended | -| GE03 | GEO-06 | A curve from three radii | -| GE04 | GEO-07 | The shape between circles | -| GE05 | GEO-08 | One interval left open | -| AR02 | GEO-09 | One rise, one run | -| PL03 | GEO-10 | One piece short | -| T01 | TYP-01 | Anatomy of a letter | -| T02 | TYP-02 | A mark in the making | -| TY01 | TYP-03 | A from three strokes | -| TY02 | TYP-04 | One arch, three glyphs | -| TY03 | TYP-05 | The joining stroke | -| TY04 | TYP-06 | A monogram in the void | -| TY05 | TYP-07 | The center you see | -| C00 | INT-01 | The exploded interface | -| C01 | INT-02 | An assembly of parts | -| C02 | INT-03 | A modular tray | -| C03 | INT-04 | Recombination | -| C04 | INT-05 | Shared frame | -| I03 | INT-06 | From parts to a whole | -| I04 | INT-07 | A browser, in detail | -| I05 | INT-08 | The screen within the frame | -| I06 | INT-09 | A conversation, constructed | -| UI01 | INT-10 | One corner rule | -| UI02 | INT-11 | The same modules, reflowed | -| UI03 | INT-12 | Position becomes value | -| K02 | TIM-01 | Common ground | -| K03 | TIM-02 | One moment, two places | -| K06 | TIM-03 | A week, constructed | -| K07 | TIM-04 | The shape of a time slot | -| K08 | TIM-05 | Where schedules meet | -| K09 | TIM-06 | Appointment buffers | -| TM03 | TIM-07 | The same interval, again | -| MU02 | TIM-08 | Three notes, one onset | -| W02 | SYS-01 | A route, constructed | -| W03 | SYS-02 | A connection, located | -| W04 | SYS-03 | One node, two paths | -| A03 | SYS-04 | A measured distribution | -| MP05 | SYS-05 | Different paths, one place | -| B01 | SRV-01 | Cloudflare · Between visitor and origin | -| B02 | SRV-02 | Vercel · From preview to production | -| B03 | SRV-03 | Stripe · Payments, combined | -| B04 | SRV-04 | Linear · Work aligned to a cycle | -| B05 | SRV-05 | Stripe · Many ways to pay | -| B06 | SRV-06 | GitHub · A change, brought together | -| B07 | SRV-07 | Figma · Rules that resize | -| B08 | SRV-08 | Notion · Knowledge, assembled | -| B09 | SRV-09 | Supabase · A shared relation | -| AG01 | AGT-01 | An agent, registered | -| AG02 | AGT-02 | One task, two agents | -| AG03 | AGT-03 | Context, carried forward | -| AG04 | AGT-04 | One matching interface | -| AG05 | AGT-05 | Only the shared scope | -| AG06 | AGT-06 | One context, two readers | -| AG07 | AGT-07 | A state worth keeping | -| AG08 | AGT-08 | Separate work, one join | -| E00 | EMP-01 | The missing corner | -| E01 | EMP-02 | An empty threshold | -| E02 | EMP-03 | An interrupted path | -| E06 | EMP-04 | An unbuilt arch | -| S01 | EMP-05 | The missing destination | -| S03 | EMP-06 | A search, unanswered | -| S04 | EMP-07 | A cloud, out of reach | -| S05 | EMP-08 | A stream, caught up | -| S06 | EMP-09 | A page, unwritten | -| S07 | EMP-10 | A field without observations | -| S08 | EMP-11 | A boundary, locked | -| S09 | EMP-12 | An envelope, unfolded | -| S10 | EMP-13 | A gear train, interrupted | -| S11 | EMP-14 | A connection, apart | -| S12 | EMP-15 | A pin, unplaced | -| S13 | EMP-16 | A week, unbooked | -| S14 | EMP-17 | An image, not yet placed | -| O03 | OBJ-01 | A keyboard, in detail | -| O04 | OBJ-02 | A lamp, drawn in elevation | -| O05 | OBJ-03 | A family of folders | -| O06 | OBJ-04 | A processor, constructed | -| O07 | OBJ-05 | Newton’s cradle, at release | -| ME01 | MEC-01 | Six blades, one aperture | -| ME02 | MEC-02 | One belt, two rotations | -| ME04 | MEC-03 | An offset becomes a lift | -| ME05 | MEC-04 | A profile finds its receiver | -| W05 | MEC-05 | A part, made in sequence | -| PL04 | MEC-06 | Unequal arms, equal moments | -| CR01 | CRF-01 | Over and under | -| CR02 | CRF-02 | A seam, joined | -| CR03 | CRF-03 | A joint that holds | -| CR04 | CRF-04 | Across the crease | -| CR05 | CRF-05 | One shared corner | -| NA01 | NAT-01 | A branching leaf | -| NA02 | NAT-02 | One edge, two cells | -| MP04 | NAT-03 | The summit in contours | -| X01 | COS-01 | One interface, many services | -| X07 | COS-02 | A common boundary | - -## Retired - -These near-duplicates left the catalogue on 2026-11-01. Their former codes are not reused, and their sources remain in the website repository. - -| Former | Drawing | Covered by | -| --- | --- | --- | -| TM02 | Room around an appointment | TIM-06 | -| S15 | No matching results | EMP-06 | -| SW03 | A history comes together | SRV-06 | -| SW02 | A shorter return | SRV-01 | -| AR03 | The last piece of the arch | EMP-04 | - -Motion-study labels M01, M03, and M04 were display labels, not catalogue codes. The motion studies now show the code of the drawing they animate (GEO-01, EMP-05); the orbit study has no catalogue drawing. diff --git a/skills/plotter/references/history/coss-product-concepts.md b/skills/plotter/references/history/coss-product-concepts.md deleted file mode 100644 index 2cc8bd3..0000000 --- a/skills/plotter/references/history/coss-product-concepts.md +++ /dev/null @@ -1,48 +0,0 @@ -# coss.com product concepts - -Historical evidence for the named revisions. Use the [current instructions](../../SKILL.md) for new work; these findings and product claims need fresh evidence before being applied to a later revision. - -Source review: 25 October 2026. Scope: two replacement local concepts in `/ui/plotter#coss-concepts`. These are proposals for review; do not publish, push, or deploy them to coss.com. -These are conceptual product diagrams. They do not claim to be infrastructure topology, standardized -electrical symbols, physical parts, performance charts or implementation availability badges. - -## Evidence and claim boundary - -- The [live homepage](https://coss.com/) presents Email, SMS, Video and Scheduling behind one SDK and - one key, with a common operational contract. Its catalog is retained without new API or availability - claims. The cosscom/coss repository’s `apps/site/src/components/home/parts.ts` supplies the same four entries. -- [SDK overview](https://coss.com/docs/sdk) and - `content/docs/(tools)/sdk/index.mdx`: one client is created with an API key and reused across products. -- [Sending email](https://coss.com/docs/email/sending), - [delivery events](https://coss.com/docs/email/delivery), and the corresponding local MDX explain an - accepted send followed by delivery reporting for individual recipients. The return line is an event, - not a promise that every recipient receives or opens the email. -- [SMS](https://coss.com/docs/sms) and `content/docs/sms/index.mdx` describe sending to a carrier and - following its reported outcome through the same key, webhooks and logs. The drawing does not promise - delivery, depict a guaranteed latency or claim the return is an SMS sent to the recipient. -- [The public documentation index](https://coss.com/llms.txt) covers implemented Email, SMS, Hooks and - Risk; it is not identical to the homepage's four-product presentation. Video and Scheduling therefore - remain conceptual room/availability illustrations of the existing marketing descriptions. No method, - status, quota, recording pipeline or synchronization behavior is invented for them. - -Live text and the checked-out primary MDX were read before implementation. Some live `.md` fetches -were unavailable in the research tool; their checked-out source supplied the detailed behavior evidence. - -## Visual direction and rejection - -The user rejected the first X01–X07 set for poor quality relative to the established illustrations. The bus, service pictograms, and separate/shared-container comparison are superseded. Their scoped product research remains useful; their geometry checks do not establish visual acceptance. - -The new pair starts from complementary geometry rather than a catalog of icons: - -| Drawing | Construction → product meaning | What it leaves out | -| --- | --- | --- | -| X01 · One interface, many services | Four planar pieces register to one circular opening → different catalog services meet one SDK contract | Physical parts, actual network topology, API availability or authorization guarantees | -| X07 · A common boundary | Two complementary regions share one continuous curved boundary → an app and coss meet through a common interface | Transport, request flow, timings, deployment topology or provider implementation | - -P00 supplies the hierarchy of silhouette, generators, grid, and measurements. B03/B04 establish how a service idea can live in a construction relationship. Neither proposal has been approved as a reference. Components live under `app/plotter/coss-concepts` and are shown only in the local Plotter showcase. - -## Geometry and review limits - -The X07 square is 240 units wide; its two generating circles have equal radius 60 and centers 120 apart. Their complementary semicircles form a shared S-profile with one path owner. The labels `4u`, `2u`, and `r = u` use `u = 60`. These are drawing units, not product dimensions. - -Geometry and browser review are recorded against specific revisions in the [source audit](source-audit.md). Product meaning, geometric consistency, and visual acceptance remain separate. Do not promote the new concepts into the approved reference set without explicit user selection. diff --git a/skills/plotter/references/history/direction.md b/skills/plotter/references/history/direction.md deleted file mode 100644 index 2c7abb3..0000000 --- a/skills/plotter/references/history/direction.md +++ /dev/null @@ -1,316 +0,0 @@ -# Historical direction and feedback - -Archived evidence, not the current workflow. Entries describe the revisions at the time, including superseded choices. Use [current direction](../direction.md) for new work; consult individual entries only when revising that study or investigating its history. - -Evidence captured from the coss UI illustration reviews on 2026-10-24–25 and the fresh-session evaluation on 2026-10-31. This is a living art-direction record, not a claim that every study has been approved. - -## Visual grammar on the page — 2026-10-31 - -The user expected the grammar on the Plotter page and found the initial small paired illustrations “poor”. The response adds a visible navigation link and a section at `/ui/plotter#visual-grammar`, then replaces the worksheet-sized pairs with full `560 × 440` studies and a useful/counterexample toggle. Registration, delegation, and iris reuse the liked construction arrangements; the other topics use fuller geometric constructions. Counterexamples change the supporting marks while retaining the main geometry. This is the implementation response to the critique, not new approval of these teaching examples. - - -The user then said they “love the new grammar examples”, asked to remove the counterexamples, and proposed hiding unrelated elements on hover. Keep these eight full-size drawings and their original appearance. The page isolates the topic’s marked elements on hover, keyboard focus, or a touch toggle; leaving the interaction restores the full drawing. Counterexample assets and controls were removed. This is positive feedback on the teaching drawings, without changing the earlier 27-reference selection. - -The user then clarified that isolation must not change the selected element’s color or original stroke treatment, and that unrelated labels and callout leaders must disappear. The isolated grid also exposed gaps where full-view strokes had shared ownership. Preserve original opacity and widths; isolate only the named marks. Restore the grid’s missing shared segments only during isolation. The page now defines the hidden C-shaped channel and distinguishes its dashed boundary from the separate callout leader. - -## Catalogue removals after expansion — 2026-10-31 - -The user requested removal of 36 distinct studies: - -- **“Not visually interesting”:** OB01, OB02, OB03, OB05, ME03, AR04, AR05, NA03, NA04, NA05, MU01, MU03, MU04, MU05, MP01, MP02, MP03, UI04, UI05, SW01, SW04, SW05, TM01, TM04, TM05, AB01, AB02, AB03, AB04, AB05, PL01, PL02, PL05. -- **Too similar to existing catalogue entries:** AR01 and GE02. -- **Explicit follow-up:** “remove OB04 too”. - -OB03 and AB05 were each repeated in the request; each is removed once. The active catalogue now contains 100 illustrations: 58 earlier drawings and 42 expansion entries. Preserve their codes and IDs without closing numbering gaps. Removed SVGs and metadata are retained only as review evidence in `apps/ui/plotter-evals/2026-10-31/catalog-expansion/removed/`. - -This feedback rejects these particular drawings, not their entire subject categories. It does not promote the remaining entries to approved references. The stated visual-interest critique should not be replaced with an invented technical diagnosis. - -## Liked revisions, catalogue expansion, and mark selection — 2026-10-31 - -After liking registration revision 2, the user also liked the reference-led delegation and iris revisions: “love them, continue with all the remaining examples, and also want them to be added to the catalogue”. Preserve those three appearances as AG01, AG02, and ME01. The initial implementation added all 78 requested subjects to the existing 58 drawings, with editable SVGs and stable IDs. The subsequent removals are recorded above; the 39 other retained revisions still await individual feedback. Catalogue inclusion does not expand the 27-reference set. The repository’s `apps/ui/plotter-evals/2026-10-31/catalog-expansion/notes.md` records this pass. - -The user asked for diagonal lines on W05’s cubes, then clarified: “W05: only cubes should have diagonal lines”. Hatch only the square core faces in both the static drawing and its animation. Leave carrier frames and surrounding machinery unhatched; keep the hatch attached to the moving core. This is a W05-specific preference, not a requirement to hatch every object. - -The user also requested a short illustrated explanation of drawing elements. The [visual grammar](../visual-grammar.md) pairs useful and unnecessary applications of each mark. It explains selection and meaning while the drafting standard remains authoritative for line values. Do not treat the available marks as a checklist to include in every drawing. - -## Rejected broad batch and single-subject revision — 2026-10-31 - -The user described the subsequent 78-drawing batch as “low quality” and “not consistent with our rules and the other examples.” They authorized the proposed response: pause expansion, rebuild one agent-registration illustration beside approved references, and use the comparison to improve the skill. This is collective rejection of the batch, not individual feedback on every concept. - -Our diagnosis is that generating large groups before establishing visual fit reproduced surface ingredients without sufficiently developing the construction relationships. The final inspection caught obvious defects but did not reject weak compositions. This repeats the earlier rejected service concepts below. The user's request to skip test suites did not remove the need for design judgment. - -The [registration case](examples/agent-registration.md) preserves the rejected version, the chosen C01/C02/I06 references, and the proposed revision. The main skill now requires a concrete reference mapping and a same-size visual comparison before expanding a collection. After viewing the revision and being asked whether it felt closer to the desired style, the user replied “i love it”. Preserve revision 2’s appearance and record this as positive feedback on that exact drawing. The subsequent catalogue request is recorded above; praise for registration alone is not evidence of reliability across other subjects. The existing 27-reference selection and the three previously liked experiments remain intact. - -## Fresh-session experiments and grid comparison — 2026-10-31 - -The user liked all three fresh-session experiments and later requested their original versions in the catalog: - -| Experiment | Catalog code and ID | Subject | -| --- | --- | --- | -| A | C04 · `particles-shared-frame` | Two unequal modules in a shared frame | -| B | K09 · `cal-appointment-buffers` | An appointment with equal buffers | -| C | S15 · `state-no-matching-results` | An indexed collection with no matching result | - -After comparing versions with and without added background grids, the user said: “i honestly prefer these examples to be without grids i'd add them only if necessary”. Keep the originals without added grids. This supersedes the assistant’s recommendation to keep the grid variants; it does not revoke explicit grid requests for existing studies or promote these experiments into the approved reference set. Prompts, originals, and feedback are preserved in the repository at `apps/ui/plotter-evals/2026-10-31/`. - -The user then proposed geometric studies such as M01 and P00 as good candidates for grids. They accepted the qualification that geometric content alone is insufficient: A is also geometric and was preferred without the grid. The resulting [Compose](../drawing.md#compose-the-static-drawing) rule is to consider a grid when geometric construction is the subject and keep it when it helps reveal that construction. The assistant’s interpretation is that the extra grids were redundant in these three examples, not that grids are incompatible with the style. - -## Current references - -The user explicitly selected the [27 approved references](../approved-references.md) on 2026-10-25. Use that exact set for future drawing and critique. It supersedes the earlier blanket emphasis on original Primitives/Particles and the historical pending-review labels below. Other current examples need refinement or a clearer fit; the user did not yet specify a reason for each and did not ask to remove them. - -Original Primitives/P00 and Linear/B04 remain approved. Original Particles/C00 is now a historical reference. Earlier endorsements of a particular detail, such as C00’s arrow caps, remain evidence about that detail rather than approval of the whole composition. - -## Reference-led refinement pass - -The user next asked to improve the remaining drawings using the selected references. All 24 candidates were revised in place: C00, C03, P01, K03, I04, I05, W02, O03, O04, O05, B08, S01, and S03–S14. Their IDs and subjects remain stable; the 27 approved SVGs are unchanged. These new revisions await user review and are not additional style references. - -The implementation response concentrates each drawing on one relationship: - -- P01 shares a tangent between two radii; K03 aligns one booking across two hour scales; W02 selects one route through a measured junction. -- C00 repeats an inset across fragments; C03 recombines equal-width parts into three equal rows; B08 inserts a reusable block into a matching page slot. -- O03 shows quarter-pitch stagger, I04 an enlarged browser corner, I05 a concentric frame and safe area, O04 a semicircle on its support axis, and O05 a tab shared by two folder widths. -- The empty states give absence a structural role: a missing index entry, an ended notification stream, an unwritten page, an empty coordinate field or week, an unoccupied image frame, an interrupted route, a locked boundary, a pending message, separated pitch circles, disconnected contacts, or an unresolved location. - -The revised forms are transparent. Grid paths are omitted or split where they would add noise or cross labels; no background patches hide them. Hero and compact empty-state versions were checked separately. This pass changes the showcase’s static studies, not the production heroes or the animation sequences. - -### Follow-up on the revised set - -The user reviewed ten studies and gave these corrections. This is specific feedback on the reference-led pass, not approval or rejection of the other revisions: - -- **C00/C03:** the user clarified that C02 is the switch reference. Use its 30 × 18 track, R9 corners, R5.5 thumb, 3.5 inset, and primary 0.95 stroke at full opacity. Matching C00 to C03’s muted secondary stroke did not resolve the inconsistency; geometry and stroke treatment must both match C02. The animated switch already follows this treatment. -- **I04:** the browser’s upper-left radius is excessive and its three chrome circles are undersized. Reduce the corner and enlarge/re-align the controls within the same detail crop. -- **I05:** the external lines feel bland. Use exterior dimensions and extensions to explain the frame and safe-area insets; extra lines need a geometric purpose. -- **B08:** the insertion route and arrow should be dashed. Treat it as movement, with a solid open cap meeting the first dash at its tip. -- **S13:** the circle around Wednesday feels inconsistent. Use a restrained weekday underline while retaining the column alignment. -- **S08:** the lock body lacks construction geometry. Explain the rounded body, keyhole axis, and their relationship, not just the shackle. -- **S09:** the separated letter/envelope result is not liked. The response uses one open envelope with its folded flap projected across the crease. -- **S10:** the two-gear result is not liked; the user suggests a third, smaller gear. The response uses a 12/8/6-tooth train: the smaller pair engages while the main drive remains separated. Keep tooth pitch and construction circles coherent across the mechanism. -- **S11:** the symmetric plug/socket revision is worse; the user preferred the former wall section on the right. Restore the fixed wall/socket relationship and its section hatching. -- **S12:** the composition is too vertical. Broaden the coordinate field and shorten the pin-to-target relationship without rotating the represented object. - -These responses remain subject to review. Preserve the other studies, the approved reference set, and the animation work. - -## Production selections - -The user explicitly selected **P00** for the main page, [**C03** for Particles](../particles-recombination.png), and [**E02** for the 404](../not-found-interrupted-path.png). These are current implementation decisions. Use the current approved reference set for the broader style; C03’s production selection does not make it a reference. The Plotter showcase owns independent snapshots of the selected drawings, so it can ship separately from the production integration. Original C00 and E00 remain separate examples. - -## Historical review evidence - -These entries record earlier feedback and its implementation response. Current reference status comes from the explicit selection above. - -| Evidence | Status and implication | -| --- | --- | -| C03: requests a third element so the composition becomes “A + B + C” | Revise C03 in place. Added an Open action alongside identity and visibility, repeated as the third row of the assembled panel; three equal rows measure 3u. This is a requested experiment, awaiting review. | -| C03 A + B + C: “it’s not vertical aligned” and the underlying grid “looks bad or it’s sparse” | Optically center the composition within its SVG and use continuous construction guides aligned to component edges and row boundaries. This is the implementation response to the critique, awaiting review. | -| User asks to hide the home and Particles illustrations on smaller screens | Show those two hero drawings only from the existing desktop split-layout breakpoint (`lg`, 1024px). This does not change the 404 or standalone showcase illustrations. | -| User rejects a shared page-hero component and asks for the 404 heading to stay centered with the illustration above | Keep main and Particles split layouts in their pages. Use an illustration-first centered stack for the production 404 page. The showcase presents the drawing on its own. | -| User asks to restore the previous Particles page, then explicitly confirms “Keep C03; restore search beneath heading” and references PR #895 for headings | Keep C03 on the right, restore search beneath the left-aligned heading/description, and remove the added hero CTAs. Use PR #895’s fluid 36–64px heading scale, leading-none, and GEOM50 on the main and Particles pages. | -| User rejected K01, K04, K05, I01, I02, D01, D02, W01, O01, O02, A01, A02, S02; W02 partly | Explicit group feedback: these went beyond the desired set. The stated general boundary was flat 2D electrical/architectural blueprints, with no 3D or skewed views. | -| K06: not clear it is a week | Revised with Mon–Sun, hourly rows, and a labeled Thursday interval. A seven-column grid alone did not establish the subject. | -| K08: good concept, meaning unclear; more labeling suggested | Preserved crossing availability bands and added named people plus a shared-meeting callout. | -| I03: good, not an excellent example | Revised from a single generic row to separate elements projecting into a shared control. | -| W03: a bit weak | Replaced the isolated switch with a switching matrix and one selected junction. | -| W02: does not really seem a blueprint; user could not say why | Replaced rounded endpoint cards and checkmarks with a continuous route whose width, bend radius, and branch spacing are measured. | -| Response to those five revisions: “much better” | Initially collective positive feedback. K06, K08, I03, and W03 were later explicitly selected as references; W02 was omitted. | -| E03/E05 set aside by the assistant | Inferred conflict with the no-tilt rule; not individually rejected by the user. | -| O03 keyboard: “doesn’t look good”; asks to show a portion and use more subtle/dashed lines | Revised as a deliberate keyboard detail with credible staggered rows and modifiers, quiet outlines, and dashed continuation. O03 is outside the current approved reference set. | -| I04 browser: “same problem as keyboard before” | Interpreted as a request for a deliberate enlarged browser detail, with subdued strokes and dashed continuation. I04 is outside the current approved reference set. | -| I06 chat: asks to add an avatar and remove the triangle on the bubble | Pair rounded, tail-free message blocks with circular avatars. I06 was later explicitly selected as a reference. | -| O05 folder: asks for two or three instead of one | Revised as three separate flat outlines sharing tab geometry and alignment. O05 is outside the current approved reference set. | -| E04: “remove” | Explicitly removed. This is a choice about E04, not a blanket rejection of all absence metaphors. | -| E02: good idea but bland/weak | Preserve the idea while strengthening its composition. Selected for the 404 page after revision. | -| B02 Vercel: not loved; wants more conceptual/metaphoric, then asks whether it is accurate and requests improvement | Replaced the broadcast-like aperture with separate preview frames and one selected preview promoted to an identical production frame. “Preview” / “Production” replaces “Draft” / “Live” because previews are already reachable deployments. Matching outlines identify the same source version, not the same build: preview promotion rebuilds for the production environment. The revised B02 drawing was later explicitly selected as a reference. | -| B03 Stripe: “ok”; wants an alternative focused on what it does | Kept B03 and added B05 as an alternative. Both were later explicitly selected as references. | -| B01 Cloudflare: asks whether the representation is accurate | Initially a request for factual review. Scope the concept clearly; B01 was later explicitly selected as a reference. | -| B09 Supabase: points to the crowded connector at owner_id and says it does not look good | Replaced the branching endpoint with a circular port and a short straight approach after the bend. This critiques that junction, not all relationship notation. Revised B09 was later explicitly selected as a reference. | -| B04 Linear: “love the Linear example” | Explicit positive reference for service concepts; preserve it. | -| Request for more popular-service examples | B05, B06, B07, and B09 were later explicitly selected as references; B08 was omitted. | - -The earlier K06/K08/I03/W02/W03 revision pass is captured in coss commit `285493c9` on `codex/blueprint-illustration-studies`. The preceding flat-direction pass is `e9077a93`. Preserve this evidence if gallery metadata later changes. - -## Showcase curation - -The user subsequently asked to remove unwanted and discarded examples and turn the lab into a showcase named **Plotter illustrations**. The gallery at `/ui/plotter` has category filters and enlarged previews. Shortlists, review controls, and page-hero mockups have been removed. - -The 13 explicitly rejected entries (K01, K04, K05, I01, I02, D01, D02, W01, O01, O02, A01, A02, S02) and the assistant-set-aside E03/E05 were removed from the drawing code. E04 was already absent. W02 stays because its revised planar route received the later collective “much better” response. Retained revisions of other critiqued examples remain subject to the evidence above: curation is not individual approval or promotion to a style anchor. - -## Motion studies - -For the P00 experiment, the user requested continuous shape changes, changing measurements, faster morphs, and longer holds. They then clarified that “every shape has its own characteristics”: carrying the same diagonal and bottom-left shaded area through every form felt repetitive. Give each stage a construction relationship specific to its geometry; let its guides and shaded regions enter and leave with that relationship. The user subsequently said “love” about the sector, tangency, inset, and chamfer sequence and requested more visual impact. This endorses that sequence, not mandatory motifs for future drawings. The next experiment animates each construction and carries generating geometry between stages, then rests; that motion refinement is awaiting review. - -The user later rejected both dotted-guide animation experiments (marching dashes and progressive drawing); both were removed. They also disliked the rounded square’s inset breaking apart into chamfer cuts. That bridge was removed while retaining the inset construction within its own stage. The circle’s requested 45° radius must coincide exactly with the first hatch line, rather than run beside it. - -The user flagged gaps and overlapping strokes where measurement extensions meet construction guides, allowing caps or continuous lines. The response uses continuous shared guides, joins the unit-scale extensions, and excludes coincident grid strokes. Give each shared segment one stroke; avoid opacity changes caused by retracing it in separate layers. - -For the capsule, the user requested a 45° upper-left 2u radius and removal of the continuous line connecting the generating-circle centers. Keep that shared axis dashed, including during the circle-to-capsule transition. - -The user then said “love it” and requested a separate animation section. The refined loop is now the first example, M01 / Changing geometry, under Animations on `/ui/plotter`. P00 remains a static illustration in the gallery. Preserve manual pause and reduced-motion behavior; inline examples also pause while offscreen. - -When relating the forms to UI elements, the user questioned the chamfer’s role, was unconvinced by a tag metaphor, and then explicitly discarded a play-triangle trial. They requested a switch derived from the pill, or placed before it, then a rounded rectangle between the switch and square. The current sequence is Avatar → Pill → Switch → Button → Card, using those UI names in the drawing. One of the pill’s generating circles becomes the sliding switch thumb; its track then becomes the rounded rectangular button before turning into the square card. This revision is awaiting review. - -The user explicitly said “never a solid bg” after seeing the filled switch thumb. Keep illustrated forms transparent: no opaque fills to hide guides, no solid background patches, and no area tint. Construction lines remain visible through the thumb; line hatching can still describe a measured region. - -The user asked for consistent continuous secondary lines, using the pill’s diagonal radius as the reference after noticing that the card’s inner square looked different. In M01, use the shared secondary-line style (0.65 SVG units, 50% opacity, butt caps and miter joins) for continuous construction geometry, inset frames, dimensions, and their marks. Keep primary outlines and the faint grid/reference scaffolding in their separate visual roles. - -After committing the five-stage version, the user requested a slider at the end of the sequence. The new experiment compresses Card into a thin track, then moves a transparent thumb from 25% to 75%, before returning to Avatar. The six-stage sequence and slider treatment are awaiting review. - -The first Slider trial was weak: the user could barely see its dotted line and was not happy with the overall result. The revision makes the displacement the subject: a larger transparent thumb, a dashed starting circle, tangent guides between the start/end positions, a 4u travel dimension, and a measured percentage scale. Dashed guides use 38% opacity; coincident grid segments are excluded along their strokes so the gaps remain visible. This revised treatment is awaiting review. - -The user questioned whether the sector animation suited an avatar but said they liked it. After a suggestion to rename the stage Circle, they explicitly chose to leave it as is and commit. Preserve both the Avatar label and its sector construction. - -The user next requested an animation for the Particles page, specifically C03. They liked the top-to-bottom assembly concept but criticized the first trial’s unstable grid, vacant destination, and stretching elements. They found the subsequent centered exploded stack boring and explicitly asked to restore the original concept, suggesting two isolated grids like B03 and a lower block that starts with only a dashed border. Build bottom-up and separate top-down using clear side lanes, with one owner for each joined seam. Both grids remain stationary. - -The next feedback explicitly requests fully rounded A, B, and C in their initial positions and dashed outlines left behind when they depart. Keep fragments rigid at 3u × 1u during travel; flatten their shared corners only at contact. Reveal the 3u × 3u dimensions and A + B + C only after assembly, then widen the completed block, and toggle the switch later. This post-assembly enlargement is explicitly requested; it does not endorse stretching separate fragments in transit. The current trial expands to 6u × 3u around its center, preserving stroke widths, corner radii, text, and control sizes. Update the width annotation with the geometry; shrink before separation. Preserve pause, offscreen pause, and reduced-motion behavior in the Particles hero and Plotter preview. This revision is awaiting review. - -The user then asked to improve C03’s grid by avoiding lines that cut through the elements. They explicitly rejected masking or covering the existing lines: rework the grid geometry itself. The lower field’s half-cell vertical offset put horizontal strokes through row centers, making it look misplaced. Use fixed, intentional edge and row-alignment guides, aligned to the actual row boundaries and the composition’s common center. Leave unnecessary interior strokes out of the paths entirely; no animated grid masks or background patches. This grid revision is awaiting review. - -For C03’s three-assembly animation, the user wants the parts to become a new common shape. They rejected withdrawing whole borders and retaining independent boxes inside a new container. Exterior paths must form the silhouette themselves, with one owner for each shared divider. They then asked to improve the colliding-edge morph and explicitly rejected changing the movement: “i just wanted the colliding edge morph be better.” Preserve the original straight eased trajectories, travel-time resizing, stagger, receiver guides, and chapter pacing. Do not add curved docking paths or early enlargement to solve this detail. The current response separates straight edges from exterior corner arcs: paired corners retain their radius until contact, then flatten together over 0.22 seconds while the surviving edge becomes the secondary divider. Only the duplicate facing line feathers out over the last 0.08 seconds before contact; no whole fragment outline disappears. Keep the 0.9-second flights, 5.4-second chapters, 16.2-second loop, source ghosts, fixed grids, and later switch toggle. This edge-only revision awaits review and stays separate from the production hero. - -## Expanded subject brief - -The user explicitly requested a keyboard, browser window, table lamp, folder, smartphone, chat, and service concepts for Cloudflare, Vercel, Stripe, and Linear, then asked for more popular-service examples. These are requested exploration areas; only the specific feedback above establishes preference or approval. The expansion does not rehabilitate earlier rejected object drawings. Render familiar objects as flat plans or elevations with meaningful construction relationships. Preserve the established no-perspective rule. - -## Empty-state set - -The user asked for concepts, states, or objects that fit this style and are in high demand, and wanted advice. They chose all twelve suggested object-for-state pairings, static, at both hero and compact empty-state sizes: - -- search (no results) -- offline -- notifications -- files -- data -- access -- email -- maintenance -- disconnected integration -- location -- bookings -- image - -These are S03–S14 under Empty states. Each one originally added a 96px version shown in the coss `Empty` component in its preview dialog; the later native-size gallery feedback removes those application cards from display. The compact version reuses the hero geometry with non-scaling 1px strokes and no labels. All twelve remain outside the current approved reference set. - -When the user asked for an honest assessment, the assistant judged most of the set to be annotated pictograms. In those, the state lived in a caption rather than the geometry, and the compact versions read as generic outline icons. The user replied “ok improve them”. The four strongest were reworked using E02’s grammar: - -- **S04:** a route from this device, cut by break slashes, with a dashed ghost reaching a cloud of tangent circles. -- **S06:** an empty text area scaled on the page diagonal, holding only a cursor. -- **S11:** the measured gap is labeled as the state. -- **S12:** the pin is held above an empty dashed target. - -The reworked studies use two label tiers: semantic labels at 11 / 72% and measurements at 10 / 50%. Each compact version keeps one construction cue that survives at 96px: the break, the empty text area, the gap, or the target. Asked whether to cut, rework, or keep the remaining eight, the user chose to rework them one or two at a time for review. Two more have been reworked so far: - -- **S03:** a typed query above a dashed four-row results list, in the style of C03’s interface fragments. -- **S10:** two gears with matching teeth, their pitch circles 40 apart instead of tangent. - -At that point S05, S07–S09, S13, and S14 remained to be reworked; the reference-led refinement pass above now covers them. - -On S11, the user noted that drawings like these often use tiny arrows to show direction. They expected one pointing right along the dashed prong lines. Use small open arrowheads in the secondary-line style on a path or axis that implies movement. Place them within the gap or route, pointing toward the destination. Hero only: they vanish at 96px. - -The user then pointed to E02, C00, and P02 as well-executed arrow caps, and to C03 and S11 as inconsistent. Draw every cap the way those three do: an open 90° chevron, each leg about 6 long at 45° to its shaft. Put it in the same group and opacity as the shaft, with the tip exactly on the end of a drawn line. On a 45° shaft the legs are axis-aligned (`m-6 0h6v-6`). On an axis-aligned shaft they offset ±4.24 on both axes. On other angles, rotate the reversed shaft direction by ±45°. On a dashed shaft, start the path at the tip so a dash, not a gap, meets the cap, or place the tip at the end of a dash. - -## Technical rigor and the October 25 expansion - -The user requested a less projecting female socket in S11, improved gears in S10, a third 404 animation, and GPU, circuit, production-chain, and Newton’s cradle studies. Their review of the first expansion is explicit: - -- **W05:** wanted a metaphor for an assembly line, not isolated fabrication steps. -- **W04:** needs a meaningful underlying grid. -- **O06:** too much cardboard-like detail, no grid, and weak fit with the established style. The construction relationship needs to carry the subject. -- **O07:** nice, but not fully convincing; refine without treating this as approval. -- **S11:** the female connector is a distinct component, not the wall itself. Keep a restrained mounted receptacle, avoiding the earlier oversized protruding housing. -- **S10:** the tooth shapes look bad and there are too many teeth. Mathematical gear detail alone did not satisfy the visual direction; use fewer, better-shaped teeth and clearer placement. -- **M03:** replace the disconnected-plug animation with **S01**, the missing destination. This replaces the earlier animation subject; it does not change the production 404. - -These revisions are work for review and do not expand the approved reference set. - -The user also asked for an exact style definition, standardized line and hatch meanings, and a prompt for technical verification. The resulting [drafting standard](../drafting-standard.md) names the style monochrome orthographic construction diagrams. The [verification prompt](../verification-prompt.md) separates mathematical, semantic, conventional, and visual evidence. Calculations support bounded claims; conceptual service drawings do not become certified engineering drawings through appearance alone. Preserve the earlier explicit arrow-cap geometry when normalizing line roles. - -**coss.com scope:** The user explicitly said not to push anything to coss.com and wants to see illustrations here. Show the proposals in the local Plotter showcase at `#coss-concepts`; do not publish, deploy, or push the website changes. Product research uses the actual `cosscom/coss` source, not this UI repository’s older `apps/www`. The subject is a shared SDK, API key, and operational contract, documented in [coss product concepts](coss-product-concepts.md). This is a brief for proposals, not permission to rewrite product claims or an approved visual anchor. - -## Rejected coss concepts and the next O06 revision - -The user explicitly rejected the first seven coss.com proposals as poor quality and below the other illustrations. Their presence in a technically checked source audit did not establish visual quality. Those seven compositions are superseded by a smaller, new exploration; neither new alternative is an approved reference. - -Our diagnosis: the product icons and shared bus explained the catalog but lacked the central geometric construction of P00, B03, B04, and C01. The response tests a common aperture assembled from different service pieces and a complementary curved interface between two regions. These are metaphors for a common product contract, not representations of infrastructure or manufactured parts. Review the composition before expanding the set again. - -The user called the nine-box **O06** “bland”, then rejected the selected-group/5× compute detail too: “still don’t like o06 i want something that reminds me to a cardboard with a cpu”. We interpret “cardboard” here as a circuit board carrying a CPU. The next CPU-board version supplied a recognizable central processor, regular pins, and routed traces, but the user then asked to remove the outer card and mounting holes, add dashed lines, and reduce crowding. The current response keeps the CPU recognition cues in an open construction field: no board enclosure, no lower contact bank, two I/O routes and two memory routes, more space before the memory package, and dashed center axes with a defined alignment role. This supersedes our inference that an abstract compute-group relationship was the right subject. Keep the blueprint hierarchy and meaningful grid, but do not remove the requested physical recognition cues in pursuit of abstraction. This open processor composition is our response, not an approved reference or a functional circuit. Do not reintroduce an enclosing card or dense peripheral detail into O06 without a new request. - -## W05 and O07 motion experiments - -For W05, the user subsequently requested faster box delivery before the drop, then asked to keep improving it. The feed retains the faster 0.70s travel, but now approaches while the conveyor is still indexing: feed 1.00–1.70s, indexing ends at 1.590269s, and the next drop begins at 1.84s. The 1.8s cycle removes the earlier nearly sequential delivery wait while retaining the fall/contact behavior. Faint fixed feed guides explain the horizontal approach; they clear the core by 4 units and end 8 units before the drop window. These are implementation decisions awaiting user review, not new approved motion references. - -The user separately said O07’s easing still did not look realistic. An initial 0.30 m timing calibration shortened the cycle to 1.113268s, but the user then supplied [this cradle video](https://www.youtube.com/watch?v=09vzFodz4SI). Inspection of the opening swings and stepped frames around 15–17.64s showed a slower, broader motion with crisp contact. The 30 cm assumption was superseded: that trial used an approximately reference-matched 2.4s cycle and 30° release, retaining the nonlinear pendulum curve and instantaneous transfer. These are visual estimates from the video, not measured physical specifications. The reference supplies motion direction while the established flat drawing style remains. The user then asked to speed it up just a little without changing the easing: the cycle first shortened to 2.2s, then to 2.0s after a further speed request, with identical normalized key times, spline controls, and 30° swing geometry. - -The next O07 request adds subtle movement to the three middle balls, like the video. The response is a shared ±0.75° sway (about 2.3 SVG units horizontally), following the same signed pendulum phase. The resting end follows that group to preserve tangency; the active end retains its existing swing, easing, and 2.0s timing. Keep the middle balls synchronized rather than introducing a delayed wave, and keep the radius leader and center mark attached to the moving center ball. This bounded motion approximation awaits user review; it is not a measured reconstruction of the video or a contact simulation. - -The user then requested stronger slowdown near the outer ball’s highest point, with immediate departure from impact and a fast return. The next revision preserves the 2.0s cadence and both swing amplitudes but smoothly redistributes time within each quarter-flight: more time near the turn, less near contact. It adds no stationary hold. The timing accent intentionally departs from the unmodified pendulum curve; keep that distinction explicit in technical claims. The shared middle sway follows the revised phase so the contact geometry remains coherent. - -The user requested animations for W05 (assembly line) and O07 (Newton’s cradle), then said both “feel slow and lack physics” and do not feel natural. They remain separate examples in the Animations section, with the static gallery drawings retained. The revised direction is a brisk assembly cycle with an accelerating drop, restrained contact response, and conveyor acceleration/deceleration; the cradle should accelerate into contact, transfer motion immediately, and slow naturally at its turning points. The user liked the faster revisions but said they were still not fully natural and W05 remained a bit slow. The next pass specifically reduced idle handoffs, restrained the insertion rebound, smoothed motor acceleration, and tightened the cradle’s arc and turnarounds. Shortening a loop alone is insufficient if every movement still uses generic easing. Existing direction still applies: transparent forms, stable construction guides, rigid moving parts, and careful shared-edge ownership. These are requested experiments, not approved motion references or full physical simulations. - -## Native-size gallery - -The user asked that the gallery SVGs not be scaled down and said enlargement dialogs were unnecessary. Main drawings now render at 560×440 CSS pixels in the gallery, with enough room per column and local horizontal scrolling on narrow screens. Descriptions stay visible inline. The user subsequently asked to remove the extra “Page not found”, “No results found”, “No notifications”, and similar application cards, so the compact 96×96 previews are no longer rendered in the gallery. Existing variant URLs locate the appropriate card instead of opening a dialog. This presentation change does not alter the drawing geometry or promote new style references. - -## Working interpretations - -These diagnoses come from examining the drawings, not from more specific user quotations: - -- W02’s cards, checkmark, and arrows gave it the grammar of a flowchart. Constructing the route itself made the drafting language more coherent. -- Flatness alone is insufficient: I02’s complete screen and S02’s oversized success pictogram also fell outside the requested set. -- The main geometry should carry the idea; adding technical marks to a weak subject does not make it fit. -- Perspective belongs to the represented object, not every diagonal mark. Radius lines and annotation leaders remain useful. -- For O03, interpreting “show a portion” as an intentional detail crop resolves the earlier ambiguous miniature keyboard. The user asked for a portion and subdued/dashed lines; credible stagger and modifier widths are our implementation response. -- Service metaphors can be conceptually clear without illustrating every product. Accuracy concerns the relationship depicted and its stated scope. In the Vercel study, we diagnosed the expanding arcs as too suggestive of broadcasting; the user requested improvement after that explanation. The selected-preview construction was our response and was later explicitly included in the approved reference set. - -## Subject guidance - -Use these as starting points, not approved concepts or mandatory motifs: - -- **Primitives:** fundamental shape relationships, tangency, radius, spacing, repeated units. -- **Particles/interfaces:** a small family of reusable fragments with visible composition rules. Keep the construction relationship legible without building an entire application screen. The current browser response uses an enlarged chrome detail instead of a miniature complete window; this is our interpretation of the keyboard comparison. For the chat study, the user specifically requested avatars and removal of triangular tails. -- **Cal.com:** a labeled weekly grid, interval composition, or named availability intersection. Distinguish abstract intersection from a literal time plot; only assign time values to an axis when the geometry supports that interpretation. -- **Workflows:** measured planar routes or switching/connection structures. The routing itself should be the visual subject. -- **Objects:** when showing a detail, preserve the object’s identifying geometry and make the crop deliberate with open edges or quiet dashed continuation. A keyboard detail should have credible key rows and modifiers. Use subdued construction lines; a crop should read as part of a larger system. Multiple folders can share a flat construction rule without implying stacked depth. -- **Services:** begin with one accurate product role or relationship, then translate it into a conceptual construction. Use B04 Linear as a reference for this balance. Check the chosen role against official product documentation and identify the scope when a service is broad. Depicting one real capability is sufficient; the drawing need not cover every company feature. Keep metaphoric geometry distinct from a literal architecture claim. -- **404/empty states:** an interrupted alignment or unresolved planar route can communicate absence. The revised E02 interrupted path is explicitly selected for the 404 page; E04 was removed. A currently open doorway URL is not approval evidence. - -Other categories remain open. Translate their subject into a flat construction relationship, then review the result against the anchors rather than assuming every object works in this style. - -## Callout leaders in the visual grammar - -The user pointed out that the “Quarter turn” annotation in Movement and transfer arrows still lacked its own grammar entry. The guide now includes **Callout leaders and labels**, reusing that construction and isolating only the bent solid leader and its text. Keep callouts separate from movement arrows, dimension marks, and hidden outlines: the leader connects a named feature to its label. Preserve both marks’ original color, opacity, and weight during isolation. - -## M04 orbits motion study - -The user asked for a Plotter animation of planets orbiting to show their different speeds, with the sun at the center and only three planets. Their review of the first version was: “looks poor. no diagonal lines on the sun. level of detail is sparse, use more elements from the visual grammar, make it look stunning and interesting.” Do not hatch the sun; keep three planets but give the drawing real drafting content. - -M04 (Nature / “Three orbits, three speeds”) in `orbits-motion-drawing.tsx` is the revision. The cycle is 12s: planets complete 4, 2 and 1 orbits (3s, 6s, 12s), counter-clockwise from one start axis, and realign when the loop restarts. Orbit radii follow T² ∝ r³. Marks and the relationship each explains: a rotating generating radius per planet shows angular speed; a 24-division angular scale with a dashed `4 6` travel arrow gives direction and position; dashed `3 5` start outlines mark where the planets leave and return; the outer orbit’s ⌀ dimension and the T² ∝ r³ note tie spacing to period; a legend keys planet size to period; the sun uses concentric rings. Guides and the dimension sit outside the planets’ swept bands. These are implementation decisions awaiting review, not an approved motion reference. - -After the rayed, continuous-circle version the user said: “no sun rays. shouldn’t the orbit be represented by a specific element in the visual grammar?” Orbits are loci: draw them with the centerline pattern (`8 3 1 3`), not continuous circles, and give the sun no rays. An earlier experiment had replaced the circular orbits with real Keplerian orbits of Mercury, Earth, the Moon and Mars (Sun at a focus, dash-dot loci, dated to 31 October 2026) and removed the sun rays, ring and ticks. The user reviewed it and said “don’t like”, then asked to return to the version above. Treat that real-orbit direction as set aside, not as a preference for the rayed sun or continuous circles; the reason was not stated. - -## Shared primary stroke — 2026-11-01 - -On the customization page, the user requested “make it 1, don’t want to see weird artifact on monitors” after discussing the shared primary stroke of 0.95. The shared standard now uses 1 SVG unit for primary outlines. This sets width; pixel alignment and display scaling still affect rasterization. Other role widths and existing unmarked drawings keep their authored treatment. - -## Uniform stroke defaults — 2026-11-01 - -The user then asked whether all strokes should be 1px and approved setting all five shared stroke defaults to 1, keeping opacity differences for hierarchy. This supersedes the primary-only change above. Primary, secondary, guide, hatch, and section widths now share that default; their opacity values and dash patterns are unchanged. - -## Catalogue-wide stroke consistency — 2026-11-01 - -After the shared token defaults changed, the user asked whether the other illustrations had also been updated. The active catalogue, animations, and live grammar drawings now use 1-unit visible strokes. Geometry, opacity grouping, dash patterns, and animation timing are preserved; the assembly’s stroke-width transition is removed so contact changes opacity without changing line weight. Invisible mask clearances and frozen reference snapshots retain their authored widths. This expands the width change beyond the five role-token drawings without migrating the remaining drawings to shared roles. - -## Opacity after the 1-unit stroke change — 2026-11-01 - -The user asked to reduce opacity after the uniform-width change so the drawings retain a similar visual weight. Shared secondary, guide, grid, hatch, and hidden opacities are reduced; primary forms remain strong. Legacy strokes are compensated using their original width, through stroke-specific opacity so filled labels and surfaces keep their contrast. Original group opacity and playback fades remain in place; nested stroke-opacity boundaries reset inherited compensation rather than multiplying it. The assembly contact transition now changes stroke opacity at the original contact times while width stays 1. The prior thin-stroke appearance is a visual target, not a claim of identical rasterization. - -The user then set the shared hidden-line opacity to `0.32`. Hidden, absent, and proposed outlines share this token. - -## Fills and catalogue consistency — 2026-11-01 - -The user requested removal of several background fills, then reported exposed lines and asked for a review of all illustrations: “While some exceptions sometimes are allowed, we should make sure that they try to be consistent in general.” Earlier, they asked whether the occasionally shaded region should become a documented story element with a CSS token. - -Our interpretation is now recorded in the [fill and line-clearance rule](../drafting-standard.md#fills-and-line-clearance): transparent ordinary forms, named semantic highlights, geometric clearance for labels and open nodes, and explicit exceptions for useful construction. This is the implementation response to the request, not user approval of every revised drawing. The [catalogue review](catalogue-consistency-2026-11-01.md) records coverage, local decisions, and verification limits. Highlights in TIM-01/03/05 share a fill-opacity token; former decorative whole-form tints are removed. - -## Responsive illustration presentation — 2026-11-01 - -The user requested: “on mobile scale the illustrations if necessary.” This supersedes the earlier website convention of keeping all drawings at native size with horizontal scrolling. Website illustrations now preserve their authored viewBox and aspect ratio, scale down to fit the available container, and stop growing at their native 560px width. The same presentation rule covers grammar, motion, customization, docs previews, and standalone animation examples. This changes presentation, not the drawing geometry or animation timeline. diff --git a/skills/plotter/references/history/examples/agent-registration-before.svg b/skills/plotter/references/history/examples/agent-registration-before.svg deleted file mode 100644 index 3a0150e..0000000 --- a/skills/plotter/references/history/examples/agent-registration-before.svg +++ /dev/null @@ -1,43 +0,0 @@ - - A place in the registry - An independent agent moves into a matching registry cell. Its circular identity mark and three capability marks stay the same; its new row is identified as agent_07. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Agent - Registry - agent_07 - - - agent_06 - agent_08 - Unlisted - Register - - diff --git a/skills/plotter/references/history/examples/agent-registration.md b/skills/plotter/references/history/examples/agent-registration.md deleted file mode 100644 index 9e79c5b..0000000 --- a/skills/plotter/references/history/examples/agent-registration.md +++ /dev/null @@ -1,43 +0,0 @@ -# Agent registration: failure and revision - -## Status and brief - -On 2026-10-31 the user rejected a 78-drawing batch as low quality and inconsistent with the established examples and rules. Agent registration was included in that collective rejection; it did not receive a separate verdict. The user authorized rebuilding this one subject against approved references and using the comparison to improve the skill before further expansion. - -- [Before](agent-registration-before.svg): preserved from the rejected batch. -- [Revision 2](agent-registration.svg): explicitly liked by the user on 2026-10-31: “i love it”. Preserve this visual revision. -- [C01](../../drawings/INT-02.svg): the approved assembly reference used for this revision. [C02](../../drawings/INT-03.svg) supplies allocation and spacing; [I06](../../drawings/INT-09.svg) supplies restrained identity fragments. - -The user’s response is positive evidence for this exact revision. The existing 27-reference selection remains unchanged. Use this case to understand the comparison and refinement process; assembly is not necessarily the right metaphor for every agent concept. - -## What failed - -The earlier drawing placed an 80-unit agent tile beside a three-row registry table, duplicated its small identity/capability marks in a row, and joined them with a labeled transfer arrow. Our diagnosis is that the marks and labels explained the subject more than the composition did. The table occupied more attention than the registration relationship. Correct stroke values did not make that arrangement fit the established work. - -The production process amplified the weakness: large batches were generated before a close reference comparison, and the final contact-sheet pass largely looked for conspicuous defects. The same generic node-and-connector tendency had already been rejected in earlier service proposals. That lesson needs to influence new concepts, not remain available only when revisiting an old study. - -## What the revision borrows - -| Decision | Approved evidence | Registration response | -| --- | --- | --- | -| Make assembly visible | C01 repeats the same fragments in separate and assembled states | Identity, name, and tools retain their geometry and horizontal positions in one registry record | -| Give the result enough presence | C01 has a substantial enclosing record; C02 organizes fragments within a shared allocation | A 336 × 96 record is the main form, with secondary guides outside and within its insets | -| Make spacing explain a relationship | C02's gaps and allocations relate real boundaries | A 24-unit inset/gap system allocates space to the identity, name, and tools | -| Keep recognition economical | I06 uses a small avatar and modest text fragments | One avatar, “Research agent,” and “Read”/“Search” labels establish the subject; an assigned example ID distinguishes the record | -| Preserve line roles | The drafting standard separates forms, detail, projection, and movement | Primary outer forms remain full-strength; face details, field baseline, projections, and assembly arrow use their respective subordinate styles | - -The same-size comparison prompted two refinements before presentation: reducing the initial 384-unit record to 336 units removed unused name-field space, and restoring primary strokes to the loose forms prevented them from reading as absent or disabled. A separate visual review prompted a clearer “Registered agent” label, stronger identifier text, and replacing the overall height dimension with the second equal allocation gap. These explanations are the assistants’ interpretation of the changes. The user subsequently liked the finished revision as a whole; they did not separately endorse each explanation as a general rule. - -## Meaning and bounds - -This is a conceptual illustration of assembling an indexed registry record from an agent definition. It does not specify an API, authentication, permission grants, persistence guarantees, or execution. The tools are descriptive capabilities in this example. A generic avatar supplies an identity cue, not a claim that the agent is a human. - -The local unit is `u = 24` SVG units. The horizontal allocation is `1u + 2u + 1u + 5u + 1u + 3u + 1u = 14u`, comprising inset, identity, gap, name, gap, tools, inset. The record is `14u × 4u`. The repeated fragments translate vertically by 148 units. The new identifier occupies the existing name allocation. Metadata in the editable SVG records the same mapping. - -No background grid is needed: the fragment projections already explain alignment. There is no hatch because no region needs an additional meaning. Do not add either merely to increase visual density. - -## How to use this evidence - -Render the approved reference, candidate, and rejected drawing at `560 × 440`, with a common font and surface. Compare the main form's presence, the relationship visible without the explanatory caption, and the purpose of each guide. Also inspect the thumbnail for loss of the central gesture. Return to the composition when those relationships are weak; do not repair them by adding decorative drafting marks. - -The revision has received a visual comparison, not a fresh-session skill evaluation or a technical certification. No test suite was requested for this pass. Keep the rejected originals separate from the catalogue’s later reference-led revisions. The positive response supports this one revision; explore other construction relationships in small groups before drawing conclusions about broader reliability. The subsequent request to add all revised subjects is recorded in [direction and feedback](../direction.md#liked-revisions-catalogue-expansion-and-mark-selection--2026-10-31). diff --git a/skills/plotter/references/history/examples/agent-registration.svg b/skills/plotter/references/history/examples/agent-registration.svg deleted file mode 100644 index 0d02642..0000000 --- a/skills/plotter/references/history/examples/agent-registration.svg +++ /dev/null @@ -1,71 +0,0 @@ - - An agent, registered - An identity, name, and two tools align into one registry record. The identity and tool shapes retain their sizes and horizontal positions. The record receives the example identifier agent_07. - Study: agent-registration, revision 2, explicitly liked by the user on 2026-10-31. Mode: conceptual diagram. Registration is represented as the assembly of one discoverable record from an agent definition; this does not depict authentication, permission grants, or execution. References: C01 assembly, C02 allocation, I06 identity fragments. Local unit u = 24 SVG units. Record width 14u = 336; height 4u = 96; horizontal allocation 1u inset + 2u identity + 1u gap + 5u name + 1u gap + 3u tools + 1u inset. Source and assembled fragments differ only by a vertical translation of 148 units. The assigned identifier is new text within the name allocation. No background grid or hatch is needed. - - - - - - - - - - - - - - - - - - - - - - Research agent - Read - Search - - - Identity - Name - Tools - - - - - - - - Registered agent - - - - - - - - - - - - - Research agent - Read - Search - - agent_07 - - - - - - - - - 14u - u - u - - diff --git a/skills/plotter/references/history/index.md b/skills/plotter/references/history/index.md deleted file mode 100644 index e6f9c69..0000000 --- a/skills/plotter/references/history/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# Historical evidence - -Read this material only when revisiting a named study, tracing a decision, or maintaining the skill from an observed failure. Current work starts with [direction](../direction.md), [grammar](../visual-grammar.md), and the [drafting standard](../drafting-standard.md). Old instructions describe their original scope and revision; later entries may supersede them. - -| Question | Evidence | -| --- | --- | -| What did the user say about a particular drawing or motion revision? | Search its ID in [direction and feedback](direction.md). Distinguish quoted preferences from the assistant's interpretation and proposed response. | -| What was excluded from the reference selection, and how was that interpreted? | [Reference-selection evidence](reference-selection.md). The current index retains all 27 selections and seven bundled snapshots. | -| Why did the registration batch fail, and what changed? | [Registration failure and revision](examples/agent-registration.md), with both editable SVGs. | -| A record cites an older code such as P00, K09, or AG01. | [Code map](code-map.md): former and current codes, and the drawings retired on 2026-11-01. | -| What was technically inspected at the October 25 snapshot? | [Source audit](source-audit.md) and [remaining-source audit](remaining-source-audit.md). These are revision-specific results, not current certification. | -| Why are forms transparent, and which highlights or crossing guides are intentional? | [Catalogue consistency review — 2026-11-01](catalogue-consistency-2026-11-01.md), covering all 100 drawings, compact variants, grammar, and sampled motion. | -| Why does the motion workflow focus on staging and timing rather than player controls? | [Motion workflow revision — 2026-11-01](motion-workflow-2026-11-01.md), with a bounded fresh-run pilot and its limitations. | -| What did the coss.com proposals claim at that time? | [Product concepts](coss-product-concepts.md). Re-establish current product facts before reusing their claims. | - -These records describe the historical coss host. The bundled evidence can be read independently. Repository commits, routes, and evaluation directories mentioned inside it are provenance, not active standalone paths or required resources for the portable workflows. The seven SVG composition anchors remain available in the [reference index](../approved-references.md). - -## Maintaining the record - -When maintaining Plotter, append useful feedback with the study/revision, date, user's preference, and any interpretation clearly distinguished. Preserve contradictory or superseded entries as evidence instead of quietly rewriting them into approval. Summarize a durable rule in its current authoritative document only when the feedback supports that scope. - -A liked illustration, catalogue addition, or successful rendering does not establish a new reference selection or a reliable skill. Record what was actually inspected. Future evaluations can use the packaged workflows and examples; this reorganization does not claim a new clean-install or behavioral evaluation. diff --git a/skills/plotter/references/history/motion-workflow-2026-11-01.md b/skills/plotter/references/history/motion-workflow-2026-11-01.md deleted file mode 100644 index fd39caa..0000000 --- a/skills/plotter/references/history/motion-workflow-2026-11-01.md +++ /dev/null @@ -1,25 +0,0 @@ -# Motion workflow revision — 2026-11-01 - -## Feedback and change - -The user questioned whether the animation skill worked, specifically calling out the prompt requirements “Include pause/resume, replay, a static mode, and a reduced-motion still” and “Deliver editable animation HTML with its required local resources” as unrelated. The user agreed to revise the workflow and test it. - -Interpretation: the skill emphasized delivery mechanics more than choosing and shaping the movement. The revised [workflow](../motion.md) prioritizes the relationship, staging, significant events, speed, holds, return meaning, and observation. Playback and packaging now follow the requested destination. Reduced-motion and readable fallback behavior remain implementation requirements; they are not the brief’s creative focus. - -Three existing animations became [annotated teaching examples](../motion-examples.md): assembly, Newton’s cradle, and orbits. The portable gallery is generated from their current sources. This does not expand the approved reference selection. The user's separate request to feature Newton’s cradle in the homepage header establishes that placement preference only. - -## Fresh-run pilot - -Three existing drawings received identical briefs with and without the revised full skill, in six fresh agents with no conversation history. The inputs were INT-02, SYS-02, and GEO-03. A separate reviewer received anonymous A/B copies, the inputs, and briefs. It inspected source and sampled poses without author notes. Delivery format, fallback, and seek requirements were common to both conditions and do not count as benefits from the skill. - -- Assembly gained cleaner placement but added an unnecessarily large whole-scene restart. The control kept the carrier fixed and reversed the parts, with busier intermediate linework. -- Routing used continuous travel and fewer effects with the skill, but its request marker could still merge visually with a junction. The control emphasized processing and arrival more explicitly. -- Both geometry runs preserved the fixed center and 24-unit offset. Measurement attachment, numeric readability, annotation motion, and timing involved tradeoffs. - -The assembly finding prompted a narrow correction: an exploded/assembled comparison can reverse meaningfully; do not invent another mechanism or scene transition just to avoid reversal. A seventh fresh run with that correction kept the carrier fixed and reversed the parts. This is evidence of the specific decision changing once, not general reliability. - -## Scope of the evidence - -The briefs, input SVGs, raw outputs, author notes, instruction snapshots, hashes, independent review, and comparison viewer are [archived in Git history at commit `d0041c3`](https://github.com/pasqualevitiello/plotter/tree/d0041c36bb7e5a2888914605db1f268b7a202732/evaluations/motion-2026-11-01). The experiment folder was removed from the current checkout on 2026-11-08; the findings above remain as historical evidence. Those raw artifacts are outside the portable skill package and are not required to use Plotter. - -Review used source, sampled browser poses, and focused runtime/geometry checks. Continuous normal-speed playback was not visually watched, and exact host-font metrics were not verified in the pilot. The sample used one model/settings combination and one run per case/condition, plus the follow-up. It did not compare the prior workflow as a third condition or isolate the new motion text from the shared static guidance. No output was promoted to the catalogue or approved reference set. diff --git a/skills/plotter/references/history/reference-selection.md b/skills/plotter/references/history/reference-selection.md deleted file mode 100644 index 5c051a1..0000000 --- a/skills/plotter/references/history/reference-selection.md +++ /dev/null @@ -1,21 +0,0 @@ -# Reference-selection evidence - -The current selected compositions and bundled snapshots are listed in the [approved reference index](../approved-references.md). These notes preserve the scope and interpretations of the original decision; they are not additional current drawing instructions. - -## Scope of the decision - -The user said the remaining illustrations do not look perfect or do not fit the style for different reasons, and could not yet identify those reasons. Treat them as revision candidates, not style references. This feedback does not request their deletion or establish a specific diagnosis for each drawing. - -At the time of the selection, the omitted static drawings were C00, C03, P01, K03, I04, I05, W02, O03, O04, O05, B08, S01, and S03–S14. In particular, original Particles/C00 is now a historical reference; C03’s production placement is a separate implementation decision. Preserve the user’s specific earlier feedback on details without promoting the whole drawing. This static selection does not revoke the separately reviewed animation work. The later C04, K09, and S15 experiments were liked and requested for the catalog; they are not additions to this 27-reference selection. - -## Working interpretation - -These are hypotheses from comparing the selected drawings with the remaining studies, not additional user-stated rules: - -- **Make a construction relationship the subject.** P00 relates circle and square; C01/I03 assemble parts; B04 aligns work to a cycle; B07 demonstrates constraints. Recognizability and technical annotations alone have been less reliable, as in the lamp, phone, and browser studies. -- **Give the composition a focal point.** K06 selects an interval, W03 selects a junction, and E00 leaves one quadrant unresolved. O05’s equally weighted folders and B08’s repeated blocks offer a less distinct central event. -- **Use measurements to explain the main idea.** P03’s progression and K07’s interval lengths support their composition. Multiple unrelated product dimensions can scatter attention, as in O04’s shade, stem, base, and overall height. -- **Spend detail on the organizing rule.** I06 reduces conversation to avatars, tail-free message blocks, and spacing. O03/I04 devote more attention to keyboard legends and browser chrome. A keyboard or browser remains a possible subject; simplify the representation around one useful relationship. -- **Make absence affect the structure.** E00’s missing corner, E02’s interrupted route, and E06’s absent keystone visibly change the construction. This is a more dependable starting point than selecting an empty-state icon and surrounding it with measurements. - -Do not force every omission into one explanation. P01 is close to the established geometric language; its weaker fit may concern composition or distinctiveness. Some newer empty-state drawings already contain structural ideas. T01/T02 and E01 show that recognizable forms can be successful. Evaluate the specific drawing against the closest approved reference instead of banning a subject category. diff --git a/skills/plotter/references/history/remaining-source-audit.md b/skills/plotter/references/history/remaining-source-audit.md deleted file mode 100644 index 245dd63..0000000 --- a/skills/plotter/references/history/remaining-source-audit.md +++ /dev/null @@ -1,91 +0,0 @@ -# Remaining Plotter source audit - -Historical evidence for the named revisions. Use the [current instructions](../../SKILL.md) for new work; these findings and product claims need fresh evidence before being applied to a later revision. - -Bounded source pass on 2026-10-25. This supplements [source-audit.md](source-audit.md); it is not rendered acceptance, a mechanical certification, or approval of every inspected drawing. The 43 studies below received a source reading focused on their principal dimensions, circle/arc relationships, interval alignment, and annotation meaning. Together with the separate audit’s 12 studies, this covered the principal static construction of all 55 registered studies at that snapshot. Later revisions require fresh checks of affected claims. The revised shared S01/M03 component has since received fresh source, geometry, marker-clearance, and limited browser checks in [source-audit.md](source-audit.md). Those named checks supersede the earlier S01 source snapshot; the broader static inventory does not verify other animations. Individual successful checks do not certify every path in a drawing. - -## Concrete findings and corrections - -| Study | Evidence | Outcome | -| --- | --- | --- | -| **E01 / `404-doorway`** | In `app/plotter/not-found-architecture-studies.tsx`, the radius leader formerly ran from `(208,248)` to `(296,160)`: length `124.45079349`, despite the swing arc having `R128` and the label `r = 4u`. It missed the arc by `3.54920651`. | **Corrected only the leader endpoint.** It now derives `(208 + 128/√2, 248 − 128/√2) = (298.50966799,157.49033201)`. The represented doorway, swing arc, label, and cap geometry are unchanged. | -| **E06 / `404-unbuilt-arch`** | In `app/plotter/not-found-geometry-studies.tsx`, the R126 leader started at `(208,176)` and the R90 leader at `(349,216)`. Their nominal-center radius residuals were `+0.49110641` and `+4.11163584`. Because the approved arch endpoints are rounded, its serialized SVG arcs have centers `(279.99998991,280.05043350)` and `(280.00000072,279.98863831)`, rather than precisely `(280,280)`. Residuals against those actual arcs were `+0.53256995` and `+4.10390924`. | **Corrected only the two leader attachment points.** They are now `(208.303044749,176.437943637)` and `(345.990882349,218.790570189)`, projected onto the existing SVG arcs. Incidence error is below `10⁻⁹` units. The approved arch paths are unchanged; these corrections do not claim that their rounded endpoints have become an exact concentric construction. | -| **T01 / `type-letter`** | In `app/plotter/object-studies.tsx`, the counter is drawn with cubic Béziers. Its upper-left quarter meets the 45° ray at `(222.25,176.25)` with radius `61.87184335` about `(266,220)`. The `r` leader ends at `(222,176)`, missing the actual outline by `0.35355339`. The counter’s cardinal radius is `62`, so it is also an approximation to a circle. | **Unchanged; needs a deliberate choice.** Preserve the letterform and call the annotation a construction radius/approximation, or replace the intended circular counter with true `R62` arcs and derive the leader endpoint. Do not silently rewrite an approved type drawing. | - -The E01/E06 edits are narrow incidence corrections, not a restyle. Browser inspection of those annotations remains part of the parent review. - -For T01, the smallest proposed wording change is `r ≈ 62`, which acknowledges an approximate nominal radius while preserving the approved cubic letterform. Re-anchoring its leader to the actual curve at `(222.25,176.25)` would be a separate small incidence correction. Neither change was applied as part of this audit. - -## Selected checks that passed - -- **P01:** the common tangent is within `0.00183` units of the R80 circle and `0.000007` units of the R40 circle. Both circles share the baseline at `y=324`. -- **P02/P03:** the corner’s offset is `104 − 80 = 24`; the proportion study uses widths `36,54,81,121.5`, each multiplied by `1.5`, on a shared baseline. Its indicated slope is `1/2`. -- **K02/K03/K06/K07/K08:** the selected overlap, one-hour UTC/UTC+03 booking, Thursday 10:00–11:00 cell, 15 + 15 = 30 minute construction, and `6u × 4u` availability extents agree with the displayed geometry. K07’s R28 leader rounding residual is approximately `0.00143`. -- **I03/I04/I05/I06:** the inspected insets, browser R24/R12 fillets, phone’s concentric R32/R24 corners and eight-unit offset, safe-area margins, and conversation spacing agree with the dimensions. The phone has `u=16`, total width `10u`, and horizontal margins `1.5u + 7u + 1.5u`. -- **W02/W03/A03:** branch bends are R24 with outlets separated by `4r`; the switch matrix uses 64-unit pitch; the coordinate datum at `(120,328)` and selected point `(312,168)` give `(6u,5u)` with `u=32`. -- **O03/O04/O05:** keyboard pitch is 72 and stagger is 18 (`¼u`); the lamp’s generating circle is R96; both folder tabs measure 64 while the bodies measure 216 and 136. -- **B06/B07/B09:** the inspected branch fillets, 176-to-264 resize with constant 56 height, and 132-wide relation tables with 32-unit rows agree with their labels. This checks diagram geometry, not every claim about the external products. -- **S01/S03/S05/S06/S07/S08/S09/S12/S13/S14:** checked relationships include 16-wide paired routes, the missing 56-wide index record, 64-pitch notification positions, a `200 × 200√2` page and `u + 3u + u` writing margins, 48-unit plot intervals, concentric R40/R24 lock arcs, the flap reflected from `y=88` to `y=248` about `y=168`, the pin’s near-tangent serialized sides, seven 40-wide day columns, and the 240:180 image frame ratio. -- **E00/E02/T02:** the missing-corner dimensions use `u=40`; the interrupted route uses concentric R52/R60/R68 bends with a 16-unit band; the C mark uses R114/R78 arcs and a 90° opening. These checks retain the qualified rounding tolerance; they are not symbolic proofs for every serialized coordinate. - -## Final five static studies - -This follow-up closes the five source-reading gaps from the first addendum. It does not change the C03 animation or other motion sources. - -| Study and source | Principal checks | Qualification / outcome | -| --- | --- | --- | -| **C00 / `particles-reference`**, `app/plotter/original-particles-blueprint.tsx` | Shared inset `188 − 164 = 24 = u`; row width `404 − 164 = 240 = 10u`; R16 leader residual `−0.005245`; switch track `30 × 18`, R9, thumb R5.5, right/top/bottom insets `3.5`. | Checked geometry passes. Historical line opacity/dash choices remain outside the newer normalized house roles; this pass does not restyle them. | -| **C03 / `particles-recombination`**, static `app/plotter/particles-blueprint.tsx` | Three fragments are `144 × 48`; the assembled panel is `144 × 144 = 3u × 3u` with `u=48`. Dividers at `y=208,256` split `y=160…304` into three equal rows. Source and target content share relative coordinates. R16 transfer bends are tangent to their straight segments. Arrow tips `(320,184/232/280)` meet the starting dash; 4.24-offset shoulders produce approximately 6-unit, 45° legs. Switch geometry matches C00/C02. | Static construction passes the inspected relationships. The distinct animation and its sampled cubic transitions were not audited or edited here. The static arrows retain legacy `4 5` dashes and `0.36` opacity; that is a future semantic-style normalization item, not a dimensional failure. | -| **B05 / `service-stripe-payment`**, `app/plotter/service-studies.tsx` | Input pills are 112 wide (`2u`); checkout pill is 56 wide (`u`); all have 32 height/R16 ends. Selected route’s two R16 bends meet straight segments tangentially. Radius leader residual `−0.019387`. Wallet/bank alternatives join the shared route at its final horizontal segment. | Geometry passes. Keep the illustrated Card → `$24 · Paid` outcome scoped to a completed successful payment. Do not imply all bank methods settle immediately or that checkout completion itself proves payment success. Stripe distinguishes session `complete` from `payment_status=paid`, and states that processing may continue after completion. [Checkout Session reference](https://docs.stripe.com/api/checkout/sessions/object). | -| **B08 / `service-notion-blocks`**, `app/plotter/popular-service-studies.tsx` | Incoming block and absent slot both measure `200 × 40`; width `5u` gives `u=40`. Page has 20-unit horizontal margins, 16-unit top/bottom margins, and 8-unit gaps between rows. Both R24 route bends are tangent; arrow tip `(386,300)` meets the first dash and points toward the matching slot. | Checked geometry passes. This is a block-composition analogy, not a claim about an exact Notion screen, fixed block size, or API move operation. Notion identifies headings, paragraphs, and to-do content as block types, which supports this scoped analogy. [Notion block reference](https://developers.notion.com/reference/block). | -| **S04 / `state-offline`**, `CloudForm`, `CloudGap`, and `OfflineStudy` in `app/plotter/system-state-studies.tsx` | Paired route uses concentric R32/R48 bends around `(240,296)`, giving a 16-unit band and R40 centerline. Gap `268 − 236 = 32`. R40 leader residual `−0.006040`. Cloud lobe seam residuals against the intended R30/R48/R36 generating circles are all below `0.006607`; their nominal bottom tangencies share `y=200`. | Checked construction passes the serialization tolerance. Adjacent cloud lobes intentionally intersect; they are not mutually tangent fillets. Offline/sync wording is illustrative empty-state copy, not verification of application connectivity or storage behavior. | - -## Coverage inventory - -These 43 codes and IDs were included in this bounded source reading: - -| Codes | Study IDs | -| --- | --- | -| P01, P02, P03 | `primitives-tangency`, `primitives-radius`, `primitives-proportion` | -| C00, C01, C03 | `particles-reference`, `particles-assembly`, `particles-recombination` | -| K02, K03, K06, K07, K08 | `cal-availability`, `cal-time-zones`, `cal-week-grid`, `cal-time-modules`, `cal-availability-plan` | -| I03, I04, I05, I06 | `interface-spacing-plan`, `interface-browser-plan`, `interface-phone-plan`, `interface-chat-plan` | -| W02, W03, A03 | `workflow-branch`, `workflow-switch-plan`, `data-coordinate-plan` | -| O03, O04, O05 | `object-keyboard-plan`, `object-lamp-elevation`, `object-folder-plan` | -| B05, B06, B07, B08, B09 | `service-stripe-payment`, `service-github-merge`, `service-figma-constraints`, `service-notion-blocks`, `service-supabase-relations` | -| T01, T02 | `type-letter`, `type-monogram` | -| S01, S03, S04, S05, S06, S07 | `state-missing-page`, `state-search`, `state-offline`, `state-notifications`, `state-files`, `state-data` | -| S08, S09, S12, S13, S14 | `state-access`, `state-email`, `state-location`, `state-bookings`, `state-image` | -| E00, E01, E02, E06 | `404-reference`, `404-doorway`, `404-interrupted-path`, `404-unbuilt-arch` | - -The separate audit covers **P00, C02, B01, B02, B03, B04, S10, S11, O06, W04, W05, O07**. Its own findings and limitations still apply. - -No registered static study remains outside the combined source-reading inventory. This means coverage of each principal construction, not exhaustive proof of all serialized paths, a pass on every legacy fill/line role, or visual approval. Compact variants were read when they shared the inspected geometry, but were not independently rendered here. Motion sequences remain outside this static addendum; the main audit separately records the bounded M03 checks. - -## Transparency scan across all 55 studies - -At the original source snapshot, all 55 registered hero drawings successfully rendered to SVG for an automated inherited-fill scan. The later S01/S10/S11/engineering revisions were source-read for fills; they add no area patch or background fill (the RC junction retains its semantic foreground dot). The full 55-drawing automated scan was not repeated after those revisions. The scan excluded text and did not flag ordinary `currentColor` semantic dots. It identified background-token fills or translucent area tints in **26 studies**: - -`P00, P02, P03, C01, C02, K02, K06, K07, K08, I06, W03, A03, B01, B02, B03, B04, B05, B06, B07, B09, T01, T02, E00, E01, E02, E06`. - -Those surviving fills conflict with the newer transparent-form direction. The count is a mechanical inventory, not permission for a blanket deletion: some currently conceal continuous guides or wires, so each affected composition needs its paths inspected when the fill is removed. This pass did not replace fills with another patch, normalize historical line roles, or change approved composition geometry. - -## Checked source snapshots - -SHA-256 after the narrow E01/E06 corrections; the S10-containing source and engineering source hashes below were refreshed after their separately documented re-review. The new shared S01 and M03 hashes are in the main audit. - -| File | Hash | -| --- | --- | -| `app/plotter/not-found-architecture-studies.tsx` | `cddb10767627b6d07aab10548b1b51cdbd1b0540bb5cb33d697a8df013f51fe7` | -| `app/plotter/not-found-geometry-studies.tsx` | `f9760542d6d79088bd33aa64af1d14ac60abc1a7b735dd4bae1f8fea87207e71` | -| `app/plotter/object-studies.tsx` | `c59c5a103b7c1e399d5c1c94003acd6e3a29b56ebe5ee5a8989ce0bb200a7e30` | -| `app/plotter/engineering-studies.tsx` | `0c2ef29222c874e1777fb62fc0dd3059b683deebbbf2caf1e50420ba30b922b2` | -| `app/plotter/original-particles-blueprint.tsx` | `085026c3b3843bb2ab144e1fe147533e5af48587673e1f94cc4e8d1c0bd31cdc` | -| `app/plotter/particles-blueprint.tsx` | `3f6da32aac516cbf8ac987277ec3f69b242a8453cf16de663b7b71b62297ec51` | -| `app/plotter/service-studies.tsx` | `fb16277ad79c6aacb3734d9e34b09816d29cc7ec8615260329a3cd8541d5f912` | -| `app/plotter/popular-service-studies.tsx` | `1331a3236bca39518600580d0aaf696dbd452ec79505fc1ea66fdcc6c3d5c12e` | -| `app/plotter/system-state-studies.tsx` | `0ba231cd9b1069e28c6a5bea028758c39812fcd5c45f313f1eab2f0d86008f30` | - -Re-run source checks and update these hashes after further edits. No source reading or attribute scan establishes thumbnail readability, narrow-layout quality, or user approval. - -Local review captures are not bundled with this skill. Regenerate the named views from Plotter when reviewing another checkout; source hashes identify the inspected revisions. diff --git a/skills/plotter/references/history/source-audit.md b/skills/plotter/references/history/source-audit.md deleted file mode 100644 index 0653315..0000000 --- a/skills/plotter/references/history/source-audit.md +++ /dev/null @@ -1,169 +0,0 @@ -# Plotter source audit - -Historical evidence for the named revisions. Use the [current instructions](../../SKILL.md) for new work; these findings and product claims need fresh evidence before being applied to a later revision. - -Recorded 2026-10-25 against the working tree based on HEAD `f6da7e24`. **Revision status:** O06, W04, W05, O07, S10, S11, and the new S01-based M03 were re-read and recalculated after user feedback. Their older board, bore/insert sequence, involute-gear, wall-socket, and plug-animation findings are superseded. The file hashes below identify the inspected revisions; subsequent edits invalidate affected checks. This bounded source, geometry, and meaning review does not certify the gallery. - -## Evidence and verdict scope - -- **Source checks performed:** read TSX geometry, inherited stroke/fill roles, SVG path commands, labels, descriptions, and the drafting standard for P00, C02, B01–B04, S10, S11, O06, W04, W05, O07, and revised S01/M03. Two replacement coss concepts have separate coverage below; the former seven were rejected for visual quality. -- **Independent calculations performed:** recomputed distances, units, incidence, tangency, angles, RC arithmetic, gear pitch geometry, cradle trajectory intersections, and marker clearance with Python’s `math` functions. The new gear profiles also received a sampled static nonintersection check. -- **Implementation evidence:** this reviewer ran Biome and focused strict TypeScript checks on the earlier corrected sources. The authors report full UI TypeScript and scoped Biome passes after the new revisions. These are attributed build results, not independent re-runs by this reviewer. Showcase corrections are separate from production integration. -- **Render review performed:** independently viewed author-rendered PNGs of all four revised engineering studies and rasterized current S10/S11/S01 SVGs. The latter rasterizer used fallback fonts; it establishes shape visibility, not browser typography. Parent browser evidence is attributed below. Final guide-only cleanup was source-reviewed; saved images may precede it. -- **Mechanism limitation:** static profile separation does not prove conjugate motion, actual tooth contact, load capacity, or manufacturability. No older involute/collision-phase result applies to the new schematic gear profiles. - -PASS below means the named claim was checked. NEEDS QUALIFICATION means a wider claim lacks evidence or a convention remains ambiguous. Legacy style findings are not silently converted into passes by a geometry result. - -The [remaining-source audit](remaining-source-audit.md) covers the other 43 principal static constructions, including E01/E06 callout corrections and the gallery-wide fill inventory. Revised S01 is rechecked here without adding another registered study. Together these reports cover all 55 principal constructions; they do not establish exhaustive path correctness or complete style normalization. M03 motion and the coss concepts are separate from that count. - -### Current integration render evidence - -The parent confirmed inspecting revised S10/S11 in hero and 96-pixel compact presentations, and exercising new M03 movement, Pause/Resume, and Show static/Play animation. Saved parent evidence: revised gears (`plotter-gears-revised.png`, local capture), revised socket (`plotter-socket-revised.png`, local capture), S01-based M03 (`plotter-s01-animation.png`, local capture). The M03 capture precedes the final guide/leader cleanup. These observations do not constitute user approval. - -The parent previously reviewed the nine-box O06 revision with contacts in light/dark themes, plus O06/W04/W05/O07 as dark gallery thumbnails beside approved references. The user subsequently called that O06 revision “bland” and also rejected its 5× compute-detail replacement. Those two render snapshots are historical; neither establishes approval of the current CPU-board direction. Saved evidence includes final GPU (`plotter-gpu-revised.png`, local capture) and dark object gallery (`plotter-objects-dark.png`, local capture). The parent reports final full reloads without the development-issue badge; transient edit-time hydration messages remain only in historical logs. This is attributed observation, not this reviewer’s independent console inspection. A complete theme/mobile pass across the whole collection was not reported. - -### User-feedback criteria checked - -| Study | Revised evidence | -| --- | --- | -| W05 | One conveyor carries identical open frames at constant pitch; a matching core descends at the center station and is seated in the right frame. | -| W04 | A 24-unit grid locates routing/terminals and is trimmed around wires, symbols, and labels. Topology and RC arithmetic remain consistent. | -| O06 | The user rejected the compute-array/detail studies and requested a recognizable board with a CPU. Latest feedback removes the enclosing card and mounting holes, asks for dashed lines, and calls the composition crowded. The revised open drawing retains the CPU and pins, reduces ten routes to four, removes the lower contact bank, spaces memory farther away, and adds dashed center axes. | -| O07 | A restrained fixed support replaces the surrounding frame; exact strings, tangent rest positions, release arc, and dimensions remain legible. | -| S11 | The female flange, recessed body, and contact pockets are separate from the hatched support; mouth gap and mating axes agree. | -| S10 | 10/8/6 broad, rounded schematic teeth replace 24/18/12 finely sampled teeth. Static geometry and pitch relationships agree. | -| M03 | The S01 route/page construction is shared by static and animated views. Its request follows the route centerline and leaves the missing address gap intact. | - -## Corrected reference drawings - -| Study / source function | Calculation and evidence | Current result | -| --- | --- | --- | -| P00 / `primitives-blueprint.tsx: PrimitivesBlueprint` | Square `240×240`; `u=40`; circle `(284,204), r=120=3u`; four side tangencies and the 45° diagonal agree. Radius endpoint is now `(284+120/√2,204−120/√2)`; angle arc endpoint is `(284+24/√2,204−24/√2)`. Incidence residuals are floating-point roundoff. Cap tip shares the radial endpoint. | **PASS geometry.** Original radial residual `0.20815` is corrected. Legacy style exceptions remain below. | -| C02 / `system-studies.tsx: ModularTrayStudy` | `u=22`; `412−148=264=12u`; widths `110=5u`, `132=6u`; gap `280−258=22`. Switch `30×18`, `R9`; thumb `R5.5`, right/top/bottom inset `3.5`. | **PASS geometry. NEEDS QUALIFICATION for convention:** the dashed layout-allocation box is not a physical hidden edge; document its conceptual role. | -| B01 / `service-studies.tsx: CloudflareEdgeStudy` | Edge `224×224=4u×4u`, `u=56`; cache `R44`; radius-leader residual `0.01796<0.05`. Hit path returns toward visitor; miss path goes toward origin. | **PASS scoped example:** a cache-eligible request with simple hit/miss outcomes. Other statuses, tiered cache, and the whole Cloudflare service are outside its scope. [Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/) | -| B02 / `service-studies.tsx: VercelDeploymentStudy` | Frames `144×72`, `R12`; spacing `192−168=24`; index `02` identifies the same source version. Description allows a rebuilt production artifact. | **PASS scoped explanation.** Preview promotion rebuilds; staged production promotion is a different flow. [Vercel promotion](https://vercel.com/docs/deployments/promoting-a-deployment) | -| B03 / `service-studies.tsx: StripeSettlementStudy` | `4×64=256`; `4×$25=$100`; `u=64`. Label now says “Gross payments”; description excludes fees, refunds, and availability. Stable ID retains `settlement`; visible title is “Payments, combined.” | **PASS arithmetic and bounded meaning.** Gross aggregation does not depict actual net/available balance or full settlement/reconciliation. [Stripe balance transactions](https://docs.stripe.com/api/balance_transactions/object) | -| B04 / `service-studies.tsx: LinearCycleStudy` | `u=68`; `408−136=272=4u`; illustrative weeks each span `2u`; pills `R16`; rounded radius-leader residual `0.01939<0.05`. Marker now says “Cycle end”; release equivalence removed. | **PASS geometry and corrected scope.** Two weeks is this example, not a universal duration or release boundary. [Linear cycles](https://linear.app/docs/use-cycles) | - -## Revised mechanical and missing-destination studies - -### S10: `system-state-studies.tsx`, `gearOutline`, `MaintenanceStudy` - -The new model uses common module `m=14` and `10/8/6` teeth. Pitch radii `70/56/42` satisfy `r=mz/2`; chosen schematic root radii are `60.9/46.9/32.9` and tips `76.3/62.3/48.3`. Those root/tip proportions and rounded trapezoidal profiles are house illustration choices, not standard involute geometry. Common module/pitch is a meaningful reference relationship; it does not make arbitrary profiles conjugate. [KHK gear-mesh explanation](https://www.khkgears.us/media/1256/gear-mesh-and-tooth-modifications.pdf) - -Centers are `(176,192)`, `(350,192)`, `(408.8,270.4)`. The smaller pair’s distance is `hypot(58.8,78.4)=98=56+42`, with pitch contact `(383.6,236.8)`. A tooth faces a valley along that centerline. Main-drive pitch gap is `174−70−56=48`, matching the dimension witnesses at `x=246/294`. This is a pitch-circle gap, not the shortest outline clearance. - -The reviewer independently rebuilt the same rounded outline equations and sampled each quadratic join at 20 subdivisions. In the static pose, segment intersections were zero; sampled minimum outline clearances were approximately `36.011` for the separated drive and `2.329` for the smaller pair. This bounded numerical check is not a proof for every point or other phases, and the visible clearance does not establish physical tooth contact. - -**PASS:** tooth counts, pitch radii, center spacing, phase relation, labeled gap, and sampled static nonintersection. **NEEDS QUALIFICATION:** engagement is schematic. No pressure-angle, conjugate-motion, continuous-contact, strength, or manufacturing claim is supported. The old 25° involute and 25-phase checks are superseded. - -### S11: `disconnected-plug.tsx` - -The female socket is now a distinct section: flange `x=344…356`, recessed body to `x=400`, and two contact pockets ending at `x=388`. The support plane is `x=356`; it is separate from the mouth at `x=344`. Male pins end at `x=264`, so the depicted mouth gap is `344−264=80`. Pins/pockets share centers `y=196/244`, spacing `48`, and height `12`. Pocket depth `388−344=44` exceeds pin protrusion `40`. - -S1 support hatch uses 16-unit strokes at −45° and `.65/.27`, only outside the body opening. It is a fixed-support convention, not material identification. Movement arrows use rounded `4.243` shoulder offsets, producing approximately `6.00051`-unit legs at 45°, within the house serialization threshold. Dashed shafts start at their tips. Duplicate horizontal-dimension witness segments found during review were removed; longer witnesses now meet the helper’s terminal segments at `y=146`. - -**PASS:** separate socket/support geometry, pin/pocket alignment, gap and spacing labels, and the checked line-role corrections. **NEEDS QUALIFICATION:** nominal geometry does not establish electrical type, safe electrical construction, contact force, or a manufactured fit. S11 is static; M03 no longer animates this drawing. - -### S01 and M03: `missing-destination.tsx`, `not-found-motion.tsx` - -Static S01 and animated M03 share the same route/page component. The paired route remains `16` wide, with concentric `R24/R40` bends and an `R32` centerline. It ends at `x=272`; the absent-page reference plane at `x=304` gives `u=32`. The source preserves those primary shapes while splitting guides around them. The external R40 leader meets the outline at `(211.716,215.716)`; radial residual is approximately `−0.000384`, below the `0.05` house threshold. Its two open-cap legs are exactly six units and 45° to the diagonal shaft. - -The hollow request marker has radius `3.5` and follows `M122,296 … H266`, length `54 + 32π + 20 + 26 = 200.530965`. Its maximum center is `x=266`; including its `.95` stroke, its right edge is `269.975`, leaving `2.025` units before the route end and the full 32-unit address gap unbridged. Both bends follow the true centerline; the moving outline stays within the route. - -The `8.4s` loop has monotonic keyTimes and six matching keyPoints. It pauses at each end and returns on the same path, so the loop closes without a jump. Source retains Pause/Resume, Replay, static fallback, reduced-motion hiding/pausing, and offscreen pausing. Parent browser review observed movement, Pause/Resume, and Show static/Play animation. Replay, reduced-motion behavior, and offscreen behavior were source-read but not independently exercised here. - -**PASS:** shared geometry, radius incidence, marker clearance, and source-level loop/control wiring. **NEEDS QUALIFICATION:** this is a request/absence metaphor, not a timing or network-behavior model. Browser evidence is scoped to the controls actually exercised; the last guide cleanup followed the saved M03 capture. - -## Revised engineering studies - -| Study / function in `engineering-studies.tsx` | Independent verification | Scope and verdict | -| --- | --- | --- | -| O06 / `ProcessorBoardStudy` | CPU package remains120 square with eight pins per side, pitch `p=12`, pin width4 and length12; first-to-last center span84=`7p`. The die56 square and RAM40×96 share center height204. Two routes per side at174/234 are symmetric about that center: left from I/O circle edges128 to CPU pin ends208; right from CPU pin ends352 to RAM pin ends404. The board enclosure, holes, lower bank, and six surplus routes are removed. Dashed axes use `8 3 1 3` at `.6/.24`; the grid omits its coincident x280 column. | **PASS named geometry and contact incidence.** This is a hypothetical processor layout, not a functional CPU/RAM circuit, vendor pinout, manufacturing layout, or electrical safety claim. | -| W04 / `RcFilterStudy` | Grid pitch `24`; terminal centers `112/448`, resistor endpoints `184/256`, and junction `328` have the same x phase. Wire `y=184` shares the row phase. Vin reaches R1, whose output and Vout share junction `(328,184)`; C1 connects that node to the lower reference. Plates at `y=256/268` stay separated; grid gaps avoid false electrical continuation. `R=1000Ω`, `C=100×10⁻⁹F`: `τ=100μs`, ideal `fc=1591.549Hz`. | **PASS topology, grid purpose, arithmetic** for an ideal unloaded low-pass referenced to the lower node. Individual IEC 60617 entries were not authenticated; no compliance claim. [TI passive-components lesson, p.13](https://www.ti.com/content/dam/videos/external-videos/zh-tw/4/3816841626001/6119035031001.mp4/subassets/passive_components_and_circuits_2.pdf) supports this topology. | -| W05 / `ProductionChainStudy` | Carrier centers `144/280/416` have pitch `136`. Each frame is `64×64`, with 8-unit walls and a `48×56` opening. The incoming `48×48` core seats at `y=208…256`, leaving 8-unit headroom; final core edges share the frame’s existing side/bottom segments rather than retracing them. Conveyor has `R16` ends and `R8` rollers. Arrow tips `(304,288)` and `(280,200)` meet starting dashes; cap legs are 6 at 45°. | **PASS assembly-line relationship and nominal geometry.** Carrier locations, loading direction, and seated state agree. Equal nominal core/opening widths do not prove a toleranced fit or a production-machine design. Guide/terminal overlaps identified in review were removed. | -| O07 / `NewtonsCradleStudy` | `u=r=22`, pivot-to-center `L=176=8u`, center spacing `44=2u`; rest centers at `y=296`. Released center `(128,272.420471)` is exactly 176 from `(216,120)` at 30°. Strings are trimmed to anchor radius 2.4 and bob radius 22, leaving exposed length 151.6. With `δ=2asin(22/(2·176))`, trajectory endpoints lie exactly 22 from the corresponding bob centers. Independent residuals are about `10⁻¹⁴`; tangent-cap legs are 6. Radius and 30° angle callouts derive from the same constants. | **PASS ideal construction and the checked line-role cleanup.** S1 hatching identifies a fixed support. This planar release diagram does not simulate collisions, damping, restitution, or subsequent motion. Refined support and dimensions were visually readable in the saved raster and parent enlarged preview. | - -For the preceding revision, the reviewer inspected four author PNGs, including the now-superseded GPU contact-bank raster (`plotter-gpu-contacts-source-review.png`, local capture); parent independently reviewed W04/W05/O07 enlarged in the light theme. Later line-ownership cleanup changed only guide extents. Saved parent evidence: circuit (`plotter-circuit-revised.png`, local capture), assembly line (`plotter-assembly-line-revised.png`, local capture), cradle (`plotter-cradle-revised.png`, local capture). These are review observations, not approval as permanent style references. - -The prior 5× O06 detail was checked mathematically and inspected in the browser, then explicitly rejected by the user in favor of a recognizable board with a CPU. The old `plotter-gpu-focal-detail.png` capture is a rejected revision, not current review evidence. The shared-coordinate scaling check does not apply to the replacement board. - -The enclosed CPU-board capture `plotter-cpu-board.png` is superseded by the open processor revision. The new drawing was inspected in the enlarged light-theme preview and Objects gallery; current capture: `plotter-cpu-open.png`. Biome and the full UI typecheck pass. A separate read-only source review confirmed the four pad incidences, concentric CPU/die, shared CPU/RAM center, exact84-unit pin span, and nonduplicated axes; its suggested isolated-axis tick cleanup was applied. Its visual acceptance remains open; it has not joined the approved reference set. W04/W05/O07 source was verified byte-for-byte unchanged from the version immediately before this O06 edit. - -## Remaining cross-cutting findings - -1. **Legacy transparency:** P00 retains a `.035` area tint and background-colored point fills; C02 and B01–B04 retain background-colored shape fills. These conflict with newer transparent-form guidance. Only requested math/wording corrections were made to those approved compositions; no blanket restyling was performed. -2. **Legacy line roles:** approved sources retain historic dash sequences and opacities. Assign meaning before normalization; text replacement cannot identify centers, hidden features, allocation boxes, and hypothetical transfer. -3. **Coincident segments:** some older grids retrace construction/object segments. P00’s `x=164` and `x=404` occur in both grid and construction layers. These remain future cleanup, not a verified one-owner result. -4. **Symbols and behavior:** RC topology and gear pitch math pass their named checks. Individual IEC database symbols and manufacturing validity were not authenticated. Geometric consistency and physical completeness are separate claims. -5. **Rendering:** source results do not prove label clearance, optical hierarchy, responsive appearance, or user acceptance. Edits invalidate earlier render snapshots of affected drawings until rechecked. -6. **Separate production follow-up:** `apps/ui/components/primitives-blueprint.tsx` still has P00’s original rounded radius/angle endpoints. Its production integration belongs to a separate worktree/PR; synchronize the exact showcase correction there as a separate change. This audit does not claim that production duplicate is corrected. - -## Replacement coss concepts: bounded review - -The user rejected the original X01–X07 set for poor quality relative to the established drawings. The prior bus/catalog/comparison geometry checks are historical and do not apply to the replacements. That code was removed from the local showcase. New X01 and X07 remain proposals, outside the 55-study inventory and the approved reference set. - -- **X01 / `common-interface-study.tsx`:** one central opening has radius `64 = 2u`, with `u = 32`. The upper-right piece is translated by exactly `(32, −32)`; its corresponding opening quadrant and projection witnesses use the same radius. The assembled three-quarter opening and the two internal seams each have one primary path owner. The selected lower-left profile band is analytically bounded by radii 64 and 80. Hatching identifies the common profile, not a physical material. -- **X07 / `shared-system-study.tsx`:** the `240×240` square uses `u = 60`. Two circle centers at `(280,148)` and `(280,268)` are `120 = 2u` apart; equal R60 arcs meet tangentially at `(280,208)`. Their complementary semicircles generate the shared S-profile. The outline/seam are separate single paths; the opposite half-circles and axes are construction references. The radial arrow endpoint is computed with `60/√2` offsets. -- **Meaning:** these are compatibility metaphors for a common SDK contract. They do not assert physical construction, infrastructure topology, or implemented Video/Scheduling API availability. The [product claim mapping](coss-product-concepts.md) retains primary-source evidence and those limits. - -Parent browser review inspected the pair in the local two-column section in light and dark themes. Saved capture: `plotter-coss-interface-studies.png` (local capture). Source geometry and visible hierarchy are separate from user acceptance; no reference approval or coss.com publication is implied. Narrow-screen layouts were not independently exercised. - -Checked SHA-256 prefixes under `app/plotter/coss-concepts/`: - -| File | SHA-256 prefix | -| --- | --- | -| `common-interface-study.tsx` | `ecec2d1d7d62` | -| `index.tsx` | `9782beedc977` | -| `shared-system-study.tsx` | `0af177359ce1` | - -## W05 and O07 motion experiments - -These separate showcase animations retain the original static gallery drawings. They have not been selected as motion references. - -- **W05, preceding revision:** the 2.25-second refinement shortened the former 3.0-second cycle. The rigid 48×48 core drops 80 units from 0.04–0.42s; a restrained 0.35-unit rebound settles at 0.470269s. Indexing starts 20ms later and finishes at 1.590269s. Feed finished at 2.16s, leaving 0.13s until the next drop. All core edges share one sampled displacement function and exact wall/floor ownership. Motor/feed interpolation uses cubic constant-jerk ramps with continuous position, velocity, and acceleration at joins. The author checked 9,001 serialized phases: rigid size, exact 136-unit pitch and 272-unit feed travel, no penetration, and gravity-curve approximation error below 0.01 unit. Calculated start/end rasters were identical. The current timing is recorded below. This remains an illustrative gravity/contact model with a driven conveyor, not a machine simulation. -- **O07, preceding revision:** the 1.8-second cadence used a restrained 26° release. Energy-derived cubic segments replaced linear angle chords, giving exactly zero endpoint speed at each turnaround and continuous flight velocity. Contact occurred at 0.45s/1.35s with matched speed magnitude 91.152327°/s and no dwell. The author checked 36,001 poses: no bob overlap, fixed 176-unit strings (residual below 6×10⁻¹⁴), complete disk bounds x116.847…491.153/y256.188…318, and a closed seam. Serialized velocity-continuity error was below 4.6×10⁻⁷°/s away from impacts. The current calibration is recorded below. Damping, compliance, finite contact duration, and interior dynamics remain omitted. A visually delayed wave through tangent rigid disks was rejected because it would require unmodeled deformation or gaps. -- **Presentation:** parent browser review confirmed active 2.25s/1.8s spline timelines and observed moving phases. The fixed support/grid, transparent forms, static gallery drawings, and annotations remain unchanged. Replay and Pause/Resume passed the preceding revision and their shared controls are unchanged. Offscreen pausing and reduced-motion static fallback remain source-reviewed rather than independently emulated. Capture from that revision: `plotter-w05-o07-rhythm.png` (local capture). The former `plotter-w05-o07-physics.png` and `plotter-w05-o07-animations.png` record superseded motion. -- **Checks:** scoped Biome and full UI TypeScript checks pass. Existing W05/O07 static functions were only exported for preview fallbacks; their geometry is unchanged. - -**Current W05 cadence:** the fast 0.70s delivery is retained, now at 1.00–1.70s within a 1.8s cycle. Visible feed starts at 1.171471s, overlapping the last 0.418799s of indexing. The next drop starts at 1.84s, giving a 0.14s handoff. Drop, rebound, and belt trajectories are unchanged in absolute time. The author rechecked 9,001 serialized phases for rigid size, contact ownership, and penetration, and compared pixel-identical loop endpoints. A separate read-only review found no source-level handoff or loop defect. Parent added fixed reference guides at y=124/180, x=80…248: 4 units clear of the incoming core's y=128…176 bounds and 8 units short of its x=256 drop edge. They do not cross moving parts or cover lines. Biome and diff checks pass; browser review confirms the 1.8s timelines and revised guides in moving phases. Full TypeScript was not rerun for these timing constants and SVG path changes. Capture: `plotter-w05-overlapping-feed.png`. The prior `plotter-w05-faster-feed.png` records the superseded sequential feed. - -**Superseded O07 timing calibration:** the same nonlinear quarter-flight integral K=1.591254382 now produces the duration as `4K√(0.30/9.80665) = 1.1132684299524582s`, rather than normalizing to a hardcoded 1.8s. The chosen 0.30 m length calibrates the motion; it is not a measurement of the drawn object. The earlier timing implied approximately 0.78427 m under the same model. Contacts occur at 0.2783171075/0.8349513225s, with matching incoming/outgoing speed magnitude 147.3806178°/s. Two source reviews confirm 385 serialized values/keyTimes, 384 valid spline segments, strictly increasing times, zero-speed turnarounds, and matching loop endpoints. The author rechecked 36,001 poses and agreement with the independent energy relation within 0.000006°/s. Geometry, bounds, annotations, and ideal collision assumptions are unchanged. Browser review confirms both 1.113268s timelines and moving phases; capture `plotter-o07-calibrated-swing.png`. Scoped Biome and full UI TypeScript checks pass. The governing nonlinear pendulum equation is described in [OpenStax, Pendulums](https://openstax.org/books/university-physics-volume-1/pages/15-4-pendulums); the 30 cm calibration is a house choice, not a value from that source. - -**O07 video reference:** the user then supplied [this video](https://www.youtube.com/watch?v=09vzFodz4SI). Parent inspected opening playback and paused/stepped frames around 15–17.64s in the browser; this was not a full-hour viewing. The observed visual rhythm suggests roughly a 2.4s cycle and 30° release, superseding the arbitrary 30 cm calibration. These are approximate visual estimates, not motion-capture data. O07 uses those values with the same nonlinear pendulum flight and instantaneous contact model. Full swept disk bounds are x106…502, y250.420…318; the outer guide fragments retain at least 6/8 units of horizontal clearance. Browser confirms active 2.4s timelines and a 30° starting release. Read-only review confirms valid serialized splines, zero-speed turnarounds, matched contact speeds of 78.99743219°/s at 0.6/1.8s, and exact loop endpoints. Across 36,001 poses, no disk overlap or string-length drift above 5.7×10⁻¹⁴ was found. Biome passes. Capture: `plotter-o07-video-rhythm.png`. The previous `plotter-o07-calibrated-swing.png` records the superseded faster trial. - -**O07 speed adjustment, before interior movement:** the user requested a slight speed-up with unchanged easing. The duration shortened from 2.4s to 2.2s, then to 2.0s after a further speed request (10% faster than the 2.2s trial). Browser comparison confirmed both animations retained byte-identical `values`, `keyTimes`, and `keySplines`; the 30° geometry, normalized motion, contact ordering, and loop were unchanged. Contact times scale to 0.5/1.5s. Biome passed. Capture: `plotter-o07-two-second-cycle.png`. - -**O07 interior movement, before turnaround emphasis:** the user next requested subtle movement of the three middle balls, as in the reference. A shared secondary angle `β = 0.025θ` gives them a ±0.75° sway; the resting outer follows the same angle. Each bob still rotates about its own fixed pivot. Read-only review sampled 60,001 signed outer angles: the touching four-ball group keeps 44-unit center spacing within 2.9×10⁻¹⁴, and the active outer never overlaps it. Maximum interior drift is 2.303769 units horizontally and 0.015078 vertically; complete bounds and guide clearances remain unchanged. The central mark and radius-leader tip track the middle bob while the label stays fixed. Browser comparison confirms the active outer angles and spline strings remain byte-identical to the preceding version; all five pendulums share its 385 key times and 2s duration. Per-segment endpoint velocity scaling preserves the intended end-ball handoff without a delayed interior wave. This is a phase-locked motion approximation, not a solved five-body contact model. Scoped Biome and full UI TypeScript checks pass; the moving preview and Replay were inspected. Capture: `plotter-o07-middle-sway.png`. - -**Current O07 turnaround emphasis:** the next request asks for more slowdown at the highest point and a faster departure/return at impact. Quarter-flight time is remapped with `F(q) = q + 0.25 sin(πq)/π`; its derivative stays in `[0.75, 1.25]`, with velocities adjusted by the chain rule. The 2s loop, 30° outer swing, and ±0.75° shared sway remain. Read-only review confirms 385 values, 384 valid monotone spline segments, strictly increasing key times, no overshoot or hold, and unchanged contacts at 0.5/1.5s. Main/contact speed is 126.3958915°/s, one-third above the previous curve; the shared speed is 3.1598974°/s. Turnaround speed remains zero, and the loop has no position/velocity seam. This deliberately accentuates the illustration’s timing rather than preserving the unmodified gravity trajectory. Browser comparison confirms unchanged angle values and updated timing for all five pendulums; the moving preview and Replay were inspected. Biome and full UI TypeScript checks pass. Capture: `plotter-o07-turnaround-emphasis.png`. - -Checked source hashes under `apps/ui/app/plotter/`: - -| File | SHA-256 prefix | -| --- | --- | -| `production-chain-motion-drawing.tsx` | `62af5a7164d8` | -| `newtons-cradle-motion-drawing.tsx` | `3930716d38c6` | -| `engineering-motion-preview.tsx` | `7e194f9de588` | -| `engineering-motion-preview.module.css` | `47531e974a1a` | - -## Reproduction notes - -Recompute from current source after edits. Preserve exact relationships and report residuals against house serialization thresholds (`0.05` SVG unit, `0.1°`), never as manufacturing tolerances. File hashes recorded below identify this source snapshot; unrelated working-tree edits may continue. - -SHA-256 prefixes, all under `apps/ui/app/plotter/`: - -| File | SHA-256 prefix | -| --- | --- | -| `primitives-blueprint.tsx` | `be989e00c285` | -| `service-studies.tsx` | `fb16277ad79c` | -| `system-studies.tsx` | `04de74c464c9` | -| `system-state-studies.tsx` | `0ba231cd9b10` | -| `disconnected-plug.tsx` | `7bd9b1e03e5d` | -| `engineering-studies.tsx` | `343bd2dc51c5` | -| `missing-destination.tsx` | `e3ba6a8f8bed` | -| `state-studies.tsx` | `c7190028b3fc` | -| `not-found-motion.tsx` | `01d467710cbd` | -| `not-found-motion.module.css` | `47531e974a1a` | - -Local review captures are not bundled with this skill. Regenerate the named views from Plotter when reviewing another checkout; source hashes identify the inspected revisions. diff --git a/skills/plotter/references/implementation.md b/skills/plotter/references/implementation.md deleted file mode 100644 index 8390a31..0000000 --- a/skills/plotter/references/implementation.md +++ /dev/null @@ -1,69 +0,0 @@ -# Website integration - -Read when editing the standalone Plotter website, its React components, or a host integration. Portable composition, geometry, and motion instructions live in the [drawing](drawing.md), [animation](motion.md), and [foundation](foundation.md) references. This file is an optional host adapter; the installed skill does not depend on the website. - -## Locate the host sources - -Use the current checkout and read its `AGENTS.md`. Paths below are relative to the standalone repository root. - -| Responsibility | Source | -| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -| Canonical portable package | `skills/plotter/` | -| Shared token and geometry source | `skills/plotter/assets/foundation/` | -| Gallery SVG wrapper and role-style opt-in | `components/plotter/blueprint-drawing.tsx` | -| Editable catalogue SVGs | `components/plotter/drawings/` | -| Catalogue compiler and SVG serializer | `scripts/build-plotter-drawings.py`, `scripts/plotter_svg.py` | -| Bundled catalogue SVGs and index | `skills/plotter/references/catalogue/`, generated by `scripts/build-plotter-catalogue.tsx` (`bun run catalogue`) | -| AGT-01 helper-fragment recipe | `skills/plotter/assets/examples/render-registration.mjs` | -| AGT-01 host file adapter | `scripts/build-plotter-registration.mjs` | -| Static MEC-05 and OBJ-05 | `components/plotter/engineering-studies.tsx` | -| MEC-05 shared core hatching | `components/plotter/production-chain-hatching.tsx` | -| MEC-05 and OBJ-05 timelines | `components/plotter/production-chain-motion-drawing.tsx`, `components/plotter/newtons-cradle-motion-drawing.tsx` | -| Engineering playback, fallback, and visibility | `components/plotter/engineering-motion-preview.tsx` | -| Resolved pilot export adapter | `scripts/export-plotter-pilots.tsx` | -| Download artifact generator | `scripts/build-plotter-downloads.tsx` | -| Website documentation | `content/docs/` | - -`BlueprintDrawing` opts into shared roles with `roles`. Token adoption currently covers **AGT-01, MEC-05, GEO-11, SYS-06, and CRF-06**; all current illustrations use 1-unit visible strokes. Legacy unmarked drawings retain their authored opacity and dash patterns, without acquiring shared role-token customization. The independent highlight-opacity token is used by TIM-01, TIM-03, and TIM-05 without changing their stroke-role adoption. The SVG-to-JSX builder preserves supported root styles, removes standalone fixed ink and the root font family so the gallery inherits its theme and loaded font, and gives repeated definitions local IDs. Font weight, optical sizing, and GEOM settings remain authored. Standalone SVGs retain their own font stack. - -Edit SVG sources and regenerate React output; catalogue and grammar components derived from those sources are generated artifacts. When the standard or AGT-01 source changes, use the repository-root sequence: - -```sh -python3 skills/plotter/scripts/build-standard.py -node scripts/build-plotter-registration.mjs -python3 scripts/build-plotter-drawings.py -``` - -Refresh distributable downloads with: - -```sh -bun scripts/build-plotter-downloads.tsx -``` - -Generation produces artifacts; visual correctness depends on inspecting the affected drawing within the requested scope. - -## Preserve the integration boundary - -The standalone website owns its layout. Its homepage introduces the drawing and animation workflows. Keep study IDs stable and keep removed studies out of active metadata. - -Catalogue codes are a three-letter family prefix (`familyPrefix` in `components/plotter/study-types.ts`) and a number, without gaps within a family. A new drawing takes the next number in its family; a retired drawing keeps its code reserved in `retiredStudies` and the [code map](history/code-map.md). After any catalogue change, run `bun run catalogue` so the bundled SVGs and index match the website. - -Present catalogue art at native `560 × 440` dimensions when space permits. Scale it proportionally to fit narrower containers instead of requiring horizontal scrolling; preserve its SVG viewBox and geometry. Preserve grammar isolation behavior: focused marks retain their original appearance, and supplemental grid segments restore only portions hidden with a form. Keep hover, keyboard, and touch access to that behavior. - -Static drawings and animation timelines remain separate. MEC-05’s static and animated core faces share a hatch component; its carrier frames remain unhatched. Playback owns pause/resume, static fallback, reduced motion, and visibility. On the website, looping drawings show no controls; they pause off-screen and fall back to the still drawing under reduced motion. Timeline edits preserve the chosen still unless redesign is requested. Current source owns exact timing; [historical feedback](history/direction.md) explains particular revisions. - -## Portable delivery from the website - -From the repository root: - -```sh -bun scripts/export-plotter-pilots.tsx /tmp/plotter-exports -``` - -This adapter renders the selected static MEC-05 drawing and sends it, along with AGT-01, through the packaged exporter. Recipients need neither React nor Bun. General authoring uses the [portable examples](foundation.md#portable-examples) and Python exporter directly. - -Resolved static SVG carries its appearance values and local definitions. Animated HTML carries its timeline, player, static fallback, and actual local resources, or inlines those resources for a single-file delivery. Neither format should rely on website imports. - -## Historical coss integration - -The original coss implementation lived under `apps/ui/app/plotter`, with the skill at `apps/ui/skills/plotter` and an unlinked `/ui/plotter` showcase. Its production hero selections and routes describe that earlier host. Preserve those details in [history](history/index.md); they are not active standalone repository paths. diff --git a/skills/plotter/references/linear.png b/skills/plotter/references/linear.png deleted file mode 100644 index f0445c3..0000000 Binary files a/skills/plotter/references/linear.png and /dev/null differ diff --git a/skills/plotter/references/motion.md b/skills/plotter/references/motion.md index 48d007c..177263d 100644 --- a/skills/plotter/references/motion.md +++ b/skills/plotter/references/motion.md @@ -58,14 +58,14 @@ Within the permitted review scope, watch a complete cycle at normal speed and in - Does the return preserve meaning and continuity? Compare position **and speed**, except at an intentional impact or reversal. - At approach, contact, and separation, do edges remain single, hatches attached, labels clear, and dimensions truthful? -Revise the weakest observed issue and replay the affected sequence. Review the chosen still independently. Sampled frames can establish poses and clearances; they do not establish rhythm. If playback inspection is unavailable, name that gap rather than calling motion visually verified. Respect a request to skip automated checks. +Revise the weakest observed issue and replay the affected sequence. Review the chosen still independently. Sampled frames can establish poses and clearances; they do not establish rhythm. `python3 scripts/render.py page.html` captures a page as it loads, so give a review file a way to open at a chosen time when you need a later pose. If playback inspection is unavailable, name that gap rather than calling motion visually verified. Respect a request to skip automated checks. ## Delivery and host behavior -The brief determines the artifact. A request to animate a site component is not a request for a standalone HTML player. Preserve the host’s existing controls and playback conventions; read [website integration](implementation.md) for this repository. +The brief determines the artifact. A request to animate a site component is not a request for a standalone HTML player. Preserve the host’s existing controls and playback conventions. - **Embedded illustration:** integrate the timeline with the host’s playback. Plotter’s website loops have no visible controls; they pause off-screen or while the page is hidden. -- **Standalone animation or review file:** include the editable timeline and its actual resources. A player with pause/resume, replay, and a way to inspect the selected still is useful here. For one-file HTML, inline the generated role stylesheet; for a folder, preserve all relative dependencies. +- **Standalone animation or review file:** include the editable timeline and its actual resources. A player with pause/resume, replay, and a way to inspect the selected still is useful here. For one-file HTML, inline the generated role stylesheet and, when the page should not depend on an installed font, the bundled Cal Sans as a data-URI `@font-face`; for a folder, preserve all relative dependencies. - **Still export:** export the selected static composition with the packaged exporter. Active animation is outside that exporter’s contract. Respect reduced motion, including preference changes while the page is open, by showing the selected still. Keep it readable before JavaScript runs and when animation is unavailable. A paused intermediate frame is not the same as that deliberately chosen fallback. diff --git a/skills/plotter/references/not-found-interrupted-path.png b/skills/plotter/references/not-found-interrupted-path.png deleted file mode 100644 index e2b1326..0000000 Binary files a/skills/plotter/references/not-found-interrupted-path.png and /dev/null differ diff --git a/skills/plotter/references/particles-recombination.png b/skills/plotter/references/particles-recombination.png deleted file mode 100644 index 22844f0..0000000 Binary files a/skills/plotter/references/particles-recombination.png and /dev/null differ diff --git a/skills/plotter/references/particles.png b/skills/plotter/references/particles.png deleted file mode 100644 index aaac9bc..0000000 Binary files a/skills/plotter/references/particles.png and /dev/null differ diff --git a/skills/plotter/references/primitives.png b/skills/plotter/references/primitives.png deleted file mode 100644 index ac4ef3d..0000000 Binary files a/skills/plotter/references/primitives.png and /dev/null differ diff --git a/skills/plotter/references/standards-background.md b/skills/plotter/references/standards-background.md new file mode 100644 index 0000000..f8723d6 --- /dev/null +++ b/skills/plotter/references/standards-background.md @@ -0,0 +1,19 @@ +# Standards background + +Read before asserting compliance with an external drawing standard, citing one of its symbols, or answering a question about the name “blueprint”. Ordinary drawings need only the house roles in the [drafting standard](drafting-standard.md). + +## What the external standards establish + +These are verified source facts, separate from the house choices in the drafting standard: + +- **ISO 128-2:2022** concerns technical line types, configurations, leaders, and references, including discipline-specific applications. Its public abstract supports treating line roles consistently; it does not establish Plotter’s pixel values. [ISO catalogue](https://www.iso.org/standard/83355.html) +- **ISO 128-3:2022** concerns views, sections, and cuts using orthographic projection methods. A cut or section therefore needs a meaningful relationship to an object and view. [ISO catalogue](https://www.iso.org/standard/83356.html) +- **ISO 129-1:2018** concerns presentation of dimensions and associated tolerances. Its scope distinguishes presentation from the meaning/application of dimensional tolerancing. Decorative dimensions cannot establish fit or manufacturability. [ISO catalogue](https://www.iso.org/standard/64007.html) +- **IEC 60617 DB** is IEC’s maintained collection of graphical symbols for diagrams. **IEC 60417** addresses symbols on equipment, a different use. A claimed IEC symbol needs the actual symbol entry and application context. [IEC TC 3](https://tc3.iec.ch/standard-as-database/) +- **NPS HABS drawing guidelines** distinguish line weights by the represented feature and require scale-aware adjustment. They differentiate hidden/missing features and overhead features. Their hatch rules depend on the view and material: plan poché and section treatment differ, and standard CAD surface patterns must not substitute for measured conditions. This demonstrates why “architectural hatch” is not one universal texture. [HABS guidelines, §§4.2–4.7](https://www.nps.gov/subjects/heritagedocumentation/upload/HABS-Guidelines-Measured-Drawings_508.pdf) + +Research used the public ISO catalogue abstracts and the cited IEC/NPS material. It did not review the full paid ISO standards or validate individual IEC symbol entries. The drafting standard defines an internally consistent illustration standard; it does not certify ISO/IEC/HABS compliance. + +## The name “blueprint” + +“Blueprint” historically identifies a reproduction process: cyanotypes commonly reproduce designs as white lines on a blue ground. Black or theme-colored SVG linework is not a cyanotype reproduction. This distinction concerns medium, not drawing accuracy. [Te Papa collection terminology](https://collections.tepapa.govt.nz/category/421176) diff --git a/skills/plotter/references/verification-prompt.md b/skills/plotter/references/verification-prompt.md index 648a1ee..6b751d2 100644 --- a/skills/plotter/references/verification-prompt.md +++ b/skills/plotter/references/verification-prompt.md @@ -14,9 +14,9 @@ Inputs - Claimed units, scale, equations, behavior, and external sources: Resolve the installed Plotter skill directory, then read its SKILL.md and -references/drafting-standard.md and references/approved-references.md. For an -existing study, also read only its relevant revision entries in -references/history/direction.md. Current direction is in references/direction.md. +references/drafting-standard.md and references/approved-references.md. Read +references/standards-background.md before judging a claim about an external +standard. Current direction is in references/direction.md. Treat appearance approval as art-direction evidence, not as proof of mathematical or product accuracy. diff --git a/skills/plotter/scripts/export-svg.py b/skills/plotter/scripts/export-svg.py index 1b1bdc3..2aae14a 100644 --- a/skills/plotter/scripts/export-svg.py +++ b/skills/plotter/scripts/export-svg.py @@ -1,7 +1,8 @@ #!/usr/bin/env python3 -"""Resolve a Plotter-authored static SVG without depending on the coss stylesheet.""" +"""Resolve a Plotter-authored static SVG without depending on a host stylesheet.""" import argparse +import base64 import json import math import re @@ -12,6 +13,7 @@ SVG = "http://www.w3.org/2000/svg" XLINK = "http://www.w3.org/1999/xlink" FOUNDATION = Path(__file__).resolve().parents[1] / "assets" / "foundation" +FONT = Path(__file__).resolve().parents[1] / "assets" / "fonts" / "CalSansVF.woff2" ET.register_namespace("", SVG) ET.register_namespace("xlink", XLINK) @@ -153,7 +155,7 @@ def target(identifier): node.set(name, URL.sub(lambda match: f"url(#{target(match[2][1:])})", value)) -def export_svg(source, *, ink=None, title=None, description=None, id_prefix="plotter", tokens=None): +def export_svg(source, *, ink=None, title=None, description=None, id_prefix="plotter", tokens=None, embed_font=False): if re.search(r"]*>", source) + if not opening: + raise SystemExit("No element found.") + view_box = re.search(r'\bviewBox="([^"]+)"', opening.group(0)) + if view_box: + values = [float(value) for value in re.split(r"[\s,]+", view_box.group(1).strip())] + if len(values) == 4 and values[2] > 0 and values[3] > 0: + return values[2], values[3] + size = [re.search(rf'\b{name}="([\d.]+)', opening.group(0)) for name in ("width", "height")] + if all(size): + return float(size[0].group(1)), float(size[1].group(1)) + return 560.0, 440.0 + + +def run(command, timeout=60): + try: + result = subprocess.run(command, capture_output=True, text=True, timeout=timeout) + except (OSError, subprocess.TimeoutExpired) as error: + return False, str(error) + return result.returncode == 0, (result.stderr or result.stdout).strip() + + +def written(path): + return path.is_file() and path.stat().st_size > 0 + + +def browser_shot(browser, page, output, width, height, scale, workdir): + base = [ + browser, "--headless=new", "--disable-gpu", "--hide-scrollbars", + "--no-first-run", "--no-default-browser-check", + f"--force-device-scale-factor={scale}", + f"--window-size={width},{height}", + f"--user-data-dir={workdir / 'profile'}", + f"--screenshot={output}", + ] + detail = "" + # A container or agent sandbox can refuse the browser's own sandbox. + for extra in ([], ["--no-sandbox"]): + output.unlink(missing_ok=True) + ok, detail = run([*base, *extra, page.as_uri()]) + if ok and written(output): + return True, "" + return False, detail + + +def themed_svg(source, theme, background): + """A copy with resolved ink and surface, for renderers without a host page.""" + opening = re.search(r"]*>", source) + tag = opening.group(0) + color = f"color:{INK[theme]}" + if re.search(r'\bstyle="[^"]*"', tag): + # Appended so it wins over a color the drawing declares for itself. + themed = re.sub(r'\bstyle="([^"]*)"', lambda m: f'style="{m.group(1)};{color}"', tag, count=1) + else: + themed = tag[:-1] + f' style="{color}">' + surface = f'' + return source.replace(tag, themed + surface, 1) + + +def render_svg(args, source, theme, output, workdir): + native_width, native_height = svg_size(source) + width = args.width or round(native_width) + height = max(1, round(width * native_height / native_width)) + background = args.background or SURFACE[theme] + order = [args.renderer] if args.renderer != "auto" else RENDERERS + tried = [] + + for renderer in order: + if renderer == "browser": + browser = find_browser() + if not browser: + tried.append("browser: no Chrome, Chromium, Edge, or Brave found") + continue + # Inlined, so the page needs no access to files outside its folder. + font_file = args.font or (FONT if FONT.is_file() else None) + font = "" + if font_file: + data = base64.b64encode(font_file.read_bytes()).decode("ascii") + font = ( + '@font-face{font-family:"Cal Sans";font-weight:400 700;' + f'src:url("data:font/{font_file.suffix.lstrip(".").lower()};base64,{data}")}}' + ) + markup = re.sub(r"<\?xml[^>]*\?>|]*>", "", source) + page = workdir / f"page-{theme}.html" + page.write_text( + "{markup}", + encoding="utf-8", + ) + ok, detail = browser_shot(browser, page, output, width, height, args.scale, workdir) + if ok: + return renderer, width, height + tried.append(f"browser: {detail or 'no screenshot written'}") + continue + + command = shutil.which(renderer) + if not command: + tried.append(f"{renderer}: not installed") + continue + copy = workdir / f"drawing-{theme}.svg" + copy.write_text(themed_svg(source, theme, background), encoding="utf-8") + pixels = str(round(width * args.scale)) + if renderer == "rsvg-convert": + ok, detail = run([command, "-w", pixels, "-o", str(output), str(copy)]) + elif renderer == "resvg": + ok, detail = run([command, "-w", pixels, str(copy), str(output)]) + elif renderer == "inkscape": + ok, detail = run([command, str(copy), "--export-type=png", f"--export-width={pixels}", f"--export-filename={output}"]) + elif renderer == "magick": + density = str(round(96 * args.scale * width / native_width)) + ok, detail = run([command, "-density", density, "-background", "none", str(copy), str(output)]) + else: + # Quick Look writes a square thumbnail named after its input. + ok, detail = run([command, "-t", "-s", pixels, "-o", str(workdir), str(copy)]) + thumbnail = workdir / f"{copy.name}.png" + if ok and written(thumbnail): + shutil.move(thumbnail, output) + sips = shutil.which("sips") + if sips and native_height < native_width: + # Trim the square thumbnail's empty band below the drawing. + rows = str(round(float(pixels) * native_height / native_width)) + run([sips, "-c", rows, pixels, "--cropOffset", "0", "0", str(output)]) + if ok and written(output): + return renderer, width, height + tried.append(f"{renderer}: {detail or 'no image written'}") + + raise SystemExit( + "Could not render. Tried:\n " + "\n ".join(tried) + + "\nInstall a Chromium-based browser or rsvg-convert, or set PLOTTER_BROWSER" + " to a browser executable. In an agent sandbox, run this command with the" + " sandbox lifted. Until a render exists, report the visual review as pending." + ) + + +def render_html(args, output, workdir): + browser = find_browser() + if not browser: + raise SystemExit("HTML needs a Chromium-based browser. Set PLOTTER_BROWSER to its executable.") + width, height = args.width or 720, args.height or 620 + ok, detail = browser_shot(browser, args.input.resolve(), output, width, height, args.scale, workdir) + if not ok: + raise SystemExit(f"Could not render the page: {detail or 'no screenshot written'}") + return "browser", width, height + + +def main(): + parser = argparse.ArgumentParser(description=__doc__) + parser.add_argument("input", type=Path, help="An .svg drawing or an .html page.") + parser.add_argument("output", type=Path, nargs="?", help="PNG path. Defaults to the input name with .png.") + parser.add_argument("--width", type=int, help="CSS pixel width to render at. Defaults to the drawing's native width.") + parser.add_argument("--height", type=int, help="CSS pixel height, for HTML pages only.") + parser.add_argument("--theme", choices=("light", "dark", "both"), default="light") + parser.add_argument("--background", help="Surface color. Defaults to the theme's.") + parser.add_argument("--scale", type=float, default=2, help="Device pixels per CSS pixel.") + parser.add_argument("--font", type=Path, help="A font file to render “Cal Sans” with. Defaults to the bundled Cal Sans.") + parser.add_argument("--renderer", choices=("auto", *RENDERERS), default="auto") + args = parser.parse_args() + + if not args.input.is_file(): + raise SystemExit(f"Not found: {args.input}") + output = (args.output or args.input.with_suffix(".png")).resolve() + output.parent.mkdir(parents=True, exist_ok=True) + is_html = args.input.suffix.lower() in (".html", ".htm") + themes = ("light", "dark") if args.theme == "both" and not is_html else (args.theme,) + + # Work beside the output: an agent sandbox may not allow the system temp folder. + with tempfile.TemporaryDirectory(prefix=".plotter-render-", dir=output.parent) as temporary: + workdir = Path(temporary) + for theme in themes: + target = output + if len(themes) > 1: + target = output.with_name(f"{output.stem}-{theme}{output.suffix}") + if is_html: + renderer, width, height = render_html(args, target, workdir) + else: + source = args.input.read_text(encoding="utf-8") + renderer, width, height = render_svg(args, source, theme, target, workdir) + print(f"Wrote {target} ({width} × {height} CSS px, {theme}, {renderer})") + + +if __name__ == "__main__": + try: + main() + except KeyboardInterrupt: + sys.exit(130)