Captain's Streams® Delivery Framework

The CS Manifest

Four altitudes. One accountability model.

For two decades, the industry applied sprint-based frameworks designed for feature teams to the delivery of infrastructure, physical installation, and operations at scale. The results were predictable: standups in server rooms, story points assigned to cable pulls, retrospectives held in substations. Captain's Streams® was not invented. It was recognised — distilled from the operating models of organisations that had already abandoned ceremony in favour of throughput.

The Manifest — four value pairs (in the tradition of "while there is value in the items on the right, we value the items on the left more"):

Operational continuity over iterative ceremony
Throughput transparency over backlog abstraction
Stream integrity over cross-functional flexibility
Earned readiness over estimated velocity

The 12 Principles

Highest priority: delivery of operational capability to those who depend on it. Delay at stream level is a system failure.
Scope changes within an active Delivery Interval™ are not welcomed — admitted only through formal Re-entry Protocol™. "Agility is not the absence of gates."
Delivery frequency is set by installation reality, not calendar preference. Forcing sprint boundaries onto physical work creates the illusion of progress and the reality of rework.
Bridge and stream operate with shared situational awareness at all times — via Station Dashboard™ and Standing Signal™, not status meetings.
Build teams around verified competencies; hold them to Gate Confirmation™ without exception. "Autonomy without accountability is drift."
The most efficient conveyance of delivery intent within a stream is direct briefing at point of execution. Documentation supplements; it does not substitute.
Working infrastructure is the primary measure of progress — a commissioned asset, a closed Field Confirmation™. "Completed stories are not."
Sustainable delivery pace. Chronic overtime signals under-resourcing or over-commitment, and must be named.
Continuous attention to installation quality enhances agility. Infra-layer tech debt compounds until it surfaces as an incident.
Simplicity — maximising work not done — is a design principle. Every process step must justify itself against throughput impact.
The best architectures and requirements emerge from stream-level teams with domain authority.
At regular intervals the stream conducts a Stream Recalibration™ against delivery data, not sentiment.

"A gate that cannot say no is not a gate. It is a ceremony."

"Velocity is a measurement. Throughput is an outcome. Know the difference before you report either."

"The sprint was designed for a whiteboard. The installation was not."

"Make it so — but verify the Gate Confirmation™ before you log it closed."

"Number One, if the stream is on schedule and the dashboard is red, believe the dashboard."

The CS Big Picture

Four altitudes. One operating model.

The CSDF Big Picture describes the full delivery system — from 36-month Fleet horizon through Wing and Squadron orchestration to Stream-level execution. Every ceremony, role, and register maps to exactly one altitude. Ambiguity is not a feature.

🛰 A4 — Fleet (350–1,250 crew · 2–6 Wings)

Fleet Charter & Governance

Owned by the Fleet Admiral. Governance variants at scale: Chief Delivery Officer of the Line, Portfolio Admiral (Portfolio Bridge Council™ above 1,000 crew).

Subspace Dependency Register™

Fleet-level bindings the Wings cannot resolve within a planning cycle. Every entry carries a Resolution Owner + hard Resolution Stardate.

Fleet Cohesion Score™

Weighted CAI / Readiness Yield / inverse Heading Deviation Index. Target band 75–100. Reviewed at the Fleet Alignment Summit.

Fleet Risk Ledger

Consolidated risk across all Wings. Maintained by the Strategic Dependency Commodore.

36-Month Horizon · Sync: Fleet Alignment Summit · Semi-annual

⇅ Subspace Dependency Flow

🧭 A3 — Wing (85–350 crew · 3–6 Squadrons)

Wing Objective Register™

Owned by the Wing Director. Sets the 18-month mission arc feeding every Squadron Manifest.

Stardate Planning™

2-day fixed quarterly event. Extension = unprepared Wing Manifest, logged as a Health Signal.

Subspace Council™

All Wing Architects + Wing Flow Engineers, chaired by the Fleet Navigation Officer. Bi-weekly. No authority to change Wing Objectives.

Architectural Runway Status

Owned by the Wing Architect. Reviewed as a Stardate Planning input alongside Squadron Manifests (72h prior).

Quarterly Interval · Sync: Stardate Planning · Quarterly

⇅ Wing Objective Flow

🛡 A2 — Squadron (15–85 crew · 3–7 Streams)

Squadron Manifest

Owned by the Squadron Commander. Programme-level decomposition into Stream Objectives.

Dependency Map™

Cross-stream bindings within the Squadron. Refreshed at the bi-weekly Dependency Charting Session.

Bearing Review

Bi-weekly sync of all Stream Captains against the Squadron's 12-week arc.

Crew Calibration

