GlassesResearch Project Vision

GlassesResearch is an evidence-based technical knowledge base for AI glasses and related wearable-computing platforms. Its purpose is to make fragmented information easier to discover, verify, preserve, connect, and teach.

What this repository is

GlassesResearch is simultaneously:

1. A research laboratory for active investigations.
2. A curated reference for verified and well-sourced knowledge.
3. A preservation archive for manuals, listings, photographs, captures, firmware, software, and disappearing web sources.
4. A navigable map of the organizations, people, components, applications, standards, communities, and resources that form the ecosystem.

What this repository is not

It is not merely a collection of links, product claims, disconnected notes, or empty folder structures. Every addition should help a reader answer a question, verify a claim, locate a source, reproduce an observation, or identify what remains unknown.

Ecosystem-wide, model-centric organization

The repository is designed to accommodate the full smart-glasses ecosystem and potentially hundreds of models. The populated model registry is the discovery layer. A dedicated chapter under models/ is created when substantive evidence exists; device-specific hardware, BLE, firmware, software, manufacturing, diagnostics, evidence, resources, and research history then stay together inside that model hierarchy.

The W610 is the current hands-on reference implementation, not the scope boundary. Models that maintainers do not own remain in scope through attributed manufacturer, regulatory, archival, repository, and community evidence.

Shared entities belong in canonical repository-wide locations such as glossary/. Model chapters reference those canonical pages rather than duplicating definitions.

Investigation-driven growth

The repository grows through named investigations. Each investigation begins with a question and records:

• the evidence collected;
• the observations made;
• the current conclusion and confidence;
• unresolved questions;
• every affected model, component, organization, resource, timeline, and knowledge page.

One investigation may update many files. The pull request should tell the story of what was learned.

Knowledge and resources

The repository maintains two complementary layers:

• Knowledge base: distilled observations, findings, diagrams, procedures, and conclusions.
• Resource catalog: external places readers can explore for themselves, with hyperlinks, notes, reliability context, and last-checked dates.

Readers should be able either to use the repository's synthesis or follow the evidence trail independently.

Reference implementation

GlassesResearch is the first practical implementation of a broader investigation method currently referred to by the working title KISS. KISS will be extracted gradually from practices that prove useful here. GlassesResearch remains focused on glasses research; it does not wait for the general template to be complete.

Standing preservation priority

Archive first, organize second. When lawful and practical, fragile firmware, APKs, SDKs, packet captures, protocol notes, model files, manuals, flashing procedures, recovery methods, tools, repositories, and community material should be preserved with provenance, hashes, licensing, and redistribution notes before link rot removes them.

Hands-on findings, externally sourced claims, community reports, and inferences must remain visibly distinct.

Standard of success

A successful visitor should be able to:

• find the relevant model chapter;
• begin with a practical question;
• trace claims back to evidence and sources;
• discover useful communities and further reading;
• understand uncertainty and conflicting evidence;
• see what research should happen next;
• contribute without creating duplicated or orphaned knowledge.