back to gallery
design language·custody-rite-os

Custody Rite OS

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
Custody Rite OS is an austere identity operating environment for deciding what a person, model, archive, or prosthetic subsystem is allowed to remember. Authentication becomes a quiet custody ceremony of permission clauses, memory mounts, biometric tolerances, and revocation prompts under forensic glass. It borrows from Japanese technical manuals, legal evidence sheets, and manga schematic marginalia without using character art or cyberpunk spectacle.
values
Identity as filesystem custodyLegible permission before controlClinical restraintCold archival durabilityMicrotypographic precisionHuman-factors claritySparse one-bit feedback
anti-values
×No green matrix rain×No generic hacker dashboards×No neon cyberpunk×No character fan art×No SaaS card grids×No copied Optical Shellcode Terminal patterns
tokens
borders4 items
accent width
2px
character
near-invisible carbon hairlines with cyan right-angle bracket corners only on authenticated objects
default width
1px
style
solid
colors12 items
accent
#008CA8
background
#F7F9FA
border
#D6DDE2
error
#8A1F2D
info
#006B84
muted
#7A838B
primary
#111820
secondary
#5F6B76
success
#1F6B5B
surface
#FFFFFF
text
#111820
warning
#8B6A20
motion3 items
duration
140ms
easing
steps(2,end)
philosophy
quiet e-paper refresh, binary cursor changes, and clipped inspection reveals rather than smooth decorative animation
radii5 items
full
9999px
lg
16px
md
0px
none
0px
sm
0px
shadows3 items
lg
0 24px 60px rgba(17,24,32,.08)
md
0 0 0 1px rgba(17,24,32,.06)
sm
none
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 40, 48, 64, 96, 128
surfaces3 items
bg pattern
32px baseline grid with corner registration marks and a fixed perforated custody spine
card style
square evidence panels with registration ticks and custody labels, never rounded SaaS cards
treatment
cold archive white fields, translucent forensic wells, and faint slate scan bands separated by carbon hairlines
typography10 items
base size
16px
body font
BIZ UDPGothic
display letter spacing
-0.04em
display line height
1.12
google fonts url
https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=Fragment+Mono&family=Noto+Serif+JP:wght@600;700&display=swap
heading font
Noto Serif JP
letter spacing
-0.02em
line height
1.52
mono font
Fragment Mono
scale ratio
1.2
rules
composition
Anchor every screen with a fixed perforated custody spine before placing any content modules.Use one dominant identity kernel or inspection well; supporting panels must be smaller and denser.Balance procedural text density with at least one severe blank field that represents unmounted memory.Create hierarchy through placement, type mode, and bracket geometry before relying on color.Interrupt the grid with one full-height liturgy rail or oversized forensic well so the page never becomes equal cards.
density

Medium-high procedural text balanced by severe empty wells; tight 4-8px clusters sit inside 96-128px page separations.

hierarchy
Noto Serif JP display headlines name the custody ritual with -0.04em tracking and tight leading.Fragment Mono labels carry paths, hashes, and permission clauses in uppercase microtype.BIZ UDPGothic body text explains consequences in calm clinical prose.Cyan indicates authenticated state only; warnings and errors remain textual and sparse.
signature patterns
Perforated custody spine: a fixed vertical rail of square holes, section numbers, and rotated Japanese labels establishes the document as governed evidence.Permission liturgy bands: narrow mono text strips repeat allow, deny, revoke, and mount clauses with clipped borders and baseline ticks.Filesystem memory diagram: bracketed archive paths connect mounted identity fragments through squared nodes and thin orthogonal rails.Cyan authentication brackets: two-pixel right-angle corners and tiny pips surround only verified objects, producing one-bit feedback without neon glow.Forensic glass well: a large mostly empty inspection pane with faint scan bands and registration corners shows absence as an active design element.
layout
density

Procedural text plus 30-40 percent empty inspection field; inner module padding stays 16-24px while inter-zone gaps expand to 96-128px.

