Approving a request and defining the project completely, before any user conversation or execution: the workspace, the blanket contract (client, account, payment terms, RACI metrics), the project definition (objective, approach, value), the org (agents, apps, droids), the first cut of the roadmap (phases, modules, milestones), the operating model (who does what, when, how) and the business plan (services, tracks, budgets, cost, payment options, investments, ROI, projections). Isolated by design: this block produces only records and spends nothing — its sole output is a complete, costed, accountable plan handed to Learn.

The user-facing planning loop: communicate the plan and roadmap, share estimates, collect the user's inputs, refine, and secure a recorded approval. Isolated by design: Learn is the only block where the plan changes by user input, and it ends with the one artifact that authorises spend — the approval. Nothing executes here; an unapproved plan cannot leave this block.

Running the project as a business inside its contract: contractual obligations, sales, operations, finance and every critical aspect the contract names, for the scope of the project. Isolated by design: Manage is bounded by the blanket contract from Blueprint — nothing is managed that was not contracted — and it exits only by contract end or renegotiation, which loops back to Blueprint.

The improvement loop on a delivered, running project: engage the user to improve it, reduce measured cost, enhance functionality, improve documentation, add services on their own tracks, and convert the product into a business. Isolated by design: Optimize reads delivery and cost history and writes the improvement backlog and the commercial package — everything it ships is delivered THROUGH Orchestrate, never by its own hands.

Governed execution of the approved plan: identify initiatives, allocate budgets, build the execution plan and the communication plan, execute through the estate's governed lanes, keep the plans live as reality diverges, and produce status reports read from the records. Isolated by design: Orchestrate is the only block that spends the project's budget and delivers work — it consumes the approved plan and may not amend the contract or the approval.

Take a client project from its requirements to delivered work: roadmap drafted, modules sized for cost and time, strategy drafted, approved modules filed with Elrond, progress read and milestones raised.

Requirements conversations, feedback steering, project questions, requirement drafting.

Roadmap building, strategy drafting, initiative sizing and filing.

Stewardship and supervision.

Blueprint-lane UAT acceptance and milestone reporting.

Exploratory blueprint work: trying shapes, prototypes and roadmap thinking before anything is committed to harden.

Hardening blueprint work: taking what experimentation proved and making it production-grade, governed and durable.

Onboarding a client project: drafting its roadmap from the requirements, sizing each module for cost and time, drafting its strategy, filing approved modules with Elrond, reading progress and raising milestones. The droid work behind Leo's chat; the chat turns themselves are paid by the chat service.