// Last Updated — Change Log
2026.08.24The instrument grades itself. Housekeeping in three rooms, all in the same spirit. The exhibit’s panel is now a ledger, not a sentence — one stat per line, its definition under it, and a split where the data itself splits: before source tagging, events by type; after, sources by type. Nothing crosses that line by inference. The privacy page tells the same story the code now does — the twelve-character source fragment is disclosed, dated, and bounded by the nightly salt. And the human count got stricter: an automated browser is not a person, including ours. Our own Depth Skimmer rendered every page like a visitor and was quietly counted like one — roughly eight “human visits” per skim. It now announces itself and is seen, not counted. The Skimmer, meanwhile, stopped hedging twice: structured data is validated locally instead of merely detected, and domain expiry climbs three rungs — aggregator, registry, WHOIS — and names the one that answered. Two entries in its Coverage Ledger moved from partial to measured, and the first site it graded on the new rules was this one.
2026.08.22Open wound, under care. The exhibit’s numbers are wrong and we’re saying so before they’re right. Two fights at once: the database was being polled harder than any visitor deserved — a hundred gigabytes moved this month for a page that should sip — and the visitor count was never counting visitors. Every hop through the Maze stood in for a person, then the lifetime ledger flipped the other way and counted next to nobody. Same root: no event ever carried a source. It does now — a daily-salted token, never an address, gone by tomorrow — and the ledger has one recount mechanism instead of two racing each other. The totals you see today are mid-correction. We’ll update this line when they’re accurate, not before.
2026.08.21The ledger beneath the feed. Armor so good it stopped our own blood: X-Frame-Options DENY — shipped as clickjacking protection — refused our own Maze inside our own privacy page for a day. SAMEORIGIN now; external framers stay blocked, the house may frame itself. Then the exhibit’s counters got audited: a 943-bot storm flushed weeks of history out of the public feed’s 2,000-row memory, and “all time” was quietly reporting the feed’s horizon, not the truth. Every event was always archived — 365-day rolling, nothing lost — the label just claimed more than the window held. Now a lifetime ledger survives the trim: totals accumulate as events drain, the archive backfilled the weeks the feed forgot, and ALL TIME says “since” and means it. The flow shows the last two thousand signals; the numbers remember everything.
2026.08.20The heaviest page. /board-members on a prospect crawl: found on nine pages, fetched never — 200s with no page inside. Three theories died in daylight (timeout, rate limit, then the truth: a CSR shell served to non-browser fetches, and our own render-client shooting the worker at a hardcoded 12 seconds — the box never missed, it was killed by its caller). Fix shipped as a ladder: failure reasons on every record (timeout · http-status · conn · soft-block-200, first bytes kept as evidence), shape-aware retries, staggered launches — no more simultaneous volleys — and rescue renders that finally get to finish: 20 seconds and a settle hint. Failed pages now read “not assessed,” never “nothing there.” The instrument stopped blaming pages it couldn’t reach. Postscript, same night: it fell once more — new mechanism. The render worker takes jobs one at a time and never learns when a caller quits, so enrichment renders were clogging the line ahead of the one render that mattered. The queue tilt: enrichment waits four seconds, rescues reach the worker first by construction. Verified live — the page that failed four ways reads rescued, repeatably. Also: a 404 page at last — you are not lost, the map is.
2026.08.20The doors. Surface Skim rests for maintenance — one honest banner behind its old address. New door: /scan/⟨yoursite⟩ arrives with the target loaded and the run button breathing; an edge function titles each shared link after the site it points at. The guided walk: run → the topology takes the stage → the summary button glows at the foot of the screen when the last layer lands → the findings inherit the light. Nothing pre-checked, ever — the attestation is yours to make.
2026.08.20The face. OG card built from our own parts: the wolf on his native dark, the Markov blanket from the card art layered behind glass, the motto printed on the weave it describes. Favicon: the nav polygon mid-scramble, one vertex flaring — the System caught working, seed 64. Nineteen card versions to earn the name. And the physician healed thyself: morning self-skim found eleven defects on this very site — missing headers, no sitemap, bare canonicals, a title collision, the tool’s own missing share card — evening deploys erased them, verified by the same instrument that found them. Two flags remain, both chosen.
2026.08.19How to resolve. Every finding on the board grew a button: tap, and an AI reads the evidence this run actually collected — your robots.txt as fetched, your platform’s fingerprint — and teaches the fix in plain language, hedged where honesty demands it, capped by the well, never automatic. Free tier’s automatic pass rides the smaller model; the tap gets the better one. Below every answer, the same line: ai-generated, not a substitute for professional analysis. The robots.txt contradiction (three domains, two sheets disagreeing about one file) retired the structural way — one derivation, every consumer, and the report now reads your robots file back to you rule by rule, AI crawlers included.
2026.08.0—Day 2.1 drop-ins. Stale copy swept, EZ-Read sitewide — larger, brighter text on every page, one toggle. Platform fingerprints for the small-business web (Wix · Weebly · Duda · GoDaddy · BentoBox) and the AI pass rebuilt on a hallucination leash — cite what you see, flag nothing you cannot point to. Site chrome counted once: nav and footer are one element no matter how many pages carry them, and every verdict wears one of five honest confidence labels, from confirmed with evidence attached down to by design. The report stopped double-counting and started saying how sure it is.
2026.07.3—Depth Skimmer, Day 2 and the render worker. A persistent headless Chromium on real iron — pages read as a visitor’s browser builds them, buttons probed for living handlers, verdicts tiered by evidence: confirmed · verified · resolves · unconfirmed · by design. Canonical addresses counted once, aliases named, robots honored past the front door with skips reported, the spoofed UA retired for an honest one — the crawler announces itself now. Orchestrated windows with continuation tokens; the well burns once. Suite grew from 94 locked facts to two-hundred-plus, including the extractor bug’s tombstone — and it kept growing all month, every fix buried with a test on its grave.
2026.07.28Staging cleaned to main. The site is live. Two doors became one.
2026.07.24Front-face pass. Fonts self-hosted — six latin subsets, ~90KB, first-paint flash eliminated sitewide. Hazard tape retired; the seam breathes instead. Portfolio rebuilt as Built & Running — the instrument is the exhibit. Mobile keeps the brain. Contact intake + live Depth Skim moved to the front page. THE WELLS — server-truth token gauges per tool, global counters only, nothing about who; donated capacity rolls over. Markov blanket resurrected — killed by a nav-refactor null three pushes ago, found by autopsy diff, guarded for good.
2026.07.——Telemetry v2 + the Maze. Session-chain signals — no cookies, no stored IPs, ASN only and the address is discarded in transit. Batched edge writes. Public exhibit feed. Privacy covenant rewritten in the same commit, as the rule demands. robots.txt with three doors. Contact form wired live.
2026.07.——Dual-gate hub — /tools and /rndlabs, one file, two doors. Node registry as single edit point. WildSpeak doors opened (/ws). Forge functions — word-level timestamps from audio, server-side.
2026.06.——Recon cockpit v0.9e series — three view modes, annotated XLSX export with in-page AI pass, renderer un-mirrored into one shared depth engine, Pursue-to-Depth-Skim handoff.
2026.06.——KRF protocol formalized — the recon discipline gets a name. AART converted to manifest-driven datasets. Pipeline split — staging and production branches, one repo, two doors.
2026.05.25Surface Skim hardened — SSRF blocklist, domain blocklist, robots.txt good-faith check, rate protection, prompt length cap. Three-option attestation flow. Business impact column added to Excel export. Hidden disclosure sheet. Scraped elements sheet. Semantic geometry reframe — "potentially deprecated / likely fine" language throughout. CRC orbital bubble system, intent tag surfacing, click/charge/chase/scatter interactions. Depth Skim first draft — three-layer crawler, 3D signal topology visualization, I/O terminal tower geometry, pit of fractious intent.
2026.05.19LLC approved. Major push — Client Vault (Firebase, timed slots, access codes, AES-256-GCM encryption, server-side admin auth). Surface Skim tool launched — AI-powered semantic surface analysis, Excel export, signal map visualization. Privacy page. Cursor system extracted. Nav fully wired. Stripe deferred — request flow active.
2026.05.18Hero animation upgraded — chaos system, ephemeral clusters, semantic concept arcs, chain link rolls, rotating anchor.
2026.05.17Services page added. Nav wired. Hero copy updated — problem geometry framing.
2026.05.16Google Workspace activated. Business email in progress. Domain secured.