Practice · The Project Explorer

Generation You Can Watch

Two observability surfaces grow with the pipeline: a nine-panel browser workbench compiled into dev builds at /dev/explorer, and a CLI sampler suite for the terminal. The roadmap treats both as deliverables of every phase, alongside the features they expose.

The nine panels

Each panel answers one question about a seed:

4 · grammar 5 · plausibility 6 · materials 7 · decoration 8 · tags structure plausibility materials decoration tags · calibration pipeline stages panels and samplers, one per stage (plus overview, PRNG and the type index)
Every stage boundary has a window on it. A defect visible at stage 7 but absent at stage 6 has already told you where it lives.

The samplers

The CLI suite prints one pipeline stage each, for eyeballing output ahead of a panel landing, or for piping with --json:

deno task sample                  # gum menu over the samplers below
deno task sample:artefact         # anatomy tree + plausibility verdict
deno task sample:materials        # anatomy tree with each part's material pick
deno task sample:decoration       # decorative layers nested per part
deno task sample:features         # annotated classifier reading, per-value provenance
deno task sample:classification   # scored tag map with per-rule contributions

The features sampler carries per-value provenance: each extracted value names the component and policy that produced it, which is how collapse-policy behaviour (the dominant-blade and dominant-container decisions on the classification page) gets checked by hand. The samplers and the Explorer's structure viewer share the same prose renderer, so what the terminal says and what the panel says never drift.

Defects live in populations

Procgen defects are population properties, and a population is invisible without tooling. The wire-wrapping gate defect surfaced in a sampling pass; the elite inflation surfaced in fire-rate measurement; the fixture skew surfaced when a re-measurement disagreed with the original sample. None of them could have been seen in a unit test or a code review, because every individual artefact involved was fine. Determinism closes the loop: anything odd in a panel arrives with the seed that produced it, so every observation is a reproducible test case by construction.

Where it lives Panels: src/routes/dev/explorer/ · Samplers: scripts/dev/ (see its README) · Shared renderer: src/lib/engine/generation/prose.ts