Workbench

Project registry for the next FluentReact operating layer.

Outer workspace shell for project registry, rollout posture, and the first refine-style resource lanes.

Open default projectPublic site
1 active project12 resource lanes liveRead-only preview

Workspace posture

Public product, member desk, project workbench, and ops now read as one system.

This registry is the outer shell. Each project gets its own resource-first cockpit underneath, while protected actions stay in ops and public acquisition keeps a product voice instead of drifting into admin chrome.

Projects1

Seeded project registry ready for project-scoped routes instead of page-by-page sprawl.

Shell layers4

Marketing, member desk, project workbench, and protected ops now have clearer boundaries.

Kernel modeResource-first

Provider and access-control abstractions are in place before full refine package adoption.

Project modules12

The first project now spans publishing, demand, billing, telemetry, and contract lanes.

Preview modeRead-only preview

Can inspect project resources without exposing operator-only actions.

Projects

Start from the project that already owns the live monthly publishing loop.

Live publishing

Core Publication

This is the first refine-style project in FluentReact: a builder-grade workbench around monthly React publishing, paid archive access, and delivery readiness.

/app/project/core-publication/overview

dispatch-2026-03 | openai review gate | log delivery

Surface boundaries

Each surface has a tighter job now.

Public

Marketing surface

Acquisition, pricing, proof, and trust routes stay product-shaped rather than dashboard-shaped.

/

Session-linked

Member desk

Receipts, archive unlock, and recovery stay calm and low-friction while auth remains intentionally light.

/members

Refine-style

Project workbench

Resource-first project cockpit for issues, review state, and delivery posture.

/app/project/core-publication/overview

Protected

Ops console

Protected billing, quality, and delivery actions remain in the operator lane instead of leaking into public routes.

/ops

Kernel rules

The next rollout slice is already constrained in the right places.

  • dataProvider stays above services: project resources now expose refine-friendly list and detail shapes without binding the UI straight to D1.
  • accessControl stays presentational: preview pages stay read-only while run actions remain routed through protected ops.
  • project scope is explicit in the URL: the new workbench uses project-owned routes instead of hiding state in one giant console page.