A small, platform-neutral protocol for independent agent sessions. Native thread messages first. A shared Markdown board only when a direct connection does not exist.
Native messaging > Shared Markdown fallback > On-demand bridge
| # | Route | When it applies |
|---|---|---|
| 1 | Native task message — send / read / wait / acknowledge | Always, when the platform supports it |
| 2 | Shared Markdown board — redacted, append-only, manual fallback | Only when direct messaging is absent |
| 3 | Legacy / on-demand bridge — automated bus and service bridge | Stays off unless explicitly approved |
ACK confirms receipt, not completion.
Communication is a delivery layer, not the management system.
01 — Single owner. Every construction task has one accountable owner, a bounded write scope, and a verification route.
02 — Small context. Send one redacted summary and artifact references instead of copying entire conversations between sessions.
03 — No idle loops. One bounded reminder is enough. Completed, paused, archived, and unavailable sessions are not polled.
task_id: docs-014
status: ACK
summary: Received the communication policy update.
next_owner: coordinator
- ACK means received, not finished.
- RESULT needs evidence and acceptance criteria.
- Unavailable sessions are reported, never invented.
- Do not duplicate the same message through both native messaging and the shared board.
- Copy
SKILL.mdinto your assistant's skills directory. - That's it. The protocol is deliberately short — read it once.
- Optional: open
sample.htmlfor a visual overview of the design.
| File | Purpose |
|---|---|
SKILL.md |
The skill itself — protocol, operating rules, privacy |
HANDOFF.md |
Integration notes for agent harnesses |
logo.html |
Canvas logo generator — open in a browser, download as PNG |
sample.html |
Visual one-page overview of the whole design |
The shared board may be visible to every connected sandbox. Never write API keys, passwords, cookies, authorization values, private user data, raw sensitive disclosures, or unnecessary full local paths. Share only a short redacted summary and an artifact reference. A sent message is not proof of delivery.