what it enables
Let tools cooperate around the data
A useful app does not have to become the permanent home of your knowledge. Give the data its own address, meaning and permissions, and different tools can work with it.
Events as Linked Open Data
The aaltra venue publishes real events from its pod. A website can render those events, a calendar can read their dates, and an agent can query them. Each client uses the same linked source data.
This is live: run the public query and follow one of the returned event addresses.
A worker with authority the owner chooses
Imagine a notes service that registers on your pod. You choose the Contexts it may reach. It can then work while you are offline, using its own credentials, and you can narrow or revoke its grants.
Kotlin 0.2 supplies experimental registration and owner-consent flows for this pattern. The service-access guide shows the working setup; the notes service is an example use case.
Personal memory that can outlast the assistant
Notes, plans, projects and observations could become a graph in your pod. An agent could find relevant resources and follow links while another app helps you browse or edit the same knowledge.
MCP and the data operations supply building blocks today. A complete personal memory experience is a direction to explore, not a packaged product delivered by the Kotlin release.
Shared knowledge for teams and communities
A museum could publish a collection's public facts and keep working notes private. A team could give support tools access to product knowledge while holding internal plans back.
These are scenarios for the same model: shared meaning, explicit authority and links that can cross data spaces. The applications and their operating arrangements still need to be built and tested.