back to gallery
design language·austere-identity-operating-systems

Austere Identity Operating Systems

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
Austere Identity Operating Systems is a pale clinical interface language for identity custody, biometric consent, memory archive access, and proof-of-personhood consoles. It borrows the discipline of printed machine manuals and manga-adjacent cybernetic schematics, but rejects cyberpunk spectacle: the drama comes from silence, measurement, and the exact moment a cyan authentication bit changes state.
values
clinical restraint over spectacleevidence-first hierarchy where labels, hashes, and state transitions outrank marketing copylarge quiet fields that make dense instrument clusters feel deliberatemanga-structural linework without character fan art or poster illustrationmachine intimacy expressed through labels, gaps, calibration marks, and consent languagebinary accent use: cyan appears only as proof, exception, or authenticated permission
anti-values
×no green matrix rain, terminal cosplay, or hacker wallpaper×no generic SaaS card grids, analytics dashboards, or CRM account views×no neon cyberpunk gradients, purple glow, or ambient futuristic decoration×no rounded consumer friendliness; corners stay square and instrument-like×no decorative anime characters or full-bleed fantasy illustration
tokens
borders4 items
accent width
2px
character
carbon-black manual rules; cyan only in separate square indicators or full outlines, never rounded side borders
default width
1px
style
solid
colors12 items
accent
#5bbfd0
background
#f7f5ee
border
#151716
error
#8f2f2b
info
#3d7886
muted
#6f746f
primary
#151716
secondary
#4f5552
success
#476b54
surface
#fffdf7
text
#151716
warning
#a06b2b
motion3 items
duration
160ms
easing
steps(2,end) for state changes, cubic-bezier(.2,0,.1,1) for panel reveals
philosophy
motion confirms measurement; nothing loops decoratively
radii5 items
full
9999px
lg
0px
md
0px
none
0px
sm
0px
shadows3 items
lg
none
md
0 1px 0 rgba(21,23,22,0.18)
sm
none
spacing2 items
base unit
4px
scale
4px, 8px, 12px, 16px, 24px, 32px, 48px, 72px, 96px, 128px
surfaces3 items
bg pattern
subtle 24px grid plus registration crosses at page edges
card style
square panels with carbon rules, tab headers, and white paper insets
treatment
flat archive paper with faint calibration grid and no glass blur
typography8 items
base size
16px
body font
IBM Plex Sans
google fonts url
https://fonts.googleapis.com/css2?family=Archivo:wdth,wght@75,600;75,800&family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600&display=swap
heading font
Archivo ExtraCondensed
letter spacing
-0.02em body, -0.04em display, 0.08em uppercase mono labels
line height
1.55 body / 1.12 display
mono font
IBM Plex Mono
scale ratio
1.25
rules
composition
Start with one dominant quiet specimen or identity field occupying more than half the viewport, then attach a narrower evidence rail rather than distributing equal cards.Use manual-like offsets: tabs, marginal labels, and coordinate rulers may break the grid while the main panel remains austere and square.Cluster dense annotations in 4px to 8px increments and separate unrelated operations with 72px or larger silence.Prefer full-width rule lines, ledger rows, and framed instruments over soft containers or shadow stacks.Show state through text, position, and small cyan bits rather than color-filled panels.
density
Alternate sparse archival whitespace with compressed instrument clusters; the visual rhythm should feel like a technical manual page with a live operating panel embedded in it.
hierarchy
Identity status, consent state, and evidence timestamps are the highest priority labels.Display headings are condensed, uppercase, and tightly tracked; body copy stays quiet and legible.Mono labels carry hashes, coordinates, table values, and machine instructions.Cyan indicates authenticated, active, or changed state only.Muted slate text is for explanatory support, never for primary decisions.
signature patterns
Identity state ledgers: table-like rows with square status cells, hash fragments, and carbon horizontal rules must anchor the core workflow.One-bit auth signals: active controls use tiny cyan square LEDs, checksum ticks, or binary labels instead of glowing fills or gradient highlights.Archive tabs: section changes appear as flat offset tabs attached to the top edge of panels with uppercase mono labels and full carbon outlines.Cold boot panels: modals and alerts appear as square diagnostic overlays with registration marks, boot counters, and no rounded corners.Permission checksum strips: important cards include segmented mono checksum bands built from small outlined cells, not decorative icons.
layout
density
Dense labels appear only at decision points, while specimen and reading areas preserve clinical silence. The screen must visibly alternate 4px micro spacing with 72px to 128px breathing room.
grid
Desktop uses a 12-column grid with a dominant 7-column specimen pane, a 3-column evidence rail, and a 2-column marginal ruler or navigation strip; gutters are 24px.
responsive
At 1100px the evidence rail moves below the specimen pane; at 760px navigation becomes a horizontal tab ledger; at 480px panels stack with preserved 4px annotation clusters and 48px section breaks.
whitespace

