program-architecture

name	program-architecture
description	Structure a multi-project program around outcomes, workstreams, decision rights, dependencies, milestones, governance, and completion criteria.

Program Architecture

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using strategy/goal, project plans, architecture decisions, owners, timelines, dependencies, and constraints. Do not fill material gaps with assumptions when they can change the result.
3. Define program outcome and boundaries, decompose into independently owned workstreams, map integration points, assign decision forums, and define evidence gates.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Every workstream has a clear owner/output and the program exposes the integration conditions required for the shared outcome.