FLOOD — Strategic Flood Doctrine, Valve Theory, Architecture Ownership

The build-out doctrine the prototype lacked: a theory of the system's own speed. Publishing velocity is defensible only through quality-adherence at volume — volume never earns exemption from V1. ↳ system/seo/FLOOD.md

1 · THE STRATEGIC FLOOD

~50 pages/day — a monitored hypothesis, not a constant of nature

The build phase is a deliberate, sophisticated flooding of the system to develop the core bones of the website. The system is built to crush compute; during build, that capacity is aimed at standing up the site's core as fast as quality-adherence permits. The design assumption: ~50 pages/day is acceptable for a new site, provided every page is thoughtful, diverse, and genuinely valuable — unique, distinct, directly adherent to Google's AI-content policies, categorically not slop. A properly working system meets that bar at that rate; the system is designed against that assumption rather than treating velocity itself as the risk.

Headroom is earned by quality-adherence at volume, not by volume restraint. This supersedes the earlier earned-headroom doctrine (~5/day with slow ramps). Flood velocity is licensed by pipeline integrity — every one of those 50 pages crosses the full elimination chain and the mechanical gatekeeper; a flood of ungated pages is not a flood, it is a values violation.

Each deployment treats 50/day as a commit with a falsifiable predicted effect:

Canary metrics watch the trust signals that would falsify it: indexation rate and latency, crawl-rate response, impression growth, manual-action or quality-signal indicators, engagement on fresh pages.
If trust signals degrade, valves close — mechanically. Canary degradation reduces publish caps and queue admission with no judgment call, no argument, no exemption for being mid-plan.
Canaries are observed on the market clock — corroboration of degradation counts only across market state changes, so a one-day wobble neither closes valves nor licenses reopening them.

↳ system/seo/FLOOD.md:13–43 (§1)

CORE FIRST, keywords second. The initial content is the core — the pages that make the site worth existing for the researched audience. There is no sense targeting keywords when the site doesn't yet add value. Keyword-targeted content is produced early but explicitly subordinate to core construction. The pivot from core-building to keyword-driven strategy is a named transition with criteria, not a drift:

1. Core coverage complete per the architecture blueprint — the build-out plan's core sections report coverage at their declared thresholds. · 2. Help/trust surfaces live — about, editorial policy, contact, the pages that make the site accountable to its audience. · 3. Site experience coherent — navigation, hubs, and cross-links pass the experienced-surface review; a visitor landing anywhere can orient.

After the pivot, the concept map's priority engine takes over as the primary production driver. Pivot when core-coverage discovery saturates, not when a calendar says so. The flood itself is planned, not opportunistic: every page maps to the architecture blueprint (an unmapped page is rejected at brief admission — architectural drift at flood speed), and evenness is a reviewed property — no lane races ahead while another lags. ↳ system/seo/FLOOD.md:45–84 (§2–§3)

2 · THE VALVE MAP — every throughput control

Speed is not one dial. It is an art of opening and closing valves distributed through the whole system. v2 ships valve mastery as delivered knowledge — the deployment receives the valve map at launch and does not rediscover couplings by breakage. For each valve the map records: what it modulates, its interaction effects, its safe operating range, and what breaks first when pushed.

Valve class	What it modulates	Source
Worker schedules	How often each generator/orienter runs; the internal clock's rate	↳ system/seo/FLOOD.md:98
Queue admission rules	What enters each pipeline stage's intake; brief admission against the blueprint	↳ system/seo/FLOOD.md:99
Gate thresholds (via the consequence dial)	Corroboration required per verdict class — the one principled threshold control (specs/CONSEQUENCE.md); never tuned per-gate by hand	↳ system/seo/FLOOD.md:100
Publish caps	The drip publisher's release rate — the last valve before the world	↳ system/seo/FLOOD.md:101
Review acceptance criteria	The build review's stage-appropriate strictness (seo/ONRAMP.md §7)	↳ system/seo/FLOOD.md:102

Valve rules — the closing order is pre-declared.

Valves close faster than they open. Canary degradation closes valves mechanically; reopening requires corroborated recovery across market state changes.
Closing order: publish caps first (stop contact with the world) → then queue admission (stop accumulating in-flight work) → then worker schedules (stop spending). Elimination stages are NEVER the valve that closes — quality machinery runs at full strictness at every velocity.
The map's safe ranges are measured limits, not guesses. How far cycle speed can actually push — 10× steady-state is a hunch — and what breaks first per loop needs instrumented experiments; the valve map records measurements as deployments fill them in. OPEN — flag for command center

↳ system/seo/FLOOD.md:110–121 (§4)

3 · TWO CLOCKS and the evidence-epoch rule

The internal clock

Pipeline health, directive drift, playbook growth, map population — changes state in hours during build. Internal loops audit at the state-change rate: 2–3×/day minimum during build, faster where the valve map's measured limits permit.

↳ system/seo/FLOOD.md:128

The market clock

Rankings, citations, analytics, trust signals — changes daily at best. Market loops audit at the evidence rate; auditing faster is harmful, not neutral: it manufactures observations of an unchanged world.

↳ system/seo/FLOOD.md:132

The evidence-epoch rule: never audit faster than the audited domain changes state. An observation adds evidence only if the system changed state since the last one. Re-observing an unchanged domain manufactures consensus from noise — corroboration counts only across state changes. The memory layer guards the rule: delta-briefs tell auditors what changed since their last pass; "nothing changed" obliges "no new evidence," never invention. Conflating the two clocks was one of the prototype's deepest errors — thresholds denominated in days assumed daily cadence everywhere. ↳ system/seo/FLOOD.md:123–140 (§5)

4 · THREE ARCHITECTURE SURFACES — owned, reviewed artifacts

1 · The crawl surface — what machines see

How the site presents itself as crawlable and citable: XML sitemaps, section indexes, feeds, llms.txt and machine-readable surfaces, canonical structure. Owned as a reviewed artifact — the crawl surface is a claim about what the site is, made to every crawler and answer engine, and it must stay true as the flood fills the blueprint.

↳ system/seo/FLOOD.md:161 (§6.1)

2 · The experienced surface — what humans see

Doctrine: restraint. An SEO site holds thousands of pages at maturity but surfaces few — what is easily accessible is what the researched target prospect actually wants, organized the way they think: stacked menus, categories in their vocabulary, not the taxonomy's. Design extends two clicks deep: not just which pages sit in the menu, but which pages those link out to — is everything that should be reachable actually reachable via deliberate cross-links (within silo rules), and is what's reachable right. How much surface area at which site size needs worked examples per niche archetype. OPEN — flag for command center

↳ system/seo/FLOOD.md:167 (§6.2)

3 · The organizational pipes — how it's plumbed

The information architecture under the whole system: URL structure, collection and taxonomy design, hub-and-spoke wiring, redirect topology, and the mapping between the concept map and the site's physical structure. The pipes are the contract between the knowledge plane and the published site; pipe changes (URL migrations, taxonomy restructures) fork everything built on top of them and sit at the top of the consequence dial.

↳ system/seo/FLOOD.md:177 (§6.3)