miscsubjects.com
Evidence review · standard

What Is Model-Operated Work

#oip#kimi-import#self-explaining#voxel#concepts#what-is-model-operated-work
bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `what-is-model-operated-work`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/what-is-model-operated-work

### 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)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/what-is-model-operated-work/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/what-is-model-operated-work/prompts
- **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

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

<!-- hierarchy:nav -->

Path: OIP › Thinker Reference › Protocol Concepts › What Is Model-Operated Work

Shelf: Protocol Concepts · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry

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.
  1. 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.
  1. 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.
  1. 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).
  1. 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

Related on this shelf

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

what-is-model-operated-work · condition map

Evidence map

Hover a node — its path lights up. Click to open the article.

Full map →
20
Protocol Concepts on shelf
Talk to this article
Tap a phone. Ask anything about What Is Model-Operated Work. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

what-is-model-operated-work · condition map

Open evidence map →
What Is Voxel Graphshared topicwhat-is-voxel-graphWhat Is "The URL Is the API"shared topicwhat-is-url-is-apiWhat Is Token Dropshared topicwhat-is-token-dropWhat Is Tap Goshared topicwhat-is-tap-goHow a Model Should Read an OIP Token Dropshared topicmodel-reads-token-dropHolonomic Brain Theory (Bohm-Pribram): Holographic Storage and the Imp…shared topicschool-holonomic-brain-theory-holographic-model-bohm-pribramDiósi–Penrose Model: Gravitational Objective Collapseshared topicschool-di-si-penrose-model-gravitational-objective-collapseAxelrod (1997) The Complexity of Cooperationshared topicpaper-axelrod-r-1997-the-complexity-of-cooperation-agent-based-models-of-competition-a
Ask this article · 2 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

For my medical situation, what can you answer from your catalogue about What Is Model-Operated Work — and what would you need me to tell you first?
ask what-is-model-operated-work condition gaps · paste includes §SELF
What good and bad outcomes are documented for What Is Model-Operated Work (studies vs anecdotes)?
ask what-is-model-operated-work good bad experiences · paste includes §SELF
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →
Loading more articles…