DOC BROWSER — the 20 doctrine documents

Every document under system/**, rendered as styled HTML with cross-links. The corpus is the source of truth; these pages are its faithful, generated mirror (site/gen_docs.py). 20 docs, grouped by directory.

SYSTEM / VALUES / FLAGS (root)

THE SEO MONEY MACHINE — SYSTEM v2
The root document. Everything in system/ descends from here.
system/SYSTEM.md
10 sections
  • 0. The mission — VALUEMAXX
  • 1. What the system is
  • 2. The doctrine hierarchy
  • 3. The core operation
  • 4. The anatomy (five layers + apex)
  • 5. The substrate (build order — leverage-first)
  • 6. Worker doctrine
  • 7. Model policy (ML, locked)
  • 8. Mission posture
  • 9. Map of system/
VALUES — The Floor
Status: v2.1 — restructured per ML's review (2026-07-21). Values and mission were
system/VALUES.md
9 sections
  • What values are, and are not
  • VF1 — The law, interpreted explicitly
  • VF2 — Honest transactions; no scamming
  • VF3 — No shitty things
  • Operator integrity (system-internal)
  • Per-deployment values
  • Enforcement mechanics
  • Relationship to VALUEMAXX
  • Legacy reference key
FLAGS FOR ML — Review Queue
Round 1 CLEARED by ML 2026-07-21 (message.txt review). Resolutions recorded below
system/FLAGS-FOR-ML.md
4 sections
  • 1. Round 1 — RESOLVED
  • 2. Round 2 — OPEN (accumulating)
  • Constants to be MEASURED from deployment data (policy approved: measure, don't design)
  • 3. Settled by prior ML directives

corpus/

LAWS — The Core Operation and Its Rules
Status: v2.0 — command-center authored. Below VALUES.md, above everything else in corpus/.
system/corpus/LAWS.md
12 sections
  • 1. The atom
  • 2. Law 1 — Matched elimination
  • 3. The three stoppers
  • 4. Granularity
  • 5. The commit boundary
  • 6. Evidence scales with consequence
  • 7. Law 2 — Teardown and reconstruction are separate
  • 8. Law 3 — Progressive commitment
  • 9. The three inputs
  • 10. The human — four locations, not a dial
  • 11. Spartan design, not token thrift
  • 12. The two planes
BLUEPRINT — The Class Anatomy
Status: v2.0 — command-center authored. The complete class map of the workforce the
system/corpus/BLUEPRINT.md
16 sections
  • OPERATING LAYER — the domain work, eight stages
  • Stage A — Framing & planning
  • Stage B — Evidence gathering
  • Stage C — Production
  • Stage D — Elimination (staffed disjoint from Stage E per Law 2)
  • Stage E — Compression & reconstruction (staffed disjoint from Stage D)
  • Stage F — Commit & delivery
  • Stage G — Standing mission
  • Stage H — Flow & logistics
  • Cross-cutting
  • MONITORING LAYER — memory and comparison
  • IMPROVEMENT LAYER — change with proof
  • SELF-KNOWLEDGE LAYER — findings, never actions
  • EXECUTIVE FUNNEL — the truthful channel
  • APEX
  • Instantiation notes for the SEO differentiation
LOOP CLOSURE — The Pod Rule
Status: v2.0 — command-center authored. The rule that generates the meta-layers,
system/corpus/LOOP-CLOSURE.md
6 sections
  • 1. The six functions
  • 2. The ratio
  • 3. Monitoring — memory and comparison
  • 4. Improvement — change with proof
  • 5. Self-knowledge — the organization knows itself
  • 6. Retirement — apoptosis
THE FUNNEL — Truthful Reporting and Bounded Escalation
Status: v2.0 — command-center authored. How the true state of the organization
system/corpus/FUNNEL.md
7 sections
  • 1. Why a funnel
  • 2. Condensers
  • 3. Bad-news conservation (the one hard invariant)
  • 4. The Executive Brief
  • 5. The escalation ladder — climb, never jump
  • 6. The four contact categories
  • 7. The command center at the apex
COMMISSIONING — The Worker Lifecycle
Status: v2.0 — command-center authored. What a worker is, how one enters the
system/corpus/COMMISSIONING.md
7 sections
  • 1. The worker is the durable unit
  • 2. Commissioning is integration, not instantiation
  • 3. The four-channel contract
  • 4. The manifest
  • 5. Standards and replacement
  • 6. Retirement
  • 7. Organizational redesign

seo/

PIPELINE — The Content Pipeline as Operating Stages
Status: DRAFT v2.0 — command-center reviewed 2026-07-20 · ML review pending
system/seo/PIPELINE.md
13 sections
  • 1. What the pipeline is
  • 2. The stage sequence
  • Stage 1 — Brief / framing
  • Stage 2 — Evidence
  • Stage 3 — Draft production
  • Stage 4 — Elimination stages
  • Stage 5 — Compression / assembly
  • Stage 6 — The mechanical gatekeeper
  • Stage 7 — The drip publisher (pull-only release gate)
  • Stage 8 — Post-publication outcome observation
  • 3. VALUEMAXX enforcement points (mission machinery, structural)
  • 4. What changed from the prototype
  • 5. Open items
RESEARCH — The Expertise Pyramid and the Persona Tournament
Status: DRAFT v2.0 — command-center review pending
system/seo/RESEARCH.md
14 sections
  • 1. Why research is the foundation, not a phase
  • 2. The expertise pyramid (Layers 0–5)
  • Layer 0 — Vertical fundamentals
  • Layer 1 — Product & market map
  • Layer 2 — Buyer psychology + objection analysis
  • Layer 3 — Competitive intelligence
  • Layer 4 — Content strategy: beats, priorities, concept map
  • Layer 5 — Voice & personality
  • Execution shape
  • 3. The persona tournament
  • 4. Personality is a testable hypothesis
  • 5. From research to running system
  • 6. What changed from the prototype
  • 7. Open items
FLOOD — Strategic Flood Doctrine, Valve Theory, Architecture Ownership
Status: DRAFT v2.0 — command-center reviewed 2026-07-20 · ML review pending
system/seo/FLOOD.md
11 sections
  • 1. The strategic flood
  • 2. Core first, keywords second
  • 3. Even flooding against an explicit build-out plan
  • 4. Valve theory — the valve map
  • 5. Two clocks and the evidence-epoch rule
  • 6. Architecture ownership — three owned surfaces
  • 6.1 The crawl surface — what machines see
  • 6.2 The experienced surface — what humans see
  • 6.3 The organizational pipes — how it's plumbed
  • 7. What changed from the prototype
  • 8. Open items
SECURITY — Injection Defense as a First-Class Discipline
Status: DRAFT v2.0 — command-center reviewed 2026-07-20 · ML review pending
system/seo/SECURITY.md
11 sections
  • 1. The premise: consume everything, trust nothing
  • 2. Data/instruction separation
  • 3. Ingestion quarantine
  • 4. Provenance and taint tracking
  • 5. The distinct-provenance corroboration rule
  • 6. Blast-radius doctrine
  • 7. The security playbook (workbook)
  • 8. The security fleet
  • 9. Escalation and values interlock
  • 10. What changed from the prototype
  • 11. Open items
ONRAMP — The Autonomous Onramp: Ramp, Graduation, Boot, Takeover
Status: DRAFT v2.0 — command-center review pending
system/seo/ONRAMP.md
11 sections
  • 1. The build is declarative, bottom-up, self-graduating
  • 2. Provisioning — the only hard human dependency
  • 3. The boot interview — a fork-tested question bloom
  • 4. Ramp-as-config
  • 5. Cooldowns — damping as its own mechanism
  • 6. The model ramp
  • 7. Build review — permanent layers at build settings
  • 8. Graduation — the definition
  • 9. Takeover mode
  • 10. What changed from the prototype
  • 11. Open items
CONTINUITY — Backup, Restore Drills, Rollback Tiers
Status: DRAFT v2.0 — command-center review pending
system/seo/CONTINUITY.md
8 sections
  • 1. Everything-as-code
  • 2. Nightly sanitized agent-layer snapshots
  • 3. The secrets ledger
  • 4. Three rollback tiers
  • 5. Restore drills — an untested backup is a hypothesis
  • 6. Scope notes
  • 7. What changed from the prototype
  • 8. Open items

specs/

LEDGER — The Append-Only Substrate
Status: DRAFT v2.0 — command-center reviewed 2026-07-20 · ML review pending
system/specs/LEDGER.md
14 sections
  • 1. Physical form
  • 2. The record envelope
  • 3. Record types
  • 3.1 candidate-registered
  • 3.2 verdict
  • 3.3 commit / decommit
  • 3.4 outcome
  • 3.5 alarm
  • 3.6 trial — pre-registration, then result
  • 3.7 escalation-forward / escalation-bounce
  • 3.8 grant
  • 3.9 heartbeat
  • 4. Rules (the invariants scripts enforce)
  • 5. What the ledger is not
CONSEQUENCE — The Stakes Rubric and the One Dial
Status: DRAFT v2.0 — command-center reviewed 2026-07-20 · ML review pending
system/specs/CONSEQUENCE.md
6 sections
  • 1. The five questions
  • 2. The tier table
  • 3. Migration table — the fifteen v1 hand-set thresholds → the dial
  • 4. What stays outside the dial
  • 5. Interaction with the ramp
  • 6. Amendment
GATES — The Gate Library Spec
Status: DRAFT v2.0 — command-center review pending
system/specs/GATES.md
13 sections
  • 1. Shape and ground rules
  • 2. load_ramp_config(gate_name) -> GateConfig
  • 3. Function inventory (the contract)
  • count_corroboration(group, cfg) -> CorroborationCount
  • check_cooldown(gate, direction_key, epoch, cfg) -> CooldownStatus
  • mark_consumed(gate, direction_key, epoch) / is_consumed(...)
  • evaluate_graduation(gate, state, cfg) -> Optional[PhaseChange]
  • write_qualified(gate, result)
  • apply_console(gate, result) -> result
  • Exit-code and state-file conventions (unified)
  • 4. The per-gate script (thin wrapper shape)
  • 5. DELETED: the AUTO_PASS_SOURCES bypass
  • 6. The values-gate template (carried by every worker)
CHANNELS — The Four-Channel Commissioning Contract
Status: DRAFT v2.0 — command-center review pending
system/specs/CHANNELS.md
6 sections
  • 1. The four channels
  • 2. The manifest wiring block
  • 3. Verdict format on channels
  • 4. Commissioning: the five-step checklist
  • 5. Decommissioning
  • 6. Drift audit: declared vs. observed

ops/

MODELS — The Intelligence Spectrum, Operationalized
Status: DRAFT v2.0 — command-center review pending
system/ops/MODELS.md
6 sections
  • 1. The spectrum
  • 2. Assignment rubric by consequence
  • 3. Assignment is a commit
  • 4. Build-phase posture: start capable, demote on evidence
  • 5. Cost posture: spartan design, not token thrift
  • 6. Escalation economics
DEPLOYMENT — Running a Deployment
Status: DRAFT v2.0 — command-center review pending
system/ops/DEPLOYMENT.md
14 sections
  • 1. Provisioning — the only hard human dependency
  • 2. Directory structure v2
  • 3. The worker pattern: cron job + manifest + directive
  • Mission
  • Reference files (read first)
  • Input
  • Output
  • Constraints
  • This run
  • 4. Deployment sequence — re-derived
  • 5. Discord architecture v2 — pull surfaces + one standing delivery
  • 6. Self-healing
  • 7. Multi-site: the profiles pattern
  • 8. Verification — a pod is verified when its loop closes on a canary