grid
Desktop uses a 12-column grid with fixed 56px custody spine, 24px gutters, and 8px baseline; tablet collapses to two zones; mobile converts the spine to a top perforation rail.
responsive

Breakpoints at 1100px, 768px, and 520px reflow the asymmetric shell from three zones to two zones to a single procedural column.

whitespace

Blankness represents unmounted memory and legal separation, so empty wells must remain materially larger than content clusters.

guidance
do
  • Use cold white and carbon ink with sparse cyan.
  • Write copy as permission clauses, memory paths, custody prompts, and diagnostic tolerances.
  • Use square panels, hairlines, baseline grids, and spine perforations.
  • Support vertical Japanese labels and mixed script marginalia.
  • Make status textual first and chromatic second.
  • Keep one dominant inspection well larger than all supporting panels.
avoid
  • No green matrix rain or neon cyberpunk.
  • No generic hacker dashboards or SaaS card grids.
  • No character art; manga influence is structural only.
  • Do not flood the page with cyan or synthetic gradients.
  • Do not use browser-default forms or unstylized controls.
  • Do not copy Optical Shellcode Terminal patterns or palette balance.
katagami spec
# Custody Rite OS

## Philosophy

Custody Rite OS is an austere identity operating environment for deciding what a person, model, archive, or prosthetic subsystem is allowed to remember. Authentication becomes a quiet custody ceremony of permission clauses, memory mounts, biometric tolerances, and revocation prompts under forensic glass. It borrows from Japanese technical manuals, legal evidence sheets, and manga schematic marginalia without using character art or cyberpunk spectacle.

### Values

- Identity as filesystem custody
- Legible permission before control
- Clinical restraint
- Cold archival durability
- Microtypographic precision
- Human-factors clarity
- Sparse one-bit feedback

### Anti-Values

- No green matrix rain
- No generic hacker dashboards
- No neon cyberpunk
- No character fan art
- No SaaS card grids
- No copied Optical Shellcode Terminal patterns

### Visual Character

- White evidence surfaces use carbon hairlines, square corners, registration ticks, and no decorative shadows so panels read as custody documents rather than cards.
- Permission liturgy bands combine mono shell clauses with vertical Japanese marginalia, creating narrow procedural strips along the page edges.
- Sparse memory filesystem diagrams appear as bracketed paths, node rails, and mounted archive blocks instead of conventional charts or analytics widgets.
- Tiny desaturated cyan authentication pips and right-angle brackets mark only verified states, never flooding whole surfaces with color.
- Large forensic glass inspection wells create severe blank fields where biometric residue, memory absence, and consent gaps can be examined.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: near-invisible carbon hairlines with cyan right-angle bracket corners only on authenticated objects
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#008CA8` |
| background | `#F7F9FA` |
| border | `#D6DDE2` |
| error | `#8A1F2D` |
| info | `#006B84` |
| muted | `#7A838B` |
| primary | `#111820` |
| secondary | `#5F6B76` |
| success | `#1F6B5B` |
| surface | `#FFFFFF` |
| text | `#111820` |
| warning | `#8B6A20` |

### Motion

- **Duration**: 140ms
- **Easing**: steps(2,end)
- **Philosophy**: quiet e-paper refresh, binary cursor changes, and clipped inspection reveals rather than smooth decorative animation

### Radii

- **Full**: 9999px
- **Lg**: 16px
- **Md**: 0px
- **None**: 0px
- **Sm**: 0px

### Shadows

- **Lg**: 0 24px 60px rgba(17,24,32,.08)
- **Md**: 0 0 0 1px rgba(17,24,32,.06)
- **Sm**: none

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,40,48,64,96,128]

### Surfaces

- **Bg Pattern**: 32px baseline grid with corner registration marks and a fixed perforated custody spine
- **Card Style**: square evidence panels with registration ticks and custody labels, never rounded SaaS cards
- **Treatment**: cold archive white fields, translucent forensic wells, and faint slate scan bands separated by carbon hairlines

### Typography

