A living specification.
Complete from the first commit. Not a document that fell behind the code: the source the code was derived from.
Greenfield
The specification is alive from the first commit.
No discovery phase. The specification controls the work from the beginning; the operations capability is built alongside the system, not retrofitted after handover.
0
Days of archaeology
The Pattern01 / 04
The Saudi Pain Pattern, Greenfield Edition
New AI capability is needed across sectors that have never run AI before.
Senior engineering talent is scarce. Regulatory clarity is required from day one, not discovered in review. And the cost of getting the first build wrong is carried for the life of the system: the specification you author on Day 1 is the operations manual on Year 15.
The Greenfield Timeline02 / 04
One Commit. One Loop. One Life.
Each stage writes into the same specification. Nothing is lost between them.
01 · Day 0 · Specification
The first commit is the specification.
The system’s intent is authored, not extracted. Regulatory posture, sovereignty stance, operational contracts, and quality gates all live in one machine-readable artifact before the first line of runtime code exists.
02 · Weeks 1-4 · Intent
The build is derived, not typed.
AI builds where the specification is the source of truth. Every module traces back to a clause. Every service exposes the invariants it must uphold. Deviation is a build failure, not a code review comment.
03 · First Deployment · Operator Action
Operations start where the build ended.
L1, L2, and L3 capability grounded in the same specification the build was derived from. The operations team joins reading the artifact, not archaeologizing it.
04 · Every Change · Agent Action
Every incident writes back.
Not a ticket log. Not a runbook update. The specification itself absorbs what production teaches. The next occurrence of the same class of failure resolves at near-zero cost.
05 · Year 5-15 · Validation
The system audits itself.
Provenance on every answer. A trail behind every change. NCA flow-down, SDAIA localization, board-level review: all of it queryable against the artifact, not reconstructed from logs.
What Every Greenfield Engagement Leaves Behind03 / 04
Three Things, Complete From Day One.
An operations capability.
Grounded in that specification, transferable to the customer’s team by design, not retrofitted through a knowledge transfer phase.
An audit trail.
Behind every change since Day 0. Nothing has to be reconstructed because nothing was ever left uncaptured.