## §OIP SYSTEM ARTICLE — NOTIFY (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
- **NOTIFY_OWNER** — Text Cyrus (the owner) a message — the "background daemon pings you when it needs a decision" primitive. Autom
  when: the AI needs the owner's input or wants to surface something — "tell Cyrus", "ask the owner", "ping me when X".
  args: message
  doc: https://miscsubjects.com/api/dispatch?key=NOTIFY_OWNER&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=NOTIFY_OWNER&body=A%20customer%20asked%20something%20I%20have%20no%20automation%20for%20%E2%80%94%20how%20do%20you%20want%20me%20to%20reply%3F&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=NOTIFY_OWNER

### 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