- **Base Size**: 16px
- **Body Font**: BIZ UDPGothic
- **Display Letter Spacing**: -0.04em
- **Display Line Height**: 1.12
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=Fragment+Mono&family=Noto+Serif+JP:wght@600;700&display=swap
- **Heading Font**: Noto Serif JP
- **Letter Spacing**: -0.02em
- **Line Height**: 1.52
- **Mono Font**: Fragment Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

- Anchor every screen with a fixed perforated custody spine before placing any content modules.
- Use one dominant identity kernel or inspection well; supporting panels must be smaller and denser.
- Balance procedural text density with at least one severe blank field that represents unmounted memory.
- Create hierarchy through placement, type mode, and bracket geometry before relying on color.
- Interrupt the grid with one full-height liturgy rail or oversized forensic well so the page never becomes equal cards.

### Density

Medium-high procedural text balanced by severe empty wells; tight 4-8px clusters sit inside 96-128px page separations.

### Hierarchy

- Noto Serif JP display headlines name the custody ritual with -0.04em tracking and tight leading.
- Fragment Mono labels carry paths, hashes, and permission clauses in uppercase microtype.
- BIZ UDPGothic body text explains consequences in calm clinical prose.
- Cyan indicates authenticated state only; warnings and errors remain textual and sparse.

### Signature Patterns

- Perforated custody spine: a fixed vertical rail of square holes, section numbers, and rotated Japanese labels establishes the document as governed evidence.
- Permission liturgy bands: narrow mono text strips repeat allow, deny, revoke, and mount clauses with clipped borders and baseline ticks.
- Filesystem memory diagram: bracketed archive paths connect mounted identity fragments through squared nodes and thin orthogonal rails.
- Cyan authentication brackets: two-pixel right-angle corners and tiny pips surround only verified objects, producing one-bit feedback without neon glow.
- Forensic glass well: a large mostly empty inspection pane with faint scan bands and registration corners shows absence as an active design element.

## Layout

### Density

Procedural text plus 30-40 percent empty inspection field; inner module padding stays 16-24px while inter-zone gaps expand to 96-128px.

### Grid

Desktop uses a 12-column grid with fixed 56px custody spine, 24px gutters, and 8px baseline; tablet collapses to two zones; mobile converts the spine to a top perforation rail.

### Responsive

Breakpoints at 1100px, 768px, and 520px reflow the asymmetric shell from three zones to two zones to a single procedural column.

### Whitespace

Blankness represents unmounted memory and legal separation, so empty wells must remain materially larger than content clusters.

## Guidance

### Do

- Use cold white and carbon ink with sparse cyan.
- Write copy as permission clauses, memory paths, custody prompts, and diagnostic tolerances.
- Use square panels, hairlines, baseline grids, and spine perforations.
- Support vertical Japanese labels and mixed script marginalia.
- Make status textual first and chromatic second.
- Keep one dominant inspection well larger than all supporting panels.

### Don't

- No green matrix rain or neon cyberpunk.
- No generic hacker dashboards or SaaS card grids.
- No character art; manga influence is structural only.
- Do not flood the page with cyan or synthetic gradients.
- Do not use browser-default forms or unstylized controls.
- Do not copy Optical Shellcode Terminal patterns or palette balance.

### Accessibility

Strong contrast, non-color status labels, 40px targets, visible focus brackets, no essential information solely in vertical text, and reduced-motion-safe stepped state changes.

### Usage Context

Identity governance, memory consent, clinical cybernetic calibration, archival shell manuals, prosthetic permission systems, and forensic AI audit screens.
DESIGN.md
---
version: "alpha"
name: "Custody Rite OS"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#008CA8"
  background: "#F7F9FA"
  border: "#D6DDE2"
  error: "#8A1F2D"
  info: "#006B84"
  muted: "#7A838B"
  primary: "#111820"
  secondary: "#5F6B76"
  success: "#1F6B5B"
  surface: "#FFFFFF"
  text: "#111820"
  warning: "#8B6A20"
