Shared shapes for a Verifiable Trust Community's live administrative console events: a hint-only channel that tells an administrator's console WHEN to re-read, never WHAT changed. THE MODEL. A console subscribes once per session with `vtc/admin/events/subscribe`, naming the topics it renders. The community answers with a stream of `vtc/admin/events/event` documents, each naming one topic and, for a count topic, the caller's current count. An event carries no record and no personal data. The console reacts by re-fetching the topic's own signed read, so the read stays the only place authorization is decided and the only place data leaves the community: the stream can neither leak a record nor grant a read. Polling those reads remains the fallback whenever the stream is down. TOPICS AND THEIR READS. Each topic names one read. A community sends a topic's events only to a caller it would answer on that read. - `actions` — the caller's visible administrative actions (`vtc/admin/actions/list`). Count topic: the caller's `waitingForMe` count. - `acknowledgements` — the acknowledge-category actions awaiting the caller (`vtc/admin/actions/list`). Count topic: the open acknowledge actions the caller has not yet acknowledged. - `joinRequests` — the community's join requests (`vtc/join-requests/list`). Count topic: the join requests awaiting a decision. - `members` — the community's members (`vtc/members/list`). No count. - `singleAdminMode` — whether single-administrator mode is in effect. Every administrator may read it. No count. - `config` — the community's stored configuration (`vtc/config/export`). No count.
https://trusttasks.org/spec/vtc/admin/events/_shared/0.1/topicTrust Tasks — the registry of Trust Task specifications.
Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.
Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.