WhiteRabbit Context Studio

https://whiterabbit.codecot.com ↗

The design of record the current practice grew out of — a workspace where source materials become derived artifacts, the plan and the progress are the same screen, and nothing runs until a human says go.

What it is. A working prototype of how the rest of this should behave, kept online because it still says things the shipped systems have not caught up with. Four repositories carry the family: a desktop project space with block-anchored discussion, a generator that turns intent into a runnable backend through build/audit cycles, a Cloudflare control plane with a queue coordinator and workers that claim runs, and a local voice-to-intent front end. Factory, the voice system and the ingest pipeline are all descendants.

The ideas worth stealing back. Source materials sit beside the artifacts derived from them — requirements normalised, constraints resolved, an API surface validated, a context snapshot — so a build is visibly a transformation rather than a prompt. A context pipeline shows the understanding forming (ingesting, deriving, planning, validating) before anything is constructed. The system states what will exist before it exists: endpoints, images, a chart, the validation suite, the repos it will create — and each of those planned cards is the same card that later carries a live status, so the plan and the progress never become two different screens. A run narrates itself on two levels at once, the phase and the thing currently being done. Cancel sits next to Building, and the screen says out loud that you may leave it.

Where the input line matters most. It does not say “ask anything”. It says define a constraint, add context, or describe the system state — the box edits a substrate rather than starting a conversation. The footer makes the promise the whole design exists to keep: the context is never lost.

Status. Perhaps 60% of it is built elsewhere, and the remainder is not abandoned — it is a backlog with a picture. The unbuilt parts are the ones the shipped systems keep asking for: discussions anchored to a block rather than to a document, a review queue that counts what is waiting on a person, and one workspace where the software, video and document pipelines are the same kind of thing.