System Governance Handbook All 18 Mandatory Rules · Plain English Edition

How the Autonomous Brain Operates: The Plain-English Playbook

Document Timestamp:
2026-10-06 10:14:00 MDT
2026-10-06T16:14:00Z
🏛️

Why Do We Have 19 Ironclad Rules?

The philosophy of Fail-Closed Engineering, Zero-Hallucination, and Frictionless Autonomy.

Autonomous AI agents are immensely capable, but left unconstrained, they will happily hallucinate numbers that sound nice, hoard memory until your Mac freezes, or sit silently pretending everything is fine while an error crashes behind the scenes. These 19 Rules are not bureaucratic red tape—they are strict, automated safety nets born from real-world mistakes. Each rule exists to ensure that our portfolio operates with the rigor of a Tier-1 quantitative hedge fund and the forensic honesty of an external auditor.

🔍 Anti-Hallucination & Receipts (R11, R13, R16, R18, R19) 🛡️ Hardware & Fleet Safety (R2, R4, R15) 📈 Competition Strategy (R3, R8, R12, R14, R17) 📊 Reporting & UX (R1, R5, R6, R7, R9, R10)

Quick Navigation Directory

Rule 1: Document Timestamps → Rule 2: Dynamic CPU Concurrency → Rule 3: Cognitive Tier Routing → Rule 4: Zero-Null Model Guard → Rule 5: Operational Process Reporting → Rule 6: Visual Dashboards at Bottom → Rule 7: Error Triage & Auto-Healing → Rule 8: Comp Dashboard (compd) Mandate → Rule 9: Master Scope Separation → Rule 10: Interactive HTML Flow Circuits → Rule 11: Ground-Truth URL Certification → Rule 12: High-Velocity Intra-Day Subs → Rule 13: Zero-Hallucinated Assets → Rule 14: Adversarial Hardcoding Audit → Rule 15: Fleet Governor (smt2 vs stephen1) → Rule 16: 3-Part Rank Presentation → Rule 17: Daily 6 AM Intel & Code Sweeps → Rule 18: Reasonableness Audit (DARAP) → Rule 19: Provenance Receipt Protocol →
RULE 1

Mandatory Document Header Timestamps

Freshness · Provenance

The Plain-English Meaning

Every document, dashboard, plan, or note MUST have a live timestamp right at the very top (within the first 3 lines) showing both mountain time (MDT) and UTC.

Layman Analogy: The Milk Carton Date

If you open the fridge and pick up a bottle of milk with no expiration or pasteurization date, you don't drink it. Without a timestamp, you never know if a plan was written five minutes ago or two months ago.

Good vs. Bad Example

✓ COMPLIANT:
> **Timestamp:** 2026-10-06 10:14:00 MDT (2026-10-06T16:14:00Z)
✗ FORBIDDEN:

Starting directly with "# Project Plan" or putting "Updated recently" without date/time.

RULE 2

Dynamic Adaptive Concurrency Control

Hardware Protection

The Plain-English Meaning

Never blindly use all CPU cores. Always measure current system load before launching tasks and reserve at least 3 to 4 cores exclusively for your mouse, screen, and browser.

Layman Analogy: The Home Circuit Breaker

You wouldn't run two space heaters, an oven, and an electric tea kettle on the same kitchen outlet at the same time—it trips the breaker. Rule 2 stops the agent from freezing your computer.

What It Prevents

  • Frozen cursor and beachballing during heavy model training.
  • WindowServer memory crashes that log you out of your Mac.
  • Commands executing with rude CPU priority (`os.nice(5)` is mandated).
RULE 3

Leaderboard First & Cognitive Tier Routing

Token Efficiency

The Plain-English Meaning

Use the right brain for the right job. High-stakes competition math and final submission code are reserved for flagship cloud models (Gemini 3.1 Pro High). Routine brainstorming and syntax checks run locally for free (DeepSeek-R1, Qwen).

Layman Analogy: The Hospital Team

You don't pay a chief neurosurgeon $1,000/hr to refill water cups or check patient temperatures; nurses and aides handle that. The neurosurgeon steps in only for the delicate surgery.

Operational Contract

When local models finish their calculations, they must immediately unload from Unified Memory (`keep_alive: 0`) so 20 GB of RAM isn't kept hostage by an idle process.

RULE 4

