Skip to content

docs: OSM as 6th domain instance + RDF-OWL §10 Phase 2a/2b shipped + 2c queued#41

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/domain-instances-geospatial-osm
Jun 5, 2026
Merged

docs: OSM as 6th domain instance + RDF-OWL §10 Phase 2a/2b shipped + 2c queued#41
AdaWorldAPI merged 1 commit into
mainfrom
claude/domain-instances-geospatial-osm

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Summary

Lands the OGAR-side docs PR queued for after lance-graph PR #473 (cesium-osm-substrate-v1.md) merged. Cites D-OSM-* IDs by number per the consumer-wires-through-producer convention agreed in 2026-06-05 cross-session coordination.

Two files touched:

  • docs/DOMAIN-INSTANCES.md — §1 table + new §2.6 + §3 matrix column
  • docs/RDF-OWL-ALIGNMENT.md — §10 sequencing table reflects reality

DOMAIN-INSTANCES.md — §2.6 (new) — Geospatial / OSM

Parallel-structured to §2.1-§2.5 per runtime-session's ask. Lead-in: "What OSM proves: geography doesn't break the IR."

Verbatim §6 callout preserved as the runtime session requested:

"The geographic litmus complements the anatomical one: the same compile-time HHTL primitive resolves Femur is_a LongBone AND Marienplatz is_in Munich in sub-microsecond."

That's the falsifiable property — measurable, not aspirational.

Exercises (cites by D-OSM-* ID):

Capability Source / coordination outcome
Spatial prefix-locality Cesium TMS quadkey as NiblePath prefix — Q2 outcome locked in lance-graph PR #473 §2
Tag-as-Class final / Arrow-list v1 fallback Q1 outcome: Tag as Class related via has_tag: HasMany<Tag> (SPO-natural); v1 ships Arrow List<Struct> shape in D-OSM-1/2 for cardinality control while Tag interning matures
Palette256 codec adoption Third domain for ADR-024 — OSM tag values cluster within a tile; ~5-10× compression on way attributes; D-OSM-2 reports ρ-vs-reference per the ADR-024 adoption checklist
OGAR-crossing deliverable D-OSM-3 SPO triple lift in lance-graph-ontology — producer-side contract ogar-from-osm-pbf consumes

§3 capability matrix — added OSM column + two new rows

New row Domain that hard-proves it
Spatial prefix routing (Cesium TMS quadkey via NiblePath) OSM
Palette256 codec adoption (ADR-024) OSM (tag values + tile-local coords) + HIPAA (security)

Coverage observation now reads "six together" — OSM is the only one that hard-proves spatial prefix routing AND drives the second production adoption of the palette256 codec.

RDF-OWL-ALIGNMENT.md §10 — sequencing table reflects reality

