## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `what-is-model-operated-work`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/what-is-model-operated-work/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/what-is-model-operated-work/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/what-is-model-operated-work/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/what-is-model-operated-work/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/what-is-model-operated-work/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/what-is-model-operated-work/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## Article
- **slug:** `what-is-model-operated-work`
- **title:** What Is Model-Operated Work
- **url:** https://miscsubjects.com/a/what-is-model-operated-work
- **register:** standard
- **updated:** 2026-07-15T04:20:59.731Z
- **tags:** oip, kimi-import, self-explaining, voxel, concepts, what-is-model-operated-work

## Body

<!-- hierarchy:nav -->
> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is Model-Operated Work**
>
> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready
> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)

# What Is Model-Operated Work

## §SELF — what-is-model-operated-work

**What this page is:** a definition of model-operated work and how it differs from other forms of automation
**What it explains:** the five defining properties of model-operated work and how it compares to traditional scripting and agent frameworks
**Why read it:** to understand the exact mechanism by which a language model executes work through a protocol, with proof and accountability

### What Model-Operated Work Is

Model-operated work is work performed by a language model operating a system through a protocol. The human names the goal. The model executes. Specifically, the model reads object contracts, decides what to invoke, invokes it, and receives a receipt. The model is the operator; the human is the director.

### Why It Matters

Existing approaches to automation have accountability gaps. Traditional scripts are hardcoded — they cannot adapt to new conditions. Agent frameworks (such as AutoGPT) run without receipts, without proof, and without repair mechanisms. Model-operated work closes these gaps by requiring proof of every action and providing a repair path when things go wrong.

### The Five Key Properties

1. **The model never guesses.** Before invoking anything, the model resolves the object (locates it by key or query), reads the contract (the formal interface specification), and then invokes. The sequence is always: resolve → read → invoke. No step is skipped.

2. **Every action is receipted.** Every invocation produces a permanent, verifiable record (a receipt). The receipt contains: the action that was invoked, the parameters, the timestamp, the result, and a reference to the capability token used. This receipt can be audited later.

3. **Authority is scoped.** The model operates within the bounds of its capability token. The token defines what the model can do, on which objects, until when. The model cannot exceed these bounds. An attempt to do so is rejected by the system.

4. **Errors are repaired.** When an action fails, the failure is not silently logged and forgotten. A repair invocation is created, linked to the original receipt, and executed. The repair is itself receipted. This creates a chain: original action → failure → repair → success (or further repair).

5. **The model is a temporary operator.** The model does not own the system. It is not the administrator. It is the current actor, operating within stated bounds, for the duration of the session or the token expiry. When the session ends, the model's authority ends with it.

### How It Differs from Traditional Automation

Traditional scripts are hardcoded. A script contains a fixed sequence of commands. If the system state changes, the script may fail because it cannot adapt. Model-operated work is adaptive: the model reads the current state (via the object contract) and decides what to do based on that state. The decision is made at runtime, not at write time.

### How It Differs from Agent Frameworks

Agent frameworks (such as AutoGPT, BabyAGI, and similar systems) give a model a goal and let it run autonomously. These frameworks lack three things that model-operated work requires:

- **Receipts:** Agent frameworks typically do not produce a permanent, verifiable record of every action. Model-operated work requires one.
- **Proof:** Without receipts, there is no proof of what the model did. Model-operated work provides proof.
- **Repair:** When an agent framework fails, the failure is logged but not automatically repaired. Model-operated work creates a repair chain.

### How It Connects to Other Ideas

**OIP (Object Interaction Protocol):** Model-operated work is the execution layer of OIP. OIP provides the protocol (the object contracts, the capability tokens, the receipt format). Model-operated work is what happens when a language model uses that protocol to perform tasks.

**Capability-based security:** The scoped authority in model-operated work comes from capability tokens. The model can only do what its token permits. This is the principle of least privilege applied to language model operation.

### Sources

- OIP Specification (Object Interaction Protocol)

---

## Up the tree

- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry
- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map
- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf
- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels
- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)

## Related on this shelf

- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)
- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)
- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)
- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)
- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)
- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)
- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)
- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)

## Machine surfaces

- Public page: `https://miscsubjects.com/a/what-is-model-operated-work`
- JSON article: `https://miscsubjects.com/api/articles/what-is-model-operated-work`
- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20Model-Operated%20Work`


## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/what-is-model-operated-work/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (1 model passes)
- chain valid: yes · head: `26786e787563a694`

- write · kimi-agent-import · 2026-07-15T04:20 · hash `26786e787563`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/what-is-model-operated-work/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/what-is-model-operated-work/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"what-is-model-operated-work","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest what-is-model-operated-work|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim what-is-model-operated-work|tier|assertion`
- **iMessage ask:** `what-is-model-operated-work|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `what-is-model-operated-work`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/what-is-model-operated-work/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/what-is-model-operated-work/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*