When the gates open.
200 dPRNs minted means 200 tonnes verified. That number is not arbitrary. It is the threshold at which the system stops being a proof-of-concept and starts being an operating infrastructure. At 200, specific gates unlock. At 300, a second wave opens. This document names every one of them.
At £450 per tonne, 200 dPRNs minted = £90,000 in verified material value on the ledger. The Covenant (7% of £450 per tonne) has fired 200 times, generating £6,300 in covenant output — meals, social dividend, and community proof. Every single dPRN carries a SHA-256 hash. That means you hold 200 immutable proof records that no one can dispute. That is not a pitch deck. That is an operating infrastructure with receipts.
| Milestone | dPRNs | Tonnes | Meals | Floor Value | Covenant |
|---|---|---|---|---|---|
| Proof Phase | 12–15 | 12–15 | 480–600 | £5,400–£6,750 | £378–£473 |
| Scale Phase | 25–50 | 25–50 | 1,000–2,000 | £11,250–£22,500 | £788–£1,575 |
| First Gate | 200 | 200 | 8,000 | £90,000 | £6,300 |
| Second Gate | 300 | 300 | 12,000 | £135,000 | £9,450 |
The choice of 200 dPRNs as the primary threshold is not cosmetic. At 12–15 tonnes per month in Phase 1 (the floor set in MD-740 and MD-741), reaching 200 dPRNs takes roughly 13–17 months of consistent operation. That window is long enough to prove the model isn't a flash, short enough to maintain urgency. More importantly, 200 dPRNs is the point at which you have a compounding proof stack: 200 individual verifications, 200 Covenant fires, 8,000 meals on the record. No single piece of due diligence can dismantle that. An auditor, investor, regulator, or journalist who shows up at 200 dPRNs faces a ledger that is structurally impossible to dismiss. Before 200, you have a promising track record. At 200, you have an operating system. The threshold is the line between those two things — and gates open at that line because the infrastructure earns them.
The 300 threshold exists for a second reason: the difference between 200 and 300 is one more scale push. Getting from zero to 200 is about proving the model. Getting from 200 to 300 is about proving you can repeat it. That repetition — not the initial proof — is what unlocks international pathways, franchise eligibility, and sovereign credit draw. Repetition is harder to fake than a first run. The 300 gates are calibrated to reward the harder proof.
The eight gates at 200 dPRN do not open in isolation — they compound. The Market Maker (G1) activates at the same moment the ABL window opens (G2) and investor credibility clears (G3). That is not three separate events. That is a single liquidity event: the system becomes fundable from three directions simultaneously. The Generals activation (G5) coincides with the jobs unlock (G6), meaning you go from a lean proof operation to an organised workforce in the same window. The node authorisation (G7) and enterprise tier (G8) mean that immediately after liquidity events, you have both the infrastructure to scale and the client tier to fill it.
This is not accidental. The threshold was designed so that every gate at 200 feeds the one above it. Market Maker volume increases ABL collateral. ABL funds second-node deployment. Enterprise clients fill second-node capacity. Generals manage the expanded workforce. The system does not open gates one at a time — it opens them as a cascade. That cascade is what makes 200 structurally different from 150 or 100. At 150, you might have half of these gates ajar. At 200, all eight fire together, and the compounding effect means the system's operating capacity more than doubles overnight.
The word "maybe" in the title is precise. These gates are contingent on reaching 300 with consistent throughput — not 300 minted over two years of intermittent operation. 300 with momentum. 300 with a team in place. 300 with the 200-gate infrastructure already operating. That "maybe" is the qualifier that separates people who reach 300 from people who just count to it.
The 300 threshold carries a qualifier that 200 does not — and that qualifier is operational. The reason 200 gates open unconditionally is that 200 is an infrastructure proof: you either minted 200 dPRNs or you didn't, and if you did, the ledger confirms it. The 300 gates require more than counting to 300. They require that the 200-gate infrastructure is already running when you reach 300. If you mint dPRN 300 without generals deployed (G5), without the enterprise tier live (G8), without the Market Maker operating (G1) — then 300 is just a number, not a threshold. The "maybe" in the title is the honest version of this: maybe you reach 300 with the full 200-gate infrastructure in play, in which case every gate above fires. Maybe you reach 300 with some of the 200 gates still ajar. In that case, close the 200 gates first before expecting the 300 gates to fire.
The sequencing is non-negotiable. G1 before G9. G7 before G14. G5 before G10. The gates are an ordered cascade, not a free-for-all. Reach 300 in order, and the second wave compounds the first. Skip the sequence, and 300 is just a count.
When you reach 200 dPRNs minted, you hold the following:
| Artifact | What It Is | Value |
|---|---|---|
| 200 SHA-256 Records | Immutable ledger entries, one per tonne | Undeniable |
| £90,000 dPRN Floor | Verified material value on the truth ledger | £90,000 |
| 8,000 Meal Records | Covenant fires documented, meals provably funded | 8,000 |
| £6,300 Covenant Total | 7% × £450 × 200 — the social dividend stack | £6,300 |
| 200 Carrot Payments | Processor incentive paid per verified tonne | Documented |
| Operational Track Record | 13–17 months of consistent verified throughput | Fundable |
The deliberate choice to call these "gates" rather than "milestones" is doctrinal. A milestone is celebratory — you reach it, you note it, you move on. A gate is structural — it is closed until the threshold is met, and it opens to reveal something that was not accessible before. The gates in this document are not congratulations. They are access points. Before 200: no ABL. After 200: ABL window open. Before 200: no Market Maker listing. After 200: live. The gate does not care how you feel about reaching it. It opens because the ledger confirms the count.
This matters for culture as much as for operations. A team that understands it is working towards a gate operates differently from a team working towards a milestone. Milestones are ceremonial. Gates are functional. The 200 dPRN gate means the team knows exactly what happens the day they mint number 200. Not "we'll celebrate." Specific things: Market Maker goes live, ABL window opens, generals activate, senior jobs unlock. That specificity creates urgency that "celebrating a milestone" never generates. Build the culture around gates, not milestones, and the count accelerates because every person on the operation knows what opens when they get there.
200 is the line.
Not a target. Not a goal. A gate.
Every tonne through Unit 18 is one step closer. Every SHA-256 record is one proof added to the stack. At 200, the stack becomes infrastructure. At 300, the infrastructure becomes a system. The gates don't open because you asked nicely. They open because the ledger says so.
MD-1005 · The 200 dPRN Threshold · Gates Open · CircularOS Sovereign Record · Milestone Doctrine · 40% Architect input across 4 sections (Why 200 · The Compounding Effect · Maybe 300 Doctrine · Gates Not Milestones) · Sealed May 2026 · Build #151 · Aliases: /md-1005 · /200-dprn-threshold · /dprn-threshold-gates · /200-dprns · /the-threshold-gates · /300-dprn-threshold