Repository Direction

Roadmap

What Plumego is hardening now, what comes next, and what stays out of scope.

Current baseline

stable roots with explicit boundaries: `core`, `router`, `contract`, `middleware`, `security`, `store`, `health`, `log`, `metrics`
extension discovery and task-routing metadata under `specs/*`
a single canonical application layout in `reference/standard-service`
milestone, plan, card, and verify workflow assets under `tasks/*`
repo-wide quality gates in `Makefile` and `.github/workflows/quality-gates.yml`
stable-root compatibility policy in `docs/DEPRECATION.md`

In progress

Phase 8: `x/ai` Stabilisation Path
Phase 9: `x/tenant` Production Readiness
Phase 13: Docs and Onboarding Sync

Planned

Phase 10: `x/discovery` Backend Expansion
Phase 11: `x/data` and `x/fileapi` Hardening
Phase 12: `x/observability` and `x/gateway` Test Depth
Phase 14: Extension Stability Evaluation

Suggested execution order

Keep Phase 13 docs and onboarding sync continuous.
Harden `x/ai` docs, examples, and stable-tier tests.
Advance `x/tenant` production readiness.
Clarify `x/data` and `x/fileapi` operational guidance.
Expand `x/discovery` backends only when explicit adapters are ready.
Raise `x/observability` and `x/gateway` test depth.
Define extension stability criteria before any promotion discussion.