miscsubjectsAI governance
Object Invocation Protocol · protocol specification

OIP system: PSYCH

· · 2 min read

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-system-psych
**This page as JSON:** https://miscsubjects.com/api/articles/oip-system-psych
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-psych/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.

PSYCH

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.

This page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.

Kind: core. Capabilities: 9. Machine system map: /api/dispatch?map=PSYCH&format=markdown. Root: /a/oip.

Operations

PSYCH_READER_V1

The instrument. Reads a corpus of one subject and emits span-cited claim voxels. Never diagnoses, never counsels. Use when: POST /api/psych/run — one instrument, N models, one subject. Arguments: input = the corpus packet built by the psych API.. Human article: /a/oip-capability-psych-reader-v1. Machine doc: ?key=PSYCH_READER_V1&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_READER_V1.

PSYCH_ADVERSARY_V1

The refuter. Attacks one standing claim against the same corpus. Defaults to refuted. Use when: POST /api/psych/challenge. Human article: /a/oip-capability-psych-adversary-v1. Machine doc: ?key=PSYCH_ADVERSARY_V1&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_ADVERSARY_V1.

PSYCH_CONSTRUCT_V1

Criterion-by-criterion coverage of a named construct against the corpus. Not a diagnosis, and says so. Use when: POST /api/psych/run with instrument PSYCH_CONSTRUCT_V1 and vars.construct. Human article: /a/oip-capability-psych-construct-v1. Machine doc: ?key=PSYCH_CONSTRUCT_V1&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_CONSTRUCT_V1.

PSYCH_CONSOLIDATE_V1

Merges near-duplicate standing claims from many runs into one claim carrying every span. Use when: POST /api/psych/consolidate. Human article: /a/oip-capability-psych-consolidate-v1. Machine doc: ?key=PSYCH_CONSOLIDATE_V1&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_CONSOLIDATE_V1.

PSYCH_INGEST

Add corpus entries for one subject. Declared frame and state are owner-supplied, never model-inferred. Arguments: JSON {subject, entries:{title,date,frame,state,substance,text}]}. Human article: [/a/oip-capability-psych-ingest. Machine doc: ?key=PSYCH_INGEST&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_INGEST.

PSYCH_RUN

Run the instrument across N models over a subject corpus. Every emitted quote is server-verified against the stored entry before the claim is kept. Arguments: JSON {subject, instrument, models:], entry_ids:[] or limit}. Human article: [/a/oip-capability-psych-run. Machine doc: ?key=PSYCH_RUN&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_RUN.

PSYCH_CHALLENGE

Send standing claims to the refuter panel. Majority refuted marks the claim refuted. Arguments: JSON {subject, claim_ids:] or all:1, models:[]}. Human article: [/a/oip-capability-psych-challenge. Machine doc: ?key=PSYCH_CHALLENGE&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_CHALLENGE.

PSYCH_PROFILE

The standing picture: claims by dimension with cross-model agreement, challenge outcomes, and every span. Arguments: $1 = subject id.. Human article: /a/oip-capability-psych-profile. Machine doc: ?key=PSYCH_PROFILE&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_PROFILE.

PSYCH_METRICS

Corpus measurements computed in code, not by a model: volume, lexical range, sentence length, register markers, term first-appearance timeline. Arguments: $1 = subject id.. Human article: /a/oip-capability-psych-metrics. Machine doc: ?key=PSYCH_METRICS&format=markdown. Invocation history: /api/invocations?object_id=PSYCH_METRICS.

9
capabilities
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance
1 / 5

Key evidence

5 claims · tier-ranked · API
system
The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.
sources: oip-s3, oip-s4
system
The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.
sources: oip-s1
system
Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.
sources: oip-s2, oip-s3
system
Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.
sources: oip-s2
system
OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.
sources: oip-s2, oip-s5

Latest from the journal

Most recent pieces, site-wide

All articles →
Seven criteria for deciding whether published content is genuinely AI-…posted 2026-08-01what-is-ai-native-contentThe five-model panel never returned a denial, and the cause was three…posted 2026-07-30seat-liveness-recordA model cited clauses 7, 8 and 12 of a three-clause rule set and passe…posted 2026-07-30invented-clause-guardWhat would advance this build, ranked, with the receipt for every item…posted 2026-07-30build-advancement-registerA benefits denial should preserve the evidence, reasons, and exact pat…posted 2026-07-30benefits-eligibility-determination-record

Related articles

Open evidence map →
Oipprotocol rootoipPhilosophy Protocolfoundation protocolphilosophy-protocolPhilosophy Source Documentationsource corpusphilosophy-source-documentationOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curl