Skip to content

Add the integration train: provable ecosystem-wide 100% parity#11

Closed
estebanzimanyi wants to merge 1 commit into
feat/object-modelfrom
feat/integration-train
Closed

Add the integration train: provable ecosystem-wide 100% parity#11
estebanzimanyi wants to merge 1 commit into
feat/object-modelfrom
feat/integration-train

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

Operationalizes MobilityDB discussion #895 (wave-based merge plan). meta/integration-train.json = 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). Stacked on #10 (catalog anchor). Wave 0 PROVEN here (2699 fns, PR #10 21/21, from_mfjson + constructors uniform); Waves 1-3 honestly gated on the MEOS-1.4 bump.

@estebanzimanyi estebanzimanyi force-pushed the feat/object-model branch 2 times, most recently from 4ec925f to 6cd5d5b Compare May 19, 2026 13:22
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 #10 21/21, from_mfjson + constructors uniform); Waves 1-3 are
honestly gated on the MEOS-1.4 bump (the single universal unblock).
@estebanzimanyi
Copy link
Copy Markdown
Member Author

Superseded by #14 (fork-branch PR carrying the same Waves 0–3 content plus the additive Wave 4 + Wave 5 entries reflecting current ecosystem state). This PR's branch lives on the org repo (predates the fork-branch-only policy).

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