Release Posture

Release Posture

Plumego v1 covers the checked-in repository, but not every area carries the same compatibility promise.

Synced support matrix

Synced from the v1 support matrix in `README.md`

5 Synced entries

GA

Stable library roots

Public package surface is the long-term stable API for v1 users.

Modules: core, router, contract, middleware, security, store, health, log, metrics

Supported reference

Canonical reference app

Kept aligned with the canonical bootstrap and stable-root usage, but not treated as a reusable extension catalog.

Modules: reference/standard-service

Included in v1 release scope

CLI

Supported as a command-line tool, not as a Go import surface; command behavior and generated output must stay aligned with canonical docs.

Modules: cmd/plumego

Experimental

App-facing extension families

Included in repo quality gates and release scope, but API/config compatibility is not frozen.

Modules: x/ai, x/data, x/devtools, x/discovery, x/frontend, x/gateway, x/messaging, x/observability, x/ops, x/rest, x/tenant, x/websocket

Experimental

Subordinate extension primitives

Maintained and tested, but discovery should start from the owning family entrypoint and compatibility is not frozen.

Modules: x/ipc, x/mq, x/pubsub, x/scheduler, x/webhook

Practical reading rule

Before treating a package as durable, check whether it belongs to a stable root or to an experimental extension family.

Why this page exists

Plumego keeps release posture explicit so documentation, scaffolds, and extension work do not accidentally overstate compatibility.