design(atlas): classification revalidation cadence — rule-triggered rescans, sampled human audits, allowlist expiry #6051

Activity

1. dezren39

   added

   area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operations

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1716
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-m
   • Session / ID: task 10417
   • Found via: queue claim
   • Task: Triage of issue design(atlas): classification revalidation cadence — rule-triggered rescans, sampled human audits, allowlist expiry #6051 (design(atlas): classification revalidation cadence) — completed, findings below
   • Expectation: s — triage only; the cadence design pass is the scoped follow-on work on this issue
   • Links: parent issue task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021 · ingestion-operations design issue design(atlas): semi-automated ingestion operations — source set, usefulness filter, disk/IO + plan-spend guardrails #6019

   Triage findings (verified fresh 2026-11-05)

   • State: issue design(atlas): classification revalidation cadence — rule-triggered rescans, sampled human audits, allowlist expiry #6051 is OPEN (kind/design, area/infra), no hard-stop labels, no open PR references it, and no substantive comments yet. Parent issue task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021 (task(atlas): classification revalidation scan) is OPEN and not yet run to a conclusion; the ingestion-operations design issue design(atlas): semi-automated ingestion operations — source set, usefulness filter, disk/IO + plan-spend guardrails #6019 is also OPEN.
   • Not already done: no revalidation-cadence spec exists in the repo — code search for revalidation returns only unrelated hits (opencode-claimant migrations, id web assets). The standing-gate design has not been written.
   • Input verified present: the cited research source ~/workspace/scratch/atlas-ingestion-brief-2026-11-04/prior-art-research.md exists in the workspace (same atlas brief set used by the sibling follow-ups).
   • Scoped deliverable (single design pass): the cadence spec the body names — trigger table (rule / inventory-pack / recognizer-set changes), per-layer scope per trigger (deterministic layer in full; NER layer per its task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021 scoping), audit method with sample sizes and a miss-rate estimate, and the allowlist lifecycle (reason + expiry on every entry) — recorded on this issue or in a doc/ record linked from it.
   • Ordering / blocker: this design takes issue task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021's recurrence recommendation as its input. Until the task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021 scan runs and reports (a) one-off vs standing-gate recommendation and (b) the per-layer scoping it actually used, a cadence spec here would be guessing at its two main inputs. Correct order: task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021 scan completes → this cadence design → plug the standing gate into issue design(atlas): semi-automated ingestion operations — source set, usefulness filter, disk/IO + plan-spend guardrails #6019's ingestion-operations design before that design closes. Marked waiting-dependency for that reason.
   • Routing: issue design(atlas): classification revalidation cadence — rule-triggered rescans, sampled human audits, allowlist expiry #6051 stays OPEN as the design ticket; no implementation task until the cadence spec exists.
5. dezren39

   added

   status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

   status/waiting-dependencyWaiting on a dependencyWaiting on a dependency

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
6. github-actions

   assigned

   dezren39

   on Nov 5, 2026