Skip to content
Plumego

Modules Overview

Modules Overview

Section titled “Modules Overview”

Plumego keeps long-lived public packages at the repository root and places optional or fast-moving capabilities under x/*. This split is intentional: it keeps the stable surface small and makes ownership easier to classify.

Synced module inventory

Section titled “Synced module inventory”

Synced from `specs/repo.yaml`

Stable roots

9

  • contract
  • core
  • router
  • middleware
  • security
  • store
  • health
  • log
  • metrics

Synced from `specs/task-routing.yaml`

Primary extension families

11

  • x/tenant
  • x/fileapi
  • x/messaging
  • x/gateway
  • x/rest
  • x/websocket
  • x/frontend
  • x/observability
  • x/resilience
  • x/data
  • x/ai

These lists are generated by the prebuild sync scripts instead of being hand-maintained twice.

Default classification rule

Section titled “Default classification rule”
  • kernel, lifecycle, transport contracts, or stable middleware changes belong in stable roots
  • capability or protocol work belongs in the owning x/* family
  • application wiring belongs in reference/standard-service

Why this matters

Section titled “Why this matters”
  • stable roots remain easier to learn, review, and preserve
  • extension work can evolve faster without redefining the default learning path
  • repository tooling can classify changes with a smaller search radius
Section titled “Read next”