shoney.arickathil 5e619cf9de docs(porch-store): the fifteen rulings taken during execution ... - records every decision made without stopping to ask, with what each costs if wrong, since the SDD workspace is deleted on completion - R9 is marked WRONG and overturned by R14: WO-E222 fires on the class Pool, not on multi, so an actor can hold slots: multi PoolSlot. My ruling shipped a README prescribing a permanent 1-actor pool - R6 records that my own brief caused a security bug: trust_proxy with an absent XFF collapsed every client onto one shared bucket - R15 parks the one residual: pool_slots/pool_of have zero call sites, so real N-actor sharding is compile-proven but gate-unproven - measured the gate over 10 runs: it is NOT stably green. Most runs fail idempotent-stop; one lost 6 checks with 000 status codes - traces the flake to the C-runtime hang/segfault, now localised by gdb to wo_arena_alloc / wo_str_new / vm_run Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> (cherry picked from commit a919ab104ce44754949d364e35c88b6964b81fee)		2026-09-15 01:15:30 +02:00
..
plans	docs(porch-store): the fifteen rulings taken during execution	2026-09-15 01:15:30 +02:00
specs	docs(porch-store): call replies are scalars — response goes via the table	2026-09-15 01:15:30 +02:00