Room 02 · Workflow

Development is not a pipeline. It is a feedback knot.

These projects often begin before there is a specification, architecture diagram, or code file. They begin with an observation that wants form.

constraints ↙ ↓ ↘ intuition ⇄ conversation ⇄ proposal ⇄ implementation ↑ ↖ ↕ ↘ │ disagreement runtime │ ↕ ↕ └── revised intent ⇄ review ⇄ evidence ↖ ↓ ↗ human acceptance for now

The process is recursive, opportunistic, and sometimes gloriously messy. Requirements change after implementation reveals what the requirement actually meant. A critic can be wrong. A test can expose a hidden assumption. Runtime can overrule a room full of persuasive explanations.

The working rhythm

01 · Thought
An observation wants form.
A question, analogy, frustration, image, or possibility appears in ordinary language.
02 · Conversation
The idea discovers itself.
Assumptions surface. Boundaries, behavior, relationships, and purpose become visible.
03 · Sketch
The thought becomes perceptible.
An SVG, animation, interface, diagram, simulation, or rough implementation gives it shape.
04 · Artifact
The idea becomes executable.
Often one central question, one self-contained page, and a few minutes of interaction.
05 · Review circle
Trust is distributed.
Different people, agents, tests, and tools generate, criticize, compare, repair, or preserve dissent.
06 · Field report
Reality answers back.
The browser, users, logs, tests, and consequences become the next prompt.

Roles, not ranks

Any role may challenge another. The builder may reveal that the specification is impossible. Runtime may invalidate the critic. A minority report may survive because the majority is confidently wrong.

Disagreement is not failure. It is information.

Small by design

A conversational artifact should usually center on one idea, open easily, reveal its mechanism, and remain honest about unfinished edges. The collection is not a contest for complexity. It is a field notebook for ideas that became interactive.