The release proof starts from the same live health route used for deployment checks.
Project guide
Runbooks, release proof, and durable operator memory.
Runbooks, route maps, release references, and current production-readiness truth for the live project.
Live publishingRefine migration activeCadence: Monthly issue cycleRead-only previewUpdated Apr 5, 2026, 2:16 PM UTCD1 live10 live routes
Operator memory
The workbench now keeps release truth, recovery routes, and support tasks in one calmer lane.
This guide is the project-side operating handoff. It keeps the live route family, current billing posture, production health snapshot, and repo-side evidence references visible without forcing the team to reconstruct context from chats and scattered docs.
WatchGuideLive payment proof12 read contracts9 guarded writes
Commercial demand proof stays visible alongside publishing and delivery posture.
Telemetry volume is part of the same operator story instead of a separate analytics silo.
Billing blockers remain the fastest read on whether wider promotion is commercially safe.
Buyer, operator, and API surfaces are now mapped in one route family instead of spread across memory.
Support and release checks now have named starting points inside the workbench.
Durable technical memory still lives in versioned docs, but this page now points to it explicitly.
Commercial caution stays visible even when hard blockers have already been cleared.
Recent operator writes and guarded runs now stay visible from the guide lane.
Live route map
The operator handoff only works when the active route family is visible.
Guide
Product docs
Public handoff surface for billing proof, member recovery, and route-boundary truth.
public: /docsBuyerDelivery guide
First-month scope, support posture, and the current paid promise for buyers.
public: /deliveryProofCheckout status
Commerce proof route for checkout, webhooks, and activation state.
public: /paddle-checkoutRecoveryMember desk
Session-linked receipt, access recovery, and archive handoff for buyers.
member: /membersContractsProject API lane
Live map of read contracts, guarded writes, response shapes, and platform edges.
project: /app/project/core-publication/apiReadinessProject billing lane
Commercial readiness, current blockers, and webhook-backed billing posture inside the workbench.
project: /app/project/core-publication/billingRunbookProject guide lane
Durable operator memory for live routes, release references, and recovery-first operating tasks.
project: /app/project/core-publication/guideProtectedOps overview
Protected operator board for revenue queue, alerts, and broader funnel health.
ops: /opsMerchantOps billing
Deeper session, webhook, and cutover evidence beyond the project-level summary.
ops: /ops/billingD1 liveHealth check
The canonical live worker-health contract for checking the deployed runtime quickly.
api: /api/healthRelease pulse
The guide should reflect current production truth instead of a frozen operations memo.
- Health route on D1: /api/health currently reports 6 leads and 319 tracked events.
- Live payment proof via Founding offer: No current billing blockers. 0 active subscriptions and 6 processed webhooks are already visible.
- Watch rollout on Guide: Keep runbooks, release evidence, and route ownership visible in the guide lane while the wider handoff milestone stays in motion.
- 12 read contracts and 9 guarded writes: The guide mirrors the same route boundary truth the runtime workbench already uses after hydration.
- Operator audit trail ready: Guarded workbench actions now emit project-scoped audit events so recent governance changes are not trapped in memory.
Current milestone
Docs and integration handoff
Package the project API, usage intervention model, and release proof into clearer docs and reusable integration guidance for the next product layer.
In progressWatch
Runbook
Each common support or release task now has a first route.
Verify the purchase path
Start from the project billing lane, then confirm checkout status and webhook proof still agree before wider promotion.
Open billing laneRecover member access
Use the member desk when the buyer needs receipt continuity, activation proof, or the quickest archive handoff.
Open member deskInspect the API posture
Review the project API lane before treating any current route as a public self-serve integration surface.
Open API laneEscalate into protected ops
Use the ops console when buyer-facing or project-level summaries suggest the issue is now execution-heavy.
Open ops consoleKeep the public handoff honest
Review the public docs surface so buyer-facing guidance and operator-facing truth do not drift apart.
Open public docsCurrent posture
The guide stays most useful when governance and commerce read as one story.
- Governance focus: Guide in watch mode.
- Operator note: Keep runbooks, release evidence, and route ownership visible in the guide lane while the wider handoff milestone stays in motion.
- Commercial focus: Live payment proof through Founding offer.
- Billing note: Keep the founding offer as the canonical billing surface while the live checkout trail keeps accumulating proof.
- Latest governance sync: Apr 5, 2026, 2:16 PM UTC by system-default.
- Recent operator ledger: Waiting for the next guarded workbench action.
Recent operator ledger
Guarded writes and pipeline runs now leave a project-scoped audit trail.
The next governed settings save or guarded pipeline run will appear here automatically.
Repo references
The live workbench now points back to the durable versioned record.
| Reference | Path | Detail |
|---|---|---|
| Release evidence | docs/release/release-evidence.md | Deployment path, version ids, production proof, and release decisions for live slices. |
| Modernization roadmap | docs/product/fluentreact-refine-modernization-roadmap-2026-03-23.md | The refine-style module map, rollout phases, and remaining project-wide modernization plan. |
| API and member handoff | docs/architecture/fluentreact-project-api-and-member-handoff-2026-03-25.md | Architecture note for public docs, project API boundaries, and member recovery posture. |
| Delivery architecture | docs/architecture/automated-monthly-delivery-architecture-2026-03-19.md | Longer-form architectural context for monthly delivery, issue publication, and downstream routes. |
Next trigger
This guide should only widen when runtime truth or release responsibility widens.
- A second project needs its own guide lane, route map, and release-evidence thread.
- Member recovery stops being session-linked and grows into a fuller authenticated account surface.
- An external integration needs signed project-to-project contracts instead of internal route references.