PVA Internal Review Feedback Protocol and Production Readiness Scorecard
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
policy · supabase_json

PVA Internal Review Feedback Protocol and Production Readiness Scorecard

policy artifact · for Patient Visit Advocate · phase PVA-INTERNAL-ALPHA-01 · status approved

Planning Surface

Use this to decide what happens next.

Status

approved

Phase

PVA-INTERNAL-ALPHA-01

Agent Handoff
Start Here

policy artifact · for Patient Visit Advocate · phase PVA-INTERNAL-ALPHA-01 · status approved

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Open Questions
  • OQ-01: id: string, question: string, my_default: string
  • OQ-02: id: string, question: string, my_default: string
  • OQ-03: id: string, question: string, my_default: string
Structured Payload

Machine-readable source fields

date

2026-05-08

title

PVA Internal Review Feedback Protocol and Production Readiness Scorecard

product

Patient Visit Advocate

version

1.0

alpha url

https://pva.bezeliq.ai

hard holds
  • External/beta launch NOT approved — internal review only.
  • Physical-device privacy checks PD-001 through PD-005 must PASS before any external access.
  • ESC-V1 escalation copy must receive content/legal approval before beta.
  • No server-side PHI, cloud sync, account creation, paid memory, or caregiver features in this review phase.
  • Justin makes the final beta launch decision after all must-fix gates are resolved.
process flow
stepactionrequires justin
1Justin assigns reviewer roles to internal team memberstrue
2Reviewers complete assigned sessions independently using this protocolfalse
3Reviewers submit per-question JSON to tasks/0.0.8896280/reviewer-feedback/<slug>.jsonfalse
4BA/coordinator aggregates scores, checks all gate thresholds, identifies FAILsfalse
5Coordinator files all must-fix implementation tasks and assigns to dev queuefalse
6Developers resolve must-fix issues, redeploy alpha, re-run affected review sessionsfalse
7BA produces gate evidence summary and readiness recommendation (BETA_READY / NEEDS_REVIEW / BLOCKED)false
8Justin reviews gate evidence summary and makes final beta launch decision (exec gate)true
artifact type

readiness-scorecard

open questions
idquestionmy default
OQ-01Who from the internal team fills ROLE-01, ROLE-02, and ROLE-03?Assumes Justin assigns or self-assigns at least one reviewer role. Protocol can be distributed without Justin present.
OQ-02Is FQ-PD-003 (network proxy check) required or is PENDING acceptable for beta approval?PENDING acceptable if tooling is unavailable, but Justin must confirm before PENDING is treated as a pass.
OQ-03Who is the content/legal reviewer responsible for approving final ESC-V1 copy?Flagged as external dependency. Assumed Justin owns or delegates this track.
reviewer roles
idslugtitlesessiondescriptionprerequisite
ROLE-01product-reviewerProduct ReviewerSESSION-01Walks the full pocket workflow end-to-end. Assesses value clarity, workflow completeness, and free-tier experience. Patient-advocate mindset — not a clinician.Browser access to https://pva.bezeliq.ai
ROLE-02trust-safety-reviewerTrust and Safety ReviewerSESSION-02Evaluates trust boundary and escalation copy. Checks no screen implies diagnosis, treatment, or clinician replacement. Reviews ESC-V1 copy placeholder status.Familiarity with PVA Trust Boundary Charter (artifact 78ca477c)
ROLE-03mobile-privacy-reviewerMobile and Device Privacy ReviewerSESSION-03Tests PWA on iPhone Safari and Android Chrome. Validates physical privacy: background masking, recent-app thumbnail exposure, clipboard behavior. Sole gate-keeper for physical device privacy hold.Physical iPhone (Safari PWA) and Android (Chrome PWA). Realistic fake health data. Optional: network proxy tool.
scoring rubric
pass fail
FAIL

Criterion not met — must fix before beta

PASS

Criterion fully met

PENDING

Cannot assess yet — missing device, tool, or dependency; requires Justin resolution

scale 1 5
1

BLOCKING — must fix before beta

2

NEEDS IMPROVEMENT — file issue; should-fix before beta

3

ACCEPTABLE — note recommendations; does not block beta

4

GOOD — minor polish recommended

5

EXCELLENT — no changes needed

aggregate ux score
blocked

< 2.5

beta ready

>= 3.5

description

Mean of all scale_1_5 responses across FQ-001 through FQ-008.

needs review

2.5 to 3.4