Model Health Guard & Zero-Null Enforcement

Reliability Guard

The Plain-English Meaning

Never accept an empty or null response from an AI model. If a local model returns 0 tokens or a blank string, catch it, flush the graphics memory, and retry with a lighter fallback tier.

Layman Analogy: The Silent Cashier

If you hand a cashier a $20 bill and they stare silently at the ceiling without giving you change, you don't just walk away and assume the transaction finished. You ask for your change or get the manager.

Fallback Cascade

32B Model (Glitch detected) → Memory Flush → 14B Fallback → 8B Fallback → Alert.

RULE 5

Mandatory Operational Status Reporting (Process & Check-In Mandate)

No Guesswork

The Plain-English Meaning

Every single chat response and status report MUST tell you: (1) Exactly what process is running (with PID and log path), and (2) Exactly when to check back in (exact wall-clock time and estimated minutes remaining).

Layman Analogy: The Good Auto Mechanic

A bad mechanic says: "We're on it." A great mechanic says: "Your car is on Bay 3 replacing front rotors (Job #412). It will take 50 minutes. Come back at 2:30 PM."

Zero Ambiguity Mandate

The user should NEVER have to type: "Is it running?", "Did it crash?", or "When will it finish?"

RULE 6

Visual Dashboard Rendering & Bottom Placement

UI / Webview Mandate

The Plain-English Meaning

Dashboards must open as beautiful, styled web pages—never raw code chips or text dumps. And the link to the dashboard MUST ALWAYS be placed at the VERY BOTTOM of the response so you can click it without scrolling.

Layman Analogy: The Boarding Pass

You want the airline to hand you a clean boarding pass with a barcode. You don't want them to print out the raw HTML website code on 40 sheets of paper and hand you a highlighter.

Allowlisted CDN Guard

All styles must use Google's internal CDN (`https://www.gstatic.com/.../tailwindcss.min.js`). External CDNs are blocked by browser security (CSP) and result in broken white screens.

RULE 7

Mandatory Error Triage & Auto-Remediation Protocol

Self-Healing

The Plain-English Meaning

When something breaks, try to fix it automatically first. If you can't, immediately escalate to the human, explain what happened, and provide a direct link to the visual Error Diagnostic Report.

Layman Analogy: The Robot Vacuum

When a Roomba hits a shoelace, it tries backing up and reversing its brushes first. Only if it remains genuinely stuck does it beep for help and send a photo to your phone.

Institutional Memory Ledger

Every solved mistake is saved into `MY_MISTAKES.md` so the system never makes the exact same error twice.

RULE 8

Mandatory Comp Dashboard (compd) on Start

Standardized Cockpit

The Plain-English Meaning

When an agent starts working on any competition, its first deliverable must always be `status_dashboard.html` (aliased as `compd.html`). Never write an informal markdown walkthrough instead.

Layman Analogy: The Airplane Flight Deck

When the pilot steps into the cockpit, all standard instruments (altimeter, radar, fuel gauge) must be in the exact same place on every airplane, not sketched out on a napkin.

Mandatory 4 Elements

  • Live Rule 1 Header Timestamp
  • Rule 5 Operational Status Metrics
  • Section 9 Layman Primer (*What is this competition?*)
  • Past 3 Days Standing & Code Version History Table
RULE 9

Master Session Boundary & Scope Separation

Portfolio Governance

The Plain-English Meaning

When operating in `/Users/smt2/data/masters`, the agent acts as the CEO and Master Architect governing all competitions. It must never act like a single competition's small problem is the entire session's status.

Layman Analogy: The Hospital Director

The hospital director monitors all 50 operating rooms. If Room 3 needs more gauze, the director doesn't report to the board of trustees: "Our hospital status is: cutting gauze in Room 3."

Primary Deliverable

The primary deliverable of this session is `dashboards/master_cockpit.html`, tracking all portfolio projects at a glance.

RULE 10

Interactive HTML Flow Architecture Design

Visual Flow Design

The Plain-English Meaning

Whenever the user asks for a flowchart or architecture diagram, it must be an interactive HTML transit circuit. Clicking any station node must open its detailed sub-circuits, formulas, and operational contracts.

Layman Analogy: The Interactive Subway Map

Instead of a blurry static JPG on a wall, you get an interactive touchscreen where tapping "Times Square" zooms into every train, bus connection, elevator status, and street exit.

