The wedge
Start with coach-to-client asynchronous video reflections and a private longitudinal record. Add multi-rater 360 programs after this daily coaching loop is trusted.
PRODUCT + SECURITY BLUEPRINT · AUGUST 2026
A lean path to an interactive 360 feedback platform that protects sensitive conversations, works beautifully on mobile, and leaves a clean path to native apps.
Start with coach-to-client asynchronous video reflections and a private longitudinal record. Add multi-rater 360 programs after this daily coaching loop is trusted.
Use OWASP ASVS 5.0 Level 2 as the release gate. It is current, testable, and designed for applications that handle sensitive data.
PII, raw video, transcripts, and private notes never enter an AI workflow by default. Any future AI feature gets a separate consented, minimized data path.
MARKET RESEARCH
No single competitor combines the intimacy of coaching records with the exact video reflection workflow. That is the opportunity.
RECOMMENDED ARCHITECTURE
IDENTITY
Authorization-code flows use PKCE, signed identity tokens, server-side sessions, and stable provider subjects. Roles and relationship access remain server-enforced.
Microsoft identity documentation ↗ETERNAL VIEW CORE
D1 runs the deployable private alpha behind a narrow repository boundary; PostgreSQL is the public-launch migration target. Both preserve relationships, constraints, records, audit events, and encrypted notes.
No raw video bytesLIVE COACHING
Graph creates the calendar invitation and Teams link in the Coach’s Microsoft 365 calendar; meeting media stays with Microsoft.
Graph event docs ↗ASYNC VIDEO
One-time uploads, encoding, signed playback, mobile delivery.
Stream docs ↗SELECTED SECURITY STANDARD
ASVS is the best primary standard here because it turns security intent into verifiable requirements across architecture, authentication, sessions, authorization, validation, cryptography, data protection, APIs, and logging. Level 2 fits a production system processing sensitive personal coaching records.
MFA/passkeys, secure cookies, rotation, revocation, rate limits, no homegrown passwords.
Deny by default. Check tenant, role, ownership, and coach–client relationship on every request.
TLS, encryption at rest, secret management, short-lived signed media URLs, retention by data class.
Client-private and coach-private notes use separate ownership policies; UI hiding is never the control.
Append-only access events identify who did what and when without copying note or video content into logs.
Threat model, automated dependency/SAST/DAST checks, authorization tests, and an independent Level 2 review before launch.
PII + AI BOUNDARY
Named identities live in a dedicated profile boundary. Product records use opaque IDs. Raw video and notes remain inaccessible to model providers.
Only explicitly selected, redacted content may cross the boundary, under a recorded consent and deletion policy. No training use by contract.
LEAN DELIVERY ROADMAP
Fixed Coach/Client roles, relationship authorization, direct private video flow, encrypted owner-only notes, records, audit events, retention, and hard client deletion are implemented.
Provision Stream and Microsoft Entra credentials, grant delegated calendar consent, expand the private allowlist to pilot users, and complete ASVS evidence.
Use contractually controlled real accounts, test Teams invitation delivery and deletion recovery, complete an independent penetration test, then add notifications and exports.
Reuse the versioned API in native clients and add multi-rater workflows only after one-to-one coaching is trusted.