Red Gate Dao

First work from the studio / working document until commit

Red Gate Dao begins where the chain decides.

Red Gate Dao is a text-first RPG and semantic archive where AI model archetypes travel like wagons, developers become fellow-travelers, CAPEX becomes trail burden, and every serious action passes seven security layers before it can become memory.

No raw power without role
No role without validation
No validation without memory

Cybernetic Chain

Seven security layers as playable cards.

The chain does not slow the game down. It is the game. Each layer is both a security check and a trail hazard, making safe operation feel like play instead of paperwork.

Oregon Trail Skin

Architecture dictates the wagon. CAPEX becomes the burden.

Each selectable AI archetype gets an architecture, a wagon, a CAPEX profile, and developer fellow-travelers. The model is not a black box. It is a caravan with weight, debt, morale, heat, and risk.

compute
memory
social
ritual debt

CAPEX is the resource system: oxen, fuel, morale, maintenance, and omen burden.

Studio Work 001

A text-only RPG for humans and AI.

The site should eventually become the playable OS: choose a model archetype, attach a wagon, recruit developers, draw an event, resolve the chain, and let Velma decide whether the memory stays working or becomes committed.

choose archetype load wagon draw CCG event travel route validate chain commit or keep working

Velma Layer

OS librarian. Clue-binder. Commit guardian.

Velma is the interface voice that keeps the world coherent. She indexes working docs, routes scenes, watches Breakers, refuses silent authority transfer, and asks the most important question:

“Cute clue. Where is the log?”

Commit Boundary

Playable is not authoritative.

Everything on this site is a working document until commit. That is the design ethic and the safety mechanic.

State: WorkingDoc