Glasses Copilot
Proof Lab
Glasses Copilot / proof

Proof Lab

End-to-end proof harness for transcript-to-cue, phone bridge delivery, fallback behavior, and production readiness.

Supabase Demo Mode

This build uses Supabase/Postgres for app state and session persistence. Hardware can still be simulated until real glasses/ring adapters are connected.

Ready now
Browser HUD active
Ready now
Mock ring controls active
Ready now
Supabase persistence active
Ready now
GitHub evidence optional
Proof Lab

End-to-end proof harness and production readiness gate.

Validate the glasses copilot loop from transcript to cue, HUD fallback, phone bridge queue/ack, and honest Even G2 readiness without requiring real glasses hardware.

Overall readiness score
88%
Blockers
0
Warnings
2
Even G2 hardware status
Not connected; readiness only.
Live Copilot Proof

Latest guided demo loop

This shows the last recorded Live Copilot loop: session, detection, cue, ring action, phone bridge send, and displayed ack.

Demo ready
not yet
Production ready
no
Persistence
unknown
Steps passed
0/8

No guided proof has been recorded in this server process yet.

Flagship demo link

Run Live Copilot Demo Mode before adding more systems.

Latest smoke verdict: ready for demo. Production blockers are shown below until DB, migrations, GitHub OAuth, token encryption, and bridge signing are configured.

Open Demo Mode
Production gate summary

Demo-ready is not production-ready

Safe to demo means Browser HUD, registry cues, proof scenarios, and PWA bridge fallback can run honestly. Safe for production requires Supabase persistence, migration verification, and signing secrets.

Current persistence mode
GitHub db
Persistence unavailable
no
Proof mutation mode
disabled
DB readiness
missing
Safe to demo
yes
Safe for production
not yet
Live sessions
db
Phone bridge
db
Deployment readiness proof

Route health and sanitized proof snapshot

Use the deployment proof API and smoke script to validate a real deployed URL. It proves route reachability and configuration status, not real glasses hardware.

Production verdict
ready for demo
Safe to demo
yes
Safe for production
not yet
Route health checklist
14 routes
Run deployment readiness proof buttonSanitized proof snapshot
/api/glasses/runtime/readiness
json / production
/api/glasses/db/proof
json / production
/api/glasses/db/persistence-proof
json / production
/api/glasses/live/proof
json / demo
/api/glasses/proof/readiness
json / demo
/api/glasses/github/status
json / diagnostic
/api/glasses/github/embeddings/status
json / diagnostic
/api/glasses/bridge/runtime/status
json / demo

What this proves

Deployment proof checks sanitized config status, route availability, readiness scores, persistence mode, migration expectations, phone bridge readiness, and hardware honesty states.

What it does not prove

It does not prove migrations were applied unless verified against the DB, and it does not prove Even G2 hardware, native push, or vendor SDK display output.

DB proof card

Persistence and migration verification

DB proof is read-only by default. Persistence write/read proof requires explicit mutation permission and is blocked in production unless GLASSES_PROOF_MUTATION_ENABLED=true.

DB configured
yes
Required table proof
API checked
Migration acknowledgement
not acknowledged
Persistence proof mode
dry-run default
DB proof endpointRun persistence proof button
Dry-run warning: no proof data is written unless mutation is explicitly requested. Manual migration acknowledgement note: set GLASSES_MIGRATIONS_MANUALLY_VERIFIED=true only after confirming required tables exist in the deployed DB. Production verdict explanation: production requires env readiness, DB connection, required tables, durable persistence, bridge signing, GitHub token encryption, and no blockers.

Blockers

No blocker checks are currently failing.

Warnings

GitHub OAuth config present or optional

GitHub OAuth may be optional for registry-only proof runs.

warn
GitHub token encryption configured

GITHUB_TOKEN_ENCRYPTION_KEY is required before production GitHub OAuth token storage.

warn

Available proof scenarios

Run scenario button calls `/api/glasses/proof/run`; mutation scenarios stay dry-run unless explicitly enabled.

Readiness JSON

Registry-only interview cue

Generate a senior interview cue from registry context without requiring GitHub evidence.

safe
Run scenario buttonregistry_only_interview_cue

GitHub evidence interview cue

Generate an answer using indexed GitHub chunks when available.

safe
Run scenario buttongithub_evidence_interview_cue

HUD ring control loop

Generate a cue and apply mock ring actions for simplify, technical, panic, and repeat.

safe
Run scenario buttonhud_ring_control_loop

Phone bridge delivery loop

Pair a mock phone, store a cue, poll pending messages, and ack delivered/displayed.

dry-run default
Run scenario buttonphone_bridge_delivery_loop

Unavailable device fallback loop

Send a cue to the unavailable Even G2 adapter and assert Browser HUD fallback remains active.

safe
Run scenario buttondevice_adapter_fallback_loop

Last proof result

No proof run is persisted on this static page. API responses return proofRun, steps, artifacts, pass/fail, warnings, and blockers.

Step-by-step timeline

Each scenario returns pending/running/passed/failed/skipped/blocked step statuses.

Artifacts panel

Artifacts are masked before display; bridge tokens and secrets are never shown.

What this proves

  • Registry-grounded cue generation works.
  • Mock ring actions can change cue variants.
  • Phone bridge queue and ack lifecycle work in safe local state.
  • Unavailable Even G2 adapter falls back to Browser HUD.

What this does not prove

  • It does not prove real Even G2 hardware is connected.
  • It does not prove native app deployment.
  • It does not prove push/WebSocket delivery.
  • It does not prove every GitHub repo is indexed.