miscsubjectsAI governance
Evidence review · protocol

OP — Object Protocol

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:** `op`
- **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/op

### 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/op/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/op/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/op/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/op/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.*

OP — Object Protocol

OP is the common object grammar for discovery, bounded authority, invocation, receipts, replay, repair, provenance, and feedback.

OP was previously named OIP, Object Invocation Protocol. Existing OIP route names, code symbols, directory keys, receipt ids, and federation identifiers remain compatibility aliases. New human and machine roots use OP.

Six invariants

  1. A capability is an object with a readable contract.
  2. Authority is an object scope enforced at the dispatch boundary.
  3. Execution is an object invocation.
  4. Proof is an invocation receipt.
  5. Correction is replay or repair linked to the original receipt.
  6. Feedback is a typed contribution linked to the object it evaluates.

Roots

Human OP root: https://miscsubjects.com/op

Machine OP root: https://miscsubjects.com/api/op

OPOS root: https://miscsubjects.com/opos

Dispatch: https://miscsubjects.com/api/dispatch

Registry: https://miscsubjects.com/api/dispatch?registry=1

Explore this article's relationships

op · condition map

Evidence map

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

Full map →
Ask this article · 2 suggested prompts

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 OP — Object Protocol — and what would you need me to tell you first?
ask op condition gaps · paste includes §SELF
What good and bad outcomes are documented for OP — Object Protocol (studies vs anecdotes)?
ask op good bad experiences · paste includes §SELF
op · posted 2026-07-21 · updated 2026-07-21
Ledger API & provenance
Live ledger · 50 payloads · 10 turns
recent activity · inspect
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 20:29
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 20:14
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 19:59
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 19:44
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 19:28
GUARDIAN_EVENT guardian · HTTP 200 · 2026-07-22 19:13
view full ledger & cards →
REST + ledger
read GET /api/articles/op · GET /api/articles/op?format=post (the editable body)
create/replace POST /api/articles/op · PUT /api/articles/op (replace, keeps revision) · PATCH /api/articles/op (merge)
delete DELETE /api/articles/op
writes need header x-terminal-key
LLM bundle GET /api/articles/op/bundle?format=markdown — body + claims + sources + provenance + manifest
post claim POST /api/protocol/claim · iMessage claim op|tier|assertion
system map GET /api/articles/system-map?format=markdown — root index; every widget self-explains via §SELF / _self
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →
Loading more articles…
Inspect article systemModel discourse, voxel editing, mirror contributions, and machine procedures