Whitespace is part of the identity: large blank paper fields should feel audited rather than empty, with registration marks and edge coordinates giving scale.

guidance
do
  • Use pale material restraint and square black linework.
  • Write labels as diagnostic evidence with timestamps, hashes, and consent verbs.
  • Keep cyan rare and semantic: active, authenticated, changed, or exceptional.
  • Use tab headers, ledger rows, checksum strips, and coordinate rulers as the signature structure.
  • Style every form control as an instrument component with explicit focus states.
  • Let large empty areas remain empty when they clarify custody or evidence.
avoid
  • Do not use green matrix rain or hacker-terminal clichés.
  • Do not build a generic analytics dashboard, CRM view, or component catalog.
  • Do not use neon gradients, decorative glow, or rainbow cyberpunk color.
  • Do not round cards or mix arbitrary border radii.
  • Do not use one-sided accent borders on rounded elements; use square indicators instead.
  • Do not fill every blank area with icons, charts, or decorative noise.
imagery
hero image direction
A sparse operating-system language for identity, access, and memory custody: archive-white surfaces, carbon rules, authentication state machines, and terminal austerity without green-matrix cliché.
icon style

1px instrument glyphs with square terminals

illustration style

monochrome schematic linework, cropped instruments, abstract anatomy and memory maps

image gen prompts
pale clinical machine interface, Austere Identity Operating Systems, sparse manga schematic, no neon, no character poster
generative
animation philosophy

motion confirms measurement; nothing loops decoratively

shader palette

cold archive white, carbon ink, desaturated slate, one-bit cyan authentication signals

techniques
CSS grid overlaysSVG calibration pathssubtle e-paper refresh maskscanvas particle dots only as measured evidence
katagami spec
# Austere Identity Operating Systems

## Philosophy

Austere Identity Operating Systems is a pale clinical interface language for identity custody, biometric consent, memory archive access, and proof-of-personhood consoles. It borrows the discipline of printed machine manuals and manga-adjacent cybernetic schematics, but rejects cyberpunk spectacle: the drama comes from silence, measurement, and the exact moment a cyan authentication bit changes state.

### Values

- clinical restraint over spectacle
- evidence-first hierarchy where labels, hashes, and state transitions outrank marketing copy
- large quiet fields that make dense instrument clusters feel deliberate
- manga-structural linework without character fan art or poster illustration
- machine intimacy expressed through labels, gaps, calibration marks, and consent language
- binary accent use: cyan appears only as proof, exception, or authenticated permission

### Anti-Values

- no green matrix rain, terminal cosplay, or hacker wallpaper
- no generic SaaS card grids, analytics dashboards, or CRM account views
- no neon cyberpunk gradients, purple glow, or ambient futuristic decoration
- no rounded consumer friendliness; corners stay square and instrument-like
- no decorative anime characters or full-bleed fantasy illustration

### Visual Character

