Find the decision. See the proof.
Search connected apps and captured AI work. Preview source evidence, then explore the people and work around it.
- Search authorized connected sources
- Preview the source evidence
Illustrative public data. No customer data or live integrations.
The rollout moved from September 9 to September 16 1–3 so Platform could complete a rollback rehearsal and finalize owner coverage. 1–2
The deployment checklist remains blocked on the IdP runbook. 4
Search the work. Keep the proof.
Search the systems your team has connected. Results honor caller access and explain why they appeared.
Illustrative public data. No customer data or live integrations.
Ranked by relevance, recency, and access.

Launch moved to September 16 for the rollback rehearsal and owner coverage.
Why shown: Direct title match · revised date corroborated by the latest decision thread
Available · Available · source dates preserved
Every claim points to its source.
Review the source behind each statement. Conflicts, stale evidence, and access gaps stay visible.
Illustrative public data. No customer data or live integrations.
The rollout moved from September 9 to September 16 so Platform could complete a rollback rehearsal and finalize owner coverage. The deployment checklist remains blocked on the IdP runbook.


+1Why shown: Each statement is mapped to the accessible source records that establish it.
Available · Available · Available · Partial · source dates preserved
Source 3 selected.
- ConflictingEarlier date disagreesAn older rollout brief still says September 9. It stays visible but does not support the grounded answer.
- StaleSnapshot needs refreshOne connected snapshot predates the final rehearsal decision, so its recency is shown before use.
- InsufficientCompletion is unsupportedNo accessible evidence confirms that the IdP runbook is complete, so the answer keeps the blocker unresolved.
- ProtectedProtected evidence excludedProtected source records are excluded from the answer and visible counts without disclosing restricted details.
See the work behind a decision.
Open a result to trace owners, source apps, AI work, and the evidence connecting them.
What shaped the SSO rollout?
Illustrative public data. No customer data or live integrations.
Give every agent the context to act.
This preview shows how Cortex MCP can give agents permission-safe search, cited sources, Context Graph relationships, and AI work lineage.
Illustrative public data. No customer data or live integrations.

Maya Voss
Platform Engineering
Search
What changed in the SSO rollout?
The rollout moved to September 16 for the rollback rehearsal. The IdP runbook remains the final blocker.
4 cited sources · updated Jul 28, 2026- Scope
- Enterprise SSO
- Access
- Maya's permissions


+1Permission and retrieval path
- 1Caller scope resolvedMaya's identity and project scope set the permission boundary.
- 2Authorized search executedCortex searches 12 connected systems and removes denied records.
- 3Graph context joinedOwners, decisions, work, and artifacts are joined from the graph.
- 4Citations attachedSource IDs, update dates, and lineage are returned with the answer.
Each returned field carries the caller scope, source identity, and retrieval time needed to verify it.
Deployment Triage
search
"What changed in the SSO rollout?"
scope
project:enterprise-sso-rollout
Illustrative MCP response
- answer
- Grounded summary
- sources
- 4 cited records
- relationships
- 11 graph edges
- lineage
- Observed events attached
- access
- Inherited from Maya

Why shown: The agent receives the source IDs and update dates behind the response.

+1

Available · Available · Available · Partial · source dates preserved