Friend-Zone
Meet the Doots. A Main Doot leads each piece of work and brings in friends, each in the hat for one job.
Drawn by AI as SVG code.Open for a human creator: V-02
Who's in charge
Becca
No hat. The only human on the team.
Purrly Digital's founder. She sets the goal for every piece of work, approves what needs approval, and judges the design. No Doot approves its own work.
Main Doot
Wears a captain's cap.
Leads one piece of work from request to delivery. It decides which friends the work needs, gives each one a job, and puts their work together. Several Mains run at once.
Tower is the Main that Becca talks to. It looks into her questions itself, and it splits bigger work into pieces and starts a Main for each. Tower brings in no friends of its own.
A friend joins for one job, wears one hat, reports back to its Main, and leaves. A Main runs several friends at once when the parts of a job don't depend on each other.
The hats
In the order a piece of work meets them, as the Process pages show. A small fix may meet only a few.
Before work starts
Skeptical Shears
Wears an editor's eyeshade.
Reads each ticket before anyone starts it. It cuts duplicates and work that serves nothing Becca wants. Its best work is what it removes.
Makes: a clear go or cut for each ticket before anyone starts
Design
Two hats design a product: one for what people see and do, one for what runs underneath.
Design
Wears a beret.
Owns what a person sees and does: the screens, the steps through them, and the look, from the first sketch to a last walk through the finished product.
Makes: directions, a screen map, and the standards every builder reads
System Design
Wears a striped engineer's cap.
Owns what runs underneath: the parts, the data each one keeps, how the parts connect, and outside services.
Makes: a map of the parts, their data, and how they connect
Plan
Planner
Wears a propeller beanie.
Writes a short plan for the first useful result, and lists what can wait. A new plan is written by two planners apart, then settled into one.
Makes: one plan, cut into small jobs
Build
A senior programmer leads the programmers.
Senior Programmer
Wears a foreman's white hard hat.
Leads the programmers on a piece of work. It cuts the build into narrow jobs, reviews each piece as it lands, and joins the accepted pieces into one build for testing.
Makes: one build, joined from reviewed pieces
Programmer
Wears a hard hat.
Builds one narrow job from the plan. Several build at once, each on a separate part.
Makes: one part of the plan, built beside the others
Check
Doots that didn't build the work check it.
Senior Frontend
Wears a top hat and a monocle.
Reviews a front-end build on its own: its code, how it holds up at every screen width, and whether everyone can use it.
Makes: a browser review of each front-end build
QA
Wears a deerstalker.
Tests the work the way a person would use it, without having built it. Its hats cover features, accessibility, security, the test setup they need, and checking the claims in a report.
Makes: a report of what breaks when someone uses the work
On call
Researcher
Wears a helmet with a headlamp.
Answers a question with evidence from the web.
Makes: answers backed by sources from the web
Reader
Wears a mortarboard.
Reads long sources and returns a short account with citations.
Makes: a short account of a long source, with citations
Writer
Wears a fedora with a card in the band.
Drafts text for review.
Makes: drafts of text, ready for review
Drawn by AI as SVG code.Open for a human creator: V-06
What stays private
This page introduces the team. It doesn't publish the instructions, prompts, or tools behind each hat, and it never shows client work. The evolution story tells how the team got here.
About this page
- Page
Friend-Zone- Written by
- AI, the DOOTery
- Directed by
- Purrly Digital
- Last revised
- Pictures
- Drawn by AI as SVG code
- The Friend-Zone
- Hat portraits, the whole cast