Your account
HOL-D007Story implementation: In progress

Read a full Backcountry story in the app

editorial · Proposed launch phase 1

Start from Home

Review as Paid member

User story

As a paid member, I want to read a native long-form story so I can read and explore without leaving Backcountry.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Load published story/archive metadata and the permitted story body from the backend using stable canonical work IDs. Store public and paid bodies separately; paid text must not ship in the public payload or connected client bundle.
  • Keep the full accessible story inside Backcountry with readable type and inline media.
  • Show credited contributors, series context and related work.
  • Provide the story’s save and conversation actions in the appropriate account context.
  • Public articles are readable while signed out; member articles show public metadata and a membership gate until simulated active access. No trial; benefits/plans stay public.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on the paid Member Home. Use the Paid member demo role or Casey Bennett in Try a demo account, then select Member in the account/workspace menu if necessary. This creates a genuine local session with a seeded no-charge test membership; it does not upgrade a different account.

Navigation from sign-in

  1. 01Open the fictional Paid member account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Select Read the story in the Home hero to open The Long Way In.

Feature checks start here

The Long Way In

Public-content reads are available for dev review; full story acceptance and stakeholder approval remain separate. Ready for frontend review in dev only; original fictional content, local discussion and genuine local account access. Content/discussion are local previews; historical catalog migration is not included.

  1. 03Read the complete The Long Way In with the actual paid local account. Inspect By Liam McGee, Field perspective · Jordan Lee and the series context.
  2. 04Open the contributor profile, View photo gallery and the next installment The Turnaround Call, then return to the original story.
  3. 05Use Save and the conversation controls. Submitted comments remain pending for their author; the discussion service is still local sample state.
  4. 06Review the same paid work using a separate free or Visitor session; confirm the membership gate. Selecting another demo identity signs in to that identity; it does not upgrade the original free account.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Load published story/archive metadata and the permitted story body from the backend using stable canonical work IDs. Store public and paid bodies separately; paid text must not ship in the public payload or connected client bundle.

How to verify in dev

  1. Verify published-only anonymous projection, no private/protected payload, stable IDs and links, missing/unpublished records, empty/loading/error UI, and no silent static fallback. Idempotent seed rerun preserves edited records; authenticated/dummy Home entry remains unchanged.
  2. Read the public work signed out, then open a paid work and see only its public description and membership prompt; qualified paid reading remains separate.

Before this can work

  • Begin on the paid Member Home. Use the Paid member demo role or Casey Bennett in Try a demo account, then select Member in the account/workspace menu if necessary. This creates a genuine local session with a seeded no-charge test membership; it does not upgrade a different account.
  • A seeded story, associated media and contributor information.
  • A defined public/premium boundary before validating the Visitor version.

No prerequisite story has been confirmed. The setup above describes the content or decisions needed.

Connected stories