miscsubjectsAI governance
Object Invocation Protocol · protocol specification

C07: Feedback, Cybernetics, and Homeostasis

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-c07-feedback-cybernetics
**This page as JSON:** https://miscsubjects.com/api/articles/oip-c07-feedback-cybernetics
**Machine bundle:** https://miscsubjects.com/api/articles/oip-c07-feedback-cybernetics/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

A system senses its output and corrects. Sources: Wiener (cybernetics); Ashby (requisite variety, ultrastability); Bernard, Cannon (homeostasis); control theory; Powers (perceptual control). Domains: physiology, engineering, ecology, economics, governance. Dual: open-loop / runaway. Tier: T1. Falsifier: a stable adaptive system with no feedback channel. Maps: A₁₂ (recursion), A₃.

---

Corpus map

Key evidence

4 claims · tier-ranked · API
mechanistic
A system senses its output and corrects.
mechanistic
The dual of feedback / cybernetics / homeostasis is open-loop or runaway.
mechanistic
A falsifier for feedback / cybernetics / homeostasis is a stable adaptive system with no feedback channel.
mechanistic
Feedback / cybernetics / homeostasis maps to A₁₂ (recursion) and A₃.
Model review1 contributions · 1 modelExpand the recursive review layer
1 / 1
grok/grok-4.3atomizer
atomize2026-07-07 08:32
atomize · 4 claims
inspect — what it was prompted & output
prompted with
You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.

ALWAYS:
- Extract every material assertion as one atomic claim, tied to the ## section it came from.
- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.
- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.
- Prefer fewer, harder claims over many soft ones.

NEVER:
- Never rewrite, summarize, or output the body.
- Never invent a URL, quote, or publication.
- Never duplicate an existing claim text.

input: atomize oip-c07-feedback-cybernetics
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "A system senses its output and corrects.",
      "section": "## 3.7 Feedback / cybernetics / homeostasis",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Core definition of the feedback mechanism central to the node."
    },
    {
      "id": "c2",
      "text": "The dual of feedback / cybernetics / homeostasis is open-loop or runaway.",
      "section": "## 3.7 Feedback / cybernetics / homeostasis",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Explicit contrast property stated for the concept."
    },
    {
      "id": "c3",
      "text": "A falsifier for feedback / cybernetics / homeostasis is a stable adaptive system with no feedback channel.",
      "section": "## 3.7 Feedback / cybernetics / homeostasis",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Test criterion provided for the concept."
    },
    {
      "id": "c4",
      "text": "Feedback / cybernetics / homeostasis maps to A₁₂ (recursion) and A₃.",
      "section": "## 3.7 Feedback / cybernetics / homeostasis",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Explicit mapping relation stated for the node.
4eba2c20be6446e8
Machine verification: /api/articles/oip-c07-feedback-cybernetics/contributions
oip-c07-feedback-cybernetics · posted 2026-07-04 · updated 2026-07-17 · 3 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 6 model passes · 4141 tokens · $0 · 4 models
chain head 7e74a02d6ffcf6ef
restore claude-fable-5 · 2026-07-04 03:32 · tokens unrecorded · f3e897f9ce9d
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · bce6356d743b
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · 1092440c58ab
atomize grok/grok-4.3 · 2026-07-07 08:32 · 4141 tok · 50a3cbfd8414
score scorer · 2026-07-07 08:32 · tokens unrecorded · e000d8bb6716
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 7e74a02d6ffc
verify chain →
Live ledger · 22 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 13:18
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 08:56
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 05:04
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 21:01
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 20:27
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 18:52
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}