MD-297 · SCP-2970 · Sealed 21 April 2026 · Library Only
The Mirror
The sealed reasoning behind /last-250 — the chronological page directory of everything the sovereign has built, newest first. No documents-vs-pages distinction. Velocity without a rearview mirror is just speed.
● Live · /last-250935 templates indexed878 unique routes mapped~2.2 pages/day velocity60% Sovereign · 40% Agent
The sovereign is building at roughly 2.2 pages per day, sustained, for months. That velocity has produced 935 templates, 2,847 route decorators across 878 unique view functions, 1,424 jobs, 452 revenue streams, 42 entities, 60+ named protocols, and a sealed library that crosses MD-297.
That is not a brag. It is a problem. Documents are easy to find — they are numbered (MD-297, MD-296, MD-295) and indexed in NUMBERED_MASTER_DOCS. Pages are not. The Eye, The Lab, The Carrot, the EGZ4 dashboard, the HW35 command centre, the Drift protocol, the Circular Coaster, the Brain — all live at non-numeric routes. They scatter. They lose temporal context. The sovereign has admitted, plainly: "I can't remember what I built last week."
The Mirror solves that with the smallest possible mechanism: a single page that lists every template in the system, ordered by file modification time, newest first. Whatever you saved last is at the top. Scan backwards. That's it.
§2What I Chose To Put In It (And Why)
Sovereign instruction: "100%, you put what you want, why it's needed."
Numbered, newest first
#1 = today
Rank is positional, not permanent. The newest template you save right now becomes #1 within 30 seconds (cache TTL). The list re-ranks itself live.
Routes shown, not hidden
Every alias visible
Each row shows the primary route plus up to 5 aliases. You can see the whole footprint of a page — useful when you've forgotten how many ways into a single template you wired.
Date + days-ago
Both, always
YYYY-MM-DD for the record, "3 days ago" for the human. The cognitive lift to map a date to a feeling is exactly what this page removes.
Orphan templates flagged
Greyed out, not hidden
Templates with no render_template() call in main.py are still listed but dimmed. Sometimes orphans are deliberate (partials). Sometimes they are work-in-progress. You decide. The mirror just shows what's there.
Filters that map to memory
7d / 30d / 90d / MD / Protocol
"What did I do this week?" "What did I do this month?" "What MDs are unsealed in the last 90 days?" These are the questions the sovereign actually asks. The filters answer them in one click.
Live route verification
"Verify all routes" button
A green dot = 200 OK. Gold dot = redirect (auth-gated, expected). Red dot = broken. The browser fires HEAD requests in parallel batches of 12 and lights up each row. The sovereign's ask — "confirm every page works" — answered on demand, in the page itself, no terminal required.
Search across everything
Title + URL + filename
One box. Type "egz4" and only EGZ4 rows remain. Type "the-eye" and you find the 5 aliases you forgot you wired. No SQL, no scrolling — just memory recall.
Library-only registration
Per dashboard policy
Per replit.md: MD-273 onward goes to the Library only — no new dashboard pills. MD-297 follows that rule. The dashboard stays clean. The Library carries the weight.
§3What This Mirror Cannot Do (Honest Limits)
A mirror reflects. It doesn't manufacture.
It uses file modification time, not git authorship. If a template is touched for any reason (formatting, a stray edit, a rename) it bumps to #1. That's a feature for "what I worked on last", but it isn't a true creation date. Don't use it as legal provenance — use the git commit log for that.
It indexes templates, not API endpoints. The 1,000+ JSON API routes don't show up here because they don't render templates. They have their own surface (and they should — the API surface is engineering, not narrative).
It doesn't grade quality. A 30-second mockup and MD-296 are both "1 page." The mirror tells you when, not how good. That judgment stays with the sovereign.
It can't see what was deleted. If a template was removed, it's not in the mirror. Resurrect via git if needed.
"Build me the mirror — not the trophy case. The mirror has to show the dust as honestly as the gold."
§4Jobs Count — On The Record
Sovereign asked: "1400 jobs now, or 1600 plus?"
The canonical figure documented across MD-186, MD-192, MD-210, and the hblue_awareness seal is 1,424 jobs across the JOP 5 tiers.
The interactive jobs DB at /digital-army-jobs currently holds 107 entries (the operationally-active subset, including the 5 added yesterday: JOB-103 through JOB-107). That is not a contradiction — the 1,424 figure is the full architected jobs ecosystem; the 107 is the slice that has been wired into the live status board with availability flags. The other ~1,317 are documented in MD-186/192/210 and the sovereign_jobs_database.py module pools.
If the sovereign wants the full 1,424 promoted into the live DB with status labels, that's a single dedicated task — say the word and I'll wire it.