fleet map
condition × inferred kind · positions are a stable layout, not geography
A small desk somewhere in the far reaches of cyberspace, still standing in the weather. Its drawers hold things found on the way in — git state, commit history, session traces — and the light is good enough to look at them together. (Try pressing / to search, or use j/k to browse.)
the objects are waiting
a few things left out in the open.
nothing set down yet
papers go in one side, pass through the machine, and come out changed enough to look at twice.
Borrowed from the fleet’s own patterns: inspect, preserve, compare, verify, then decide.
Small computational exhibits over the same witnessed ledger: distributions, relationships, and absences. Each one answers a question; none invents a project story.
Pyodide is idle · open the exhibits to compute
Drag a nudge onto the timeline, or click one to place it. These are hypothetical prompt interventions, not live injections.
Observed roots are separated from hypothetical branches. Export/provenance can be added when this becomes a saved notebook.
condition × inferred kind · positions are a stable layout, not geography
active strands crossing the current window
recorded live surfaces and missing request telemetry
pressure signals against the whole fleet
five instrument surfaces · local evidence only
One careful boundary at a time. Nothing runs until you ask it to.
A browser page cannot make a provider key truly secret. Remote requests send selected project facts to the endpoint you configure. Use a scoped key, a local gateway, or a server-side proxy for anything sensitive.