Taking R U OK? Day through a production vertical sliceR U OK? Day production qualification map

Wellbeing Studio Production Pilot 01 · August 2026

R U OK? Day production qualification map

A production-history map showing how a bounded campaign definition became a technical vertical slice, participant-access proof, staging and runtime hardening, parallel launch-candidate content integration, and finally a product correction that kept proven infrastructure while removing mandatory authentication from the core RUOK journey.

Read the analysis

Production rule

Prove infrastructure. Qualify runtime. Let product requirements remain reversible.

  1. 01

    Defined

    Product boundary

    R U OK? Day is deliberately bounded. It must prove a focused architecture slice rather than become the whole future Studio.

    • Production Pilot 01 v1.1
    • RUOK Product Specification v1
  2. 02

    Implemented

    Technical vertical slice

    The real Wellbeing Studio application can represent and serve the campaign experience. No parallel microsite architecture is introduced to hit the date.

    • 2c56d6b
  3. 03

    Implemented / remediated

    Participant access proof

    Neon Auth and Magic Link access are implemented, staging readiness is established, and a defect that could strand an authenticated participant on sign-in is corrected.

    • f18b5f8
    • 043f4fe
    • 0efb911
  4. 04

    Hardened

    Runtime reliability

    The staging Postgres path is hardened for transient-read behaviour and regional execution rather than treating local success as sufficient.

    • c6a23a8
  5. 05

    Parallel integration

    Launch Candidate content

    Content Master v0.2 progresses through LC1, including media-integrity remediation. At this evidence point the production and LC1 branches are parallel, so the history is shown as parallel rather than rewritten as a single linear release.

    • 1892158
    • d57e18b
    • 72966d4
  6. 06

    Canonical re-specification

    Product correction

    Mandatory authentication is removed from the core campaign journey. Neon Auth remains proven infrastructure, but capability no longer creates participant requirement.

    • RUOK Product Specification v1

What this shows

The production history is not represented as a heroic straight line. It includes parallel branches, remediation and a deliberate product reversal — because those are part of the evidence of how the work was governed.

Evidence treatment

The production history is represented as semantic staged evidence with explicit commit identifiers, branch relationships and product corrections rather than as a flattened Git graph screenshot.

Commit identifiers are included as provenance markers, not as a claim that every branch or launch gate shown here is already merged, promoted or complete.