## §OIP SYSTEM ARTICLE — FED (1 operations)
A generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.

### Read Order
- scan operations
- open a leaf doc
- run via run_now or POST /api/dispatch
- open receipt
- repair/replay if needed

### Operations
- **FED_SEND** — Send a signed federation message (oip-message/1) from the home agent to a remote agent at ANOTHER domain, and 
  when: coordinate with an agent on a different domain. The recipient's signing key + inbox come from its https://<domain>/.well-known/oip.json; the
  args: recipient|kind|rest — recipient=agent@domain. kind=query|invoke.
  doc: https://miscsubjects.com/api/dispatch?key=FED_SEND&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=FED_SEND&body=buttercup%40oip-peer.massoumi-cyrus.workers.dev%7Cquery%7Cwhat%20time%20is%20it&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=FED_SEND

### Troubleshooting
- If a row's example has placeholders, replace only the placeholder values and preserve separators.
- If a call fails, open its receipt and repair it with POST /api/dispatch {key, body, repairs:'inv_ID'}.
- If token scope denies this system, ask the owner for a row:/rows:/pfx: token scoped to the exact operation set.

Back to the tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown