Builder Level

Zero to Builder

It's not just about producing a design. It measures you growing into a builder. The 9 cells in the PurplePrint logo are your growth gauge. Fill them all and you go from zero to builder.

Cells fill from the bottom row up, and a lit cell never turns off

Real measurement

From early builder to grown builder

This is the report my-growth actually produces. Not a summary, the full per-session view like this. It shows how the same person moves from 'following along' to 'directing·self-evolving' across sessions.

$ /purpleprint:my-growth

Early builder

Zero to Builder report

When	Lead stage	Density	One-line character
2026-07-04	3 · Driven discussion	0.35	When a constraint hits, names the fix path·settings directly and leads the agent
2026-07-05	4 · Orchestrator	0.45	After boot, checks permission state and requests analysis directly: orchestrating

Trend Moving past merely answering the agent's prompts (following) toward driven leadership: pointing to config paths directly, using system commands to break past environment limits.

Current lead stage Stage 3 ~ 4 boundary

To level up In the design phases (Phase 0~2), when the agent offers candidate proposals, instead of 'just go ahead', back-check the proposal from your user persona's concrete context and raise one structural concern. That settles you firmly into the orchestrator stage.

$ /purpleprint:my-growth

Grown builder

Zero to Builder report

When	Lead stage	Density	One-line character
2026-06-05	4 · Orchestrator	0.35	Directs a dual-agent (Claude+Codex) workflow · routes artifacts
2026-06-12	4 · Orchestrator	0.45	Decides direction (Tauri) with rationale + assigns R&R directly + challenges design via reference cases
2026-06-22	4 · Orchestrator	0.48	Directs 'design through discussion' + requests recursive checks on their own
2026-06-25	4~5 boundary	0.55	Designs the technical strategy themselves + structural critique of artifact quality + foresees the long-term migration path of a stopgap
2026-07-02	5 · Human agent	0.62	Directs interrogation of a feature's essence by user value/PAIN + articulates the domain purpose-chain·user journey directly
2026-07-03	4~5 boundary	0.55	Independently challenges whether an implementation is real vs mocked + internalizes recursive checks every session

Trend Deepened from orchestration·relay-centric early on into a driven, self-evolving flow: articulating the domain model directly, challenging whether implementations are real, and running recursive checks on their own.

Current lead stage Stage 4 ~ 5 boundary (Orchestrator → Human agent)

To level up You already challenge, back-solve, and self-evolve. What's left is raising how often you refute·redefine the AI's proposed direction itself against root/the three chains. That reaches the fully-peer stage.

All content-free behavioral tallies. Your chat·project never goes to the server.

How it's measured

Density, not length

Growth = the density of voluntarily “thinking like an agent”. More or longer words don't raise it.

Content-free

Your chat·ideas never go to the server. Only behavioral signals (like which decisions you made yourself) are tallied.

Accumulates by day

Not a single score. You watch it grow as a curve across sessions.

Each time you finish a design document, the coach looks back at the stretch you just completed and updates the nine cells automatically. Nothing to invoke. To see the full timeline, call my-growth (or pp_my_growth) and the host AI samples your local chat logs session by session. Either way, only the tally reaches the server.

Already measured? → See your growth curve (sign-in required)

Coming: public builder profiles

For those who want it, we're preparing a public profile to show your builder level·strengths·what you've made (opt-in, content-free). A directory where builders like you discover each other.

Start in your agent and start your first session. Growth begins to accumulate.