Your account

User story

As a creator, I want readers to explore my published work and community activity separately so they can understand my contribution beyond one story.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Resolve creator portfolios, public activity and organization-related work from canonical published work/person relationships; accessible metadata never confers access to a paid body.
  • Use the same person/profile ID for all selected professional roles and published-work credits; do not create a separate Creator login or duplicate public profile.
  • Collect the Creator’s attributed published work separately from their Community Activity.
  • Link each credited work to its original native story/gallery/video and back to the correct Creator identity.
  • Keep own-work management and public portfolio presentation distinct; Creator verification alone does not unlock member reading or immediate publication.
  • Use the same public person ID and profile header as People discovery; open this portfolio from public author/photographer/athlete credits rather than a disconnected sample profile.
  • Separate Published work from Community activity on the public page; only approved public activity is visible, and linked premium work keeps its public description plus membership gate.
  • Show credited roles, canonical work links and mutually confirmed organization affiliations without presenting an affiliated organization as the author or duplicating work.

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 Liam McGee (Creator) 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 Creator 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 to open your own person page; use footer Explore → People to compare other people.
  3. 03For portfolio review choose View Liam McGee in People, then Published work or Community activity.

Feature checks start here

Public portfolio

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. 04On Liam McGee switch between Published work and Community activity. Open the public The Quiet Between Storms and return through By Liam McGee.
  2. 05Open Member edition · Words The Long Way In and Member edition · Photography Beyond the Frame. Paid reader access is checked separately from the public person profile.
  3. 06Compare another person from All people: Jordan Lee has an Athlete profile; Maya Hart currently has no published editorial portfolio. Do not expect an affiliation on every profile.
  4. 07For the signed-in professional use Professional → View public profile for the same identity. Preparing/sharing new editorial work remains separate planned workflow scope.

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.
  • Resolve creator portfolios, public activity and organization-related work from canonical published work/person relationships; accessible metadata never confers access to a paid body.
  • Resolve profile credits and portfolio entries to stable person/content IDs; filter activity and content by public visibility/entitlement, and use approved organization relation IDs instead of copied biographies.

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. Open a creator and linked public/paid work; follow canonical links and confirm the independent public/paid boundary.
  3. Verify direct-credit and directory routes resolve to the same person/work and that pending activity, draft credits and protected bodies never enter the public portfolio.

Before this can work

  • Begin on Professional Home using Liam McGee (Creator) or your own verified account with that professional label. Use the account/workspace menu → Professional. Professional labels do not include paid reader access.
  • Use the separate Paid member role fixture when reviewing protected reading; Creator identity does not supply paid entitlement.

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

Connected stories