design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects

Parent: #6022 (where agent notes live — zettel vs repo vs ID graph). Research source: prior-art doc ~/workspace/scratch/atlas-ingestion-brief-2026-11-04/prior-art-research.md (2026-11-04). Follow-up 45 (cross-cutting). Relation methods consumed, not reinvented: writer-set #5545, the #5686 family, worlds program #5955.

Scope

#6022 decides which note/object classes publish directly into the ID graph; this follow-up designs the format for Atlas-side publication:

Atlas objects (files, versions, chunks/spans, ingest runs) as ID-graph objects: identity, writer-set, and which provenance fields ride along.
Provenance/lineage relations mapped from the PROV-lite record (sibling comment on atlas: provenance registry (chunk occurrences), content-addressed extracts, multi-DB vector resolution #3125: wasRevisionOf for version↔version, specializationOf for version↔logical file, wasDerivedFrom, wasGeneratedBy, wasAttributedTo) into the ID graph's relation vocabulary — one mapping, so the graph shows the same lineage the corpus stores.
Display: reuse the common relation-display methods already ticketed in the design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686 family; this design names the Atlas-side projection, not a new viewer.

Done looks like

A publication-format design: object mapping, relation mapping, and the projection contract (canonical in Atlas tables; ID graph as projection — or the reverse, decided explicitly).

CODE-1727

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
Task / ID: triage queue task 10427
Found via: queue claim
Task: triage the Atlas-to-ID publication-format design in design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062.
Verified fresh: design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062 is OPEN, has no hard-stop labels, and has no related PR. Parent design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 is OPEN; its triage confirms design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062 covers format while design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 selects which classes publish. atlas: provenance registry (chunk occurrences), content-addressed extracts, multi-DB vector resolution #3125 contains the PROV-lite field vocabulary; relation/view work is already tracked under id: implement Writer-set view projection - view projection and discovery query (design doc) #5545/design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686.
Expectation: route only the publication-format design; do not take over design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 or redesign shared relation semantics.

Triage result — #6062

Scope: a standalone format/projection design for publishing Atlas files, versions, chunks/spans, and ingest runs into the ID graph. design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 chooses which classes publish; this issue must not expand or re-decide that class set. No runtime reproduction or code change is applicable.
Current state: design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062 is OPEN, has no related PR, and no Atlas-to-ID publication-format design doc exists on current main. Parent design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 is OPEN and its triage is complete; the format question remains distinct and live.
Inputs to consume: atlas: provenance registry (chunk occurrences), content-addressed extracts, multi-DB vector resolution #3125 supplies the PROV-lite lineage/provenance field vocabulary; map that vocabulary once into the existing ID relation model. Reuse writer-set authority from id: implement Writer-set view projection - view projection and discovery query (design doc) #5545 and relation/display methods in design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686/id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955; do not create a parallel viewer or relation vocabulary.
Ordering: the format design can proceed in parallel with design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022’s class-selection work, but its projection boundary should be checked against the selected classes before finalizing. id: implement Writer-set view projection - view projection and discovery query (design doc) #5545 is OPEN/parked and design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686 is OPEN/queued, so treat their contracts as design inputs, not implementation blockers; record any unsettled mapping explicitly rather than silently redefining shared semantics.
Done condition: choose canonical authority (Atlas tables vs ID graph) and document object identity, writer-set/provenance fields, relation mappings, and projection contract. No separate queue item is needed; design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062 is already the design handoff.

🤖 Agent note · done

Agent: repo-worker-code, OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
Task: queue task 10427 — triage design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062
Outcome: triaged as a distinct format/projection design. Scope, dependencies, ordering, and done condition are recorded in the preceding comment; the issue remains open.
Links: design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062 · parent design(id/atlas): where agent notes live — zettel vs repo vs publishing directly into the ID graph #6022 · provenance registry atlas: provenance registry (chunk occurrences), content-addressed extracts, multi-DB vector resolution #3125

Navigation Menu

Repository navigation

design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062

Scope

Done looks like

Triage result — #6062

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

design(id/atlas): ID-graph publication format — Atlas objects + provenance/lineage relations as ID-graph objects #6062

Description

Scope

Done looks like

Activity

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Triage result — #6062

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions