-
harden dashboard resolver adversarial cases
Kevin Crutt
-
acer: seed component 1 - dashboard resolver (pid,device,ts) -> tightest route
Jessedbrown +1: Claude Fable 5 - tools/behcs/dashboard-resolver.mjs: pure deterministic table-driven
resolver; LAW = tightest possible, NEVER tighter than evidence; 8-rung
demotion ladder (dirty->INVALID, unknown device->GLOBAL_READONLY,
pid/device conflict->GLOBAL_READONLY never guess, bad pid->DEVICE,
malformed/future/stale ts->DEVICE, full proven tuple->AGENT_TIGHT)
- eyes/hands per GAP|1: eyes=route/hbp free read, hands=route/post gated
POST operator-cosign, global scope exposes NO hands
- injection-safe by construction: pipe/CR/LF rejected at rung 1, routes
built only from table keys + regex-validated PID + fixed literals
- room bands scout/review/write/test from PID P-field, declared as DRAFT
ASSUMPTION - bilateral contest welcome
- sealed parity baseline (12 cases, fixed clock, bundle_sha16=
eb3e518644a672e0) - liris pyramid run IS the byte-match, STEP|166 pattern
- pre-hardened against the assigned attack list: missing pid, unknown
device, stale/malformed/future ts, conflict, broad-vs-tight…