Glasses Copilot
Knowledge Hub
Glasses Copilot / knowledge

Knowledge Hub

GitHub-aware foundation, app registry context, memory tools, sources, and indexing 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
GitHub source connection

Knowledge is honest about its evidence.

The copilot always uses the canonical registry. When a real GitHub token is configured and repos are indexed, answers can also cite safe source chunks. Until then, it stays in registry-only mode. Public repos such as craftyguru/insait can be indexed explicitly without exposing a browser token.

Connection
Loading
Evidence mode
Registry only
Mapped repos
0
Chunks
0
Connect GitHubOAuth: needs configPrivate repo access: disabled
Safe file policy
Indexes docs, configs, app routes, server/lib/api code, database schemas, and tests.
Skips .env files, keys, certs, build output, node_modules, media, binaries, and oversized files.
Embeddings are optional. If disabled or unavailable, keyword retrieval remains the fallback.
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
Ask InSAiT glasses output

Ask InSAiT, then send a short answer to glasses.

This calls the server Ask route when OpenAI is configured. Full answers and source context stay on the dashboard; the glasses receive only a compact status, answer, error, source hint, or clear command.

No Even Hub bridge session is selected. Configure the companion dashboard base URL, enable command sync, then refresh.

Bridge sessions
0
Last command
none
No command has been sent yet.
What the AI knows right now

Current knowledge mode is registry-only.

This summary separates registry facts from indexed repo evidence. If repo chunks are not indexed, answers must stay honest and say registry-only.

Registry knowledge
available
GitHub repo evidence
needs connection
Indexed files
registry mode
Embeddings
disabled
Persistence mode
unavailable
Supabase persistence
needs env
Current answer mode
registry-only
Best next knowledge action

Use registry demo mode

The copilot can answer from the app registry now. Connect GitHub later when you want repo-backed implementation evidence.

Open Live Copilot

Known vs Not Yet Known

Known: app registry facts, app descriptions, senior-dev explanations, and declared routes/APIs from the registry.
Not yet known: real repo implementation details unless indexed, live production DB state unless DB proof passes, Even G2 runtime behavior, native phone app behavior, and real deployment state unless smoke ran against the deployed URL.

Current empty states

GitHub later: registry demos are supported now; OAuth and repo selection unlock code evidence.
No repo mapped: okay while organizing apps; app-to-repo mapping unlocks indexing.
No indexed files: okay for registry-only answers; safe indexing unlocks file evidence.
Embeddings disabled: okay because keyword fallback works; embedding config unlocks vector or hybrid retrieval.
Supabase/DB later: okay locally; DATABASE_URL plus migrations unlock durable proof.
Retrieval not verified: okay before QA; Retrieval Test unlocks evidence confidence.
Knowledge tools

Manage what the copilot knows.

App Map, Sources, Knowledge Cards, Import, Notes, and Retrieval Test stay on separate routes, but this page explains how they connect.

6 tools
App Map

Inspect the canonical 10-app registry and app boundaries.

Sources and Cards

Review imported source material and jump into structured cards.

Knowledge Cards

Edit structured facts the copilot can reuse.

Import

Bring in ChatGPT exports, notes, and memory files.

Notes

Capture quick project facts for future retrieval.

Retrieval Test

Check whether answers will cite real repo evidence or stay registry-only.

Knowledge Quality

Per-app knowledge readiness

This separates registry facts from GitHub-backed implementation evidence. Registry-only is valid for demos; repo claims require indexed and matched files.

1/11 beyond registry

XFlow

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

XFlow: A control plane for routing app events, operator actions, and cross-system workflows. 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..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

Verixet

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

Verixet: A governance layer for billing state, customer access, and entitlement decisions. Auth: Supabase JWT model expected for owner/admin access.. Billing: Stripe-oriented billing model; exact production integration should be verified from repo source.. Entitlements: Entitlements should derive from subscription/customer state..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

Rataify

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

Rataify: A product for turning user or system signals into clear ratings and decisions. Auth: Expected authenticated workspace/admin access.. Billing: Unknown until app repo is connected.. Entitlements: Unknown until app repo is connected..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

AudAiX

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

AudAiX: An audio intelligence layer for voice capture, transcription, and AI-assisted listening workflows. Auth: Owner dashboard auth today; production voice sessions need stricter user/session boundaries.. Billing: Usage-based cost tracking is expected for model/audio calls.. Entitlements: Audio features should be gated by plan/session permissions..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

Crevux

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

Crevux: A creative workspace for generating and managing media assets. Auth: Authenticated creator/operator access expected.. Billing: Likely usage-based due to generation cost; exact implementation needs repo verification.. Entitlements: Generation limits should map to plan or credit state..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

WordGeni

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

WordGeni: A content engine for turning ideas into polished growth, product, and marketing copy. Auth: Authenticated creator/admin access expected.. Billing: Usage/cost tracking expected for model calls.. Entitlements: Prompt and generation access should map to plan limits..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

JournOwl

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

JournOwl: A reflection product for capturing thoughts and turning them into useful personal knowledge. Auth: Private user auth with strong data isolation required.. Billing: Unknown until product repo is connected.. Entitlements: Personal memory features should be user-scoped and plan-gated if monetized..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

UrSite

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

UrSite: A site-building workflow for launching polished web experiences faster. Auth: Authenticated owner/editor access expected.. Billing: Likely subscription or project-based; verify from repo before claiming.. Entitlements: Publishing/custom domain features should map to plan access..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

PitStrike

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