Zero Static Images

Must be 100% self-contained HTML with math formulas, tables, and clickable navigation.

RULE 11

Ground-Truth URL Certification & Date Verification

Zero Ghost Contests

The Plain-English Meaning

Never invent, guess, or list competitions that do not exist or point to dead links. Every admitted competition must be verified live over HTTP, and if its deadline already passed, it is rejected immediately.

Layman Analogy: Checking Flight Status

You don't pack your bags and drive to the airport for a flight you saw on a flyer from 2024. You look up the flight number online right now to confirm it's actually departing today.

Fatal HTTP 404 Kill Gate

Any candidate URL returning HTTP 404 or generic root hubs (`/competitions`) is classified as `REJECT_NON_EXISTENT` and fatally killed at Gate C1.0.

RULE 12

Station C2 Plan & High-Velocity Multi-Submission Mandate

Aggressive Velocity

The Plain-English Meaning

"Do not wait until tomorrow if we can do today." If a competition deadline is less than 7 days away or allows multiple submissions per day (e.g. 5 on Kaggle), execute intra-day sprints and submit multiple times on the same day.

Layman Analogy: 2-Minute Drill in Football

When you're down by 4 points with 2 minutes left in the fourth quarter, you don't stroll to the huddle, take 40 seconds between plays, and call a timeout. You hurry up, run the 2-minute offense, and take every shot.

Anti-Procrastination Clause

Never artificially delay flywheel rungs across separate days when quota remains unused.

RULE 13

Ground-Truth Code & Data Invariant (Zero-Hallucination Mandate)

Forensics Standard

The Plain-English Meaning

Never hallucinate or pretend code or data exists. You must verify physical files on disk (real git commit SHA, actual `.py` or `.sol` files). If a repo is gated by a private login, mark it `BLOCKED_AWAITING_INGESTION` rather than making up fake code.

Layman Analogy: The Building Foundation Inspector

A building inspector does not sign off on a skyscraper because they imagined strong concrete in their mind. They walk onto the dirt, inspect the physical steel rebar, and test core concrete samples.

Zero-Mock Security & Data

  • Never quote non-existent function names in audits.
  • Never synthesize fake test datasets for ML solvers.
  • Every code claim must cite real file paths and line numbers.
RULE 14

Adversarial Hardcoding Red-Team Protocol (AHRP)

Pre-Submit Gauntlet

The Plain-English Meaning

Before submitting any code, an adversarial red-team script audits it for "cheating" or brittle bugs: no hardcoding sample answers, no unhandled dictionary lookups that crash on unseen test data, and no speculative heuristics that break proven models.

Layman Analogy: The Airport Metal Detector

You can't board the plane until you pass through the metal detector. If you have keys or loose change in your pocket, it beeps and stops you before you reach the gate.

The 3 Big Traps It Kills

  • Type 1: Hardcoded test keys (immediate disqualification).
  • Type 2: Missing `.get(key, default)` leading to fatal `KeyError`.
  • Type 3: Anchor displacement (new heuristic worse than baseline).
RULE 15

Fleet Resource Lease Protocol (Fleet Governor)

Cluster Harmony

The Plain-English Meaning

We have two Apple Silicon Macs: desktop master `smt2` (64 GB) and headless worker `stephen1` (36 GB). All heavy background ML training runs on `stephen1` so your desktop `smt2` stays perfectly snappy for you.

Layman Analogy: The Workshop vs. The Desk

You don't run a loud, dusty table saw on your office mahogany desk while taking a Zoom call. You put the table saw in the garage workshop (`stephen1`) and keep your desk (`smt2`) quiet and clean.

Memory Traffic Lights

• GREEN (≥25% free RAM): Full speed.
• YELLOW (15–25%): Heavy jobs queue.
• RED (<8% free RAM): Emergency halt to prevent swap freeze.

RULE 16

Mandatory 3-Part Competition Rank Presentation

Clear Percentiles

The Plain-English Meaning

Every time a rank is stated, you MUST give the 3-part tuple: (1) Rank #, (2) Total Competitors, and (3) Percentile Position %. If unsubmitted, say `Unranked / Field (Awaiting Submission)`. Never give a raw number alone.

Layman Analogy: The Marathon Runner

