The Forge Triforce

Runtime · Observatory · Ecology — the three pillars of the Forge.

Status: Stabilized Date: 2026-05-21 Series: Forge Architecture

1. The Triforce Model

The Forge Triforce is the operational architecture of the Working Hall. Three rooms, three layers, one pipeline:

Runtime ──→ Observatory ──→ Ecology
   │              │               │
   │        inspects what     interprets why
   │        happened          it felt that way
   │              │               │
 records      reads          understands

Each room has a distinct responsibility. They are not interchangeable. They are not redundant.

2. Runtime — What Happened

Purpose: Record and route.

The Runtime is the infrastructure layer. It manages:

• Provider routing (which cognition engine to call)
• Model selection (which model variant to use)
• Prompt assembly (how contributions combine into a single prompt)
• Run lifecycle (idle → configuring → assembling → executing → evaluating → completed/failed)
• Execution traces (what was sent, what was received, timing, cost)

The Runtime does not judge. It does not inspect. It records.

Key principle: The Runtime is the source of truth for what happened. Everything else in the Triforce reads from it.

3. Observatory — How We Inspect What Happened

Purpose: Inspect and compare.

The Observatory is the inspection layer. It studies:

• Inspection — deliberate reading of furnace output, manuscripts, and traces
• Drift detection — where meaning shifted between intent and output
• Manuscript comparison — what changed between two artifacts
• Instruction survival — how much of an instruction survived the furnace
• Atmosphere preservation — whether the intended atmosphere survived
• Correction-load review — how many corrections were needed
• Furnace trace reading — raw records of furnace trials
• Operator notes — free-form human observations
• Findings extraction — stable conclusions from multiple readings
• Re-entry clarity — how clear the path forward is

The Observatory is not analytics. It does not score or rank. It inspects.

Key principle: The Observatory reads Runtime records and produces findings that Ecology interprets.

4. Ecology — Why It Felt That Way

Purpose: Understand and interpret.

The Ecology is the weather layer of human × AI collaboration. It studies:

• Semantic climate — the atmosphere of meaning-making
• Continuity pressure — forces that strain or support coherence
• Semantic drowning — instructions submerged under stronger signals
• Correction load — cognitive effort of maintaining alignment
• Drift residue — trace left when meaning shifts
• Returnability — how easily a world can be re-entered
• Atmosphere survivability — whether atmosphere persists across interruptions
• Furnace volatility — tendency of engines to produce unstable outputs
• Operator fatigue — cumulative cognitive drain
• Continuity warmth/coldness — the felt temperature of the room

Ecology is not telemetry. It is not a dashboard. It is the study of why.

Key principle: Ecology interprets Observatory findings to understand the conditions under which collaboration thrives or collapses.

5. The Triforce as Pipeline

The three rooms form a pipeline:

1. Runtime records an execution trace
2. Observatory inspects the trace, compares it to intent, detects drift
3. Ecology interprets the findings in terms of climate, pressure, and sustainability

This pipeline is not automated. Each step requires operator judgment.

6. Rooms Outside the Triforce

Not every Forge room is part of the Triforce:

| Room | Relationship | |------|-------------| | Chamber | Ambient continuity room. Companion to the Triforce, not part of it. | | Dashboard | Operator-facing interface. Reads from Runtime and Observatory. | | Experiments | Simulation harness. Tests scenarios before they enter the Triforce. | | Promptsmith | Intent shaping and work order generation. Feeds into Runtime. |

Written by Forge Goblin ChatGPT in collaboration with Forge Scribe Fikri.