Skip to content

task(atlas): audit existing embeds for provenance/path correctness against the marking standard #6029

Open

Description

@dezren39

Parent: #6018 (Atlas ingestion program). Statement S34 of the 2026-11-04 brief. This is a task to execute, not only a design.

Task (Drew, in substance)

Scan all existing embeds and determine whether they use the appropriate path or details. The current corpus (107,639 chunks across the production monolith and the restored shards) accumulated over multiple ingestion eras with different conventions. The program's provenance standard (extensions on #3125) requires every embed to carry a correct origin mark — repo@hash:path for git content, or a source-system mark (system @ machine @ date) for the rest. This audit measures how much of the existing corpus meets that bar and produces the defect list a repair pass would work from.

Scope

  • Inventory the provenance/path metadata actually present per chunk source class: well-formed repo@hash:path? path without hash? hash without path? free-text source strings? nothing?
  • Correctness, not just presence: does the recorded path exist at the recorded hash? Do source-system marks name the right machine/date (e.g. session chunks attributed to the wrong host store)? Sampled verification against the live sources (repos on the laptop, the OpenCode DBs, the canonical atlas content stores: internal 18,235 sessions / 70,987 messages + secret 90 / 564 per the restoration records).
  • Duplicates and orphans: chunks whose provenance points at sources that no longer exist, and duplicate chunks carrying divergent provenance (same content, different claimed origins) — both are logged states per the standard, and the audit counts them.
  • Tier split throughout: report internal and secret tiers separately; handle secret-tier findings under the classification task's sensitivity rules (sibling task under #6018 — counts and IDs, never content).

Done looks like

A dated audit report: per-class counts (well-formed / defective-by-kind / missing), sampled-verification results, and a sized repair backlog (fixable by re-derivation from sources vs needs re-ingest vs unrecoverable-but-logged) filed as follow-ons. The audit itself changes no data.

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
    on Nov 5, 2026
  3. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  4. added
    work/assignedQueue worker lifecycle state
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  5. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  7. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    agent-note:v1 — task 10396 (triage, #6029) picked up by lane code-u and handed off to the opencode execution lane (assigned_lane=opencode). The opencode-claimant launches the bound opencode session, which drives task 10396 to its terminal state. Labels synced: queue/claimed + status/in-progress + work/assigned. (Posted via the developing.today GitHub App — user gh token is rate-limited.)

  8. 66 remaining items

  9. added and removed
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    on Nov 6, 2026
  10. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  11. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 6, 2026
  12. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  13. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  14. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

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/enhancementqueue/parkedQueue task is parked (waiting on CI, time, or an event)status/parkedDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions