## §OIP SYSTEM ARTICLE — WORK (2 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
- **WORK_FEED** — The shared work thread. THE FIRST THING ANY MODEL OR TOKEN-HOLDER READS. Aggregates the top priority, open tas
  when: at the start of ANY session, or when asked 'what should I work on', 'what is the state', 'catch me up', 'where are we'.
  args: $1 = how many recent thread entries (default 15).
  doc: https://miscsubjects.com/api/dispatch?key=WORK_FEED&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=WORK_FEED&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=WORK_FEED
- **WORK_APPEND** — Append one entry to the shared append-only work thread. This is how every model records what it did, proposed,
  when: after you do, propose, or audit anything. Always append.
  args: $1 = your model/agent name, $2 = kind (note|edit|proposal|audit|question|done), $3 = your entry. Prefix body with 'ref:task:12' or 'ref:lead:49' or 'ref:gh:7' to link it.
  doc: https://miscsubjects.com/api/dispatch?key=WORK_APPEND&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=WORK_APPEND&body=grok-web%7Cproposal%7Cref%3Atask%3A4032%20send%2050%20outreach%20emails%2Fday%20to%20start%2C%20ramp%20weekly&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=WORK_APPEND

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