Your account
All stories
HOL-D057Story implementation: In progress

Set up an HOL-owned database for the demo

Demo improvement · Across launch phases · Completed work and checks

The connected staging dummy-account slice is verified. This infrastructure story remains In progress: release evidence establishes each environment separately, and enduring ownership, recovery and real-user onboarding have remaining acceptance.

HOL owns separate staging and prod backend projects. Staging has verified genuine dummy sessions, private-profile persistence and role/Home checks. The release procedure freezes one source revision, isolates and audits target builds, checks the active staging version and promotes only reviewed hosted schema. Environment-specific delivery is recorded in release receipts; real-user onboarding and broader operational acceptance remain separate.

Implementation status is separate from stakeholder approval and publication.

Goal

As an HOL operator, I want the Backcountry database to belong to HOL and begin with isolated test data so the team can develop the demo and retain control of its information.

Technical release and environment review

  1. Review the environment ownership and isolation record plus the exact reviewed migration histories.
  2. Review the technical release evidence for source/artifact identity, target/database match, row-level privacy, genuine dummy sessions and zero synthetic staff grants.
  3. Review independent UI acceptance for identity, chosen Home, refresh/sign-out and base-path navigation; track remaining ownership/recovery and real-user onboarding separately.

Backend requirements

  • Promote the connected demo through isolated dev, staging and HOL prod using reviewed target-specific migration manifests; each hosted app must use its own database and protected server credentials.
  • Record the HOL organization/project identity and named access, and resolve an enduring HOL administrator and billing authority before relying on the setup operationally.
  • Choose and document test and real-data environments. Keep disposable development/staging data isolated from future real HOL feedback; do not use Andy’s personal account for HOL production data.
  • Confirm region, plan, access and backup/reset ownership. Store secrets through approved secure configuration, outside public pages and project notes.
  • Review the existing schema, seed data and row-level security tests; migrate only to the approved test environment and verify the checks and reset procedure.
  • Connect only after the exact target is approved and verified. Public fictional accounts have no real staff authority; hosted individual signup/recovery and outbound email remain deferred.
  • Review the provisional schema against owner-only account privacy, constrained canonical content IDs, separate trusted staff scopes/MFA and separate entitlement before further migration.
  • Stage local migrations and RLS tests for the first D085/D058/D089 identity/save slice; do not treat the earlier staging advisor result as proof of these feature policies.
  • Freeze one reviewed source revision, capture and audit isolated target builds, verify staging before prod, and preserve deployment versions, exact asset hashes, backend checks and rollback evidence.
  • Do not run generic local migration pushes, copy users/data between environments, reset hosted data, modify applied migration bytes or treat a static frontend deployment as proof of backend readiness.

Completed maintenance · 1 item

Each item records a bounded result, with its location, change and review evidence. Linked stories provide additional context.

  1. Completed:

    Connect and verify the staging dummy-account demo

    technical review
    Where:
    Andy staging app and HOL staging backend
    What changed:
    Applied the separately approved reviewed 44-version schema, seeded nine fictional identities and installed the server key only in protected Worker storage.
    Expected result / How to check:
    Read the technical release receipt and independent account/Home and profile Save/refresh/restore checks. No browser link alone proves the database or permission boundary.

    Evidence: Connected-staging release receipt dated October 19; Backend API/RLS/session probes and UI2 12-scenario acceptance.

    Staging connected; individual signup/recovery, real email and billing remain deferred.

Connected stories