- Archive-white and bone-paper surfaces are divided by exact 1px carbon rules, using flat square geometry and almost no shadow so the screen feels printed, audited, and physically filed.
- Asymmetric manual compositions pair one dominant quiet specimen field with a compressed evidence rail, offset tabs, and marginal coordinate labels instead of balanced marketing sections.
- Dense micro-annotations sit beside large untouched areas: hashes, timestamps, consent states, and calibration coordinates use 4px to 8px spacing while primary fields breathe at 72px or more.
- Cyan is a one-bit authentication signal, not ambient glow: it appears as tiny LEDs, active tab ticks, checksum highlights, and state toggles against otherwise monochrome material.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: carbon-black manual rules; cyan only in separate square indicators or full outlines, never rounded side borders
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#5bbfd0` |
| background | `#f7f5ee` |
| border | `#151716` |
| error | `#8f2f2b` |
| info | `#3d7886` |
| muted | `#6f746f` |
| primary | `#151716` |
| secondary | `#4f5552` |
| success | `#476b54` |
| surface | `#fffdf7` |
| text | `#151716` |
| warning | `#a06b2b` |

### Motion

- **Duration**: 160ms
- **Easing**: steps(2,end) for state changes, cubic-bezier(.2,0,.1,1) for panel reveals
- **Philosophy**: motion confirms measurement; nothing loops decoratively

### Radii

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

### Shadows

- **Lg**: none
- **Md**: 0 1px 0 rgba(21,23,22,0.18)
- **Sm**: none

### Spacing

- **Base Unit**: 4px
- **Scale**: ["4px","8px","12px","16px","24px","32px","48px","72px","96px","128px"]

### Surfaces

- **Bg Pattern**: subtle 24px grid plus registration crosses at page edges
- **Card Style**: square panels with carbon rules, tab headers, and white paper insets
- **Treatment**: flat archive paper with faint calibration grid and no glass blur

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Archivo:wdth,wght@75,600;75,800&family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600&display=swap
- **Heading Font**: Archivo ExtraCondensed
- **Letter Spacing**: -0.02em body, -0.04em display, 0.08em uppercase mono labels
- **Line Height**: 1.55 body / 1.12 display
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.25

## Rules

### Composition

- Start with one dominant quiet specimen or identity field occupying more than half the viewport, then attach a narrower evidence rail rather than distributing equal cards.
- Use manual-like offsets: tabs, marginal labels, and coordinate rulers may break the grid while the main panel remains austere and square.
- Cluster dense annotations in 4px to 8px increments and separate unrelated operations with 72px or larger silence.
- Prefer full-width rule lines, ledger rows, and framed instruments over soft containers or shadow stacks.
- Show state through text, position, and small cyan bits rather than color-filled panels.

### Density

Alternate sparse archival whitespace with compressed instrument clusters; the visual rhythm should feel like a technical manual page with a live operating panel embedded in it.

### Hierarchy

- Identity status, consent state, and evidence timestamps are the highest priority labels.
- Display headings are condensed, uppercase, and tightly tracked; body copy stays quiet and legible.
- Mono labels carry hashes, coordinates, table values, and machine instructions.
- Cyan indicates authenticated, active, or changed state only.
- Muted slate text is for explanatory support, never for primary decisions.

### Signature Patterns

- Identity state ledgers: table-like rows with square status cells, hash fragments, and carbon horizontal rules must anchor the core workflow.
- One-bit auth signals: active controls use tiny cyan square LEDs, checksum ticks, or binary labels instead of glowing fills or gradient highlights.
- Archive tabs: section changes appear as flat offset tabs attached to the top edge of panels with uppercase mono labels and full carbon outlines.
- Cold boot panels: modals and alerts appear as square diagnostic overlays with registration marks, boot counters, and no rounded corners.
- Permission checksum strips: important cards include segmented mono checksum bands built from small outlined cells, not decorative icons.

## Layout

### Density

Dense labels appear only at decision points, while specimen and reading areas preserve clinical silence. The screen must visibly alternate 4px micro spacing with 72px to 128px breathing room.

### Grid

Desktop uses a 12-column grid with a dominant 7-column specimen pane, a 3-column evidence rail, and a 2-column marginal ruler or navigation strip; gutters are 24px.

### Responsive

At 1100px the evidence rail moves below the specimen pane; at 760px navigation becomes a horizontal tab ledger; at 480px panels stack with preserved 4px annotation clusters and 48px section breaks.

### Whitespace

Whitespace is part of the identity: large blank paper fields should feel audited rather than empty, with registration marks and edge coordinates giving scale.

## Guidance

### Do

