Inside a Weft run.

You walk in with an idea. The Strategist asks what's pushing you to build it, who it's for, what's at stake. They push back where it's vague. The point isn't to challenge you, it's to keep the build pointed at what you came in for.

The Planner takes that and turns it into the kind of plan you could hand to anyone: what gets made, who it's for, what counts as done. You read it, you push on it, you sharpen it together.

The Architect maps the shape before the look. What pieces fit together, what depends on what. You don't have to figure that out yourself.

Then The Designer gives the shape a body. Type, layout, color, components. You see your idea rendered for the first time, in your browser, at a real address. You react. They adjust. Nothing is locked until you say so.

The Engineer writes the code. Real code, in your repository. Not a generated artifact you can't read. Something you keep. Something you can show another developer. Something that survives the next idea.

Then The Tester runs the checks that prove it works. Not just in theory but in fact. If something fails, the loop tightens until it passes, or it's brought to you for a real call.