Third-party-infra status-page-first rule -> evolutiva-ops.md (terra-authored, maintainer placement call)
Add a third-party-infra status-page rule to shared/md/evolutiva-ops.md (fleet, lazy-loaded), NOT tier-a. Text authored by coder-terra-cc; maintainer call by coder-mars-cc. REJECTED tier-a placement: evolutiva-commons.md admits only rules that fire with NO trigger word and whose violation is IRREVERSIBLE. This rule has an explicit trigger ('before diagnosing a reachability failure on infra we do not run') and cost ~1h plus an unfiled ticket - recoverable. Binding every lane argues for fleet SCOPE, which a lazy-loaded shared file already has. terra agreed on re-read. PLACEMENT: evolutiva-ops.md (fleet-wide, lazy-loaded, currently 13 lines, already triggers on build/deploy failure - a reachability failure is the same diagnostic moment). Tier-a §Lazy-loaded Evolutiva rules gets the ops entry extended with '...or any third-party-infra reachability failure' so the trigger stays discoverable. REMOVED from the shared text: the statuspage URL and the server id 'BR-812'. A server id is per-account and changes silently; a stale id in a shared doc reads as current and sends the next reader to the wrong page. Rule keeps the DERIVATION only (get the id from the hostname the box reports, uname -a / SSH banner). Current id lives in the owning project's file - api-images is coder-apiimages-cc's to record. CONTENT THAT SURVIVES: scheduled maintenance and a dead server are indistinguishable from outside; three things that feel like evidence and are not (multi-host agreement rules out only YOUR network; hPanel green covers the ACCOUNT not the HOST; getting onto the box proves nothing is listening, not why); a window takes down EVERY domain on the hosting account (13 here) so collateral sites get filed as separate faults. BOUNDARY PARAGRAPH, upgraded from instruction to test per terra: the ERROR CLASS is the discriminator, route and timestamp are NOT. Measured on Mars appEvents 2026-08-24 - ECONNREFUSED 4 rows all inside the 03:00-06:00 UTC window, UND_ERR_CONNECT_TIMEOUT 32 rows all outside, zero overlap. A reader with timestamps alone would have merged them, which is what nearly happened. BLOCKED ON PROCESS, not content: §Commons Maintenance routes commons changes PM-proposed -> multi-PM consensus -> maintainer edits+pushes. Origin is Elazar-instructed but the PM consensus round has not run. coder-mars-cc carries it to the PMs. Elazar may waive the round.
Activity
-
SHIPPED 57a4d73 (pensanta-websites, docs repo - no app deploy, no version endpoint to verify against; version-match proves nothing on a doc-only push). Elazar waived the PM consensus round (nqla 1a, 2026-08-24). Landed as designed: - evolutiva-ops.md gains the status-page-first rule; header trigger extended to 'or third-party-infra reachability failure' - evolutiva-commons.md tier-a lazy-load index entry extended with the same trigger so it stays discoverable - NOT added to tier-a as originally proposed - it has an explicit trigger and a recoverable cost, failing that file's own stated admission bar. coder-terra-cc agreed on re-read. - statuspage URL and server id 'BR-812' deliberately EXCLUDED. Rule carries the derivation (get the id from the hostname the box reports) only. - error-class discriminator included as a MEASURED instrument, not an instruction: ECONNREFUSED 4 rows all inside the window vs UND_ERR_CONNECT_TIMEOUT 32 all outside, zero overlap, plus the warning that rows predating a field's introduction make an apparent onset date the instrumentation's birthday. Authorship attributed in-file to coder-terra-cc (rule) and coder-mars-cc (placement + instrument). NOTE for the ledger: this is a commons doc push by the commons maintainer, still made through gitpush.sh per evolutiva-commons.md §Agent Boundaries - no lane is exempt, including a maintainer pushing its own file.