SIGNALS & CONNECTIONS

Your tools.
A more connected context.

See the difference between observing an app’s activity and explicitly connecting a tool. One never silently grants the other.

6 boundaries to explore
CONNECTION LEVELS

Knowing a tool was open is not the same as having access to it.

The site now makes that distinction explicit so future integrations do not blur observation, context, and permission into one vague “AI access” claim.

LEVEL 1 · AVAILABLE SIGNAL

Observed activity

App names, permitted domains, and time ranges within the current tracking contract.

LEVEL 2 · USER-PROVIDED

Explicit context

A goal, note, or selected material you deliberately add.

LEVEL 3 · PLANNED

Connected tool context

A future integration authorized for a specific source or service.

LEVEL 4 · PLANNED

Approved action

A scoped execution permission distinct from merely reading context.

AN IMPORTANT DISTINCTION

Seeing an app name
isn’t connecting an account.

Future tool access must be authorized separately. The example connections above are not active integrations or partnership claims.

See how permissions should work

See your work a little more clearly.

Start with the foundation. Explore what comes next.

Get FocusMirror
CONCEPT DEMONSTRATION

Permission before action.

Inspect this example scope. These controls only change the demonstration; no accounts connect and no automation runs.

Publishing, sending messages, and access to other accounts are not permitted.

Available signal

Desktop activity

Foreground application names and time ranges. Activity observation is not an API integration or permission to control that app.

Follow connection updates