PRODUCT + SECURITY BLUEPRINT · AUGUST 2026

Build the coaching relationship.
Buy the solved infrastructure.

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.

01

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.

02

The standard

Use OWASP ASVS 5.0 Level 2 as the release gate. It is current, testable, and designed for applications that handle sensitive data.

03

The boundary

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

Proven parts, assembled with purpose.

No single competitor combines the intimacy of coaching records with the exact video reflection workflow. That is the opportunity.

RECOMMENDED ARCHITECTURE

Own the experience.
Rent the risk-heavy plumbing.

1

IDENTITY

Google + Microsoft OIDC

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 ↗
→
2

ETERNAL VIEW CORE

TypeScript API + relational store

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 bytes
→

LIVE COACHING

Microsoft Teams

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

Cloudflare Stream

One-time uploads, encoding, signed playback, mobile delivery.

Stream docs ↗

SELECTED SECURITY STANDARD

OWASP ASVS 5.0
Level 2

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.

✓

Identity & sessions

MFA/passkeys, secure cookies, rotation, revocation, rate limits, no homegrown passwords.

✓

Authorization

Deny by default. Check tenant, role, ownership, and coach–client relationship on every request.

✓

Data protection

TLS, encryption at rest, secret management, short-lived signed media URLs, retention by data class.

✓

Isolation

Client-private and coach-private notes use separate ownership policies; UI hiding is never the control.

✓

Auditability

Append-only access events identify who did what and when without copying note or video content into logs.

✓

Verification

Threat model, automated dependency/SAST/DAST checks, authorization tests, and an independent Level 2 review before launch.

PII + AI BOUNDARY

Private by architecture,
not by promise.

PROTECTED CORE

PII · videos · private notes

Named identities live in a dedicated profile boundary. Product records use opaque IDs. Raw video and notes remain inaccessible to model providers.

FUTURE, OPT-IN ONLY

Minimized AI workspace

Only explicitly selected, redacted content may cross the boundary, under a recorded consent and deletion policy. No training use by contract.

LEAN DELIVERY ROADMAP

Earn complexity in stages.

  1. BUILT

    Secure product foundation

    Fixed Coach/Client roles, relationship authorization, direct private video flow, encrypted owner-only notes, records, audit events, retention, and hard client deletion are implemented.

  2. CONFIGURE

    Connect production providers

    Provision Stream and Microsoft Entra credentials, grant delegated calendar consent, expand the private allowlist to pilot users, and complete ASVS evidence.

  3. PILOT

    Validate the coaching loop

    Use contractually controlled real accounts, test Teams invitation delivery and deletion recovery, complete an independent penetration test, then add notifications and exports.

  4. LATER

    Native app, then true 360

    Reuse the versioned API in native clients and add multi-rater workflows only after one-to-one coaching is trusted.