Skip to content

Add the integration train: Waves 0–5 dependency-ordered manifest + verifier [supersedes #11]#14

Open
estebanzimanyi wants to merge 1 commit into
MobilityDB:feat/object-modelfrom
estebanzimanyi:feat/integration-train
Open

Add the integration train: Waves 0–5 dependency-ordered manifest + verifier [supersedes #11]#14
estebanzimanyi wants to merge 1 commit into
MobilityDB:feat/object-modelfrom
estebanzimanyi:feat/integration-train

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

Summary

Supersedes #11. The original PR's branch lives on MobilityDB/MEOS-API:feat/integration-train (predates the fork-branch-only policy). This PR rebuilds it from the fork with the additive Wave 4 + Wave 5 manifest entries:

Update Where
Wave 4 — Downstream bindings (MobilityDuck / MobilitySpark / MobilityAPI / JMEOS / GoMEOS / MEOS.NET) meta/integration-train.json#/waves[4]
Wave 5 — Service-agent + data-lake + stream layers (anchor-defined) meta/integration-train.json#/waves[5]
Ecosystem repo enumeration broadened in doc preamble docs/integration-train.md
Stripped "owner: live X session" framing per the standing-down memory meta/integration-train.json
Current-status line updated for 2026-05-21 both files

Wave 4 — what's in it

Each binding regenerates against the Wave-0 MEOS-1.4 C surface via the meos-idl.json catalog. Each is bump-independent within its repo; the cross-binding gate is byte-identical regeneration (proves single SoT).

Wave 5 — what's in it

Three sub-layers, all anchor-defined and downstream of Wave 4:

Branch base

This PR is on feat/integration-train (fork) and uses the same base as #11: feat/object-model (MEOS-API PR #10). Stack relationship unchanged.

Action requested

Makes ecosystem-wide 100% parity provable at one point instead of
asserted from per-PR isolation-green. meta/integration-train.json is the
PR dependency DAG + per-wave gates + merge order; verify-train.sh
composes the train and runs each wave's gate (PASS only when just-run
green here, else BLOCKED with the exact gate it needs). Operationalizes
MobilityDB discussion #895 (wave-based merge plan). Stacked on
feat/object-model (the catalog anchor): Wave 0 verifies here (2699 fns,
PR MobilityDB#10 21/21, from_mfjson + constructors uniform); Waves 1-3 are
honestly gated on the MEOS-1.4 bump (the single universal unblock).
@estebanzimanyi estebanzimanyi force-pushed the feat/integration-train branch from b25000c to 06f058a Compare May 21, 2026 07:27
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.

1 participant