Monthly. Role Capacity Register + Velocity feed Crew Adjustments and Capacity Forecast.

12-Week Arc · Sync: Bearing Review · Bi-weekly

⇅ Squadron Manifest Flow

🚀 A1 — Stream (5–12 crew)

Stream A — North

Stream Captain · Number One · Stream Crew Member (×n)

Stream B — South

Stream Captain · Number One · Stream Crew Member (×n)

Stream C — East

Stream Captain · Number One · Stream Crew Member (×n)

Stream N — [Region]

Streams scale horizontally within Squadron guardrails. No stream shares a Stream Captain.

6-Week Cycle · Sync: Signal Review · Weekly

Fleet Sync Kadenz (nested)

Altitude	Primary Cadence	Sync Event	Frequency
Stream	6-week Cycle	Signal Review	Weekly
Squadron	12-week Arc	Bearing Review	Bi-weekly
Wing	Quarterly Interval	Stardate Planning	Quarterly
Fleet	36-month Horizon	Fleet Alignment Summit	Semi-annual

Value Flow Corridors™: the path from customer need (Fleet/Wing) through Squadron into Stream delivery and back as a measurable outcome. A Corridor without measurable outcome for two Intervals running is Blocked.

"Altitude does not generate value — Streams do." / "The Fleet does not fly. The Fleet enables flying."

The Role Cosmos

Seventeen accountability nodes. Four altitudes.

Captain's Streams® defines seventeen Accountability Nodes™ in the CS Role Charter®, distributed across the Four Altitude Model. Each carries a single, non-delegable accountability. Role ambiguity is the primary cause of stream failure.

A1 — Team & Stream Leadership

SCM

Stream Crew Member

Executes stream-level delivery work. Confirms readiness at Readiness Muster; updates the Course Log at every Daily Heading Check.

TWO

Technical Warrant Officer

Owns technical/installation competency within the stream; verifies Gate Confirmation before a Field Confirmation is logged closed.

Ceremony Marshal

Facilitates the ceremony cadence at Stream level; enforces timeboxes without exception.

ATL

Away Team Lead

Leads work executed off the main stream site; reports back into the Course Log.

Stream Captain

Accountable owner of stream priorities (RACI: A/R). Confirms Readiness verbally at Stardate Planning — no proxies. Requires CS-III + one cycle as Number One.

Number One

Deputy to the Stream Captain; Responsible for activating an Away Team. Assumes command when the Captain is off-shift.

SEO

Stream Enablement Officer

Removes stream-level blockers; escalates impediments unresolved beyond ceremony cadence.

IWO

Integration Warrant Officer

Informed on Integration Contract sign-off; verifies cross-team technical handoffs.

Backlog Navigator

Responsible for the Manifest's stream priorities; maintains Dilithium Point™ estimates.

A2 — Squadron

SQC

Squadron Commander

Leads 3–7 Streams (15–85 crew); chairs the bi-weekly Bearing Review and monthly Crew Calibration across the Squadron.

A3 — Wing

Wing Director

Leads 3–6 Squadrons (85–350 crew); chairs Stardate Planning, owns the Wing Objective Register™.

Wing Architect

Sits on the Subspace Council™; owns Architectural Runway Status for the Wing.

WFE

Wing Flow Engineer

Sits on the Subspace Council™; maintains Wing-level flow metrics feeding the Fleet Cohesion Score™.

A4 — Fleet

Fleet Admiral

Accountable and Responsible for the Fleet Charter. Governance variants at scale: Chief Delivery Officer of the Line, Portfolio Admiral (Portfolio Bridge Council™ above 1,000 crew) — named once, primary title remains Fleet Admiral.

FCA

Fleet Ceremony Architect

Owns the Ceremony Format across all altitudes; approves any deviation from the 12-ceremony catalogue.

SDC

Strategic Dependency Commodore

Fleet-level escalation path for Subspace Dependencies a Wing cannot resolve within a planning cycle.

FNO

Fleet Navigation Officer

Chairs the bi-weekly Subspace Council™; maintains the Fleet Dependency Register. No authority to change Wing Objectives — surface, escalate, broker only.

RACI — Core Decisions

Decision	Accountable	Responsible	Consulted
Stream Priorities	Stream Captain	Backlog Navigator	Number One, Fleet Admiral (as CDOL)
Activate Away Team	Stream Captain	Number One	—
Change Fleet Charter	Fleet Admiral (as PA)	Fleet Admiral (as PA)	Fleet Admiral (as CDOL)
Adapt Ceremony Format	Fleet Ceremony Architect	Fleet Ceremony Architect	—
Approve Integration Contract	Fleet Admiral (as CDOL)	—	Integration Warrant Officer (informed)

