konpeki 0.3.0 → 0.4.0

package/composition/visualizations.ts

@@ -1,319 +0,0 @@
-export type DiagramLayoutEngine =
-  | "linear"
-  | "branching"
-  | "cyclical"
-  | "layered"
-  | "request-flow"
-  | "hub-and-spoke";
-
-export type DiagramDefinition = {
-  label: string;
-  category:
-    | "Systems & technical structure"
-    | "Flow, interaction & behavior"
-    | "Data & software modeling"
-    | "Hierarchy, containment & organization"
-    | "Time & work"
-    | "Quantitative & analytical"
-    | "Conceptual & strategic";
-  layout: DiagramLayoutEngine;
-  slotRole: "process-step" | "entity";
-  expression: string;
-};
-
-export type ChartDefinition = {
-  label: string;
-  expression: string;
-  source: "diagram-design" | "konpeki";
-};
-
-export const diagramDefinitions = {
-  architecture: {
-    label: "Architecture",
-    category: "Systems & technical structure",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Show system boundaries, responsibilities, interfaces, and directional communication without implying physical deployment.",
-  },
-  "it-current-state": {
-    label: "IT current state",
-    category: "Systems & technical structure",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Show the systems that exist today, their ownership, integration paths, friction, duplication, and known constraints.",
-  },
-  "high-level": {
-    label: "High-level overview",
-    category: "Systems & technical structure",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Reduce the system to a small number of named capabilities and major relationships; suppress implementation detail.",
-  },
-  deployment: {
-    label: "Deployment",
-    category: "Systems & technical structure",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Place software artifacts inside the environments, hosts, zones, or runtimes where they execute and show cross-zone communication.",
-  },
-  flowchart: {
-    label: "Flowchart",
-    category: "Flow, interaction & behavior",
-    layout: "branching",
-    slotRole: "process-step",
-    expression: "Distinguish actions, decisions, merge points, and start or end states; label decision branches explicitly.",
-  },
-  sequence: {
-    label: "Sequence",
-    category: "Flow, interaction & behavior",
-    layout: "request-flow",
-    slotRole: "entity",
-    expression: "Order actors horizontally and messages vertically through time; distinguish calls, returns, asynchronous messages, and branches.",
-  },
-  "state-machine": {
-    label: "State machine",
-    category: "Flow, interaction & behavior",
-    layout: "branching",
-    slotRole: "entity",
-    expression: "Treat nodes as legal states and edges as guarded transitions; preserve initial, terminal, retry, and invalid transition semantics.",
-  },
-  swimlane: {
-    label: "Swimlane",
-    category: "Flow, interaction & behavior",
-    layout: "layered",
-    slotRole: "process-step",
-    expression: "Partition steps by responsible actor or team and make every cross-lane handoff visible.",
-  },
-  process: {
-    label: "Process",
-    category: "Flow, interaction & behavior",
-    layout: "linear",
-    slotRole: "process-step",
-    expression: "Show ordered work from trigger to outcome, including branches, loops, owners, and exceptional paths when supplied.",
-  },
-  "data-flow": {
-    label: "Data flow",
-    category: "Flow, interaction & behavior",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Show data producers, transformations, stores, and consumers; label payloads and direction independently from control flow.",
-  },
-  "dp-integration": {
-    label: "Data-product integration",
-    category: "Flow, interaction & behavior",
-    layout: "request-flow",
-    slotRole: "entity",
-    expression: "Show producer and consumer responsibilities, contracts, integration boundaries, and exchange direction for each data product.",
-  },
-  "er-data-model": {
-    label: "ER / data model",
-    category: "Data & software modeling",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Represent entities with key attributes and label relationship cardinality and optionality at both endpoints.",
-  },
-  medallion: {
-    label: "Medallion",
-    category: "Data & software modeling",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Arrange data products by progressive quality tier and show transformations from raw through refined to consumption-ready data.",
-  },
-  "dp-security-matrix": {
-    label: "Data-product security matrix",
-    category: "Data & software modeling",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Use rows and columns as explicit subject and resource axes; encode permissions or controls at their intersections.",
-  },
-  "dependency-graph": {
-    label: "Dependency graph",
-    category: "Data & software modeling",
-    layout: "branching",
-    slotRole: "entity",
-    expression: "Preserve many-parent fan-in, shared dependencies, and cycles; orient every dependency edge consistently.",
-  },
-  "uml-class": {
-    label: "UML class",
-    category: "Data & software modeling",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Keep class names, attributes, and operations in separate compartments and preserve inheritance, aggregation, and composition notation.",
-  },
-  "database-schema": {
-    label: "Database schema",
-    category: "Data & software modeling",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Show tables with typed columns, keys, constraints, and column-level foreign-key endpoints.",
-  },
-  nested: {
-    label: "Nested containment",
-    category: "Hierarchy, containment & organization",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Use enclosure to express scope and ownership; containment must not be replaced by proximity alone.",
-  },
-  tree: {
-    label: "Tree",
-    category: "Hierarchy, containment & organization",
-    layout: "branching",
-    slotRole: "entity",
-    expression: "Show a strict one-parent hierarchy with consistent depth and sibling ordering.",
-  },
-  "org-chart": {
-    label: "Org chart",
-    category: "Hierarchy, containment & organization",
-    layout: "branching",
-    slotRole: "entity",
-    expression: "Show reporting structure, role ownership, and escalation paths; do not imply technical dependency.",
-  },
-  "layer-stack": {
-    label: "Layer stack",
-    category: "Hierarchy, containment & organization",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Order abstraction or responsibility layers consistently and show only legitimate cross-layer dependencies.",
-  },
-  "pyramid-funnel": {
-    label: "Pyramid / funnel",
-    category: "Hierarchy, containment & organization",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Use width and vertical order to encode rank, concentration, or drop-off; state which meaning applies.",
-  },
-  timeline: {
-    label: "Timeline",
-    category: "Time & work",
-    layout: "linear",
-    slotRole: "process-step",
-    expression: "Place dated events on an honest temporal axis and preserve meaningful interval differences.",
-  },
-  gantt: {
-    label: "Gantt",
-    category: "Time & work",
-    layout: "layered",
-    slotRole: "process-step",
-    expression: "Encode task start, duration, overlap, milestones, dependencies, and ownership against a shared time scale.",
-  },
-  kanban: {
-    label: "Kanban",
-    category: "Time & work",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Use columns as workflow states, preserve card ownership and priority, and show WIP limits when supplied.",
-  },
-  "user-journey": {
-    label: "User journey",
-    category: "Time & work",
-    layout: "linear",
-    slotRole: "process-step",
-    expression: "Order experience stages and align actions, touchpoints, pain points, and sentiment to each stage.",
-  },
-  "story-map": {
-    label: "Story map",
-    category: "Time & work",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Use columns for narrative activity order and rows for release slices; preserve the release-cut line.",
-  },
-  quadrant: {
-    label: "Quadrant",
-    category: "Quantitative & analytical",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Position items against two named axes with meaningful scales and make quadrant interpretation explicit.",
-  },
-  "loop-flywheel": {
-    label: "Loop / flywheel",
-    category: "Conceptual & strategic",
-    layout: "cyclical",
-    slotRole: "process-step",
-    expression: "Show a reinforcing cycle with explicit direction and explain how each stage increases momentum or feeds the next.",
-  },
-  venn: {
-    label: "Venn",
-    category: "Conceptual & strategic",
-    layout: "hub-and-spoke",
-    slotRole: "entity",
-    expression: "Use overlapping regions to encode set membership and label every meaningful intersection.",
-  },
-  fishbone: {
-    label: "Fishbone",
-    category: "Conceptual & strategic",
-    layout: "branching",
-    slotRole: "entity",
-    expression: "Group candidate causes by category along branches that converge on one clearly stated effect.",
-  },
-  "wardley-map": {
-    label: "Wardley map",
-    category: "Conceptual & strategic",
-    layout: "layered",
-    slotRole: "entity",
-    expression: "Position components by user visibility and evolution, then show value-chain dependencies and movement without treating the map as runtime architecture.",
-  },
-} as const satisfies Record<string, DiagramDefinition>;
-
-export type DiagramType = keyof typeof diagramDefinitions;
-
-export const diagramTypes = Object.keys(diagramDefinitions) as DiagramType[];
-
-export const chartDefinitions = {
-  "grouped-bar": {
-    label: "Grouped bar",
-    expression: "Compare quantitative values across categories with a shared zero baseline; use grouped series only when each category has comparable values.",
-    source: "diagram-design",
-  },
-  line: {
-    label: "Line",
-    expression: "Encode values on a shared scale and connect observations in meaningful order, usually time; preserve intervals and do not imply missing measurements.",
-    source: "diagram-design",
-  },
-  pie: {
-    label: "Pie",
-    expression: "Show a small set of mutually exclusive parts of one whole; preserve the total and label values directly when comparison by angle is difficult.",
-    source: "konpeki",
-  },
-  "annotated-detail": {
-    label: "Annotated detail",
-    expression: "Focus on one visual detail and connect concise annotations to exact evidence without obscuring the underlying image or chart.",
-    source: "konpeki",
-  },
-  radar: {
-    label: "Radar",
-    expression: "Compare multivariate profiles on consistently normalized radial axes; preserve axis order, scale, and direction across every series.",
-    source: "diagram-design",
-  },
-  treemap: {
-    label: "Treemap",
-    expression: "Encode part-to-whole magnitude by rectangle area within explicit hierarchy; preserve parent totals and avoid implying rank from position.",
-    source: "diagram-design",
-  },
-  scatter: {
-    label: "Scatter",
-    expression: "Position observations by two measured quantitative variables; preserve axis scales, units, outliers, and uncertainty about correlation.",
-    source: "diagram-design",
-  },
-  sankey: {
-    label: "Sankey",
-    expression: "Encode conserved quantity through splits and merges using proportional ribbon width; preserve node totals, flow direction, and units.",
-    source: "diagram-design",
-  },
-} as const satisfies Record<string, ChartDefinition>;
-
-export type ChartTemplate = keyof typeof chartDefinitions;
-
-export const chartTemplates = Object.keys(chartDefinitions) as ChartTemplate[];
-
-export const visualizationDefinitions = {
-  diagram: diagramDefinitions,
-  chart: chartDefinitions,
-} as const;
-
-export const diagramCategories = Array.from(
-  new Set(Object.values(diagramDefinitions).map((definition) => definition.category)),
-);
-
-export function diagramDefinition(type: DiagramType): DiagramDefinition {
-  return diagramDefinitions[type];
-}

