Skip to main content

Future State

Status: target, not shipped

These pages describe where Wrkbelt's architecture is going — not where it is. Each page below names its tracking ticket and OpenSpec proposal so you can check the current implementation status.

What lives here​

A page is in future-state/ if it describes work that has been designed but not shipped. The shape of the design is settled enough to write about; the code is not in main yet.

What does NOT live here​

  • Shipped architecture — lives in ../current-state/, verified against the code on main.
  • Speculative ideas — early thinking that hasn't reached a designed-but-not-shipped state lives in OpenSpec change proposals at openspec/changes/, not here.
  • Backlog items — work tracked only in Jira, not in OpenSpec. If it's worth describing architecturally, it earns a future-state page; otherwise the Jira ticket is enough.

Current future-state pages​

  • Multi-instance runtime — production hardening on top of the live autoscaled cluster: consolidated dashboards and threshold validation against production traffic. Tracking: WEN-987 (v0.7.0 epic).
  • Audit archival — Atlas Online Archive replacing the 24-hour TTL. Tracking: WEN-992. OpenSpec: openspec/changes/add-audit-archival/.
  • Authorization and RBAC — cross-hierarchy permission cascade, OAuth2 connect flow.
  • Catalog and enablement — CatalogAdmin CRUD, integration availability, orphan cleanup, catalog cache invalidation.

Why this section exists​

The architecture section is the new-engineer entry point. Without an explicit future-state section, the only way to know "where is this going?" is to read OpenSpec change proposals, scan Jira, and triangulate. That's a high tax for a routine question.

Future-state pages collapse that — for each major subsystem, here is the next step.