Glasses Copilot
Interview Prep
Glasses Copilot / interview

Interview Prep

Registry-grounded answers for system design, APIs, auth, billing, and portfolio questions.

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
Interview intelligence

Evidence-aware answers for your full 10-app ecosystem.

Pick the app, question type, and answer mode. The copilot uses the registry first and adds GitHub evidence only after real safe-file indexing exists.

App focus
XFlow
Question
System design
Mode
Clear spoken answer
Evidence
Registry only
15-second glasses cue
XFlow System design
> own boundary: Workflow automation and operator control plane
> risk: GitHub indexing is not connected yet
> name registry vs GitHub evidence
Say
I can explain XFlow clearly because I separate the product goal, the system boundary, and the operational tradeoff.
Persistent cue card

XFlow

1/2

I would answer clearly by connecting the product goal to the technical boundary.

XFlow is a control plane for routing app events, operator actions, and cross-system workflows.

I would describe XFlow as a control-plane pattern: app events enter a normalized routing layer, decisions are logged, and operators can inspect or replay outcomes.

Interview session state

Separate interview cockpit

Topic
manual
Collection
ecosystem-core
Mode
fast
Started
10:15:22 AM
Backend
not checked
Latency
none
GitHub path
unknown
Last section
none
Cache warm
unknown
Core indexed
unknown
Sites indexed
unknown
Pinned
0

The dashboard calls a server-side interview proxy, which calls /api/even-agent?format=json with the server token. No OpenAI, GitHub, or Even tokens are exposed to the client.

App focus
Question intake
Talk-track presets
Question type
Answer mode
Fast rewrites
Practice prompts

Live transcript practice

Send cue to HUD is local-only for now; shared realtime HUD state will need a WebSocket or persisted cue channel.

Live cue preview
> Run live cue generation
Detected app/topic preview appears here.

Microphone practice

Mic support
unavailable
State
idle

Browser microphone speech recognition is not available in this browser. Use manual transcript practice.

Live transcript preview

No interim microphone text yet.

Final transcript segments appear here.

Ring mapping: long press panic, swipe up technical, swipe down simplify, double tap follow-up defense.

Ring practice mode

Profile
Interview HUD
Controls
enabled
Last action
none

Ring practice rewrites the current answer locally. Real hardware pairing is not connected yet.

HUD draft
> own boundary: Workflow automation and operator control plane
> risk: GitHub indexing is not connected yet
> name registry vs GitHub evidence

Best answer

I would answer clearly by connecting the product goal to the technical boundary. XFlow is a control plane for routing app events, operator actions, and cross-system workflows. I would describe XFlow as a control-plane pattern: app events enter a normalized routing layer, decisions are logged, and operators can inspect or replay outcomes. I would be careful not to claim repo-level details until indexing is connected.

Technical keywords detected

wouldexplainarchitectureyourecosystemevent-driven routingoperator visibilityidempotent replaytyped route contracts

Evidence Used

Registry-only warning · 62%

GitHub repo indexing is not connected or no indexed chunks matched this question.

Using registry-only context. Repo evidence has not been indexed yet.
registryregistryregistry only
app: xflow
repo: no repo evidence
file path: registry profile
indexedAt: not available
score 0.720confidence 0.720
XFlow registry profile

A control plane for routing app events, operator actions, and cross-system workflows. Production status: internal_alpha.

App context used

Domain
Workflow automation and operator control plane
Auth
Owner-scoped dashboard auth; production should use Supabase JWT verification.
Billing
No direct billing model in this dashboard yet.
Entitlements
Future routes should respect app-level entitlements before firing actions.
Status
internal alpha

Avoid saying

  • Do not invent file paths, database schemas, or repo contents.
  • Do not say every app is production-ready when the registry marks several as needs review.
  • Do not hide uncertainty; name what is registry-grounded versus what needs GitHub verification.

Follow-up questions they may ask

  1. 1What boundary does XFlow own compared with the other apps?
  2. 2How would you test XFlow before production?
  3. 3What would GitHub indexing add to this answer?

Strong closing sentence

I can explain XFlow clearly because I separate the product goal, the system boundary, and the operational tradeoff.