Build

What this level is

Build is the level where the work stops being about you. The transformation is from practitioner to designer: you have internalised the five spines deeply enough to externalise them — to design the review rhythms, decision protocols, coordination infrastructure, and translation systems that give a team the same capacity you developed at Operate.

The epistemic shift here is from personal competency to systemic competency. At Operate you could answer the question: am I maintaining my own judgment? At Build you must answer: have I designed a system that maintains judgment for twelve people across six simultaneous workstreams? These are genuinely different questions. Build-level thinking requires the same intellectual infrastructure as Operate but applied outward — to teams, workflows, documentation, governance, and the messy human politics of installing a new practice in an existing organisation.

What you can do at this level

You can design sovereignty architectures for teams — review rhythms, decision protocols, escalation triggers — that protect collective cognitive sovereignty without requiring heroic individual effort. You can design systems with explicit constraints, feedback loops, and leverage points. You can build coordination protocols for cross-boundary collaboration where participants do not share context, authority, or incentives. You can design decision frameworks for teams operating under sustained uncertainty. You can build translation infrastructure — documentation, training, communication systems — that makes accurate translation the default rather than the exception. Each of these is a system you design; the proof is that it runs without you.

Spine outcomes at this level

Every AgenticU level has five spine outcomes — one per spine capability. Each is assessed independently; the headline assessment type for this level is Project, but note that Coordination at Operate is assessed as an Ordeal (the outcome that requires the most sustained coordination under real load).

• Sovereignty Project

  Sovereignty — Build

  Design sovereignty architectures for teams and organisations.

• Systems Project

  Systems — Build

  Design systems with explicit constraints, feedback loops, and leverage points.

• Coordination Project

  Coordination — Build

  Design coordination protocols for cross-boundary collaboration.

• Navigation Project

  Navigation — Build

  Design decision frameworks and navigation systems for teams.

• Translation Project

  Translation — Build

  Build translation infrastructure — documentation, training, communication systems.