Roadmap

The bulk of this has landed: install.sh with prerequisite detection, a wagoe new scaffold that produces a project which boots, a setup wizard needing no external services, automatic migrations, seed data, a production build path, and a CI smoke test that walks install → new project → serving app inside a bare container and asserts on HTTP rather than exit codes.

What remains is deliberate QA: the same path exercised across an environment matrix and by people who did not write it. A framework gets one first impression.

The stability policy now defines what is public, what is internal, and how deprecations work. Bringing the existing surface up to that standard is the work — auditing protocols for changes we would not want to make after 1.0.0, and adding the ^:deprecated metadata and changelog headings the policy requires.

A small number of module dependency cycles are still tolerated by an allowlist rather than resolved. Module wiring and platform system wiring are more coupled than they should be — several optional libraries are effectively mandatory dependencies of the platform. Both are the kind of thing that is cheap to fix before a stability promise and expensive after.

Wagoe has strong conventions, which makes it well suited to coding assistants that know them. Planned: guided skills for project setup, scaffolding, migrations, configuration preflight and debugging, so an assistant follows the framework’s own workflow instead of guessing at it.

A showcase application built on the framework, and a migration guide for people arriving from Kit or Luminus. Then the community launch — announcements, a chat channel, and a demo.

Wagoe already scales vertically through configuration, and the ports.clj seam is what makes scaling out tractable: swap an in-process adapter for a distributed one without touching business logic. Cache, jobs, auth and tenancy are already replica-safe. The remaining pieces:

See Sizing & Scaling for the current readiness matrix.