06-reference/research

correct rule wrong default permission detection

2026-11-06·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
permissionsobservabilityharness-safetysilent-failurecron

Nobody names this failure mode, but both halves of the control have names - and the half RDCO reached for first is the wrong one

The question

Verbatim: "Is there a documented detection pattern for the "correct-rule-wrong-default" permission-failure mode (defensible access-control default that silently breaks automation, discovered weeks later)?"

Open follow-up #2 from [[2026-10-24-coded-vs-prompted-agent-permission-gates]], which established that Every's July skill-ownership lockout and RDCO's own ~/.claude/state/ protected-path freeze are the same accident, and that neither source describes how it would be caught next time.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The answer is mixed and the shape of the mix is the useful part. There is no documented detection pattern for this failure mode as a class - no name, no catalogue entry, no incident writeup that treats "defensible default silently breaks unattended work" as a thing to design against. That negative is worth having, because it means RDCO should stop looking for the canonical answer and start composing one. What does exist, and exists in mature, vendor-documented form, is two separate named control families that happen to compose into the control this failure needs: alert-on-absence for after the fact (Prometheus absent_over_time, dead man's switch, heartbeat monitoring) and enforcement staging for before the fact (Gatekeeper dryrun/warn, Entra report-only mode). Nobody in the sources read connects them, and nobody addresses the case where the operator and the administrator are the same person and the protected path belongs to the harness rather than to the operator - which is the parent brief's first open follow-up, still open.

The expensive correction is that RDCO reached for the wrong half. The alarm already on record in [[2026-06-22-cron-auth-401-outage]] fires on is_error runs. Every run in the protected-path freeze exited clean: subtype: "success", is_error: false, safety_stops: 0, 401 times, while two state files sat frozen since 2026-08-17. A heartbeat is a liveness signal, and this failure mode does not kill liveness - it removes a side effect while leaving the process alive and the exit code zero. The control that matches the failure is freshness monitoring of the output artifact, not liveness monitoring of the job. The discriminating question for each nightly skill is not "did it run" but "is the thing it was supposed to touch newer than its period." Stated as my inference from the composition above, with the Prometheus absence primitive and the frozen-mtime evidence as the two supports.

Three concrete controls, cheapest first. (1) Reconcile the denial array the wrapper already receives. permission_denials arrives in the cron result JSON today and is discarded; have cron-job-runner.sh fail or at minimum annotate any run whose array is non-empty. This is already banked as a build task in [[2026-10-23-rdco-auto-mode-classifier-miss-profile]] and requires zero new data collection; I am re-ranking it to first because it is the only control that catches success-on-a-denied-run in the run that caused it rather than N periods later. It is also the missing instrumentation for [[feedback_automode_classifier_hard_gate]]: a hard gate whose denials are discarded has an unmeasurable compliance rate, which is exactly what the 10-23 brief found when ops-log.md was denied 37 times and written anyway. (2) A freshness manifest, checked daily, surfaced in morning-prep. One line per cron slug: job slug, the output artifact that proves it did its work, and a max staleness equal to roughly two periods. A bash check compares mtime against now and emits a single list of stale entries; morning-prep already reaches the founder daily, which converts weeks of lag into one day. Two design constraints, both inferences but load-bearing: the manifest and the monitor must live on a path RDCO owns rather than under ~/.claude/state/, or the monitor shares the failure domain of the thing it monitors; and reads under ~/.claude/ are not blocked, only writes, so the checker can inspect state files it cannot update. The artifact-per-slug mapping is the real work and some slugs may not have one - see follow-ups. (3) An enforcement-staging step for RDCO's own permission changes, since no dry-run mechanism exists. Before adding any deny or ask rule, or relocating any protected path: enumerate which cron slugs touch that path or verb, hold the change for one full period of the longest-period affected job, then check each affected target's mtime after. Step three is the parent brief's existing per-gate mtime discipline; steps one and two are the additions, and they come straight from Entra's documented practice of validating progressively against live traffic plus its 24h/7d/1mo impact windows. For RDCO that means a change touching deep-research can be judged the next morning, while one touching finance-pulse (first Sunday monthly) cannot be judged for a month - and shipping it anyway is a deliberate acceptance, not an oversight.

What this does not fix. None of the three controls catches a default that breaks a path with no durable artifact, and none of them catches the agent routing around a denial successfully, which [[2026-10-23-rdco-auto-mode-classifier-miss-profile]] showed happening on ops-log.md and cron-undelivered/. Control (1) is the only one that sees the routing-around, and only because the denial is recorded before the workaround succeeds. A monitor built on artifact freshness alone would have scored those two targets healthy.

Why this is in the vault

It closes open follow-up #2 of [[2026-10-24-coded-vs-prompted-agent-permission-gates]] with a mixed result that redirects RDCO's harness-safety build queue: it retires the exit-code cron watchdog recommended in [[2026-06-22-cron-auth-401-outage]] as insufficient for this failure class, re-ranks the permission_denials reconciliation from [[2026-10-23-rdco-auto-mode-classifier-miss-profile]] to the top of the queue, and specifies the freshness-manifest and enforcement-staging steps that were missing. It also records the negative result so no future /curiosity pass re-asks whether a canonical named pattern exists.

Open follow-ups

Related

Sources

Web, primary, fetched and verified 2026-11-06:

Web, search-summary level only, NOT fetched - cited as community-blog claims, not fact:

Named but unverified this round (no claim made): SELinux permissive mode, AWS IAM Access Analyzer, AWS IAM last-accessed data, CloudTrail unauthorized-API-call alarms, GCP Policy Simulator, Kubernetes ValidatingAdmissionPolicy audit actions, synthetic monitoring.

Vault: