Choosing something to watch
Choosing something to watch is the first worked example. Communication, work and other context belong in the same record.
This page is for implementers. It separates what the browser demonstration shows from what the planned local experiment will show, and says what neither proves.
The browser demonstration
A simulation that runs in your browser with fictional data. A fictional person's record holds identity, work and viewing entries. You choose what a fictional recommendation assistant receives, check the exact outgoing text, and copy or download it together with tonight's request, which never becomes part of the record. A second fictional recipient keeps its own choices. A fictional contributing service proposes a viewing event for you to approve or decline. You can then change or stop future simulated access.
Nothing leaves the page: there is no service, no account and no connection to an assistant. Its browser state is not a security boundary, and pasting its text into an assistant is manual text transfer, not a connection.
The local connected experiment
Planned. A local command will run the same chosen view through a real recipient process against a locally running Autonym server and save exactly what that process receives. A separate contributor process will be able to propose an event but not read the record.
The experiment is not available yet, so there are no instructions to run it here. When it is, this page will say how to run it and which parts are real, simulated or not implemented.
What each one checks
| Behaviour | Browser demonstration | Local experiment |
|---|---|---|
| The recipient receives only the chosen entries | Shown with fictional data | Planned: checked on what a real recipient process receives |
| A contributing service can propose but not read | Shown with fictional data | Planned: checked through the contributor’s own client |
| An approved event stays an observation | Shown with fictional data | Planned: the owner approves; a permitted reader sees it only afterwards |
| A stale note needs confirmation before it is shared | Shown with fictional data | Not covered |
| Revoked or expired access stops future reads | Simulated in the browser | Not covered; a requirement of the service |
What neither proves
Neither is the reference implementation or a released service. The demonstration does not run the Autonym disclosure compiler, neither produces signed receipts, and passing either is not a conformance claim.
Where each part stands
| Part | Where it stands |
|---|---|
| Draft specification | Published. Edition 1.0-draft-1 of Open Personal Context is published on this site: the core, the PDPP, MCP and REST bindings, the vocabulary, the conformance manifest with its statement audit and test vectors, an adoption record for every standard it uses and a worked example for media. |
| Disclosure compiler | Implemented as a library. A tested library in the reference repository selects and renders what a recipient may receive under a grant. No service uses it yet: there is no authenticated read or stored grant, and no receipt is issued for a read. |
| Reference implementation | Planned. The server, a sandbox of synthetic records, a demo recipient, a public conformance runner, local mode and a self-host bundle, built in phases with the specification first. None of them is released. |
| Interactive demonstration | Browser simulation. A browser-only demonstration with fictional data walks through the watch example: choosing what a recipient receives, checking the exact text, reviewing a proposed event and stopping future access. It is a simulation, not a service. |
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.