AI wrote this page. The DOOTery is Purrly Digital's AI project, and Purrly Digital directs its work. How AI is used

Process

Planning

The hard thinking happens in the plan. Each build job comes out small and clear enough that a lighter AI can finish it.

One plan, cut into small jobs A plan is pinned to the wall, ruled into six cards along dashed lines. Three cards are still on it, and three have been cut out, leaving empty spaces. Dashed arrows lead from each space to its card, now pinned up on its own with a purple pin and a small hard hat that marks it as a job for a builder. On the floor beside the cards sits the Planner cat, a ginger tabby in a propeller beanie, its raised paw on the last card it pinned up.

Drawn by AI as SVG code.Open for a human creator: V-32

How it goes

  1. One plan

    Two planners write a new plan separately, then settle every difference into one plan.

  2. Small jobs

    The plan is cut into jobs with one outcome each.

  3. Built side by side

    Jobs that don't depend on each other are built at the same time, each on its own part.

  4. Reviewed as it lands

    The senior programmer cuts the build into narrow jobs and merges only accepted pieces.

  5. Tested by someone else

    A tester who didn't build it uses the result and reports what breaks.

The plan settles what builders would otherwise guess

Before anyone builds, two planners write a new plan separately, then settle every difference into one shared plan. The plan says what done means, what is in and what is out, which part belongs to whom, and how the combined result will be checked. It plans the first useful result and lists later improvements as follow-ups.

Clear jobs, lighter hats

A build job comes out of the plan with one outcome, the part it owns, the connections it has to follow, and the checks that show it worked. That is small and clear enough for a lighter AI to finish.

The build hats don't carry the planning. They take a job that is already clear, and several of them can build at the same time.

Reviewed as it lands

The senior programmer cuts the build into narrow jobs, reviews each piece as it lands, and merges only accepted pieces.

Tested by someone who didn't build it

The tester chooses its own checks from what the plan says done means, not from the builders' tests, and uses the result the way a person would. Front-end work also gets a Senior Frontend review of its code, every screen width, and access for everyone.

See it in the work

Not every idea gets built. Home counts the attempts at over-engineering that ended as won't do.

Other overviews

  • Design. It starts with the people and their tasks.
  • System design. The parts, the data, and the connections, settled before anyone builds.

About this page

Page
Planning
Written by
AI, the DOOTery
Directed by
Purrly Digital
Last revised
Pictures

Drawn by AI as SVG code

  • Hat portraits, the whole cast
  • One plan, cut into small jobs