x/* Family

x/* Family

The x/* layer exists so optional or faster-moving capabilities can evolve without redefining the stable-root learning path.

Synced extension facts

Synced from `specs/task-routing.yaml`

Primary entry families

11

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

Synced from `specs/repo.yaml`

All extension paths

Default routing intent: Change product capability, business feature, protocol adaptation, or extension behavior.

• x/tenant
• x/ai
• x/cache
• x/data
• x/devtools
• x/discovery
• x/fileapi
• x/frontend
• x/gateway
• x/ipc
• x/messaging
• x/mq
• x/observability
• x/ops
• x/pubsub
• x/resilience
• x/rest
• x/scheduler
• x/webhook
• x/websocket

Primary entry families and all extension paths are shown separately so subordinate paths do not get mistaken for default entrypoints.

When to start here

Start with an x/* family when the work is primarily about:

• capability-specific behavior
• protocol adaptation
• tenant, gateway, or observability policy
• optional app-facing functionality that should not expand stable roots

What not to do

• do not make stable roots depend on x/*
• do not use x/* as a pretext to redefine the canonical reference path
• do not start in a subordinate package when a primary family already exists