Skip to content

armgit / qm

Public Imported from GitHub
0

Multiplayer agent harness for work.

Drop the Hand-managed infrastructure lens from the Wall of shame (#2510)

Regan Bell9f1a3ac189f9
diff --git a/docs/SPEC.md b/docs/SPEC.md
index 18c14a85e..2992a4ec6 100644
--- a/docs/SPEC.md
+++ b/docs/SPEC.md
@@ -168,12 +168,6 @@ Replacing or swallowing a failure so the evidence needed to diagnose it disappea
- **Rejected session titles:** `sanitizeTitle` returned `undefined` for rejected model output. The fallback title made the request look successful, while neither the rejected text nor the rule that rejected it reached the error log. _Status:_ [qm#1303](https://github.com/yc-software/qm/pull/1303) records the rejection rule and a bounded sample in the durable error log.
- **Failed transaction rollback:** `withPgTransaction` and copied transaction handlers awaited `ROLLBACK` before rethrowing the original error. If rollback also failed, its exception replaced the actual transaction failure. _Status:_ still present on main; [qm#1834](https://github.com/yc-software/qm/pull/1834) proposes preserving the original error and discarding the broken connection.
-### Hand-managed infrastructure (1 example)
-
-Changing deployed infrastructure by hand (console edits, one-off CLI calls) instead of in the infrastructure-as-code that owns it. Hand edits drift from the code, get reverted by the next apply or deploy, and leave sibling environments configured differently. Put the setting in the Terraform or deploy config and apply it from there; if an emergency forces a live edit, land the matching code change before calling the work done.
-
-- **Load balancer and task settings** (2026-10-20): A production deployment ran two blue/green stacks whose load balancers were configured by hand. Request logging was on for one stack and off for the other, so after traffic moved, per-route latency could not be measured. A web-ui CPU increase was first applied with a one-off task-definition registration, and the next config-driven deploy would have reverted it. _Status:_ the CPU size is in deploy config; load balancer logging is still hand-managed.
-
### Historylessness (always reviewed, 5 examples)
Growing the codebase to keep every path it ever took alive. The canonical case: a conditional that string-matches IDs or prefixes because older rows lack a typed field. Trust the typed field; rows without it get no special handling, and if they matter, migrate them once. The same goes for compatibility shims, dual reads and writes, and old endpoints or data shapes kept beside their replacement. Make the breaking change and let people adapt; agents can usually smooth over the breakage for existing users. If keeping an old shape truly seems necessary, ask the user rather than building it. The codebase represents the system at its current best, without sedimentary layers of how it got there.