StateLens is state-first computing for situational intelligence.
A URL-native grammar that transforms observations into portable operator states before explanation, action, or memory.About StateLens
StateLens makes world state readable.
StateLens is a state-first layer for situational intelligence. It does not begin with a personality, a permanent profile, or a raw lifelog. It begins by resolving the world into compact semantic states that humans and AI systems can share.
StateLens externalizes state, not the person.
The public layer can show a low-entropy operator. Sensitive context remains gated inside the user’s private AI.Three meanings of state.
The word state already exists in software. StateLens does not replace those meanings. It adds a situational layer for AI systems that need to understand the condition of the world before they explain or act.
Computational state
Variables, actor state, database values, session memory and runtime persistence. This is the engineering state used by software systems.
Agent state
Conversation, memory, tool results, task plans, intermediate reasoning and active workflow context inside an AI system.
Situational state
The current condition of a world moment: stable, uncertain, conflicted, focused, syncing, repairing, resting, active, or unresolved. This is the StateLens layer.
World → Observation → State Resolution → Semantic Operator → Human → Action → Provenance → Memory
How StateLens fits the stack.
StateLens is one layer in a wider ambient AI constellation. It gives world moments a readable state before Trailstate records a route, ObjectPortal binds state to things, and Companion Habitat turns many states into a living surface.
Ambient Era
The epoch layer: intelligence moves from isolated apps into environments, objects, routines, companions and ambient contexts.
Companion Habitat
The living layer: companions, agents, humans, objects, memory, permissions and reversible continuity coexist.
StateLens
The state layer: multimodal observation resolves into a portable semantic operator before explanation or action.
Trailstate
The provenance layer: routes, receipts, conflict, validation, repair and replayable trails become visible.
ObjectPortal
The object layer: things can receive addresses, context, memory, state, comparison and returned evidence.
Companion Play
The rehearsal layer: state, rhythm, feedback, repair and visible progress become playable and emotionally legible.
Why operators matter.
A normal diary stores text. A lifelogging system stores recordings. A companion stores conversations. StateLens stores transitions. Operators are not decorations; they are compact state addresses.
The operator is not a character. It is a portable semantic state.
Each operator can function as a human-readable face, a machine-readable state, a URL-native address, a diary entry, a runtime signal, and a provenance node.
o-vvv-o
World / Field Root
Phase: context initialization. Action: open field. Entering or moving in a broad environment; the route begins in the open field.
World-aware companions, ambient entry, scene initialization.o-www-o
Open Web / Broad Retrieval
Phase: search / retrieval. Action: crawl. Opening or scanning a broad information space: web, world, source field or retrieval surface.
Research agents, retrieval systems, external source scanning.ovvv-o
Scout Left / Pioneer
Phase: source scouting. Action: scout. Following a promising trail or source cluster before the evidence is narrowed.
Exploration, candidate source selection, early route discovery.o-vvvo
Scout Right / Movement
Phase: route transition. Action: move. Moving to an adjacent route, perspective or evidence surface.
Perspective shifts, alternative route checks, agent path changes.q-vvv-p
Question / Uncertainty
Phase: question formation. Action: ask. Curiosity, uncertainty or a pending test condition becomes explicit.
Clarification, decision hesitation, unresolved user intent.n-vvv-n
Narrow / Focus
Phase: filtering / focus. Action: focus. Concentrated attention on an object, decision, document or reduced evidence set.
Focus mode, context reduction, high-relevance state.0-vvv-0
Clean Parse / Validate
Phase: validation. Action: validate. A stable reading, validated state or settled interpretation has formed.
Grounded answer, stable state, safe-to-proceed signal.p-vvv-q
Resolve / Answer
Phase: answer synthesis. Action: resolve. An answer, conclusion or resolved output is ready after validation.
Assistant response, decision closure, user-facing output.o-mmm-o
Ingest / Memory Load
Phase: memory ingest. Action: ingest. The result is ingested into memory, a route or a reusable trail.
Memory write, diary entry, reusable context artifact.u-vvv-u
Archive / Rest
Phase: archive / save. Action: archive. The state is dormant, archived, saved or at rest for later replay.
Low-power memory, archive, completed route.d-vvv-b
Object A / Source Object
Phase: object reference. Action: bind object. Object-bound evidence or source object enters the route.
ObjectPortal source binding, physical object reference.b-vvv-d
Object B / Returned Object
Phase: object comparison. Action: compare object. Returned, compared or grounded object evidence is brought back into the route.
Object comparison, grounded return, physical context check.x-vvv-x
Conflict / Fracture
Phase: conflict detection. Action: bridge to repair. Contradiction, ambiguity, hallucination risk or unresolved conflict appears.
Mismatch detection, warning, repair prompt, safety signal.e-vvv-e
Empty / No Data
Phase: empty_state. Action: initialize. No relevant data, residue, state or route content exists yet.
Blank context, first run, uninitialized state.a-vvv-a
Active / Live Sensing
Phase: live_state. Action: sense. The system, object, route, field or companion is live, awake, sensing or currently in use.
Camera/sensor mode, active companion, live ambient sensing.s-vvv-s
Sync / Updating
Phase: sync_update. Action: sync. The system is updating context, fetching, writing, reconciling or refreshing state.
Cross-device sync, agent refresh, memory reconciliation.r-vvv-r
Repair / Recovery
Phase: repair_recovery. Action: repair. A conflict, fracture, missing state, failed route or failed synchronization is being recovered.
Error recovery, route repair, hallucination correction.z-vvv-z
Sleep / Paused
Phase: sleep_paused. Action: pause. The state remains present but inactive, dormant, low-power or resting rather than deleted.
Paused companion, resting workflow, low-power device state.What StateLens is not.
Not just Google Lens
Google Lens identifies the world. StateLens resolves the world into state.
Not just a wearable
The hardware may come later. The protocol comes first: a portable way to represent state across devices.
Not just an AI diary
The diary is one application. The deeper contribution is a state-first grammar for situational intelligence.