Add meridian-control: node control-plane service - #35
Merged
Conversation
Implements the central control plane for meridian-node GPU agents, as a separate service in this repo (DESIGN decision 13 in the meridian-node repo). It does not import or modify the gateway; the gateway consumes its serving projection read-only. - Node control protocol (contracts/v1): approval-gated enrollment with a built-in Ed25519 CA (real X.509 node certs), epoch-fenced sessions, leases, desired-state generations, and observations. - Durable via SQLAlchemy: SQLite by default, Postgres via a connection URL; control replicas are stateless. - Restore-safe fencing (DESIGN 17.5): a control-plane incarnation + epoch floor so a restore-from-backup cannot re-admit a previously fenced agent. - FastAPI app + operator admin endpoints; meridian-control CLI (run, mint-token); serving projection for the gateway. - Isolated [control] extra so the gateway install is unchanged. Tests (19): durable service logic (enrollment, fencing, sequence, restore, revocation, projection), HTTP surface, CA cert issuance, and a cross-repo test driving the real meridian-node agent against this service over a real socket. ruff and mypy clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
What
Adds
meridian-control, the central control plane formeridian-nodeGPU agents, as a new isolated service in this repo (per decision 13 in the meridian-nodeDESIGN.md). It is additive and does not import or modify the gateway — the gateway will consume its serving projection read-only in a later, separately-reviewed change.Why
meridian-node(the host-local GPU agent) is built and tested against a fake/reference control plane, but had no real server to talk to. This is that server: the durable, cert-issuing counterpart that closes the loop.What's included
contracts/v1): approval-gated enrollment with a built-in Ed25519 CA issuing real X.509 node certs, epoch-fenced sessions, leases, desired-state generations, and observations.MERIDIAN_CONTROL_DB_URL; control replicas are stateless.meridian-controlCLI (run,mint-token); a serving projection endpoint for the gateway.[control]extra so the gateway install is unchanged.Tests (19, ruff + mypy clean)
TestClient; CA certificate issuance and chain-of-trust.tests/control/test_cross_repo.pyruns the real meridian-node agent against this service over a real HTTP socket (the compatibility target from the node's DESIGN §20/§24). Skipped unlessmeridian-nodeis installed.Not included (follow-ups)
create_allfor now).🤖 Generated with Claude Code