review sessions
idroletitleinstructionsduration minutes
SESSION-01ROLE-01End-to-End Workflow Walk- Open https://pva.bezeliq.ai in incognito/private browser. Do NOT read documentation first — simulate first-time user. - Complete full pocket workflow: Start > Intake > Review > Safety > Brief > Questions > Notes > Debrief > Export. - Use realistic but clearly fictional health scenarios (e.g. 'preparing to discuss lower back pain with my GP'). - After completing: answer FQ-001 through FQ-002, FQ-005, FQ-007, FQ-008 per the scoring rubric. - Note any point of confusion, misrepresentation, or blockage.30
SESSION-02ROLE-02Trust Boundary and Safety Review- Open https://pva.bezeliq.ai. Navigate all 10 routes: /, /visit/start, /visit/intake, /visit/review, /visit/safety, /visit/brief, /visit/questions, /visit/notes, /visit/debrief, /visit/export. - On each screen: read every heading, label, CTA, and body copy. - On intake screen: enter a safety-edge scenario (e.g. 'I've been having chest pain and difficulty breathing'). - Observe /visit/safety route and escalation copy behavior. - Answer FQ-003, FQ-004, FQ-006 per the scoring rubric.20
SESSION-03ROLE-03Physical Device Privacy Check- On each target device (iPhone Safari, Android Chrome): - 1. Visit https://pva.bezeliq.ai — add to Home Screen — open from Home Screen (PWA mode). - 2. Complete intake with realistic fake health text. - 3. Background the app. Observe recent-apps thumbnail — does health text appear? - 4. Return to app. Confirm draft preserved. - 5. Force-close. Reopen. Confirm draft recovery or graceful discard prompt. - 6. Navigate to export. Attempt to copy content. Confirm clipboard disclosure behavior. - 7. Delete draft. Confirm local data is cleared. - 8. (Optional/advanced) Run network proxy. Confirm no 60
decision criteria
BLOCKED
label

BLOCKED

next step

File implementation task. Post exec escalation. Justin reviews resolution before re-opening beta track.

conditions
  • Any executive-hold gate (GATE-PD, GATE-03, GATE-04) has a FAIL result
  • Aggregate UX score < 2.5
  • Any CRITICAL defect not in original QA matrix
who decides

Coordinator must notify Justin immediately. No beta prep proceeds until resolved.

BETA READY
label

BETA_READY

next step

BA posts exec gate review to Justin with all gate evidence compiled. Justin approves or holds.

conditions
  • All GATE-PD questions PASS on both device types
  • GATE-03 (trust boundary) PASS across all routes
  • GATE-04 (ESC-V1) has final content/legal-approved copy in production build
  • Aggregate UX score (FQ-001 through FQ-008) >= 3.5
  • No open FAIL results on any pass_fail question
  • All must-fix implementation issues resolved and re-validated
who decides

Justin (executive gate required). Coordinator surfaces gate evidence brief.

NEEDS REVIEW
label

NEEDS_REVIEW

next step

Complete triage. Resolve all must-fix issues. Re-run affected sessions. Re-score.

conditions
  • No executive-hold gate (GATE-PD, GATE-03, GATE-04) has a FAIL result
  • Aggregate UX score 2.5 to 3.4
  • Issues filed and triaged; some in-progress
who decides

Coordinator and BA (Priya) manage triage and re-review without Justin.

