Reference architectures

A reference architecture describes a best-practice setup for one supporting system, for example browser testing or a CI/CD pipeline. Many projects benefit from the same patterns, but each project usually needs them tuned to its own context. A reference architecture is a planning tool, not a template or a strict prescription. It gives the team a goal to plan and the background context to plan it well.

Supporting systems do not change what a user sees, but they let the team deliver the work that does. For that reason, Roko Platform plans every reference architecture as an Enabling delivery goal.

Use one

1. Open the list

   Select Playbooks in the sidebar, then the Reference Architectures card. The list shows each architecture's state for this project.

2. Add it to the Roadmap

   Open an architecture, select Add to Roadmap, pick a Horizon and select Create goal. The platform creates an Enabling delivery goal with the architecture's title and summary. The goal's Planned from property links back to the architecture.

3. Start working

   Plan and build the goal as usual. An agent connected to the platform over MCP pulls the architecture into its context, compares it with the project's code and working model, and helps you decide which parts fit this project.

When the project already has the system, select Already done. When the project does not need it, select Not relevant. Remove from the Roadmap and Undo reverse either choice.

Per-project state

The architecture is shared across projects, and each project records its own state against it.

A project can plan each reference architecture at most once. Only Add to Roadmap creates the linked goal. An agent can read an architecture over MCP, but it cannot plan one or set one aside.