Heimdall/docs/app-profiles/streampixels.md
Meta Vens 8476c0290b R21.4: document StreamPixels' public origin
docs/app-profiles/streampixels.md carried no public origin, so the
allowlist entry in src/app-profiles.ts (https://streampixels.gamecult.org)
had only ops config as a corroborating source, not a doc owner. Add the
line, corroborated by gamecult-ops/nginx/streampixels.gamecult.org.conf:14
and StreamPixels' own .env example, so all four allowlist entries have
a doc owner.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-08 14:51:45 +02:00

77 lines
2.5 KiB
Markdown

# StreamPixels Access Profile
## What this file is
This file records how StreamPixels should fit onto Heimdall in
`docs/architecture.md` without turning streamer-audience data into shared auth
sludge.
It is a boundary note, not a command to rewrite StreamPixels around Repixelizer.
## Public origin
`https://streampixels.gamecult.org` — this is the `allowedReturnOrigins` entry
Heimdall's built-in `streampixels` profile carries (`src/app-profiles.ts`).
Corroborated by `gamecult-ops/nginx/streampixels.gamecult.org.conf:14`
(`server_name streampixels.gamecult.org`) and StreamPixels' own `.env` example.
## Current repo boundary
The current StreamPixels architecture already makes useful splits:
- the web app owns the remembered viewer session
- the service owns provider OAuth exchange and identity resolution
- the overlay remains auth-free
- creator memberships and operator roles are separate from general viewer state
That is already compatible with the shared backbone idea.
## What StreamPixels can reuse
- signed local session mechanics
- linked-identity and signed OAuth-state patterns
- provider adapter structure
- creator/operator capability evaluation
- grant/invite primitives where they fit
In the service-first Heimdall version, the most likely reusable slice is:
- provider OAuth authority
- identity-linking authority
- managed Twitch/YouTube credential custody for creator connections
- entitlement refresh
- shared claim semantics
## What StreamPixels should keep separate
- viewer audience profiles
- creator memberships tied to streamer spaces
- creator connector bindings and feature semantics
- overlay/runtime state
- audience-facing app data in general
In plain language:
- Heimdall can authenticate and authorize the control plane
- Heimdall can also own OAuth flow and token custody for creator-side provider
connections when that reduces auth duplication
- StreamPixels still owns which creator a connection belongs to, what
subscriptions or sync flows it drives, and how failures are surfaced
- StreamPixels audience data stays StreamPixels data
## Capability direction
Likely capability families:
- `viewer_access`
- `creator_access`
- `creator_admin`
- `operator_access`
These should bind onto the existing StreamPixels creator/operator separation
instead of flattening it into one GameCult-member gate.
## Invariant
If a future shared access store exists, it must not become the canonical home
for streamer-audience identity and product data. That stays with StreamPixels.