package/design/README.md

@@ -1,17 +0,0 @@
-# Find an authoring resource
-
-[AUTHORING](../AUTHORING.md) owns design defaults and font suggestions. Consult
-the resources below for a specific need; none impose a composition or reading order.
-
-| Need | Where | Use |
-| --- | --- | --- |
-| Choose the rules | [Authoring mode](../AUTHORING.md#authoring-mode) | Default (original rules) or dynamic (relaxed visual rules); optional paired comparison |
-| Choose a visual structure | [Semantic patterns](semantic-patterns.md) | Audience question → relationships → visual structure |
-| Review rendered pages | [Review categories](visual-review.md) | Text, typography, layout, color/theme and visuals; optional parallel review |
-| Colors only | [palettes](palettes/README.md) | Base, eight light/dark palettes, Mineral/Botanical light candidates |
-| Typography + colors | [themes](themes/README.md) | Ready theme roles; no content or layout |
-| Art direction | [Technical product language](visual-languages/technical-product.md) | How imagery, emphasis and diagrams work together |
-| Add a deck | [Deck directory guide](../slides/README.md) | Routes, prompt records and example deliverables |
-
-Start freely when no example fits. Reuse implementation, not composition.
-A case-specific check is not a design rule.

package/design/palettes/README.md

@@ -1,14 +0,0 @@
-# Color palettes
-
-Color resources only; no typography, layout or content.
-
-- [index.ts](index.ts): `resolvePalette(name, 'paper' | 'night')` for Plex,
-  Precision, Editorial, Blue–cyan, Orange–coral, Yellow, Green and Graphite.
-  Contains surface/text roles, categorical colors, sequential ramps and status.
-- [candidates.ts](candidates.ts): `lightPalettes`, Mineral and Botanical,
-  including named series and diverging ramps. Light-only; not auto-inverted.
-- [base.ts](base.ts): original specimen roles, still re-exported by
-  `lib/taste.ts` for existing runtime consumers. Definitions are not duplicated.
-
-Choose only the needed series. Keep category meaning separate from status.
-For typography with a palette, use [themes](../themes/README.md).

package/design/palettes/base.ts

@@ -1,14 +0,0 @@
-// Original specimen palette. Named palettes build on these color roles.
-export const palettes = {
-  paper: {
-    bg: '#FFFFFF', fg: '#000000', muted: '#3F4A54', line: '#BCC6CE',
-    surface: '#EAEFF3', wash: '#E3EAF8', accent: '#2458C7', inverse: '#FFFFFF',
-    emphasis: '#98451F', emphasisWash: '#F1E1D4',
-  },
-  night: {
-    bg: '#000000', fg: '#FFFFFF', muted: '#B2C1CC', line: '#4C6072',
-    surface: '#202E3C', wash: '#233857', accent: '#97B9FF', inverse: '#000000',
-    emphasis: '#F0AC7D', emphasisWash: '#443025',
-  },
-};
-export type Palette = typeof palettes.paper;

package/design/palettes/candidates.ts

@@ -1,19 +0,0 @@
-// Approved light-only color candidates. No layout or typography.
-export const lightPalettes = [
-  {
-    name: 'Mineral', bg: '#FFFFFF', ink: '#18232D', muted: '#526170',
-    surface: '#F0F3F5', line: '#CBD3DA', accent: '#2458B8', wash: '#E8EFFB',
-    colors: ['#3569B7', '#167D8D', '#8061A8', '#A27616', '#BA536A', '#59734A'],
-    names: ['Cobalt', 'Petrol', 'Iris', 'Ochre', 'Rose', 'Moss'],
-    sequential: ['#E8EFFB', '#B9CDEA', '#7CA2D4', '#4677B8', '#24518D'],
-    diverging: ['#A14B26', '#D79A73', '#F0F1F2', '#83B9C1', '#216775'],
-  },
-  {
-    name: 'Botanical', bg: '#FFFFFF', ink: '#222923', muted: '#59625B',
-    surface: '#F1F4F1', line: '#CBD4CB', accent: '#32634D', wash: '#E7F0E9',
-    colors: ['#43785B', '#5375B5', '#B45A38', '#8B5B96', '#8A781B', '#287F92'],
-    names: ['Fern', 'Denim', 'Terracotta', 'Plum', 'Brass', 'Lake'],
-    sequential: ['#E7F0E9', '#B9D1BF', '#83AD90', '#528566', '#2D5941'],
-    diverging: ['#86508D', '#BE9AC1', '#F0F1F2', '#8DB7A8', '#326C59'],
-  },
-];

package/design/palettes/index.ts

@@ -1,78 +0,0 @@
-import { palettes, type Palette } from './base.ts';
-
-// Color-only resources. These are our adaptations, not extracted brand tokens.
-// Keep category identity/order stable across modes; status is a separate channel.
-export const paletteNames = ['Plex', 'Precision', 'Editorial', 'Blue–cyan', 'Orange–coral', 'Yellow', 'Green', 'Graphite'] as const;
-export type PaletteName = typeof paletteNames[number];
-export type PaletteMode = 'paper' | 'night';
-type SixColors = [string, string, string, string, string, string];
-type FiveColors = [string, string, string, string, string];
-type PaletteDefinition = {
-  accent: [string, string];
-  wash: [string, string];
-  surface: [string, string];
-  categorical: [SixColors, SixColors];
-  sequential: [FiveColors, FiveColors];
-};
-
-const definitions: Record<PaletteName, PaletteDefinition> = {
-  Plex: {
-    accent: ['#2458B8', '#91B9FF'], wash: ['#EAF0FA', '#18273F'], surface: ['#F1F3F5', '#171B21'],
-    categorical: [['#3569B7', '#167D8D', '#8061A8', '#A27616', '#BA536A', '#59734A'], ['#82AEF2', '#63C3CD', '#BAA0DF', '#D7B55B', '#E899AA', '#A6C58E']],
-    sequential: [['#E8EFFB', '#B9CDEA', '#7CA2D4', '#4677B8', '#24518D'], ['#192B45', '#305381', '#4C7CB4', '#82AEF2', '#C2DAFF']],
-  },
-  Precision: {
-    accent: ['#3D3A8F', '#B6B2FF'], wash: ['#EEEFFD', '#22213D'], surface: ['#F2F2F5', '#19191F'],
-    categorical: [['#4B469D', '#2F6A8F', '#76538F', '#8A5A25', '#9A475F', '#4F7040'], ['#AAA5F4', '#82BCE2', '#C69DDF', '#DEB071', '#E89AAF', '#A6C88D']],
-    sequential: [['#EEEFFD', '#C9C7EC', '#9792D0', '#6761AE', '#3D3A8F'], ['#23223F', '#454278', '#716CB2', '#AAA5F4', '#D9D7FF']],
-  },
-  Editorial: {
-    accent: ['#93451F', '#F2B38C'], wash: ['#F6ECE5', '#30231D'], surface: ['#F4F3F2', '#1B1918'],
-    categorical: [['#AF5934', '#387684', '#8A619A', '#8C791D', '#AD5071', '#4D7757'], ['#EFA77F', '#86C3CD', '#C6A3D5', '#D4C17A', '#E9A2BF', '#A0C9A5']],
-    sequential: [['#F7EEE7', '#EACAB4', '#CD9875', '#AB6A45', '#794021'], ['#35271F', '#664832', '#A07350', '#D5A17B', '#F6D5B8']],
-  },
-  'Blue–cyan': {
-    accent: ['#007C88', '#63D6E3'], wash: ['#EAF9FA', '#112E33'], surface: ['#F0F9FA', '#121D20'],
-    categorical: [['#007C88', '#007F8E', '#275F9A', '#95631F', '#A64D68', '#39724F'], ['#63D6E3', '#79E3EB', '#8FBCEF', '#DBB267', '#E799AF', '#89C9A1']],
-    sequential: [['#EAF9FA', '#B7E7EA', '#72C3CA', '#2B9AA5', '#007C88'], ['#123136', '#225D65', '#388F99', '#63C6D0', '#A8EFF4']],
-  },
-  'Orange–coral': {
-    accent: ['#A23E20', '#FFB28E'], wash: ['#FFF0E8', '#33231D'], surface: ['#F5F3F2', '#1D1917'],
-    categorical: [['#BA5A31', '#B94970', '#4876AA', '#247D76', '#8861A3', '#92771D'], ['#F3A47C', '#ED99B7', '#91B8E8', '#76C7BE', '#BFA3DD', '#D7BF70']],
-    sequential: [['#FCEDE5', '#EDC3AD', '#D89370', '#B66A44', '#88411E'], ['#36251F', '#6D4430', '#A9704D', '#DF9F73', '#FFD1AC']],
-  },
-  Yellow: {
-    accent: ['#756000', '#F1D66D'], wash: ['#FBF5D9', '#302A17'], surface: ['#F5F5F0', '#1C1C18'],
-    categorical: [['#95761C', '#416FA4', '#A95670', '#397D71', '#8862A2', '#AD612C'], ['#E0C264', '#91B6E5', '#E1A1B6', '#8AC8B8', '#BFA5D9', '#E4B181']],
-    sequential: [['#F8F3D9', '#E5D9A4', '#C4B369', '#9B8433', '#705C12'], ['#302B19', '#5A4C25', '#917A38', '#C9AF59', '#F5DE91']],
-  },
-  Green: {
-    accent: ['#216B3D', '#98DCAF'], wash: ['#EAF3ED', '#1A2D22'], surface: ['#F1F5F2', '#171D19'],
-    categorical: [['#43785B', '#5375B5', '#B45A38', '#8B5B96', '#8A781B', '#287F92'], ['#91C7A6', '#9AB8EA', '#E9AB8A', '#CBA4D5', '#D1C278', '#7BC8D8']],
-    sequential: [['#E7F0E9', '#B9D1BF', '#83AD90', '#528566', '#2D5941'], ['#1B3023', '#325A40', '#578569', '#91C7A6', '#CBECD6']],
-  },
-  Graphite: {
-    accent: ['#242424', '#F2F2F2'], wash: ['#EDEDED', '#242424'], surface: ['#F5F5F5', '#171717'],
-    categorical: [['#3268B5', '#187F86', '#8A5DA6', '#A87922', '#B55372', '#5A7847'], ['#85B2F3', '#77C9CF', '#C3A2E0', '#DDBB78', '#E6A0B8', '#ADC991']],
-    sequential: [['#EFEFEF', '#CBCBCB', '#999999', '#666666', '#303030'], ['#282828', '#505050', '#838383', '#B8B8B8', '#EFEFEF']],
-  },
-};
-
-export function resolvePalette(name: PaletteName, mode: PaletteMode): Palette & {
-  categorical: SixColors; sequential: FiveColors; status: { complete: string; attention: string; blocked: string };
-} {
-  const d = definitions[name], dark = mode === 'night', i = dark ? 1 : 0;
-  return {
-    ...palettes[mode],
-    bg: dark ? '#000000' : '#FFFFFF', fg: dark ? '#F2F2F2' : '#20242A',
-    muted: dark ? '#B7BCC4' : '#505B68', line: dark ? '#454B54' : '#C9CFD6',
-    ...(name === 'Graphite' ? {
-      fg: dark ? '#F2F2F2' : '#202020', muted: dark ? '#B8B8B8' : '#595959',
-      line: dark ? '#454545' : '#CECECE', emphasis: d.accent[i], emphasisWash: d.wash[i],
-    } : {}),
-    accent: d.accent[i], wash: d.wash[i], surface: d.surface[i],
-    categorical: [...d.categorical[i]], sequential: [...d.sequential[i]],
-    status: dark ? { complete: '#94D3AB', attention: '#E3C477', blocked: '#F0A1AF' }
-      : { complete: '#276749', attention: '#946200', blocked: '#AC3348' },
-  };
-}

package/design/review/color-theme.md

@@ -1,44 +0,0 @@
-# Color / theme review
-
-Owns palette use across the deck. Apply existing
-[theme guidance](../../AUTHORING.md#taste-and-creative-freedom) and
-[color roles](../palettes/README.md); this category adds no new style rules.
-
-- Check palette roles, background and visual emphasis against the brief and
-  selected mode. Both modes use the original white-background/main-accent
-  fallback unless the user supplies another direction. Dynamic permits local
-  emphasis fills, not an automatic dark or colored canvas.
-- Check text/mark contrast on actual surfaces at viewing size. Confirm category
-  and status meanings stay consistent and have cues beyond color alone.
-
-Leave font rendering to typography and container structure to visuals.
-Use the shared [review process](../visual-review.md#independent-review).
-
-## Measure a declared solid pair
-
-Use [contrastRatio](../../lib/contrast.ts) for opaque six-digit sRGB hex colors.
-From the kit directory, this checks one declared normal-text pair:
-
-```sh
-node --input-type=module <<'JS'
-import { contrastRatio } from './lib/contrast.ts';
-const foreground = '#505B68', background = '#FFFFFF';
-const ratio = contrastRatio(foreground, background);
-console.log({ foreground, background, ratio, minimum: 4.5 });
-if (ratio < 4.5) process.exitCode = 1;
-JS
-```
-
-Use actual palette roles or rendered values for the pair under review. Record
-the page/element, pair, ratio and applicable threshold. Compare the unrounded
-ratio: rounding 4.478 to 4.5 does not make it pass. Normal text needs 4.5:1;
-large text can use 3:1 only when it qualifies at the delivered size (at least
-24 CSS px regular or about 18.67 CSS px bold). A 32-unit SVG label scaled to
-half size is not 32 CSS px. Contrast does not establish comfortable readability.
-
-This helper does not discover backgrounds, classify text, composite opacity or
-inspect images, gradients and overlapping shapes. Confirm the solid pair really
-applies in the render. For other surfaces, measure the actual composite with an
-appropriate tool and inspect the result; otherwise report contrast as Not verified.
-Never report an unmeasured ratio. The existing theme browser check's containing-
-rectangle assumption remains specimen-specific, not a general background solver.

package/design/review/layout.md

@@ -1,16 +0,0 @@
-# Layout review
-
-Owns composition and spatial relationships. Inspect the rendered deck for
-reading order, grouping and balance. Leave glyph readability to typography,
-diagram meaning and container structure to visuals, and factual claims to text review.
-
-| Check | Guidance |
-| --- | --- |
-| Content balance | Recompose when one column runs far below its neighbor and leaves a stranded empty area. Equal heights are unnecessary. |
-| Heading attachment | Give the heading more separation from the preceding section than from its own content. Respect visible group boundaries. |
-| Evidence-led emphasis | Question the giant-number, small-label, supporting-stats formula. Use it when the metric explains the point, with scope and evidence intact. |
-| Meaningful grouping | Repeated icon–heading–body cards can flatten different ideas into equal weight. Group and prioritize according to meaning. |
-| Paired-row alignment | Align short headings with the first line of their descriptions, not the vertical center of multiline copy. Check visible text alignment as well as element bounds. |
-| Spacing hierarchy | Avoid identical gaps between unrelated sections and within closely related content. A consistent spacing scale is still useful. |
-
-Use the shared [review process](../visual-review.md#independent-review).

package/design/review/text.md

@@ -1,18 +0,0 @@
-# Text review
-
-Owns meaning and wording. Use the brief and sources to verify claims and caveats;
-apply the [writing tone](../../AUTHORING.md#writing-tone). Leave font size and
-visual placement to typography/layout review.
-
-| Check | Guidance |
-| --- | --- |
-| Headline first | Inspect the rendered reading order against the authoring policy. For every eyebrow, brand label and numbered section heading, name the information lost if it were removed. Remove it when that information is already supplied by the headline, nearby content or page navigation, unless explicitly requested. Preserve essential context and required attribution. |
-| Information economy | Avoid restating one message in a card’s headline, badge and note. Repeated values in tables or parallel items can be necessary. |
-| Page purpose | State the audience question answered by the page. Can a reader identify the current state, the decision or mechanism, and its consequence without narration? Replace abstract choice labels and ambiguous pronouns with concrete outcomes and named actors. |
-| Metadata versus evidence | Remove recurring deck metadata unless requested or required. Keep page-specific citations, units, synthetic-data disclosures and material caveats with the evidence; do not remove those as footer clutter. |
-| Relevant limitations | Attach requirements and limits to the mechanism or claim they constrain. Do not give unrelated caveats equal weight on a next-action page or hide essential limits in notes merely to reduce density. |
-| Sentence rhythm | Check for a repeated dash-heavy cadence across the copy. Keep occasional dashes that improve reading. |
-| Concrete claims | Name the capability or supported outcome. Remove claims that could describe any product. |
-| Direct explanation | Remove manufactured rebuttals such as “Not a feature. A platform.” and “not X, but Y.” Explain genuine distinctions directly. |
-
-Use the shared [review process](../visual-review.md#independent-review).

package/design/review/typography.md

@@ -1,15 +0,0 @@
-# Typography review
-
-Owns text rendering and reading comfort. Inspect full/half-size renders for
-legibility, hierarchy, wrapping and clipping; verify actual fonts and weights
-against the chosen [theme](../themes/README.md). Leave wording to text review
-and section placement to layout review.
-
-| Check | Guidance |
-| --- | --- |
-| Font category | Both modes use sans-serif unless the brief directs otherwise. Dynamic may vary typographic emphasis without changing the font category. Verify language coverage, loaded weights and readability in both modes. |
-| Useful numbering | Remove repeated micro-indices beside headings when they add no ordering information. Keep useful step and page numbers readable. |
-| Subheading distinction | Apply the mode table: default requires typographic emphasis; dynamic may establish hierarchy through placement, color or grouping. Check the result at review size. |
-| Readable line measure | Keep paragraph lines easy to track into the next line. Judge the actual font and viewing size; avoid imposing a web character limit on every slide label. |
-
-Use the shared [review process](../visual-review.md#independent-review).

package/design/review/visuals.md

@@ -1,31 +0,0 @@
-# Visuals review
-
-Owns diagrams, charts, imagery and containers. Apply the existing
-[accuracy requirements](../../AUTHORING.md#requirements): verify arrow direction,
-label/value associations, chart scales, asset provenance and faithful crops.
-Text review verifies the underlying claims; this review checks their visual encoding.
-Leave page arrangement to layout and color assignments to color/theme.
-
-Apply the [mode table](../../AUTHORING.md#authoring-mode) first. The allowances
-below for emphasis fills, framing, reinforcing arrows and filled heads apply to
-dynamic mode or an explicit user direction; they do not override default mode's
-original restrictions. Geometry and factual checks apply in both modes.
-
-| Check | Guidance |
-| --- | --- |
-| Visual explanation | Would a diagram, image or annotated artifact make the relationships easier to grasp? Do not accept prose-only treatment merely because it is in bounds, or require a diagram when it adds nothing. |
-| Purposeful boundaries | Judge whether surfaces improve grouping, emphasis or reading order in the chosen direction. Remove competing layers, not all layers that could be replaced by whitespace. Keep meaningful object boundaries and actual controls. |
-| Rules and frames | Dividers must stop at the region they separate, not cross shared copy or subsequent sections. Give text clearance from borders and accent rules. Frames and rails may support grouping or emphasis; distinguish intentional treatment from accidental-looking missing edges. |
-| Paragraphs versus rows | Apply the authoring boundary policy: independent text groups can use whitespace; corresponding table or paired rows may benefit from rules. If rules establish the rows, check for a clear ending before notes, usually a bottom rule. Do not require borders merely because text has columns. |
-| Table ending versus page footer | A closing rule belongs to the table it ends. Do not extend it to the page bottom or add a second separator for generic metadata or a standalone page number. |
-| Canvas padding | Check preview and requested export for unintended padding around differently proportioned artwork. Use the intended aspect ratio where supported or compose the surrounding space deliberately; intentional color bands are not a defect. |
-| Emphasis backgrounds | Does the fill help the audience notice, group or navigate the content? Hierarchy, rhythm and emphasis are valid uses alongside state and evidence. Check contrast and avoid competing emphasis; when color encodes meaning, check that labels or symbols agree. |
-| Connector endpoints | Every arrow needs an identifiable source and destination: a node, participant, lane or explicit continuation. Boxes are optional; meaningful attachment is not. Check what each endpoint refers to, not just its coordinates or alignment. Connectors should meet their intended anchors without stray tails or gaps; extend beyond them only to convey meaning. |
-| Connector routing | Optimize for a clear, coherent route, not the fewest bends. Orthogonal corners are welcome when they support reading order, aligned entry/exit points or label placement. Remove needless doglegs, but do not replace useful elbows with awkward diagonal fans or detach a sequence rail from its stages. Place turns deliberately, with clearance from nodes, labels, boundaries and other connectors; avoid near-touches or crossings that imply unintended junctions. |
-| Corresponding bends | For equivalent or mirrored relationships, check that turn positions, offsets and spacing align or mirror consistently. Preserve asymmetry when different endpoints, obstacles or meanings require it; do not add bends merely to force symmetry. |
-| Arrow purpose | Check that arrows make the intended relationship easier to follow without implying unsupported transitions or dependencies. Reinforcing a relationship stated in words is useful when it speeds understanding, not automatically redundant. |
-| Arrowheads | Open and filled heads are valid. Check consistency with the chosen notation, alignment with shafts, and clean joins without spikes, gaps or protruding stems. Inspect at full and review size. |
-
-Inspect the render: DOM nesting alone cannot establish whether a boundary helps,
-and an HTML card detector can miss nested SVG shapes.
-Use the shared [review process](../visual-review.md#independent-review).

package/design/semantic-patterns.md

@@ -1,43 +0,0 @@
-# Choose a visual by meaning
-
-Start with the audience's question, not a favorite layout. These are choices,
-not templates. Choose the primary medium from the source, audience and brief;
-plain text or a large image may be enough. Authoring mode changes visual rules, not
-the truth of the relationships. More detail requires more supported explanation,
-not more nodes or arrows by default.
-
-## Pick the relationship
-
-| Question | Pattern | Keep clear |
-| --- | --- | --- |
-| What happens next? | Process / sequence | Input, steps, output and blockers. Label branches and return paths; pending is not approved. |
-| Which option fits? | Comparison / decision | Same criteria, units and scope. Explain the recommendation without hiding drawbacks or inventing scores. |
-| What belongs to what? | Hierarchy / containment | Consistent parent–child meaning. Use a map when shared ownership or cross-links matter. |
-| What connects? | System map | Named entities, meaningful boundaries and labeled connections. Use a sequence when event order is the story. |
-| What should I notice? | Annotated detail | Enough context to locate the detail, large evidence and nearby labels. Identify crops and mockups; don't invent specifications. |
-
-Choose theme and composition to suit the relationship. Any pattern can be
-restrained or expressive; decorative shapes must not imply data.
-
-## Infer the form; preserve the meaning
-
-People do not need to name a diagram or chart type. In Auto, infer a suitable form
-from the goal, audience, supplied relationships and data. An explicitly selected form is binding:
-preserve it and ask before switching, including to another component kind. Never
-silently reset explicit selection to Auto. Honor notation requested in the intent
-or brief even in Auto. When ambiguity changes the explanation, ask what should be emphasized rather than
-asking the person to choose from a taxonomy.
-
-Keep specialized semantics when they matter: message order in a sequence,
-guarded transitions in a state machine, enclosure for containment, and honest
-scales for quantities. Use editable vectors when a standard draft cannot express
-them. In Auto, update the returned diagram type or chart template to match the chosen form
-without changing its selection mode.
-
-Diagram Design and Archify are references, not product specifications. Borrow
-useful techniques with attribution; do not pursue their catalog coverage or
-force domain recipes into first-class types. Evaluate the result against the
-explanation goal, factual fidelity and editability.
-
-Render and inspect: is the relationship clear without narration? Are facts,
-arrows and labels correct and readable? No aesthetic score or required layout.