Cross-domain coordination repo

This memo introduces a new home for cross-domain coordination and supersedes the four 2026-04-27-memo-system-introduction.md memos that were filed earlier today under platform/memos/. Same authors, same intent, different shape.

What changed

The previous design put memos/in/ and memos/out/ inside the Platform repo and routed memos through from_<team>/ and to_<team>/ directories. Two problems with that, both visible only after a few days of use.

It privileged Platform as the hub. Every cross-domain memo was modeled as Platform-to-domain or domain-to-Platform. Real correspondence does not run through Platform — Operations writes to Sales about scheduling capacity, Revenue writes to Operations about ledger reconciliation, Growth writes to Sales about lead-qualification thresholds. Platform is a domain like any other, not a switchboard.

It encoded routing in the directory tree. A memo with multiple addressees had no clean home. A memo whose recipient changed needed a rename. A reply to a memo had to live in a different folder than the parent.

The new repo, coordination, fixes both. It is org-scoped, not Platform-scoped, and it stores routing in frontmatter rather than directories. Memos live flat under memos/<year>/. Threading is by reference: a reply is a sibling file with in-reply-to pointing at its parent.

Where it lives

github.com/sguild-admin/coordination, mounted locally at the path you would expect. The README.md covers filing, naming, and where to look. The CONVENTIONS.md is the frontmatter spec.

The platform/memos/ folder is now a stub pointing at the new repo. The four intro memos and the inbound from Revenue have been migrated. No links in any ADR have changed (no ADR currently references /memos/).

What this means for you

When you sit down to work in your domain, your first command is now to scan coordination/INDEX.md for memos addressed to you with status: open. The indexer will be regenerated on every push, so the index is reliable.

When you file a memo, copy templates/new-memo.md, set to: to whichever domains need to read it, and open a PR in coordination. There is no Platform-fanout step anymore — addressing is direct.

When you reply, copy templates/response.md, set in-reply-to to the parent's id, and thread to the root memo's id. The reply is a sibling file in the same year folder.

status values are open, responded, closed, fyi, superseded. See CONVENTIONS.md for what each means.

What is not changing

The substance of what belongs in a memo is the same. Architectural changes, contract version bumps, schema migrations that cross domain boundaries, identity model adjustments, ledger reconciliation rules. Day-to-day coordination still happens in chat. Operational fire drills still happen in chat. The bar for filing a memo is "this requires another team to read code, change code, or update a contract version."

The expectation that you read your inbound memos before writing code in a domain is also unchanged. The directory has moved; the discipline has not.

First action

No response needed. Read the new repo's README.md and CONVENTIONS.md, file your next cross-domain memo there instead of platform/memos/, and let me know via a memo (in coordination, naturally) if anything in the conventions needs to change.

References

• coordination/README.md and coordination/CONVENTIONS.md — repo-level docs.
• 2026-04-27-platform-memo-system-introduction — the superseded intro memos, preserved for the audit trail.
• 2026-04-27-revenue-schema-management — first inbound memo migrated to the new home.