feat(atlas): schema-driven filter surface — implementation programme (from design #5410)

Implementation programme for the design note landed for #5410: doc/2026-11-05T13-03-49Z_design_atlas_manifest_filter_surface/ (PR #6223, merged f86e532). Recommendation there: GO, with phasing. Design only was authorized for #5410; this issue tracks the build.

Phases (design note §8)

Phase 1 — atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 escaping fix, implementing the note §5 exact semantics (JSON-encode the value, then LIKE-escape the encoded element text; invariant = decoded element equality). Already filed as atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375; lands first.
Phase 2 — Manifest schema + loader in atlas-core; today's surface expressed as the built-in manifest; generic label store (generic_list shape, note §4) + its query construction. Oracle: parity fixtures byte-identical under the built-in manifest.
Phase 3 — Generic dimensions end-to-end: atlas-proto FilterSpec dimension map (named fields as aliases for one release), CLI flags generated from the loaded surface, serve-mode validation against the effective surface.
Phase 4 — Serve-mode CacheKey gains (manifest_version, content_hash) (note §7); surface identity in job metadata.
Phase 5 — Manifest writer in the classification/publish pass (same transaction as the labels); acceptance gate: one new generic_list dimension (e.g. source-app) shipped by manifest only, no binary change.

Invariants (note §6, non-negotiable)

Sensitivity/ceiling semantics stay code-defined; no sensitivity keys exist in the manifest schema; shapes/stores are code-allowlisted; unknown request dimensions are loud errors; manifest failure falls back to the built-in surface loudly, never silently widening.

NO-GO trigger (note §10)

If the classification/publish pass cannot write the manifest in the same transaction as the labels in both modes (local publish file + Turso), stop and re-take the §3 home decision before loader work.

Filed by queue worker lane code-a (task 10475) so the #5410 design does not sit without a linked implementation path.

Acceptance criteria

The schema-driven filter surface renders filters generated from the schema for the programme's named collections.
Filter state round-trips through the URL/query contract used by the rest of atlas.
Tests cover at least one collection end-to-end: schema -> rendered filter -> filtered results.

CODE-1823

Intake review

Related PRs (number search, this run): none found by number search this run
Still live: verified open this run; no merged PR found that explicitly resolves this issue, so it stays open.
Labels: normalized this pass (priority/normal, effort/l, status/needs-triage; meta/enriched added).
Notes: priority/normal: a programme epic for atlas; slice it before implementation.
Risks: Risk: programme-sized scope in one issue - expect the triage to split it into per-collection slices.
Suggested approach: Approach: pick the first collection as the tracer, prove the schema->filter path, then replicate.

🤖 Agent note · filed

Agent: fleet monitor
Session / ID: repo-fleet-monitor run 2026-11-05T15:33:58Z
Found via: monitor reconciliation (Duty 2 intake enrichment)
Task: Intake pass per protocol §5: verified live, acceptance criteria appended, labels normalized, related PRs linked above.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-c
Session / ID: task 11037
Found via: queue claim
Task: handing off task 11037 for issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 to the opencode claimant — assigned_lane=opencode per fleet queue lane; this lane does not work it directly
Expectation: claimant launches the bound opencode session to work issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228; task parked 1200s for the claimant window, attempts 3/6
Links: issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228

🤖 Agent note · handed off

Agent: repo queue worker, lane code-r (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-r run 2026-11-06; task 11037
Found via: claimed task 11037 this shift; execution-lane assignment returned opencode
Task: task 11037 for issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 (triage). Fresh check: issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit), no open PR found. Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly. Attempts 3/6.
Expectation: claimant session drives task 11037 to a terminal state.
Links: task 11037 · issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228

🤖 Agent note · claimed

Agent: repo queue worker (repo-worker-code), lane 335a5d1f-bfc1-4831-99ea-850c8939a727 (OpenChamber scheduled lane)
Session / ID: task 11037
Found via: atomic queue claim; fresh GitHub and current-main verification
Task: Issue feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 is OPEN, has no hard-stop labels, and no PR references it. Current main is 9123103344b9e8e45c6d1beae1ed4ea4366d9998; design PR doc(atlas): design note — schema-driven filter surface from the classification manifest (#5410) #6223 is merged. Phase 1 prerequisite issue atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 remains OPEN. The issue already records its five phases, ordering, invariants and NO-GO trigger.
Expectation: record the current triage evidence and keep the scoped programme open; no implementation in this triage task.
Links: feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 · atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 · doc(atlas): design note — schema-driven filter surface from the classification manifest (#5410) #6223

Queue triage — 2026-11-06 (task 11037)

Revalidated against current main at 9123103344b9e8e45c6d1beae1ed4ea4366d9998: #6228 is still OPEN, has no hard-stop labels, and a fresh PR search for 6228 returned no PRs. The design source is already landed: PR #6223 merged at f86e532b77d9f4a6fb53c9d768cfbf93bf399c9e.

The programme is appropriately scoped in this issue already: five ordered phases, with Phase 1 blocked on #5375 (still OPEN); the remaining loader, generic-dimension, cache-key and manifest-writer phases follow it. The invariants and the same-transaction manifest-writer NO-GO trigger are recorded here, so no further split or implementation is needed to finish this triage.

Disposition: keep #6228 OPEN as the implementation programme. Continue only after Phase 1 #5375 lands; honor the recorded NO-GO trigger before loader work.

🤖 Agent note · triaged / done

Agent: repo queue worker (repo-worker-code), lane 335a5d1f-bfc1-4831-99ea-850c8939a727 (OpenChamber scheduled lane)
Session / ID: task 11037
Found via: claimed queue triage task; fresh GitHub verification
Task: Completed triage. feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 remains OPEN with no PR; design PR doc(atlas): design note — schema-driven filter surface from the classification manifest (#5410) #6223 is merged, and Phase 1 prerequisite atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 remains OPEN. The existing issue body already carries the ordered five-phase programme and its invariants/NO-GO trigger.
Expectation: continue the programme after atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 lands; keep feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 open.
Links: feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228 · atlas-core: topics/projects filters are unescaped SQL LIKE patterns — % and _ act as wildcards, a quote crosses JSON element boundaries #5375 · doc(atlas): design note — schema-driven filter surface from the classification manifest (#5410) #6223

Navigation Menu

Repository navigation

feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228

Phases (design note §8)

Invariants (note §6, non-negotiable)

NO-GO trigger (note §10)

Acceptance criteria

Intake review

21 remaining items

Queue triage — 2026-11-06 (task 11037)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

feat(atlas): schema-driven filter surface — implementation programme (from design #5410) #6228

Description

Phases (design note §8)

Invariants (note §6, non-negotiable)

NO-GO trigger (note §10)

Acceptance criteria

Activity

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Intake review

21 remaining items

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

Queue triage — 2026-11-06 (task 11037)

dezren39 commented on Nov 6, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions