↓
DS
AOS / GPT Sprint Operating System

GPT sprint document map

Start with the minimum viable project pack, then create and refresh the right documents as evidence moves through each four-week sprint.

Start here
Minimum entry gate

What must exist before mobilisation can begin?

Seven concise records are enough to start safely. They can be incomplete, but each needs an owner and an authoritative source.

7 / 7minimum records defined
Mobilisation → Sprint 4

When each core document is created

Required documents establish the gate. Living documents refresh every sprint. Exit evidence unlocks the next stage.

Always live

Documents that follow the whole project

Event refreshed
Simple operating rule

Generate early. Improve with evidence.

1Create shellKnown facts + explicit gaps
→
2RefreshChange only impacted sections
→
3ApprovePeople own material decisions
Normalised register

Asset library

Explore a synthetic catalogue shaped by the aggregate analysis, with lifecycle, automation and operating context.

0 records
AssetScenarioLifecycle familyTypePriorityAutomationStatus
Day one → week four

Four-week sprint factory

Create every required asset shell early, then replace assumptions with evidence as the sprint progresses.

Factory ready Waiting for an authorised project trigger
Local simulation
Generation sequence

Day-one asset factory

Core asset state

First 15 controls

0 / 15 ready
Change once / regenerate safely

Shared fact and synergy map

Documents become coordinated when they depend on the same governed facts rather than copying prose between files.

Project Genome 8 shared fact domains Canonical context exposed through MCP
Impact simulation

What happens when a fact changes?

1Change eventScope milestone moves by two weeks
→
2Impact analysis11 dependent assets identified
→
3Targeted refreshOnly affected sections regenerate
→
4ApprovalMaterial changes routed to owners
Trigger → controlled output

Automated project workflows

Six reusable workflows connect commercial activation, discovery, engineering, assurance, reporting and operation.

Control backlog

15 missing assets

The most material additions required to make the project approach genuinely traceable, governable and self-updating.

Approved reuse

Precedent intelligence

Move beyond “reusable = yes” by distinguishing exemplars, templates, patterns, methods, evidence and live operating assets.

Selection logic

Precedent fit score

Promotion gate

From client asset to reusable IP

  1. Detect a successful approved asset
  2. Remove or parameterise client material
  3. Record context and limitations
  4. Assign quality, owner and expiry
  5. Test on a synthetic scenario
  6. Approve and monitor future outcomes
Agent orchestration

Automation control

Monitor project events, regeneration jobs, approval gates and publication controls.

Event queue

Asset refresh runs

listening
Guardrails

Automation policy

Local data manager

Demo configuration

Stored in this browser

Production path

Data sources and integration status

The demo uses a publication-safe synthetic catalogue. These are the systems required to make project assets live and self-updating.

System connections

Integration status

7 planned
Background jobs

Refresh schedules

Security boundary

Production controls

1IdentityMicrosoft Entra roles and project-scoped access
2SecretsAzure Key Vault; no credentials in generated assets
3EvidenceVersioned sources and immutable approval records
4Client boundaryPrecedent sanitisation before cross-project reuse
Evidence-aware assistance

Project operations assistant

Ask questions across the reconciled register and the proposed operating model.

✦
Project Operations AI grounded in the operating model