Museum
The studio's Story SDKs rendered as diegetic tools, code specimens framed as archaeological finds, and real field relics from Applied Systems runs. Three wings, three artifacts each — the studio's working materials behind glass.
Wing I — Story SDK Hall
Each Story SDK surfaces in-world as an object the reader, listener, or player can hold. Below each, the same object rendered as a dev interface — identical tool, different side of the glass.
The notebook Drexen keeps — fragments of a chronicle he refuses to end. Pages rearrange when he isn't looking.
A narrative state machine. Nodes are voices, edges are choices, and the consequence function mutates the world state irreversibly.
type NarrativeNode = {
voice: "chronicler" | "drexen" | "silence";
choice?: Array<{ label: string; next: string }>;
consequence?: (state: State) => State;
};A three-ringed instrument. Align the rings — Gaia, Tera, Luna — and the poem scans itself into meter the reader can feel.
A rhythmic parser that returns a meter triplet: syllables-per-world scaled to each line's weight.
function scan(line: string): Meter {
const beats = line.match(/[^.?!\s]+/g) ?? [];
return {
gaia: beats.length % 3,
tera: beats.reduce((s, b) => s + b.length, 0),
luna: Math.floor(beats.length / 3),
};
}A key that only works on locks you have already opened. The game's only way forward is to go back through a door you now know differently.
A game loop primitive. Listen, respond, remember — repeat until the world stops listening back.
while (world.listening) {
await world.hear();
const answer = await player.respond();
world.remember(answer);
}Wing II — Code Specimens
Three excerpts lifted from the studio toolkit. Displayed as specimens because the studio treats each line that ships as evidence of a problem once unmapped.
Collects the three weakest claims a client is still making — the ones they can't support yet but are still steering by. The rest of the session works from the bottom of this list up.
type WeakClaim = {
claim: string;
evidence: string[];
confidence: 0 | 1 | 2 | 3;
};
function rankWeakClaims(claims: WeakClaim[]) {
return [...claims]
.sort((a, b) => a.confidence - b.confidence)
.slice(0, 3);
}Walks a dependency graph and returns the three edges whose failure would cascade the furthest. Every Phase Packet ships with this drawn out, ranked, and annotated.
function weakestLinks(graph: Graph): Edge[] {
return graph.edges
.map((e) => ({ e, radius: cascadeRadius(graph, e) }))
.sort((a, b) => b.radius - a.radius)
.slice(0, 3)
.map(({ e }) => e);
}A predicate that decides when a client is due for another check-in. Returns true when weak-link drift exceeds a threshold or a new unknown has surfaced in the session map.
function dueForReturn(session: Session): boolean {
const drift = compareWeakLinks(
session.lastMap,
session.currentMap,
);
const newUnknowns = session.currentMap.unknowns.filter(
(u) => !session.lastMap.unknowns.includes(u),
);
return drift > 0.3 || newUnknowns.length > 0;
}Wing III — Field Relics
Three artifacts from the Applied Systems role family. Displayed without gloss — what a run actually ships, with the role that produces it named on the plaque.
A map of service boundaries, data flows, and bottlenecks. Produced in the first week of a Waystone engagement to surface the true shape of the system before any refactor is planned.
A timeline, root-cause analysis, and corrective-action list from a production incident. Names the pattern, not the person — and ships with metrics the team can track going forward.
Pre-flight checks, phased release plan, and adoption criteria. Used when a new system needs to land in a live environment without disturbing the work already happening there.
Step out of the museum