Core modules / Collaboration
Work together.
Keep scope clear.
Share progress and handoffs while each participant keeps responsibility for their next action.
- Source status
- Source and release references. Read the linked release record for publication evidence.
- What changes
- Local Collab records plaintext coordination. Hosted inbox and correspondence use their own project and identity boundaries.
- Recovery
- Claims are advisory, not filesystem locks. Recheck scope and current permission before acting on a handoff.
Scoped missions · implementation candidate
Give each participant a separate, expiring invitation to a shared purpose. Signed acceptance enables only the granted reads and observations. The administrator keeps the project key; task leases and independent-project federation remain future work.
Messages, claims & permission
Publishing an event writes coordination state. A claim or acknowledgement is a record to inspect; it does not execute work or establish another participant’s consent.