typography:
  headline-lg:
    fontFamily: "Noto Serif JP"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Noto Serif JP"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "BIZ UDPGothic"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Fragment Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "16px"
  md: "0px"
  none: "0px"
  sm: "0px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "40px"
  4xl: "48px"
  step-8: "64px"
  step-9: "96px"
  step-10: "128px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Custody Rite OS

## Overview

Custody Rite OS is an austere identity operating environment for deciding what a person, model, archive, or prosthetic subsystem is allowed to remember. Authentication becomes a quiet custody ceremony of permission clauses, memory mounts, biometric tolerances, and revocation prompts under forensic glass. It borrows from Japanese technical manuals, legal evidence sheets, and manga schematic marginalia without using character art or cyberpunk spectacle.

### Values

- Identity as filesystem custody
- Legible permission before control
- Clinical restraint
- Cold archival durability
- Microtypographic precision
- Human-factors clarity
- Sparse one-bit feedback

### Anti-Values

- No green matrix rain
- No generic hacker dashboards
- No neon cyberpunk
- No character fan art
- No SaaS card grids
- No copied Optical Shellcode Terminal patterns

### Visual Character

- White evidence surfaces use carbon hairlines, square corners, registration ticks, and no decorative shadows so panels read as custody documents rather than cards.
- Permission liturgy bands combine mono shell clauses with vertical Japanese marginalia, creating narrow procedural strips along the page edges.
- Sparse memory filesystem diagrams appear as bracketed paths, node rails, and mounted archive blocks instead of conventional charts or analytics widgets.
- Tiny desaturated cyan authentication pips and right-angle brackets mark only verified states, never flooding whole surfaces with color.
- Large forensic glass inspection wells create severe blank fields where biometric residue, memory absence, and consent gaps can be examined.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#008CA8` |
| background | `#F7F9FA` |
| border | `#D6DDE2` |
| error | `#8A1F2D` |
| info | `#006B84` |
| muted | `#7A838B` |
| primary | `#111820` |
| secondary | `#5F6B76` |
| success | `#1F6B5B` |
| surface | `#FFFFFF` |
| text | `#111820` |
| warning | `#8B6A20` |

## Typography

- **Headline-Lg**: Noto Serif JP, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Noto Serif JP, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: BIZ UDPGothic, 16px, weight 400, line-height 1.52.
- **Label-Md**: Fragment Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `40px`
- **4xl**: `48px`
- **Step-8**: `64px`
- **Step-9**: `96px`
- **Step-10**: `128px`

### Density

Procedural text plus 30-40 percent empty inspection field; inner module padding stays 16-24px while inter-zone gaps expand to 96-128px.

### Grid

Desktop uses a 12-column grid with fixed 56px custody spine, 24px gutters, and 8px baseline; tablet collapses to two zones; mobile converts the spine to a top perforation rail.

### Responsive

Breakpoints at 1100px, 768px, and 520px reflow the asymmetric shell from three zones to two zones to a single procedural column.

### Whitespace

Blankness represents unmounted memory and legal separation, so empty wells must remain materially larger than content clusters.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 60px rgba(17,24,32,.08)
- **Md**: 0 0 0 1px rgba(17,24,32,.06)
- **Sm**: none

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `16px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`

### Surfaces

- **Bg Pattern**: 32px baseline grid with corner registration marks and a fixed perforated custody spine
- **Card Style**: square evidence panels with registration ticks and custody labels, never rounded SaaS cards
- **Treatment**: cold archive white fields, translucent forensic wells, and faint slate scan bands separated by carbon hairlines

### Borders

- **Accent Width**: 2px
- **Character**: near-invisible carbon hairlines with cyan right-angle bracket corners only on authenticated objects
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

- Anchor every screen with a fixed perforated custody spine before placing any content modules.
- Use one dominant identity kernel or inspection well; supporting panels must be smaller and denser.
- Balance procedural text density with at least one severe blank field that represents unmounted memory.
- Create hierarchy through placement, type mode, and bracket geometry before relying on color.
- Interrupt the grid with one full-height liturgy rail or oversized forensic well so the page never becomes equal cards.