PitStrike: An interactive product centered on competitive or tactical user action. Auth: Unknown until source is connected.. Billing: Unknown until source is connected.. Entitlements: Unknown until source is connected..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

1ofakindpiece

registry-only

quality 35/100Needs repo mapping
registry status
Ready for registry answers
repo mapped
no
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

1ofakindpiece: A commerce-style product for unique pieces, inventory, and customer presentation. Auth: Buyer/admin access model needs repo verification.. Billing: Likely Stripe/checkout if commerce is active; do not claim until indexed.. Entitlements: Inventory and purchase permissions need verification..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs repo mapping.

InSAiT Glasses Copilot

repo mapped

quality 50/100Needs indexing
registry status
Ready for registry answers
repo mapped
yes
indexed files
0
embedding coverage
disabled
retrieval verified
not yet
freshness
never indexed
Known

InSAiT Glasses Copilot: Live technical conversation copilot that generates senior-dev HUD cues from app knowledge and sends them to browser, Phone Bridge, and future glasses targets. Auth: Local dev allows owner fallback; production requires owner-scoped auth and server-side GitHub token handling.. Billing: No production billing is claimed for this platform yet; cost and readiness surfaces exist for proof and planning.. Entitlements: Demo tools require Supabase persistence; production entitlements must be DB-backed and verified before deployment claims..

Not yet known

Repo-level file paths, implementation details, schemas, and runtime behavior are not verified until GitHub indexing and retrieval pass.

Recommended next action: Needs indexing.

Embeddings status

Vector search is opt-in; keyword search stays live.

Current retrieval mode: keyword fallback.

Vector
Disabled
Model
text-embedding-3-small
Dims
1536
Embedded
0
Pending
0
Failed
0
Registry only: no matching repo chunks.
Keyword: deterministic chunk scoring.
Vector: embedding similarity when configured.
Hybrid: keyword + vector evidence reranked.
Repo selection and indexing

Manage approved GitHub repos

Approved repos are app-aware and indexed with the safe file policy. Missing or unauthorized repos show their own status instead of blocking the whole Knowledge Hub.

Repository
App
Status
Chunks
Last indexed
No repositories are selected yet. Use the craftyguru/insait public repo option for this platform, or connect GitHub with a real token to list private repos.
GitHub later

What it means: The copilot is using registry-only context, not repo-backed code evidence.

Why it is okay now: Registry-only answers are acceptable for app-boundary explanations. Public craftyguru/insait indexing can still prove repo evidence without exposing a browser token.

What unlocks it later: Configure GitHub OAuth to list account repos and private repos.

No repo mapped

What it means: No repository is currently mapped to a registry app.

Why it is okay now: The registry still provides canonical app knowledge while repo mapping is missing.

What unlocks it later: Map craftyguru/insait to InSAiT Glasses Copilot, then run safe indexing.

No indexed files

What it means: No safe source chunks are available for retrieval yet.

Why it is okay now: The product can still demo registry-only context honestly.

What unlocks it later: Run safe indexing after a repo is selected.

Embeddings disabled

What it means: Vector retrieval is off or not configured.

Why it is okay now: Keyword retrieval and registry context still work.

What unlocks it later: Configure the embeddings provider and backfill indexed chunks.

Supabase persistence required

What it means: Knowledge status is not proving durable database state.

Why it is okay now: Registry context can answer app-boundary questions while GitHub evidence is unavailable.

What unlocks it later: Configure Supabase, apply migrations, then rerun DB proof and deployment smoke.

Retrieval not verified

What it means: No manual retrieval check has confirmed whether a generated answer cites repo evidence.

Why it is okay now: This is expected before QA; registry-only mode remains honest.

What unlocks it later: Open Retrieval Test and check whether answers cite real repo evidence or stay registry-only.

App and platform knowledge map

Searchable registry foundation

Evidence mode: Registry only

XFlow

Automation

not connected

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

Verixet

SaaS platform

not connected

A governance layer for billing state, customer access, and entitlement decisions.

Rataify

Decision intelligence

not connected

A product for turning user or system signals into clear ratings and decisions.

AudAiX

Audio AI

not connected

An audio intelligence layer for voice capture, transcription, and AI-assisted listening workflows.

Crevux

Creative AI

not connected

A creative workspace for generating and managing media assets.

WordGeni

Content AI

not connected

A content engine for turning ideas into polished growth, product, and marketing copy.

JournOwl

Personal knowledge

not connected

A reflection product for capturing thoughts and turning them into useful personal knowledge.

UrSite

Web publishing

not connected

A site-building workflow for launching polished web experiences faster.

PitStrike

Interactive experience

not connected

An interactive product centered on competitive or tactical user action.

1ofakindpiece

Commerce

not connected

A commerce-style product for unique pieces, inventory, and customer presentation.

InSAiT Glasses Copilot

Live interview copilot / glasses HUD / phone bridge

not connected

Live technical conversation copilot that generates senior-dev HUD cues from app knowledge and sends them to browser, Phone Bridge, and future glasses targets.

What this AI knows

Canonical product boundaries
Known route and API groups from registry
Auth, billing, entitlement notes
GitHub chunks only after real indexing

Missing context

XFlow: repo not verified yet
Verixet: repo not verified yet
Rataify: repo not verified yet
AudAiX: repo not verified yet
Crevux: repo not verified yet
WordGeni: repo not verified yet

Suggested questions

How do all 10 apps fit together as one ecosystem?
Which app owns billing and entitlement decisions?
What evidence is registry-only versus GitHub-backed?
Which products are production-ready and which need verification?