PA (Portfolio Admiral) and CDOL (Chief Delivery Officer of the Line) are governance variants of the Fleet Admiral role, not separate Accountability Nodes — see Career Ladder below.

CS Career Ladder™ (competency, orthogonal to position)

Stage 1

Cadet

No prerequisite

Stream Crew Member

Stage 2

Officer

≥6 months + CS-I

Ceremony Marshal, Technical Warrant Officer

Stage 3

Commander

≥18 months + CS-II + Away-Team-Lead cycle

Number One, Away Team Lead, Backlog Navigator

Stage 4

Captain

≥36 months + CS-III + 1 cycle as N1

Stream Captain, Stream Enablement Officer, Integration Warrant Officer

Stage 5

Commodore

≥60 months + CS-IV (Distinction)

Fleet Admiral (CDOL/PA), Fleet Ceremony Architect, Strategic Dependency Commodore

The Ceremony Cadence

Twelve ceremonies. Full altitude coverage.

Every ceremony in the CSDF has a defined owner, a defined output, and a defined maximum duration. Ceremonies without outputs are not ceremonies — they are meetings, and meetings are not billable against the programme.

Ceremony	Altitude	Cadence	Timebox	Owner	Mandatory Output
Daily Heading Check	Stream	Daily	15m (strict)	Stream Captain	Updated Course Log, Impediment Delta
Stream Review	Stream	Per Iteration (2 wks)	90m	Squadron Commander	Reviewed Manifest, Velocity Record
Fleet Retrospective	Stream	Per Iteration	60m	Stream Captain	Improvement Orders (max 3), Retro Log
Readiness Muster	Stream	Before Iteration Start	45m	Stream Captain	Committed Iteration Manifest
Bridge Sync	Cross-Altitude	Weekly	30m	Wing Director	Cross-Stream Impediments, Fleet Pulse Report
Stardate Planning	Wing	Start of Quarter	2 days (fixed)	Wing Director	Quarterly Mission, Stream Allocations
Impediment Court	Squadron	Weekly	30m	Squadron Commander	Resolved/Escalated, Owner Log
Dependency Charting Session	Squadron	Bi-weekly	60m	Stream Captains (peer)	Refreshed Dependency Map, Risk Markers
Readiness Board Review	Stream	Weekly	20m	Stream Captain	Promoted/Blocked Items, Board Delta
Crew Calibration	Squadron	Monthly	45m	Wing Director	Crew Adjustments, Capacity Forecast
Fleet Demonstration	Fleet	End of Quarter	3h	Fleet Admiral	Ratified Delivery Record, Acknowledgement Log
Course Correction Board	Stream	On Heading Deviation > Threshold	90m	Squadron Commander	Corrective Bearing Order, Updated Course Log

The 15-Minute Rule: the Daily Heading Check runs for exactly 15 minutes. If a topic cannot be resolved in 15 minutes, it is logged as an impediment and assigned to the Number One for offline resolution before the next Heading Check. The Heading Check does not extend. The Heading Check does not negotiate. The Heading Check ends at 15 minutes.

Definition of Ready (6)

Item carries an ID in the Manifest.
Acceptance criteria countersigned by the Stream Captain.
Upstream dependencies captured and resolvable.
Effort estimated in Dilithium Points™.
No blocking impediment.
Constraints documented.

Definition of Done (6)

Acceptance criteria met and logged in the Course Log.
Demonstrated at Stream Review.
Integration points verified.
Manifest marked "Delivered" with date/reviewer.
No open impediments.
Velocity recorded.

The Metrics Layer

Eight KPIs. One truth.

Every altitude reports into the same instrument panel. A Stream Captain and a Fleet Admiral read different rows of the same table — never a different table.

Warp Velocity™

Ø Dilithium Points / iteration, 3-iteration trailing average.

Heading Deviation Index™

(planned−delivered)/planned×100. >20% triggers Alert.

Ceremony Adherence Index™

Ceremonies held/planned. Target ≥95%.

Impediment Decay Rate™

Average impediment lifetime. Target <3 days.

Readiness Yield™

Committed/candidate items. Target ≥80%.

Dilithium Burn-Down™

Remaining Dilithium Points per iteration.

Cross-Stream Dependency Ratio™

>40% signals coupling that needs resolving.

Fleet Cohesion Score™

Weighted CAI/Readiness Yield/inverse-HDI. Target band 75–100.

"Raw data without context is not a result — it is navigation data."

Organisational Maturity

Five positions. One index.

The CS Maturity Model™ places an organisation on a five-position scale, assessed via the CS Organisational Assessment (CSOA®).