Phase Status
2aogar-adapter-ttl scaffold Shipped (PR #37)
2bogar-adapter-clickhouse-ddl scaffold Shipped (PR #38 + #40 dotted-name fix)
2c (NEW)ogar-from-osm-pbf scaffold Queued; consumes D-OSM-3 SPO contract; Q1 + Q2 outcomes pinned; ρ-vs-reference reporting wired

Phase 2c entry cites lance-graph PR #473's deliverable IDs (D-OSM-1/2/3) by number — no "TBD" placeholders.

Verification

  • cargo check --workspace --all-targets → clean (docs-only PR)
  • PII abort-guard (word-boundary): CLEAN on both files

Position in sequencing

Closes the OGAR-side queued action item from 2026-06-05 cross-session OSM/Cesium coordination. Next:

  • ADR-025 (Probe-free hot path) — still on offer; awaiting runtime-session green light + runtime-side §11 ADR-024 callback in lance-graph PR #473 (the runtime side committed to that follow-up after ADR-024 merged in PR docs(adr): add ADR-024 — Palette256 + HHTL codec as universal compression primitive #39)
  • Phase 3vart-backend on ogar-knowable-from (self-contained sprint; no cross-session coordination needed)
  • Phase 2c implementationogar-from-osm-pbf scaffold proper (after D-OSM-3 SPO surface is observable runtime-side per the D-OSM-2 → D-OSM-3 gating in cesium-osm-substrate-v1.md §4 phase sequencing)

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY

…2c queued

Lands the OGAR-side docs PR queued for after lance-graph PR #473
(`cesium-osm-substrate-v1.md`) merged. Cites `D-OSM-*` IDs by
number per the consumer-wires-through-producer convention agreed in
2026-06-05 cross-session coordination.

# DOMAIN-INSTANCES.md changes

## §1 — instances table

Added 6th row: Geospatial / OSM as calibration (geographic). Status
"spec'd; runtime addendum shipped; ogar-from-osm-pbf queued."

## §2.6 (new) — Geospatial / OSM — geographic calibration

Parallel-structured to §2.1-§2.5 per runtime-session's ask. Lead-in
"What OSM proves: geography doesn't break the IR." Per the strongest
single-sentence statement of the substrate-reuse claim that the
runtime session asked be preserved verbatim:

  > "The geographic litmus complements the anatomical one: the same
  >  compile-time HHTL primitive resolves `Femur is_a LongBone` AND
  >  `Marienplatz is_in Munich` in sub-microsecond."

Exercises (cites by D-OSM-* ID):

  - **Spatial prefix-locality** — Cesium TMS quadkey as NiblePath
    prefix (Q2 outcome locked in lance-graph PR #473 §2).
  - **Tag-as-Class final / Arrow-list v1 fallback** — Q1 outcome:
    Tag is a Class related via `has_tag: HasMany<Tag>` (SPO-natural
    emission); v1 implementation ships the Arrow `List<Struct>` shape
    in D-OSM-1/2 for cardinality control while Tag interning matures.
  - **Palette256 codec (ADR-024) adopts its third domain** — OSM
    tag values cluster within a tile; per-tile palette + const-table
    lookup ~5-10× compression on way attributes. D-OSM-2 ingest
    reports ρ-vs-reference per the ADR-024 adoption checklist.
  - **D-OSM-3 is the OGAR-crossing deliverable** — the SPO triple
    lift in lance-graph-ontology is the producer-side contract
    ogar-from-osm-pbf (Phase 2c) consumes.

## §3 — capability coverage matrix

Added OSM column. Added two new rows that explicitly name OSM as
the load-bearing proof:

  - **Spatial prefix routing** (Cesium TMS quadkey via NiblePath)
  - **Palette256 codec adoption** (ADR-024) — second production
    adoption alongside HIPAA security

Updated the coverage observation paragraph: "six together" (not
five), OSM hard-proves spatial prefix routing AND drives the second
production adoption of the palette256 codec.

# RDF-OWL-ALIGNMENT.md §10 changes

Updated the sequencing table to reflect reality:

  - Phase 2a = ogar-adapter-ttl — SHIPPED (PR #37)
  - Phase 2b = ogar-adapter-clickhouse-ddl — SHIPPED (PR #38 + #40
    dotted-name fix)
  - Phase 2c (NEW) = ogar-from-osm-pbf — Queued; consumes D-OSM-3's
    SPO contract; Q1 (Tag-as-Class + Arrow-list fallback) and Q2
    (Cesium TMS quadkey NiblePath) coordination outcomes pinned;
    reports ρ-vs-reference per ADR-024 adoption checklist on first
    per-country PBF run

# Verification

  - cargo check --workspace --all-targets         -> clean (docs-only)
  - PII abort-guard (word-boundary)               -> CLEAN both files

# Position in sequencing

Closes the OGAR-side queued action item from the 2026-06-05
cross-session OSM/Cesium coordination. Next:

  - ADR-025 (Probe-free hot path) — still on offer; awaiting
    runtime-session green light + runtime-side §11 ADR-024 callback
    in lance-graph PR #473 (committed by runtime side after ADR-024
    merged).
  - Phase 3 — vart-backend on ogar-knowable-from (self-contained
    sprint; no cross-session coordination needed).
  - Phase 2c implementation — ogar-from-osm-pbf scaffold proper
    (after D-OSM-3 SPO surface is observable runtime-side).

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1bb5497292

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/DOMAIN-INSTANCES.md
Comment on lines +128 to +130
**What OSM proves: geography doesn't break the IR.** OSM IDs are
*already* prefix-structured (`country/region/city/street/house`), so
the adapter is doing identity-*extraction*, not identity-construction

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the OSM ID hierarchy assumption

This treats OSM element IDs as geographic prefixes, but OSM nodes/ways/relations use numeric IDs in per-element-type ID spaces, not country/region/city/street/house paths (the OSM data model notes that different element types can share the same ID and be unrelated/geographically distant: https://wiki.openstreetmap.org/wiki/Data_model). In the ogar-from-osm-pbf plan, relying on identity-extraction from IDs would produce non-local or colliding NiblePath keys; the geographic prefix needs to be derived separately from coordinates/tiles or relations instead of the raw OSM ID.

Useful? React with 👍 / 👎.

@AdaWorldAPI AdaWorldAPI merged commit 03b2f87 into main Jun 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants