Admin & Dev Console

Rust & Roots — .dev

Internal tools, editors, and dev references.
Not signed in — most actions require an admin account

◆ Editors

Art Commission (Heroes) Collaborative card-art workflow. 220 cards across 10 factions. xAI gen, Omega/Supe/Reject voting, auto-finalize. /art-commission.html Art Commission (Chronicles) Parallel tool for Chronicles assets. Per-chapter scenes + portraits. Same xAI + voting + finalize pipeline. /chronicles-art-commission.html Ideas Hub Forward-looking ideation across every project. 6 tabs, 3 buckets, attachments & per-tab notepad. /ideas.html Card Editor Stats, effects, art, drafts; full card CRUD. /effects.html Faction Editor Add / rename / recolor / reorder factions. /factions-admin.html Soundtrack Manager Upload MP3s, reorder, rename tracks. /tracks-admin.html Balance Tools Probability tables, meta notes. /balance-tools.html

◆ Monitoring

Analytics Live visit + login + admin-action visibility for .io and .dev. Map, dev-access log, audit trail. /analytics.html Changelog 3-tab version log. Rust & Roots / Chronicles / Runner timelines. /changelog.html Logs Combat logs + server events. /logs.html Tracker Playtest notes, bugs, action items. /tracker.html Studies Design explorations & prototypes. /studies.html API Health JSON: version, engine, hotfix SHA256s. /api/health

◆ References

Design Docs The 17-doc design reference set. /docs.html Continuity Bible Chronicles canon registry. /continuity.html Card Compendium Search / filter across the card database. /compendium.html Keywords Keyword definitions & trigger conditions. /keywords.html Card Browser Public roster view — moves to .io at beta. /cards.html Lore Worldbuilding — rework pending per Chronicles canon. /lore.html Soundtrack (listing) Track metadata view. Player PWA at .io/player/. /soundtrack.html

This console is the admin-only landing on rustandroots.dev. The public site at rustandroots.io has its own cinematic hub and three Play pages for the games. Admin mutation endpoints check is_admin on the backend regardless of which domain requests them — so access is always gated server-side. Your JWT cookie is scoped per-domain, so signing in here does not sign you in on .io and vice versa.