Adrift

No structure; leadership cannot answer "what ships and when" without a meeting.

Charted

Intent documented, inconsistently applied; ≥1 Stream exists on paper.

Underway

Streams operational; all core ceremonies on cadence; output predictable per quarter.

In Formation

Multi-stream coordination; Dependency Ledger active; metrics live on the Fleet Dashboard®.

Fleet-Ready

Fully embedded; internal certification pipeline; recognised as a CS Reference Organisation.

CSOA® — 12 Assessment Dimensions

Scored 1–5 by ≥2 CS Senior Assessors over 3 days → CS Maturity Index (CSMI). Output: Position Certificate + Findings Register + Recommended Remediation Backlog. Reassessment every 12 months.

Stream IntegrityCeremony FidelityRole CoverageLedger DisciplineMetric ActivationEscalation ClarityStakeholder LegibilityRetrospective YieldCertification DensityTooling AlignmentStrategy TraceabilityInstitutional Memory

CS Transformation Journey™

Phase 0

Signal

2–3 weeks

Phase 1

Chartwork

6–10 weeks

Phase 2

First Wake

3–4 months

Phase 3

Running Straight

4–6 months

Phase 4

Fleet-Ready

2–3 months

Total: 12–18 months. "Compressing Phase 1+2 correlates with a 2.7× higher likelihood of reverting to Position 2. — CS Internal Benchmark."

Professional Certification

The CS Certification Architecture

Captain's Streams® certification is competency-based and prerequisite-enforced. There are no entry-level Masters. Certification exams are administered exclusively through accredited Examination Harbors™, per the CS Credential Integrity Act™.

CSM^®-Master

Nomination + 2 days + oral panel

€12,500 · Renewal 2yr: €2,100

▲

CSM^®-Senior

4 days + portfolio + panel

€6,400 · Renewal 3yr: €1,200

▲

CSM^®-Practitioner

3 days + practical

€3,200 · Renewal 3yr: €790

▲

CS Foundation (CSF)

2 days + online exam · No prerequisites

€1,850 · Renewal 3yr: €490

Full path CSF → CSM®-Master: €24,000–€34,000 (ex. VAT), subject to experience prerequisites. All credentials listed in the CS Credential Registry™ (public verifiable; lapsed 24 months shows as "Inactive — Renewal Eligible").

Faculty & Assessor Tracks

CS Certified Trainer (CSCT)

Requires CSM®-Senior + Trainer Assessment

€8,900 · Renewal yearly: €1,800

CS Senior Assessor (CSSA)

Requires CSM®-Senior + 3 co-assessments

€9,600 · Renewal 2yr: €1,950

Role-Qualifying Certifications

Level	Credential
CS-I	Certified Stream Associate®
CS-II	Certified Stream Practitioner®
CS-III	Certified Stream Captain®
CS-IV	Certified Fleet Officer®
CS-IV Distinction	Certified Portfolio Admiral®

Distinct numbering track tied to the Career Ladder (Cadet → Officer → Commander → Captain → Commodore, see Roles), not to be confused with the CSF/CSM® credential pyramid above.

Partner Ecosystem

CS Partner Program™

Four partner tiers, gated by certified headcount and audit depth.

Bronze

€4,800 / yr

2 certified Practitioners.

Silver

€14,500 / yr

5 certified Practitioners, min. 2 CSM®-Practitioner.

Gold

€38,000 / yr

10 certified Practitioners, subject to Audit.

Flagship

€95,000 / yr

20+ certified Practitioners, min. 1 CSM®-Master, White-Label rights.

CS Platform® is the reference tooling — contractually required for Gold and Flagship partners. CS Marketplace™ listing: €2,400/yr.

Practitioner Perspectives

From the bridge.

Before CS, we had fourteen people in a room twice a week discussing work that six of them weren't involved in. After Stardate Planning, we had six people in a room once a quarter discussing work that all of them were involved in. The savings from eliminated ceremony alone justified the training investment in the first Interval.

Stream Captain, Infrastructure Rollout Programme

Tier-1 European Network Operator

The Subspace Dependency Register was the missing piece. We had three Wings quietly blocking each other for two quarters and nobody with the authority to say so out loud. Now every cross-Wing binding has a Resolution Owner and a Stardate. No more "we thought that was your team."

Squadron Commander, Regional Deployment Wing

Critical Infrastructure Programme

I had my reservations. Six thousand four hundred euros for a four-day course is a significant investment, and I came in sceptical. I left as a CSM®-Senior with a committed Wing Interval Plan and a clear mandate from our Fleet Admiral. Make it so.

Wing Director, now certified CSM®-Senior

European Infrastructure Programme