Your account
HOL-D013Story implementation: In progress

Find guides, creators, and other people

people · Proposed launch phase 2

Start from Home

Review as Guide

User story

As a guide, I want members to discover my profile by role and expertise so I can connect with people looking for my knowledge.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Use backend published person projections for directory, filters, public detail and visible associations. Keep one canonical person with overlapping professional labels; do not merge stale bundled profiles over backend results.
  • One person has one public profile with any combination of self-service Guide, Creator and Athlete labels; D090 owns setup. Verified email gates publication, not HOL approval.
  • Qualifications entered by the person are visibly distinct from separately verified claims. Public affiliations require both-side consent through D098.
  • Show the guide’s self-published identity, self-declared qualifications and separately verified credential claims, expertise and broad service regions consistently in the guide profile and public People discovery.
  • Let readers identify a Guide and reach relevant approved work or sessions; expose only approved public fields.
  • Guide identity does not grant paid-member access, a verified-credential badge or editorial answer-publication authority.
  • Change only permitted own-profile fields; use D071/D029 only for separately verified claims and D098 for mutual affiliations; ordinary professional setup uses D090.
  • Keep draft/requested identity changes separate from the currently published public profile, with a visible result and an opt-out for broad place presence.
  • Provide a dedicated public person detail page for each published Guide, Athlete and Creator/contributor, independent of the viewer’s own My Backcountry account. The same canonical person may hold overlapping professional attributes.
  • Public person pages show self-published name/image, biography and selected role labels, expertise/disciplines, broad region/service area, public website, supported credentials and mutually confirmed organization affiliations; ordinary member profiles remain subject to their existing privacy choice.
  • Open a mutually confirmed Guide → tour company or Athlete → manufacturer/brand affiliation as a labeled link to the corresponding public organization page, with a reverse people link. Displaying an affiliation does not imply HOL endorsement or paid sponsorship.

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 Professional Home using Maya Hart (Guide) or your own verified account with that professional label. Use the account/workspace menu → Professional. Professional labels do not include paid reader access.

Navigation from sign-in

  1. 01Open the fictional Guide account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02From Professional Home select View public profile. Use footer Explore → People for Search people and role/expertise filters.

Feature checks start here

Public person profile and People directory

Public-content reads are available for dev review; full story acceptance and stakeholder approval remain separate. Current public pages and supported account links are connected in dev. Only the visible workflow described here is available; credentials, privacy edge cases and unrelated editorial/operator workflows require separate acceptance and remain incomplete.

  1. 03Search Maya Hart, Jordan Lee and Liam McGee; use Filter people by role and Filter people by expertise, clearing filters between examples.
  2. 04Open each dedicated public page and inspect biography, broad region, role labels and any public relationships. These are person pages, not My Backcountry.
  3. 05On Maya Hart open View Teton Meadow Guides, then return through its Connected people link. On Jordan Lee compare Alpine Field Co. Where a profile has no affiliations or published work, use its honest empty state.
  4. 06For your own professional account use account/workspace menu → Professional → View public profile. Normal professional publication does not require HOL approval; self-entered qualifications are not verified credentials.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Selected authorization is the public read/content-seeding slice only. Existing write, participation, editorial management, event operations, gift redemption, payment and delivery requirements below are separate later work unless already authorized elsewhere.
  • Use backend published person projections for directory, filters, public detail and visible associations. Keep one canonical person with overlapping professional labels; do not merge stale bundled profiles over backend results.
  • Persist owner profile fields, self-selected professional labels/affiliations, requested changes and public-visibility choices as distinct data; connect only owner-published permitted fields and mutually confirmed affiliations to the public person ID.
  • Authorize own permitted-field changes; verified-claim changes go through D071/D029 and affiliations through D098. Reject self-verification, cross-owner writes and private field leakage in People/search/place responses.
  • Maintain stable credited-person identity across profiles, work and directory results; support stale-update conflicts, opt-out/revocation and index refresh without changing paid entitlement.
  • Project one stable person identity and permitted self-published professional fields into public directory/detail/search; ordinary members stay private or member-visible under their separate settings.
  • Store typed person–organization relationships with both-party consent/publication/removal state and agreed labels; expose reciprocal links only for allowed targets and never infer sponsorship or paid membership.

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. Browse/search Guide, Athlete and Creator profiles signed out; changed published information must remain current after reload, and unavailable profiles have an honest state.
  3. Use separate Guide/Creator/Athlete owners, reviewer and public reader to test permitted fields versus pending/verified/private fields.
  4. Request and approve an affiliation change, then revoke/opt out; verify consistent public discovery after reload and unchanged paid access.
  5. Compare public Guide/Athlete/Creator fields and reciprocal organization links as Visitor/free/paid; revoke an affiliation and verify no stale or private claim remains public.

Before this can work

  • Begin on Professional Home using Maya Hart (Guide) or your own verified account with that professional label. Use the account/workspace menu → Professional. Professional labels do not include paid reader access.
  • Use fictional credentials and broad service regions only; real verification and publication are not connected.

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

Connected stories