Skip to content

task(atlas): personal-inventory pattern pack — owner-specific identifiers as highest-severity detectors #6049

Open

Description

@dezren39

Parent: #6021 (classification revalidation scan). Research source: prior-art doc ~/workspace/scratch/atlas-ingestion-brief-2026-11-04/prior-art-research.md (2026-11-04). Follow-up 28 (Cluster 5).

Finding (research, in substance)

Generic scanners can't know that a specific street address is sensitive; the owner's own inventory can. A working personal setup layers: (1) secrets via gitleaks-class rules, (2) generic PII via Presidio, (3) matches against the owner's own PII inventory (home address, family names, personal phone, ID/account fragments) loaded from a private file — matches in lower tiers flagged HIGH severity. This third layer is the highest-precision detector available to a personal corpus, and it is unique to it. (Pattern source: https://github.com/danielrosehill/claude-pii-scanner-plugin/blob/HEAD/README.md)

Task

  • Assemble the inventory pattern pack: Drew's addresses, phone numbers, family names, account/ID fragments — patterns, not a plaintext dossier; the pack itself is secret-tier material (stored only in the secret tier / secret store, referenced by name).
  • Wire it as layer 3 of the classification scan (sibling designs under task(atlas): classification revalidation scan — verify nothing sensitive sits at the wrong tier #6021): any hit in the internal tier = HIGH severity quarantine + remediation follow-on.
  • Maintenance rule: how the pack is updated (new address, new account) without scattering copies.

Done looks like

The pack exists in its secret home, the scan consumes it, and one internal-tier sweep with the pack active is reported (counts by pattern class only — never the matched content).

Activity

  1. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  2. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  3. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triaged

  4. added
    user/escalatedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure, deployment, and operationskind/enhancementtask/triageQueue packet kind: verify, reproduce, and route this itemuser/escalatedQueue or user escalation state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions