Skip to main content

Production Rollout Paths

This page converts the Production track into implementation sequences. Use it when teams need to know what to do first, what to enforce next, and which standards can wait until later maturity.

Fastest Path

Tutorial-First Implementation Sequence

Use the tutorials to establish working controls quickly, then formalize against the PRD-STD series.

1

Starter Config Files

15 min

Standardize local AI tool behavior with shared rules, prompts, and PR templates.

Prompt hygienePR template
Open step
2

CI/CD Pipeline Starter

15 min

Add baseline quality, dependency, and security checks that prevent unsafe merges and releases.

Quality gatesSecurity scanning
Open step
3

First AI-Governed PR

30 min

Run a complete prompt-review-test-merge flow and teach the team the expected operating pattern.

Code reviewTestingTraceability
Open step
4

Policy Templates

20 min

Formalize acceptable use, data handling, and escalation expectations to support enforcement.

Policy baseline
Open step
5

Standards Gap Analysis

Ongoing

Map what is implemented to PRD-STD Level 1 and Level 2 requirements, then close gaps in order.

Compliance progression
Open step

Compliance Progression

Adopt Standards in Enforceable Order

Prioritize the standards that reduce the highest production risk first, then broaden controls as maturity improves.

1

Level 1 Foundation

Implement code review, security scanning, and dependency/license compliance before claiming governed AI-assisted delivery.

PRD-STD-002PRD-STD-004PRD-STD-008
Open step
2

Level 2 Managed

Expand to prompts, testing, quality gates, agent governance, and AI product/runtime controls.

PRD-STD-001/003/007PRD-STD-009..016
Open step
3

Level 3 Optimized

Add documentation and technical debt controls so AI-assisted delivery remains maintainable over time.

PRD-STD-005PRD-STD-006
Open step

By Team Shape

Choose a Rollout Path That Matches Your Organization

Each path maps to the same standards library but changes sequence and depth based on team size and governance needs.

Individual Developer / Small Team

Need fast adoption with lightweight controls.

  1. Complete Starter Config Files and First AI-Governed PR tutorials.
  2. Adopt Level 1 standards with lightweight CI enforcement.
  3. Use Policy Templates to define acceptable use and data handling rules.
  4. Add Level 2 controls as the team starts shipping customer-facing changes.

Platform-Enabled Product Organization

Multiple teams need consistent enforcement and reusable pipelines.

  1. Start with CI/CD Pipeline Starter and Policy Templates to create shared defaults.
  2. Define a Level 1 minimum control baseline for every repo.
  3. Add Level 2 quality gates, prompt standards, and agent governance in platform templates.
  4. Track compliance evidence and exceptions in a regular governance review cadence.

AI Product Team (Model-Driven Features)

Shipping AI runtime behavior with safety, data, and reliability obligations.

  1. Implement Level 1 baseline controls first for all AI-assisted engineering work.
  2. Prioritize Level 2 AI product standards (010-016) before broad feature rollout.
  3. Pair runtime controls with observability, fallback, and incident response playbooks.
  4. Adopt Level 3 sustainment standards to control knowledge erosion and technical debt.

Implementation Mapping (Tutorials to Standards)

Tutorial / AssetImmediate Implementation OutcomeStandards Covered
Starter Config FilesShared prompting and PR hygiene baselinePRD-STD-001, PRD-STD-002
CI/CD Pipeline StarterAutomated build/test/security/license checksPRD-STD-003, PRD-STD-004, PRD-STD-007, PRD-STD-008
First AI-Governed PREnd-to-end developer workflow and review behaviorPRD-STD-001, PRD-STD-002, PRD-STD-003
Small-Team Multi-Agent StarterAgent handoffs, contracts, and approval controlsPRD-STD-009
Policy TemplatesAcceptable use and data handling governanceSupports multiple standards; foundational policy evidence

Do Next

Recommended 30-Day Rollout

This sequence is the fastest way to establish a credible production baseline before scaling into full compliance.

  1. Week 1: Run the starter config and CI/CD tutorials, then choose a Level 1 control owner. Open
  2. Week 2: Pilot the first AI-governed PR flow and tune review/test gates based on actual failures. Open
  3. Weeks 3-4: Perform a standards gap analysis and schedule Level 2 adoption in dependency order. Open