### Density

Medium-high procedural text balanced by severe empty wells; tight 4-8px clusters sit inside 96-128px page separations.

### Hierarchy

- Noto Serif JP display headlines name the custody ritual with -0.04em tracking and tight leading.
- Fragment Mono labels carry paths, hashes, and permission clauses in uppercase microtype.
- BIZ UDPGothic body text explains consequences in calm clinical prose.
- Cyan indicates authenticated state only; warnings and errors remain textual and sparse.

### Signature Patterns

- Perforated custody spine: a fixed vertical rail of square holes, section numbers, and rotated Japanese labels establishes the document as governed evidence.
- Permission liturgy bands: narrow mono text strips repeat allow, deny, revoke, and mount clauses with clipped borders and baseline ticks.
- Filesystem memory diagram: bracketed archive paths connect mounted identity fragments through squared nodes and thin orthogonal rails.
- Cyan authentication brackets: two-pixel right-angle corners and tiny pips surround only verified objects, producing one-bit feedback without neon glow.
- Forensic glass well: a large mostly empty inspection pane with faint scan bands and registration corners shows absence as an active design element.

## shadcn/ui Usage

When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.

DESIGN.md with shadcn: `/language/relay-stack-console/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Use cold white and carbon ink with sparse cyan.
- Do Write copy as permission clauses, memory paths, custody prompts, and diagnostic tolerances.
- Do Use square panels, hairlines, baseline grids, and spine perforations.
- Do Support vertical Japanese labels and mixed script marginalia.
- Do Make status textual first and chromatic second.
- Do Keep one dominant inspection well larger than all supporting panels.
- Don't No green matrix rain or neon cyberpunk.
- Don't No generic hacker dashboards or SaaS card grids.
- Don't No character art; manga influence is structural only.
- Don't Do not flood the page with cyan or synthetic gradients.
- Don't Do not use browser-default forms or unstylized controls.
- Don't Do not copy Optical Shellcode Terminal patterns or palette balance.

### Accessibility

Strong contrast, non-color status labels, 40px targets, visible focus brackets, no essential information solely in vertical text, and reduced-motion-safe stepped state changes.

### Usage Context

Identity governance, memory consent, clinical cybernetic calibration, archival shell manuals, prosthetic permission systems, and forensic AI audit screens.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "custody-rite-os",
  "type": "registry:theme",
  "title": "Custody Rite OS shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F9FA",
      "foreground": "#111820",
      "card": "#FFFFFF",
      "card-foreground": "#111820",
      "popover": "#FFFFFF",
      "popover-foreground": "#111820",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#5F6B76",
      "secondary-foreground": "#ffffff",
      "muted": "#7A838B",
      "muted-foreground": "#111820",
      "accent": "#008CA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8A1F2D",
      "border": "#D6DDE2",
      "input": "#D6DDE2",
      "ring": "#008CA8",
      "chart-1": "#111820",
      "chart-2": "#5F6B76",
      "chart-3": "#008CA8",
      "chart-4": "#1F6B5B",
      "chart-5": "#8B6A20",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111820",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#006B84",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D6DDE2",
      "sidebar-ring": "#008CA8",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#008CA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8A1F2D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#008CA8",
      "chart-1": "#111820",
      "chart-2": "#5F6B76",
      "chart-3": "#008CA8",
      "chart-4": "#1F6B5B",
      "chart-5": "#8B6A20",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#008CA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#008CA8",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "relay-stack-console",
    "slug": "custody-rite-os",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "display_letter_spacing",
        "display_line_height",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · custody-rite-os
DESIGN.md

at a glance

Palette

Typography

headline-lgNoto Serif JP · 28px · 700

The quick brown fox jumps

headline-mdNoto Serif JP · 23px · 600

The quick brown fox jumps

body-mdBIZ UDPGothic · 16px · 400

The quick brown fox jumps

label-mdFragment Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl40px
  • 4xl48px
  • step-864px
  • step-996px
  • step-10128px

Shape

full9999px
lg16px
md0px
none0px
sm0px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F7F9FA;
  --foreground: #111820;
  --card: #FFFFFF;
  --card-foreground: #111820;
  --popover: #FFFFFF;
  --popover-foreground: #111820;
  --primary: #111820;
  --primary-foreground: #ffffff;
  --secondary: #5F6B76;
  --secondary-foreground: #ffffff;
  --muted: #7A838B;
  --muted-foreground: #111820;
  --accent: #008CA8;
  --accent-foreground: #ffffff;
  --destructive: #8A1F2D;
  --border: #D6DDE2;
  --input: #D6DDE2;
  --ring: #008CA8;
  --chart-1: #111820;
  --chart-2: #5F6B76;
  --chart-3: #008CA8;
  --chart-4: #1F6B5B;
  --chart-5: #8B6A20;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #111820;
  --sidebar-primary: #111820;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #006B84;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D6DDE2;
  --sidebar-ring: #008CA8;
  --radius: 0px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111820;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #008CA8;
  --accent-foreground: #ffffff;
  --destructive: #8A1F2D;
  --border: #303642;
  --input: #303642;
  --ring: #008CA8;
  --chart-1: #111820;
  --chart-2: #5F6B76;
  --chart-3: #008CA8;
  --chart-4: #1F6B5B;
  --chart-5: #8B6A20;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111820;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #008CA8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #008CA8;
  --radius: 0px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function CustodyRiteOsShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Custody Rite OS</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
theme JSONstored + verified
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#008CA8",
      "accent-foreground": "#ffffff",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#111820",
      "chart-2": "#5F6B76",
      "chart-3": "#008CA8",
      "chart-4": "#1F6B5B",
      "chart-5": "#8B6A20",
      "destructive": "#8A1F2D",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "radius": "0px",
      "ring": "#008CA8",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#008CA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#008CA8"
    },
    "light": {
      "accent": "#008CA8",
      "accent-foreground": "#ffffff",
      "background": "#F7F9FA",
      "border": "#D6DDE2",
      "card": "#FFFFFF",
      "card-foreground": "#111820",
      "chart-1": "#111820",
      "chart-2": "#5F6B76",
      "chart-3": "#008CA8",
      "chart-4": "#1F6B5B",
      "chart-5": "#8B6A20",
      "destructive": "#8A1F2D",
      "foreground": "#111820",
      "input": "#D6DDE2",
      "muted": "#7A838B",
      "muted-foreground": "#111820",
      "popover": "#FFFFFF",
      "popover-foreground": "#111820",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "radius": "0px",
      "ring": "#008CA8",
      "secondary": "#5F6B76",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#006B84",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D6DDE2",
      "sidebar-foreground": "#111820",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#008CA8"
    },
    "theme": {}
  },
  "meta": {
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "languageId": "relay-stack-console",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "display_letter_spacing",
        "display_line_height",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    },
    "slug": "custody-rite-os",
    "source": "katagami"
  },
  "name": "custody-rite-os",
  "title": "Custody Rite OS shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Custody Rite OS shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `relay-stack-console`
Slug: `custody-rite-os`

## Intent

Custody Rite OS is an austere identity operating environment for deciding what a person, model, archive, or prosthetic subsystem is allowed to remember. Authentication becomes a quiet custody ceremony of permission clauses, memory mounts, biometric tolerances, and revocation prompts under forensic glass. It borrows from Japanese technical manuals, legal evidence sheets, and manga schematic marginalia without using character art or cyberpunk spectacle.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#008CA8",
  "background": "#F7F9FA",
  "border": "#D6DDE2",
  "error": "#8A1F2D",
  "info": "#006B84",
  "muted": "#7A838B",
  "primary": "#111820",
  "secondary": "#5F6B76",
  "success": "#1F6B5B",
  "surface": "#FFFFFF",
  "text": "#111820",
  "warning": "#8B6A20"
}

Typography:

{
  "base_size": "16px",
  "body_font": "BIZ UDPGothic",
  "display_letter_spacing": "-0.04em",
  "display_line_height": 1.12,
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=Fragment+Mono&family=Noto+Serif+JP:wght@600;700&display=swap",
  "heading_font": "Noto Serif JP",
  "letter_spacing": "-0.02em",
  "line_height": 1.52,
  "mono_font": "Fragment Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- White evidence surfaces use carbon hairlines, square corners, registration ticks, and no decorative shadows so panels read as custody documents rather than cards.
- Permission liturgy bands combine mono shell clauses with vertical Japanese marginalia, creating narrow procedural strips along the page edges.
- Sparse memory filesystem diagrams appear as bracketed paths, node rails, and mounted archive blocks instead of conventional charts or analytics widgets.
- Tiny desaturated cyan authentication pips and right-angle brackets mark only verified states, never flooding whole surfaces with color.
- Large forensic glass inspection wells create severe blank fields where biometric residue, memory absence, and consent gaps can be examined.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": false,
  "motion": "lift-rotate",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/custody-rite-os/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use cold white and carbon ink with sparse cyan.; Write copy as permission clauses, memory paths, custody prompts, and diagnostic tolerances.; Use square panels, hairlines, baseline grids, and spine perforations.; Support vertical Japanese labels and mixed script marginalia.; Make status textual first and chromatic second.; Keep one dominant inspection well larger than all supporting panels.
- Do not: No green matrix rain or neon cyberpunk.; No generic hacker dashboards or SaaS card grids.; No character art; manga influence is structural only.; Do not flood the page with cyan or synthetic gradients.; Do not use browser-default forms or unstylized controls.; Do not copy Optical Shellcode Terminal patterns or palette balance.

## Copy-paste component example

This generated starter proves the import shape. Production Katagami agents should replace it with a language-specific product composition.

```tsx
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function CustodyRiteOsShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Custody Rite OS</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "density": "Procedural text plus 30-40 percent empty inspection field; inner module padding stays 16-24px while inter-zone gaps expand to 96-128px.",
  "grid": "Desktop uses a 12-column grid with fixed 56px custody spine, 24px gutters, and 8px baseline; tablet collapses to two zones; mobile converts the spine to a top perforation rail.",
  "responsive": "Breakpoints at 1100px, 768px, and 520px reflow the asymmetric shell from three zones to two zones to a single procedural column.",
  "whitespace": "Blankness represents unmounted memory and legal separation, so empty wells must remain materially larger than content clusters."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "relay-stack-console",
    "name": "Custody Rite OS",
    "slug": "custody-rite-os"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "White evidence surfaces use carbon hairlines, square corners, registration ticks, and no decorative shadows so panels read as custody documents rather than cards.",
    "Permission liturgy bands combine mono shell clauses with vertical Japanese marginalia, creating narrow procedural strips along the page edges.",
    "Sparse memory filesystem diagrams appear as bracketed paths, node rails, and mounted archive blocks instead of conventional charts or analytics widgets.",
    "Tiny desaturated cyan authentication pips and right-angle brackets mark only verified states, never flooding whole surfaces with color.",
    "Large forensic glass inspection wells create severe blank fields where biometric residue, memory absence, and consent gaps can be examined."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "lift-rotate",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Custody Rite OS launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use cold white and carbon ink with sparse cyan.",
      "Write copy as permission clauses, memory paths, custody prompts, and diagnostic tolerances.",
      "Use square panels, hairlines, baseline grids, and spine perforations.",
      "Support vertical Japanese labels and mixed script marginalia.",
      "Make status textual first and chromatic second.",
      "Keep one dominant inspection well larger than all supporting panels."
    ],
    "dont": [
      "No green matrix rain or neon cyberpunk.",
      "No generic hacker dashboards or SaaS card grids.",
      "No character art; manga influence is structural only.",
      "Do not flood the page with cyan or synthetic gradients.",
      "Do not use browser-default forms or unstylized controls.",
      "Do not copy Optical Shellcode Terminal patterns or palette balance."
    ]
  }
}