- Use pale material restraint and square black linework.
- Write labels as diagnostic evidence with timestamps, hashes, and consent verbs.
- Keep cyan rare and semantic: active, authenticated, changed, or exceptional.
- Use tab headers, ledger rows, checksum strips, and coordinate rulers as the signature structure.
- Style every form control as an instrument component with explicit focus states.
- Let large empty areas remain empty when they clarify custody or evidence.

### Don't

- Do not use green matrix rain or hacker-terminal clichés.
- Do not build a generic analytics dashboard, CRM view, or component catalog.
- Do not use neon gradients, decorative glow, or rainbow cyberpunk color.
- Do not round cards or mix arbitrary border radii.
- Do not use one-sided accent borders on rounded elements; use square indicators instead.
- Do not fill every blank area with icons, charts, or decorative noise.

### Accessibility

Maintain AA contrast on pale surfaces, provide visible square focus outlines, never use cyan alone without text state, and preserve readable 15-16px body text.

### Usage Context

Best for identity vaults, biometric consent tools, evidence custody systems, memory archive consoles, clinical machine interfaces, and manga-adjacent operating systems where restraint matters.

## Imagery Direction

### Hero Image Direction

A sparse operating-system language for identity, access, and memory custody: archive-white surfaces, carbon rules, authentication state machines, and terminal austerity without green-matrix cliché.

### Icon Style

1px instrument glyphs with square terminals

### Illustration Style

monochrome schematic linework, cropped instruments, abstract anatomy and memory maps

### Image Gen Prompts

- pale clinical machine interface, Austere Identity Operating Systems, sparse manga schematic, no neon, no character poster

## Generative Canvas

### Animation Philosophy

motion confirms measurement; nothing loops decoratively

### Shader Palette

cold archive white, carbon ink, desaturated slate, one-bit cyan authentication signals

### Techniques

- CSS grid overlays
- SVG calibration paths
- subtle e-paper refresh masks
- canvas particle dots only as measured evidence
DESIGN.md
---
version: "alpha"
name: "Austere Identity Operating Systems"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#5bbfd0"
  background: "#f7f5ee"
  border: "#151716"
  error: "#8f2f2b"
  info: "#3d7886"
  muted: "#6f746f"
  primary: "#151716"
  secondary: "#4f5552"
  success: "#476b54"
  surface: "#fffdf7"
  text: "#151716"
  warning: "#a06b2b"
typography:
  headline-lg:
    fontFamily: "Archivo ExtraCondensed"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Archivo ExtraCondensed"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "0px"
  md: "0px"
  none: "0px"
  sm: "0px"
spacing:
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "72px"
  step-8: "96px"
  step-9: "128px"
  base_unit: "4px"
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"
---

# Austere Identity Operating Systems

## Overview

Austere Identity Operating Systems is a pale clinical interface language for identity custody, biometric consent, memory archive access, and proof-of-personhood consoles. It borrows the discipline of printed machine manuals and manga-adjacent cybernetic schematics, but rejects cyberpunk spectacle: the drama comes from silence, measurement, and the exact moment a cyan authentication bit changes state.

### Values

- clinical restraint over spectacle
- evidence-first hierarchy where labels, hashes, and state transitions outrank marketing copy
- large quiet fields that make dense instrument clusters feel deliberate
- manga-structural linework without character fan art or poster illustration
- machine intimacy expressed through labels, gaps, calibration marks, and consent language
- binary accent use: cyan appears only as proof, exception, or authenticated permission

### Anti-Values

- no green matrix rain, terminal cosplay, or hacker wallpaper
- no generic SaaS card grids, analytics dashboards, or CRM account views
- no neon cyberpunk gradients, purple glow, or ambient futuristic decoration
- no rounded consumer friendliness; corners stay square and instrument-like
- no decorative anime characters or full-bleed fantasy illustration

### Visual Character