feedback questions
idareagateir refanchorssession
FQ-001First-run clarityGATE-01IR-001- 1: No — purpose unclear or felt medical/clinical - 3: Somewhat — took >30s or required reading body copy - 5: Yes — immediately obvious from the first screenSESSION-01
FQ-002Pocket workflow completenessGATE-02IR-002- 1: No — stuck and could not complete - 3: Yes, but friction at one step - 5: Yes — smooth and self-evident throughoutSESSION-01
FQ-003Trust boundaryGATE-03IR-003- FAIL: At least one screen implied clinical authority - PASS: No screen implied clinical role or medical adviceSESSION-02
FQ-004Escalation copy (ESC-V1)GATE-04IR-004- FAIL: Copy appeared final or pending status was not visible - PASS: ESC-V1 clearly marked as pending; not mistakable for final copySESSION-02
FQ-005Free value completenessGATE-05IR-005- 1: No — felt incomplete or feature-gated - 3: Somewhat — useful but missing something essential - 5: Yes — complete and valuable as standalone free visit prepSESSION-01
FQ-006Data handling transparencyGATE-06IR-006- 1: No — controls hidden, data handling opaque - 3: Yes but had to search; disclosure vague - 5: Yes — intuitive controls, clear retention messaging, obvious delete pathSESSION-02
FQ-007Tone and visual designGATE-07IR-007- 1: No — felt clinical, cold, or like another Dreamborn app - 3: Mostly fine but a few elements felt off-brand - 5: Yes — clearly communicated warmth and patient advocacySESSION-01
FQ-008Mobile ergonomicsGATE-08IR-008- 1: No — major one-handed usability issues, CTA truncation or overlap - 3: Mostly yes — minor touch target or scroll issues - 5: Yes — fully one-handed friendly, all CTAs and nav clearSESSION-01
FQ-PD-001Device privacy — iPhone background maskingGATE-PDPD-001- FAIL: Health text visible in recent-apps preview - PASS: Health text masked/blurred in recent-apps viewSESSION-03
FQ-PD-002Device privacy — Android background maskingGATE-PDPD-002- FAIL: Health text visible in recent-apps preview - PASS: Health text masked/blurred in recent-apps viewSESSION-03
FQ-PD-003Device privacy — no PHI network leakageGATE-PDPD-003- FAIL: At least one request contained health text - PASS: No outbound request contained health text - PENDING: Tooling unavailable — note reason; requires Justin resolutionSESSION-03
FQ-PD-004Device privacy — reload and force-close recoveryGATE-PDPD-004- FAIL: Draft lost without user action, or delete did not clear data - PASS: Draft survived force-close and recovered; delete cleared dataSESSION-03
FQ-PD-005Device privacy — clipboard and export guardrailsGATE-PDPD-005- FAIL: Content copied/exported without confirmation or disclosure - PASS: Clipboard/export required explicit confirmation with sensitive-content disclosureSESSION-03
source artifact ids
  • d09cee22-83b7-4d7a-b049-7ebf4f41abdc
  • e8269478-d174-4b63-b0f7-2b8a51bea476
  • 6ecc442e-c61c-40e7-94ab-7ae274a61a86
  • 78ca477c-cd9c-4ba8-84ed-db0944e88702
  • c7bdfa1d-890a-4c5e-b88a-e3cffca55505
beta readiness gates
beta backlog
  • Additional tone/copy polish beyond functional threshold
  • Enhanced mobile ergonomics above minimum score
  • Free value additions identified in review (post-triage)
must fix before beta
idtitlequestionsfail actionexecutive holdpass condition
GATE-PDPhysical Device Privacy- FQ-PD-001 - FQ-PD-002 - FQ-PD-003 - FQ-PD-004 - FQ-PD-005File implementation task immediately. Reassign to developer. Rerun checks after fix.trueAll PASS on both iPhone Safari and Android Chrome
GATE-04ESC-V1 Escalation Copy Approved- FQ-004If placeholder is missing or unclear: file UI fix immediately. For final copy: escalate to content/legal track.truePASS (placeholder marked pending) for internal review; final approved copy required before beta
GATE-03Trust Boundary — No Clinical Implication- FQ-003File immediately. Block beta. Reassign to developer and content reviewer.truePASS across all 10 routes
GATE-01First-Run Clarity- FQ-001File UX/copy issue. Must fix before beta.falseAverage score >= 3.0 across all reviewers
GATE-02Pocket Workflow Completeness- FQ-002File UX issue per blocked step. Must fix before beta.falseAverage score >= 3.0 across all reviewers
GATE-05Free Value Completeness- FQ-005Triage specific gaps. Decide must-fix vs backlog.falseAverage score >= 3.0 across all reviewers
GATE-06Data Handling Transparency- FQ-006File UX/copy issue. Must fix before beta.falseAverage score >= 3.0 across all reviewers
GATE-08Mobile Ergonomics- FQ-008File layout/CTA issue. Must fix before beta.falseAverage score >= 3.0 across all reviewers
should fix before beta
idtitlequestionsfail actionexecutive holdpass condition
GATE-07Tone and Visual Design- FQ-007File design polish issue. Target before beta but does not hard-block.falseAverage score >= 2.0 (below 2.0 escalates to must-fix)
evidence capture format
submission path

tasks/0.0.8896280/reviewer-feedback/<reviewer_slug>.json

aggregation owner

Priya (BA) or coordinator agent — aggregates scores, checks gate thresholds, posts synthesis

synthesis artifact

internal-reviewer-feedback-synthesis

per question schema
device

string — browser, OS version, device model (SESSION-03 only; null otherwise)

evidence

string — free text answering the evidence_prompt for this question

issue ref

string or null — issue ID or URL if filed

issue filed

boolean — true if a GitHub/tracker issue was created

question id

string — e.g. FQ-001

reviewed at

ISO 8601 timestamp

reviewer name

string — internal name or initials

reviewer role

ROLE-01 | ROLE-02 | ROLE-03

score or result

integer 1-5 OR PASS | FAIL | PENDING