editions

Operations of the Distribution API. Paths are relative to your deployment's API host.

POST /api/distribution-api/editions/plan

What a proposed edition would resolve to

Validates a proposal and returns the manifest an operator commits, plus the biome set it resolves to. It WRITES NOTHING. An edition’s authority is the git artifact the distribution plane resolves — a lock that cannot be traced to a commit is not a lock, so authoring stays build-time and this surface plans.

Authentication: none

Request body: application/json EditionProposalDto

GET /api/distribution-api/editions/plan-baseline

The baseline edition the vendor composes a proposal against

Operator plane. The edition composition POST editions/plan diffs a proposal against, read from the same sealed lock the plan reads. It is the starting point of an edition proposal, not an installation's read of its own edition: no installation role is admitted, and on a deployment where nobody holds platform_operator of the configured operator realm nobody is admitted.

Authentication: none

GET /api/distribution-api/editions/running

The distribution edition this deployment runs

Read from the resolved lock the deployment already vendors — the same artifact biome-host-api reads. This is a second READER of one artifact, never a second owner.

Authentication: none