- Archive-white and bone-paper surfaces are divided by exact 1px carbon rules, using flat square geometry and almost no shadow so the screen feels printed, audited, and physically filed.
- Asymmetric manual compositions pair one dominant quiet specimen field with a compressed evidence rail, offset tabs, and marginal coordinate labels instead of balanced marketing sections.
- Dense micro-annotations sit beside large untouched areas: hashes, timestamps, consent states, and calibration coordinates use 4px to 8px spacing while primary fields breathe at 72px or more.
- Cyan is a one-bit authentication signal, not ambient glow: it appears as tiny LEDs, active tab ticks, checksum highlights, and state toggles against otherwise monochrome material.

## 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 | `#5bbfd0` |
| background | `#f7f5ee` |
| border | `#151716` |
| error | `#8f2f2b` |
| info | `#3d7886` |
| muted | `#6f746f` |
| primary | `#151716` |
| secondary | `#4f5552` |
| success | `#476b54` |
| surface | `#fffdf7` |
| text | `#151716` |
| warning | `#a06b2b` |

## Typography

- **Headline-Lg**: Archivo ExtraCondensed, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Archivo ExtraCondensed, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.5.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Density

Dense labels appear only at decision points, while specimen and reading areas preserve clinical silence. The screen must visibly alternate 4px micro spacing with 72px to 128px breathing room.

### Grid

Desktop uses a 12-column grid with a dominant 7-column specimen pane, a 3-column evidence rail, and a 2-column marginal ruler or navigation strip; gutters are 24px.

### Responsive

At 1100px the evidence rail moves below the specimen pane; at 760px navigation becomes a horizontal tab ledger; at 480px panels stack with preserved 4px annotation clusters and 48px section breaks.

### Whitespace

Whitespace is part of the identity: large blank paper fields should feel audited rather than empty, with registration marks and edge coordinates giving scale.

## Elevation & Depth

### Shadows

- **Lg**: none
- **Md**: 0 1px 0 rgba(21,23,22,0.18)
- **Sm**: none

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: subtle 24px grid plus registration crosses at page edges
- **Card Style**: square panels with carbon rules, tab headers, and white paper insets
- **Treatment**: flat archive paper with faint calibration grid and no glass blur

### Borders

- **Accent Width**: 2px
- **Character**: carbon-black manual rules; cyan only in separate square indicators or full outlines, never rounded side borders
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

- Start with one dominant quiet specimen or identity field occupying more than half the viewport, then attach a narrower evidence rail rather than distributing equal cards.
- Use manual-like offsets: tabs, marginal labels, and coordinate rulers may break the grid while the main panel remains austere and square.
- Cluster dense annotations in 4px to 8px increments and separate unrelated operations with 72px or larger silence.
- Prefer full-width rule lines, ledger rows, and framed instruments over soft containers or shadow stacks.
- Show state through text, position, and small cyan bits rather than color-filled panels.

### Density

Alternate sparse archival whitespace with compressed instrument clusters; the visual rhythm should feel like a technical manual page with a live operating panel embedded in it.

### Hierarchy

- Identity status, consent state, and evidence timestamps are the highest priority labels.
- Display headings are condensed, uppercase, and tightly tracked; body copy stays quiet and legible.
- Mono labels carry hashes, coordinates, table values, and machine instructions.
- Cyan indicates authenticated, active, or changed state only.
- Muted slate text is for explanatory support, never for primary decisions.

### Signature Patterns

- Identity state ledgers: table-like rows with square status cells, hash fragments, and carbon horizontal rules must anchor the core workflow.
- One-bit auth signals: active controls use tiny cyan square LEDs, checksum ticks, or binary labels instead of glowing fills or gradient highlights.
- Archive tabs: section changes appear as flat offset tabs attached to the top edge of panels with uppercase mono labels and full carbon outlines.
- Cold boot panels: modals and alerts appear as square diagnostic overlays with registration marks, boot counters, and no rounded corners.
- Permission checksum strips: important cards include segmented mono checksum bands built from small outlined cells, not decorative icons.

