The Architect

The Bureau files this classification from a 30-item forced-choice examination. Nothing on this page describes you — it describes the type, so you can decide whether the description is worth filing. The examination is free and takes six minutes.

I.Documented strengths

• Spends one week on the right abstraction so a hundred wrong ones become unnecessary
• Detects the scaling wall years before finance detects the budget
• Reads the entire design doc — including the footnotes; is always right about the footnotes

II.Known limitations

• Has estimated 'two weeks, properly done' for nine consecutive quarters
• Mistakes the elegance of a solution for the market's demand for it
• Will still be defending the abandoned design in the parking lot after the meeting

III.Recommended assignments

Platform & infrastructure groups, early-stage architecture decisions, codebases entering their second era.

IV.Why this type fits the role

• Architecture is the primary metric here, not a side effect. The subject optimises for the second era of a system by default.
• Decisions here are expensive to reverse, and this is the only archetype in the file who enjoys paying that cost early.
• Second-era codebases are the subject's native habitat: broken but not unfixable, which the Bureau considers the good case.
• The subject builds the tools that make the other five archetypes faster. Measurable, compounding, and rarely contested.

V.What drains this type

• Without design authority the subject will supply it unasked, in writing, to the highest visible address. This is documented.
• Hourly billing rewards arrival, not the week of reading that precedes good judgement. The subject loses money by being right early.
• A support queue is measured in tickets per week. This contribution is measured in tickets that never arrive. The metric will not know.