How an app becomes a participant in the system rather than an island. App Intents expose its content and actions to Siri, Spotlight, and Shortcuts — the question is which capabilities to offer the system, and under what control.
Most software waits to be opened. Connect is the discipline of building an app the system can reach into — exposing its content and its actions so Siri, Spotlight, Shortcuts, and system intelligence can find them and invoke them on the user's behalf. App Intents and App Schemas are the surface; entity schemas contribute the app's content to the semantic index; View Annotations let a person refer to what is on screen in conversation.
The discipline is not “adopt App Intents.” It is deciding which of the app's capabilities become things the system may call, what each one is allowed to do, and where the user stays in the loop. Participation is a grant of authority — and a grant you can scope.
The app stops being an island. The question is which doors you open, and who is allowed through them.
Connect is the actions side — the app's capabilities offered to the system. Context is the content side — the same entity schemas feeding the semantic index the model retrieves from. One framework, two disciplines.
The essay, the build, and the field notes arrive in dedicated sessions. This page states what is coming rather than pretending it is already here.
Exposing capabilities to the system without handing over control. The boundary is the work.
Every action exposed to the system is a grant of authority. Which capabilities, what each may do, and where the user stays in the loop — that is governance.
Governed Intelligence →The actions side and the content side of one framework. The entity schemas you expose for Siri are the same ones that feed the semantic index a model retrieves from.
Context Intelligence →The practical implementation — defining intents, entities, and schemas in Swift — lives in the workshop.
Developer →