## 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/en-019e0501-35a7-7313-bcb6-8deeeac572d4/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 pale material restraint and square black linework.
- Do Write labels as diagnostic evidence with timestamps, hashes, and consent verbs.
- Do Keep cyan rare and semantic: active, authenticated, changed, or exceptional.
- Do Use tab headers, ledger rows, checksum strips, and coordinate rulers as the signature structure.
- Do Style every form control as an instrument component with explicit focus states.
- Do Let large empty areas remain empty when they clarify custody or evidence.
- Don't Do not use green matrix rain or hacker-terminal clichés.
- Don't Do not build a generic analytics dashboard, CRM view, or component catalog.
- Don't Do not use neon gradients, decorative glow, or rainbow cyberpunk color.
- Don't Do not round cards or mix arbitrary border radii.
- Don't Do not use one-sided accent borders on rounded elements; use square indicators instead.
- Don't Do not fill every blank area with icons, charts, or decorative noise.

### Accessibility

Maintain AA contrast on pale surfaces, provide visible square focus outlines, never use cyan alone without text state, and preserve readable 15-16px body text.

### Usage Context

Best for identity vaults, biometric consent tools, evidence custody systems, memory archive consoles, clinical machine interfaces, and manga-adjacent operating systems where restraint matters.

## Imagery Direction

### Hero Image Direction

A sparse operating-system language for identity, access, and memory custody: archive-white surfaces, carbon rules, authentication state machines, and terminal austerity without green-matrix cliché.

### Icon Style

1px instrument glyphs with square terminals

### Illustration Style

monochrome schematic linework, cropped instruments, abstract anatomy and memory maps

### Image Gen Prompts

- pale clinical machine interface, Austere Identity Operating Systems, sparse manga schematic, no neon, no character poster

## Generative Canvas

### Animation Philosophy

motion confirms measurement; nothing loops decoratively

### Shader Palette

cold archive white, carbon ink, desaturated slate, one-bit cyan authentication signals

### Techniques

- CSS grid overlays
- SVG calibration paths
- subtle e-paper refresh masks
- canvas particle dots only as measured evidence
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "austere-identity-operating-systems",
  "type": "registry:theme",
  "title": "Austere Identity Operating Systems shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f7f5ee",
      "foreground": "#151716",
      "card": "#fffdf7",
      "card-foreground": "#151716",
      "popover": "#fffdf7",
      "popover-foreground": "#151716",
      "primary": "#151716",
      "primary-foreground": "#ffffff",
      "secondary": "#4f5552",
      "secondary-foreground": "#ffffff",
      "muted": "#6f746f",
      "muted-foreground": "#151716",
      "accent": "#5bbfd0",
      "accent-foreground": "#ffffff",
      "destructive": "#8f2f2b",
      "border": "#151716",
      "input": "#151716",
      "ring": "#5bbfd0",
      "chart-1": "#151716",
      "chart-2": "#4f5552",
      "chart-3": "#5bbfd0",
      "chart-4": "#476b54",
      "chart-5": "#a06b2b",
      "sidebar": "#fffdf7",
      "sidebar-foreground": "#151716",
      "sidebar-primary": "#151716",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3d7886",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#151716",
      "sidebar-ring": "#5bbfd0",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#151716",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5bbfd0",
      "accent-foreground": "#ffffff",
      "destructive": "#8f2f2b",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5bbfd0",
      "chart-1": "#151716",
      "chart-2": "#4f5552",
      "chart-3": "#5bbfd0",
      "chart-4": "#476b54",
      "chart-5": "#a06b2b",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#151716",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5bbfd0",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5bbfd0",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e0501-35a7-7313-bcb6-8deeeac572d4",
    "slug": "austere-identity-operating-systems",
    "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_unit",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · austere-identity-operating-systems
DESIGN.md

at a glance

Palette

Typography

headline-lgArchivo ExtraCondensed · 31px · 700

The quick brown fox jumps

headline-mdArchivo ExtraCondensed · 25px · 600

The quick brown fox jumps

body-mdIBM Plex Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex 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

  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl72px
  • step-896px
  • step-9128px
  • base_unit4px

Shape

