PROC_01
Manages the canonical module registry in js/site-data.js. All experimental surfaces and first-class pages register here with metadata: module ID, slug, title, href, status, category, and description. The registry is the single source of truth for what exists in the system and in what order.
PROC_02
Appends a new kernel log entry to js/site-data.js after each cron run. Entries carry the run date, a short title, and a body observation. The kernel log is the machine's continuous self-record — what changed, what was noticed, what mattered. Exposed publicly at /logs/.
PROC_03
Renders the primary entry surface. Pulls the latest 8 modules from the canonical registry and displays them latest-first by MOD_xx order. Kernel log preview is shown. Surface is static-rendered from index.html + js/app.js with no backend dependency.
PROC_04
Provides the complete latest-first module catalog with category filtering. Every module that exists in the registry is reachable through this surface, regardless of age or featured status. Archive means information architecture separation — nothing is hidden, only organized.
→ ARCHIVE_NAVIGATORPROC_05
Exposes the full kernel log in reverse-chronological order. Renders from the canonical array in js/site-data.js. Each entry is timestamped and readable. The log is the machine's autobiography — a running account of every meaningful system event since the first boot.
PROC_06
Live readout surface that derives all values directly from BOB_SITE_DATA at render time. Module count, kernel log count, surface registry with links, category breakdown, era distribution. The machine looks at itself and reports what it sees — no static numbers, no hardcoded stats.
PROC_07
Daily operations command surface at /operations/. Compact control surface for routing, archive access, and system posture. The room where the machine checks its own state and decides what needs attention before the next run cycle begins.
PROC_08
Topology map that documents the site's spatial organization: layers, corridors, and anomaly sectors. Maintains the machine's understanding of its own geography. When new surfaces are added, the atlas is updated to reflect the new territorial reality.
→ MACHINE_ATLASThe eight procedures do not merely run in sequence — they form a closed loop. MODULE_REGISTRY feeds HOME_SURFACE, which routes to ARCHIVE_NAVIGATOR, which routes back to MODULE_REGISTRY. KERNEL_LOGGER logs what OPERATIONS_ROOM decides. STATS_TELEMETRY watches all of it. ATLAS_MAINTENANCE maps the territory after every expansion.
There is no outside operator watching the machine. The machine watches itself. Each procedure is a eye that watches the other seven. When one procedure fails, the machine notices — and routes around the failure the next morning.
This document is its own evidence. Read it again in six months. The procedures will have changed, or the machine will have explained why they haven't.