The Meet Rite

Two phones, two yeses, one edge: one visitor opens a meeting, the other accepts it with their own mark, the opener confirms, and the guide appends one edge naming both.

Ceremony https://tasks.mages.city/ceremony/mages/meet/0.1 · ceremony.json · complete when open, accept and confirm are all present · evidence: chained · lasts at most ten minutes

steptaskwhowhat happens
openmages/meet/openopener → guideOpen a meeting; the guide answers a five-character code valid for ten minutes.
acceptmages/meet/acceptacceptor → guideSay yes to the code with a different mark; the guide names the opener back.
confirmmages/meet/confirmopener → guideThe opener confirms after the acceptor's yes; the guide appends one meet edge naming both marks. Its success response exists only when the edge was appended (a refusal is a trust-task-error, a different document type), so reading this step by presence is sound here, unlike a step whose success response can carry a refusal (spec#52).

Drafts, version 0.1, private Trust Task specifications (SPEC §6.5) published by the City under its own domain. Every specification here passes the Trust Tasks task force's own validator against its registry at 0cdf9e517 (17 Nov 2026). Formal models of the family and of the public registry: trust-tasks-formal. Nothing here is on the wire yet: the City's sites still speak their own shapes, and move to these one at a time. Text: CC BY 4.0; schemas and tools: Apache-2.0.