## §OIP SYSTEM ARTICLE — OWNER (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
- **OWNER_REPORT** — Send a report to the owner and prove it arrived. Returns the inbound ledger row id that witnessed the message 
  when: every report, inventory, digest or answer addressed to the owner. Use EMAIL_SEND_TRACKED for outreach to third parties instead.
  args: $1 = subject (the [OWNER REPORT] prefix is added). $2 = body text. $3 = seconds to wait for the ledger row (default 30, max 60; observed round trip is about 25s).
  doc: https://miscsubjects.com/api/dispatch?key=OWNER_REPORT&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=OWNER_REPORT&body=six%20tasks%20closed%2C%20both%20articles%20live%7CLinks%20first%3A%20https%3A%2F%2Fmiscsubjects.com%2Fa%2Ftesofensine%20...&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=OWNER_REPORT

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