feat(platform): persist metadata fabric bindings on canonical mainline - #92
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replacement for superseded PR #17, rebuilt from canonical main at 8bf0cd5.\n\nThis M3-3 slice adds a tenant-scoped append-only Metadata Fabric binding ledger, content-bound binding/provider evidence contracts, PlatformGateway commit/read with exact replay and separation-of-duties checks, migration 097, CI and staging-candidate inventory parity, ADR-049, roadmap/System-of-Record updates, and focused PostgreSQL rehearsal coverage.\n\nLocal verification: 636 required platform tests passed; binding contract suite passed; migration, platform, metadata-fabric, and DolphinScheduler validators passed; Ruff and compile checks passed; temporary PostgreSQL rehearsal verified created then no-op replay, cross-tenant isolation, FORCE RLS, and immutable UPDATE/DELETE rejection.\n\nClaim boundary: provider mutations are not executed by M3-3; provider minimum privilege, OIDC, durable catalog, live OpenLineage, production ingestion, and production_ready remain false. Do not run staging or production workflows from this PR.