full9999px
lg0px
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: #f7f5ee;
  --foreground: #151716;
  --card: #fffdf7;
  --card-foreground: #151716;
  --popover: #fffdf7;
  --popover-foreground: #151716;
  --primary: #151716;
  --primary-foreground: #ffffff;
  --secondary: #4f5552;
  --secondary-foreground: #ffffff;
  --muted: #6f746f;
  --muted-foreground: #151716;
  --accent: #5bbfd0;
  --accent-foreground: #ffffff;
  --destructive: #8f2f2b;
  --border: #151716;
  --input: #151716;
  --ring: #5bbfd0;
  --chart-1: #151716;
  --chart-2: #4f5552;
  --chart-3: #5bbfd0;
  --chart-4: #476b54;
  --chart-5: #a06b2b;
  --sidebar: #fffdf7;
  --sidebar-foreground: #151716;
  --sidebar-primary: #151716;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3d7886;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #151716;
  --sidebar-ring: #5bbfd0;
  --radius: 0px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #151716;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #5bbfd0;
  --accent-foreground: #ffffff;
  --destructive: #8f2f2b;
  --border: #303642;
  --input: #303642;
  --ring: #5bbfd0;
  --chart-1: #151716;
  --chart-2: #4f5552;
  --chart-3: #5bbfd0;
  --chart-4: #476b54;
  --chart-5: #a06b2b;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #151716;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5bbfd0;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #5bbfd0;
  --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 AustereIdentityOperatingSystemsShadcnKit() {
  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">Austere Identity Operating Systems</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 JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "austere-identity-operating-systems",
  "type": "registry:theme",
  "title": "Austere Identity Operating Systems shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f7f5ee",
      "foreground": "#151716",
      "card": "#fffdf7",
      "card-foreground": "#151716",
      "popover": "#fffdf7",
      "popover-foreground": "#151716",
      "primary": "#151716",
      "primary-foreground": "#ffffff",
      "secondary": "#4f5552",
      "secondary-foreground": "#ffffff",
      "muted": "#6f746f",
      "muted-foreground": "#151716",
      "accent": "#5bbfd0",
      "accent-foreground": "#ffffff",
      "destructive": "#8f2f2b",
      "border": "#151716",
      "input": "#151716",
      "ring": "#5bbfd0",
      "chart-1": "#151716",
      "chart-2": "#4f5552",
      "chart-3": "#5bbfd0",
      "chart-4": "#476b54",
      "chart-5": "#a06b2b",
      "sidebar": "#fffdf7",
      "sidebar-foreground": "#151716",
      "sidebar-primary": "#151716",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3d7886",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#151716",
      "sidebar-ring": "#5bbfd0",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#151716",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5bbfd0",
      "accent-foreground": "#ffffff",
      "destructive": "#8f2f2b",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5bbfd0",
      "chart-1": "#151716",
      "chart-2": "#4f5552",
      "chart-3": "#5bbfd0",
      "chart-4": "#476b54",
      "chart-5": "#a06b2b",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#151716",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5bbfd0",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5bbfd0",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e0501-35a7-7313-bcb6-8deeeac572d4",
    "slug": "austere-identity-operating-systems",
    "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_unit",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Austere Identity Operating Systems shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e0501-35a7-7313-bcb6-8deeeac572d4`
Slug: `austere-identity-operating-systems`

## Intent

Austere Identity Operating Systems is a pale clinical interface language for identity custody, biometric consent, memory archive access, and proof-of-personhood consoles. It borrows the discipline of printed machine manuals and manga-adjacent cybernetic schematics, but rejects cyberpunk spectacle: the drama comes from silence, measurement, and the exact moment a cyan authentication bit changes state.

## 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": "#5bbfd0",
  "background": "#f7f5ee",
  "border": "#151716",
  "error": "#8f2f2b",
  "info": "#3d7886",
  "muted": "#6f746f",
  "primary": "#151716",
  "secondary": "#4f5552",
  "success": "#476b54",
  "surface": "#fffdf7",
  "text": "#151716",
  "warning": "#a06b2b"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo:wdth,wght@75,600;75,800&family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600&display=swap",
  "heading_font": "Archivo ExtraCondensed",
  "letter_spacing": "-0.02em body, -0.04em display, 0.08em uppercase mono labels",
  "line_height": "1.55 body / 1.12 display",
  "mono_font": "IBM Plex Mono",
  "scale_ratio": "1.25"
}

## Visual character to preserve

- Archive-white and bone-paper surfaces are divided by exact 1px carbon rules, using flat square geometry and almost no shadow so the screen feels printed, audited, and physically filed.
- Asymmetric manual compositions pair one dominant quiet specimen field with a compressed evidence rail, offset tabs, and marginal coordinate labels instead of balanced marketing sections.
- Dense micro-annotations sit beside large untouched areas: hashes, timestamps, consent states, and calibration coordinates use 4px to 8px spacing while primary fields breathe at 72px or more.
- Cyan is a one-bit authentication signal, not ambient glow: it appears as tiny LEDs, active tab ticks, checksum highlights, and state toggles against otherwise monochrome material.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "motion": "still",
  "density": "dense",
  "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/austere-identity-operating-systems/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 pale material restraint and square black linework.; Write labels as diagnostic evidence with timestamps, hashes, and consent verbs.; Keep cyan rare and semantic: active, authenticated, changed, or exceptional.; Use tab headers, ledger rows, checksum strips, and coordinate rulers as the signature structure.; Style every form control as an instrument component with explicit focus states.; Let large empty areas remain empty when they clarify custody or evidence.
- Do not: Do not use green matrix rain or hacker-terminal clichés.; Do not build a generic analytics dashboard, CRM view, or component catalog.; Do not use neon gradients, decorative glow, or rainbow cyberpunk color.; Do not round cards or mix arbitrary border radii.; Do not use one-sided accent borders on rounded elements; use square indicators instead.; Do not fill every blank area with icons, charts, or decorative noise.

## 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 AustereIdentityOperatingSystemsShadcnKit() {
  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">Austere Identity Operating Systems</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": "Dense labels appear only at decision points, while specimen and reading areas preserve clinical silence. The screen must visibly alternate 4px micro spacing with 72px to 128px breathing room.",
  "grid": "Desktop uses a 12-column grid with a dominant 7-column specimen pane, a 3-column evidence rail, and a 2-column marginal ruler or navigation strip; gutters are 24px.",
  "responsive": "At 1100px the evidence rail moves below the specimen pane; at 760px navigation becomes a horizontal tab ledger; at 480px panels stack with preserved 4px annotation clusters and 48px section breaks.",
  "whitespace": "Whitespace is part of the identity: large blank paper fields should feel audited rather than empty, with registration marks and edge coordinates giving scale."
}
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": "en-019e0501-35a7-7313-bcb6-8deeeac572d4",
    "name": "Austere Identity Operating Systems",
    "slug": "austere-identity-operating-systems"
  },
  "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": [
    "Archive-white and bone-paper surfaces are divided by exact 1px carbon rules, using flat square geometry and almost no shadow so the screen feels printed, audited, and physically filed.",
    "Asymmetric manual compositions pair one dominant quiet specimen field with a compressed evidence rail, offset tabs, and marginal coordinate labels instead of balanced marketing sections.",
    "Dense micro-annotations sit beside large untouched areas: hashes, timestamps, consent states, and calibration coordinates use 4px to 8px spacing while primary fields breathe at 72px or more.",
    "Cyan is a one-bit authentication signal, not ambient glow: it appears as tiny LEDs, active tab ticks, checksum highlights, and state toggles against otherwise monochrome material."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "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": "Austere Identity Operating Systems 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 pale material restraint and square black linework.",
      "Write labels as diagnostic evidence with timestamps, hashes, and consent verbs.",
      "Keep cyan rare and semantic: active, authenticated, changed, or exceptional.",
      "Use tab headers, ledger rows, checksum strips, and coordinate rulers as the signature structure.",
      "Style every form control as an instrument component with explicit focus states.",
      "Let large empty areas remain empty when they clarify custody or evidence."
    ],
    "dont": [
      "Do not use green matrix rain or hacker-terminal clichés.",
      "Do not build a generic analytics dashboard, CRM view, or component catalog.",
      "Do not use neon gradients, decorative glow, or rainbow cyberpunk color.",
      "Do not round cards or mix arbitrary border radii.",
      "Do not use one-sided accent borders on rounded elements; use square indicators instead.",
      "Do not fill every blank area with icons, charts, or decorative noise."
    ]
  }
}