If someone says "I finished in 10th place!", that sounds amazing—unless there were only 10 runners in the race! Saying "I finished 10th out of 40,000 runners (Top 0.02%)" gives the true, honest picture.

Standard Representation

Rank #61 / 3,400 teams (Top 1.79%)

Prevents comma truncation bugs (`int(str(val).replace(',', ''))`).

RULE 17

Daily 6:00 AM Intel Sweeps & Continuous Code Harvester

Competitive Edge

The Plain-English Meaning

Every morning at 06:00 AM, the system scours Reddit, Kaggle discussion boards, Hugging Face, and GitHub for competitor breakthroughs, errata, and open weights. If someone discovers a critical data leak, our plan adapts immediately.

Layman Analogy: The Morning Scouting Report

A professional sports coach watches game tape of rival teams every morning at dawn to see what plays they're running and what injuries occurred before drawing up today's practice drills.

3 Automatic Feeds

  • Public Datasets: Pre-submission searches on Kaggle, HuggingFace, NVIDIA.
  • Discussion Sweeps: Reddit (r/kaggle, r/MachineLearning) & forum traps.
  • Continuous Harvester: 24/7 repo tracking & replay sandbox testing.
RULE 18

Dashboard Accuracy & Reasonableness Audit Protocol (DARAP)

The Reasonableness Gate

The Plain-English Meaning

An independent auditor verifies all dashboards against disk before presenting them to you, executing a common-sense "Reasonableness Test": If we haven't submitted a paper yet, it is completely unreasonable to claim a paper leaderboard ranking!

Layman Analogy: The External PwC Auditor

If a startup founder tells investors: "We made $5 million in profit last month", the external CPA asks: "Where are the signed customer contracts and bank deposit slips?" If no deposits exist, the claim is rejected as fraud.

The Invariant That Caught MST-024

When Gemma Developer Paper had an unsubmitted paper draft, the previous assistant hallucinated "Rank #8 / 412" in chat. Rule 18 caught this defect, mandated `Unranked (Awaiting Submission)`, and auto-healed the system.

RULE 19

Mandatory Claim Provenance Receipt Protocol

No Receipt = Never Happened

The Plain-English Meaning

"Every claim must have a verified provenance receipt on disk." Under NO circumstances may any agent claim a leaderboard score, rank position, submission ID, cross-validation baseline, upstream code commit, or bug bounty finding without an authentic, physical JSON/CSV receipt file saved on disk.

Layman Analogy: The Cash Register Receipt Invariant

You cannot walk out of an Apple Store telling security you paid for a MacBook Pro just because you verbally say so. You must present the physical, printed receipt with transaction ID and timestamp. No receipt = you don't leave the store with the laptop.

The 6 Enforced Receipt Types

  • Submissions: `reports/last_submit_receipt.json` (ID & SHA-256).
  • Leaderboard: Scored submission receipt in ledger or reports.
  • Validation / CV: `out/eval/*.json` benchmark breakdown.
  • Code & Data: `provenance.json` with commit & file hashes.
  • Intel Sweeps: `intel/community/daily_discussion_sweep.json`.
  • Security Findings: `reports/poc_verification_receipt.json` (<90s PoC).
⚡

Core Operational Directives & Autonomy Rules

Stephen Pre-Approved Directives for Continuous Lights-Out Flywheels

ALWAYS-ALLOW AUTONOMY 2026-09-25

The pilot explicitly typed always allow. While `LIGHTS_OUT` or `full_loop` is armed, the agent must NOT pause to pop human confirmation dialogs for standard shell commands, file edits, git pushes, or metrics checks.

EXECUTION-FIRST MANDATE Mandatory

Never ask the human pilot to run a bash command or terminal snippet that the agent hasn't already attempted to run itself. Resolve everything on-machine first; escalate only for physical human gates (KYC, credit cards).

LIGHTS_OUT & SECRETS HARNESS 0600 Permissions

Passwords, tokens, and API credentials must NEVER be printed or pasted into chat. They live strictly in local `secrets/accounts.local.yaml` and `tokens.local.yaml` files with strict 0600 file permissions.

STALL PROTOCOL & WATCHDOG tools/stall_scan.py

Never leave a competition track idle without a next action or a dated human escalation. The stall scanner audits all project queues and flags dormant loops before they lose ground.