Pace Commons — Running Membership UX & Access Policy

Pace Commons — Running Membership UX & Access Policy

A running member should know three things: what is available, why access is waiting, and how to get moving again when billing needs attention.

Pace Commons is an original fictional study pairing a responsive member workspace with a separate, tested Node.js access policy. It is independent work, not a client commission or a live subscription service.

Three moments, one clear next step

Active membership: the next session and current access period are visible together. Returned from checkout: the interface waits for confirmation rather than treating a browser redirect as proof of payment. Payment needs attention: the preview remains understandable while full access is paused. On phones, the membership recovery action moves ahead of the plan.

What works in the local study

The scenario selector changes all three views. Plan and billing actions open honest contextual previews. Desktop and 390-pixel phone layouts were inspected, including the waiting and recovery flows.

A separate pure Node.js policy passed 21 local tests covering member ownership, signed-out access, checkout flags, exact paid/grace cutoffs, canceled or expired access, malformed inputs and unchanged source data. Its identity and subscription inputs are synthetic and already trusted; this is not an authentication or provider-integration test.

What production would add

Verified server identity, persistent member/customer mapping, database authorization, authenticated billing sessions, verified payment events with replay/retry handling, and provider sandbox acceptance tests. Clerk, Supabase, Stripe, email and analytics are not connected in this sample. The paid/grace access policy would be agreed with the product owner.

Original interface, typography, track illustration, responsive behavior and policy implementation by Launch in Seven, with AI assistance. Fictional brand, member, pricing and session titles. Public screenshots show the proof; reusable source remains private.