Bilateral Trust Tasks, composed into multi-party ceremonies.

From dtgwg-trust-tasks-tf discussion #28: five founders constitute a worker-owned co-op (Thread A), then apply for federation membership in TCF (Thread B). Each numbered step in either thread is a bilateral Trust Task exchange whose policy is one instance of this decision pipeline. Pick a gate, edit its routes, drop a sample scenario into the simulator, watch which route fires, then version the policy and roll it back — fail-forward. Also see the Meta · Thread close tab for the alternative flows when a ceremony doesn't reach COMPLETE — per sankarshanmukhopadhyay #16738059, threads can also terminate REFUSED / FAILED / ABANDONED / INCOMPLETE.

Curious which Trust Tasks each ceremony actually emits or consumes, and which of those slugs are published in the trusttasks.org registry versus still proposed? See the companion page Trust Tasks, mapped by ceremony — an eight-card per-ceremony breakdown plus a catalog of every Trust Task slug we reference, tagged registered / framework-reserved / proposed.