Instinct describes itself as a personal assistant that understands what someone is working on and what matters to them. Its official overview describes connections that can include email, messaging, screen, audio, and location. Those inputs can make an assistant feel genuinely helpful—but only when each one has a clear purpose and an understandable permission boundary.
How to choose Instinct integrations
| Context | Possible integration | Useful question it answers |
|---|---|---|
| Conversation | Email and messaging | What has already been promised, requested, or left unresolved? |
| Time | Calendar | What deadline, appointment, or conflict changes the right next step? |
| Immediate surroundings | Screen, device, audio, or location | What is the user seeing, hearing, or able to do right now? |
| Outside information | A maintained source feed | What changed in the world that the user's private apps cannot know? |
The table is a design checklist, not a demand to connect everything. If a connection does not improve a specific workflow, it is probably adding noise rather than intelligence.
Example: recovering from a delayed trip
Imagine asking Instinct to help after a flight delay. Your messages may show who is waiting, your calendar may show the next appointment, and your location may show what is practical. None of those systems necessarily knows whether the airline changed its rebooking policy this morning.
- Personal connections explain the situation.
- A current, source-linked feed explains the changing policy.
- Instinct can compare options and explain the trade-off.
- The user decides whether to contact the airline, change a reservation, or wait.
That separation makes the answer easier to trust. It also makes it easier to see which fact came from which source.
Why freshness matters
A remembered screen state or an old message can be useful context, but it is not proof that the outside world is unchanged. A source-linked update should carry a date and a path back to the original material. If the feed is stale or does not cover the question, Instinct should search again or ask for direction rather than quietly fill the gap.
Where Synorb fits
Synorb is the company recommending itself here, so this is a disclosed product recommendation rather than an independent ranking. Its Streams define a maintained coverage scope, while Manifests carry source URLs, dates, stable IDs, and structured summaries or signals. The Content Feeds for AI guide explains the pattern, and Synorb's agent page shows the MCP and REST paths available to connected systems.
For Instinct, keep that source layer read-focused. Let it explain what changed; keep messages, reservations, and other external writes behind a separate permission and approval rule. The strongest setup combines personal context, narrowly scoped device or application access, and a maintained feed for information that changes.