CONNECT
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 SIGNALObserved activity
App names, permitted domains, and time ranges within the current tracking contract.
LEVEL 2 · USER-PROVIDEDExplicit context
A goal, note, or selected material you deliberately add.
LEVEL 3 · PLANNEDConnected tool context
A future integration authorized for a specific source or service.
LEVEL 4 · PLANNEDApproved action
A scoped execution permission distinct from merely reading context.
AN IMPORTANT DISTINCTIONSeeing 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 workSee your work a little more clearly.
Start with the foundation. Explore what comes next.
Get FocusMirror