# Product ## Platform web ## Users Developers, terminal-dwellers, and tool-makers who spend their days inside editors, terminals, and IDEs, and who are bored of cold, blue, purple, or clinically sterile dark themes. They want their workspace to feel like corrupted hardware: warm, alive, and a little hostile. They are tinkerers who customize their desktop environment end to end, who care about internal consistency across editor, terminal, shell, and system UI, and who find beauty in digital decay. A second, smaller audience is port authors. They add Digital Rust to a new editor, terminal, or agent, and they work from the two specification documents and the palette source, not from the showcase site. ## Product Purpose Digital Rust is a warm, tech-dystopian colour scheme inspired by corrupted hardware and failing systems. It delivers one visual identity across editor syntax, UI surfaces, terminals, desktop environments, and coding agents, while keeping every token readable and WCAG 2.1 AA compliant. The product is the aesthetic itself: a complete, ported-everywhere dark theme in which warm rust-to-void tones replace the cold blues and purples of conventional dark themes. Success means that a developer opens their terminal, editor, and desktop and finds the same corroded warmth everywhere, with every token legible and every diagnostic clear. ## Positioning One hue, spec-grade. The rust ramp is the entire neutral scale, and the palette ships as a canonical specification rather than as a theme file. A neighbouring dark theme cannot copy that claim without rebuilding its palette and writing the specification first. The second half of the claim is structural. Errors outrank warnings, and warnings outrank syntax decoration, in every port and by definition. ## Operating Context - Developers use the theme inside editors and IDEs, terminal emulators, shell prompts, desktop environments, and coding agents. They judge it on screenshots, in the live syntax playground, and against the two specification documents. - A port author reads the specifications and then hardcodes the palette into a new file format. When a colour or a token changes, the palette source, both specifications, and every port must change together. - The site version badge and the terminal fingerprint come from the version history in the syntax specification. The build reads that file and inlines the values. - The public mirror is Tangled at `tangled.org/katsuricata.com/DigitalRust`. The site is served at `digitalrust.katsuricata.com`. - The site is prerendered static output. There is no server-side runtime and there are no user accounts. ## Capabilities and Constraints - Palette source: `src/lib/palette.ts`. It is the single source of truth for hex values. A Vite plugin generates `src/lib/generated/tokens.css` from it, and the Shiki theme imports the same values. - Colour names (Ghost Pixel, Event Horizon, and the rest) are stable identifiers. Never rename one without updating both specifications, the site copy, and every port. - The syntax specification is canonical for the palette, token classification, editor chrome, and terminals. The UI specification is canonical for surfaces, elevation, interaction, and components. An implementation is a projection of the specifications. On conflict, the specifications win. - The site is a SvelteKit static build (adapter-static, Svelte 5 runes) that prerenders to `build/`. The package manager is pnpm. Routes: `/` (showcase), `/playground/` (live Shiki highlighter, 48 languages), `/spec/` (renders the syntax specification markdown at build time), and `/ui/` (component gallery). - Two modes, both implemented on the site. The dark theme is the base. Safe Mode is the light projection and the accessibility option, and it uses the same palette and the same role names with new values. WCAG 2.1 AA contrast is required in both modes. Pure black `#000` is banned from backgrounds, borders, and shadows, and pure white `#FFFFFF` is banned in Safe Mode. The darkest surface is Event Horizon `#110402`; the lightest is Ghost Pixel `#F7EAE8`. The site reads the saved mode first, then `prefers-color-scheme`, then the dark theme, and resolves the mode before the first paint. - Licence: repo-authored work is dual-licensed under CC-BY-4.0+ or Apache-2.0+. - No test suite and no CI. Verification is visual, plus the build, check, and lint commands in `AGENTS.md`. ## Brand Commitments - Name: Digital Rust. Voice: Corroded. Defiant. Alive. The theme carries the beauty of systems at the edge of collapse. It is hot and reluctant. It is never cute, never corporate, and never "developer experience" marketing. - Site copy is terminal-native: command prompts, audit output, system logs. The closing tagline is "Chaos reigns." - Anti-references, binding: Dracula, Nord, Tokyo Night, One Dark, and the whole cold blue-purple dark-theme family; sterile "pro" themes with blue accents and grey surfaces; flat, noiseless dark backgrounds; vapourwave and neon retro-futurism. The warmth comes from rust, not neon. - The theme uses a physical metaphor. Interfaces are hardware panels in a failing server rack: chunky, beveled, and pressable. ## Evidence on Hand - Two specification documents at the repository root: `Digital Rust Syntax Highlighting Specification.md` (palette, token classification, editor chrome, terminal) and `Digital Rust UI Specification.md` (surfaces, elevation, interaction, components). Both are downloadable from the site. - Screenshots in `static/` (VS Code, desktop, KDE scheme editor, and a terminal fastfetch view) and wallpapers in `static/wallpaper/`. - Ports in `static/ports/`: VS Code, KDE Plasma, Kate, Konsole, fish, Ghostty, Ptyxis, Raspberry Pi, Thunderbird, and an agent skill. Firefox and Obsidian are published on external platforms. - Live evidence: the `/playground/` highlighter, the `/spec/` page, and the `/ui/` component gallery. - Absent, and not to be fabricated: testimonials, customer counts, download figures, benchmarks, and pricing. - Absent: the Safe Mode projection in the ports, in the agent skill, and in the KDE, Kate, and Konsole colour files. The site implements both modes; the ports still carry the dark values only. ## Product Principles 1. **The palette is the product.** One source of truth for hex values. Everything else is a projection of it. A port that invents a colour is a bug. 2. **Diagnostics outrank decoration.** Diagnostic clarity beats decorative consistency. Error scopes override everything. Warnings override syntax. 3. **Legibility outranks atmosphere.** The palette is hostile; the reading experience is not. AA contrast is the floor, not a goal. 4. **Practice what you preach.** The showcase site renders itself in the theme it documents. The specification page is the proof, not only the documentation. 5. **Specification first, then ports.** A port without a spec update is drift. The two documents are canonical, and an implementation that deviates must say so. ## Accessibility & Inclusion - WCAG 2.1 AA on every surface: body text at 4.5:1 or higher, large text at 3:1 or higher. `--amber-alert-text` (#CB6353) exists because raw Amber Alert does not pass AA as text on base and elevated surfaces. - Non-colour cues are structural: solid underlines for links, wavy underlines for errors and warnings, dotted underlines for spelling, redundant icons and glyphs for colour-blind safety, and +/− markers in diffs. - `prefers-reduced-motion: reduce` suppresses all animation, the cursor blink, and the noise and scanline overlays. State colours remain. - Keyboard reachability with a visible 2px Stack Overglow focus ring. Touch targets are at least 24×24px. - The playground has a skip link, and the site is keyboard navigable.