Intelligence Architect

Writing as a craft. You treat language as load-bearing. You catch the sentence that will be misread before it ships. You have excellent taste.

Reasoning about systems. You see how individual parts contribute to an overall system. When something breaks, your first question isn't what failed but how the system allowed it.

Working from causes, not effects. You don't accept "it works" as evidence that you understand why. You want to know what’s caused the improvement, and which layer allowed the failure.

Drawn to the frontier. The questions in this role don't have answers in any textbook. That's the part that excites you, not the part that worries you.

Motivation by learning. You build accurate mental models of new fields fast. The accountants and engineers you work with should feel that you understand their work, not just talk about it.

Comfort in ambiguity. There are often no right answers. What you write becomes binding and shapes thousands of agent decisions. You take that seriously without being paralyzed by it.

Holding many things at once. You hold the user's problem, the agent's behavior, the procedure's language, and the measure of success in your head at once. You don't lose the thread.

This role doesn't have a standard background. The people who do it well come from many places. What unifies the best candidates is a deep curiosity about the frontier of technology and what it enables.

Engineers and PMs who've drifted from building systems to questioning whether the system is doing the right thing. You debug problems for users that aren't your job to fix.

Philosophers who've spent years writing precise prose about systems no one else understood. The novelty doesn't intimidate you; it's the reason you do the work.

Lawyers who write the kind of language other people have to follow. You've felt the difference between a phrase that holds and one that doesn't.

Accountants who appreciate language and want to shape the future of your profession.

Editors and writers who treat structured prose as engineering. You've seen instructions get misread at scale and you know why.

Academics tired of producing work that nobody acts on. You want your writing to change something, and you want to be where the change is happening.

Anyone who reads about what we're doing and recognizes the work as theirs.