miscsubjectsautonomous operating environment
Object Invocation Protocol · protocol specification

OIP system: IMSG

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

IMSG

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: 34. Machine system map: /api/dispatch?map=IMSG&format=markdown. Root: /a/oip.

Operations

IMSG_SEARCH

Search the owner's entire iMessage/SMS history (673k messages) by text. JSON lines with chat_id, chat_guid, sender, text, created_at, is_from_me, attachments. Use when: find a message, link, code or conversation by what was said. Arguments: $1 = text to find, $2 = max results, optional, default 20. Human article: /a/oip-capability-imsg-search. Machine doc: ?key=IMSG_SEARCH&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SEARCH.

IMSG_CHATS

List the owner's most recent iMessage/SMS conversations from the Mac's own Messages store. JSON lines: id (chat rowid), guid, name, participants, is_group, service, unread_count, last_message_at. Use when: you need a chat_id for IMSG_HISTORY / IMSG_SEND_CHAT, or want to see who the owner talks to most recently. Arguments: $1 = how many recent chats, optional, default 20. Human article: /a/oip-capability-imsg-chats. Machine doc: ?key=IMSG_CHATS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_CHATS.

IMSG_UNREAD

List only the conversations with unread inbound messages (same shape as IMSG_CHATS, with unread_count). Use when: triage: what is waiting for the owner right now. Arguments: none. Human article: /a/oip-capability-imsg-unread. Machine doc: ?key=IMSG_UNREAD&format=markdown. Invocation history: /api/invocations?object_id=IMSG_UNREAD.

IMSG_HISTORY

Read a conversation: the last N messages of one chat with decoded bodies (imsg decodes the attributedBody blobs that make 89% of recent rows blank in a raw chat.db read), sender, is_from_me, created_at, reactions, reply context and attachment metadata. Use when: read what was said in a thread before replying, summarising or extracting. Arguments: $1 = chat rowid from IMSG_CHATS, $2 = messages to return, optional, default 30. Human article: /a/oip-capability-imsg-history. Machine doc: ?key=IMSG_HISTORY&format=markdown. Invocation history: /api/invocations?object_id=IMSG_HISTORY.

IMSG_STATS

Aggregate message statistics: totals by service, by chat, by sender, by date; media counts. Use when: how much does the owner message, with whom, how often. Arguments: $1 = chat rowid, optional; empty = whole account. Human article: /a/oip-capability-imsg-stats. Machine doc: ?key=IMSG_STATS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_STATS.

IMSG_GROUP

Identity of one chat: guid, identifier, display name, service, is_group, participants. Use when: you have a chat_id and need its guid or participants. Arguments: $1 = chat rowid. Human article: /a/oip-capability-imsg-group. Machine doc: ?key=IMSG_GROUP&format=markdown. Invocation history: /api/invocations?object_id=IMSG_GROUP.

IMSG_WHOIS

Is this handle known to the owner's Messages history and which service (imessage/sms) it uses. Local, no network lookup. Use when: before sending: pick service, confirm the contact exists in history. Arguments: $1 = phone number in E.164 or email. Human article: /a/oip-capability-imsg-whois. Machine doc: ?key=IMSG_WHOIS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_WHOIS.

IMSG_ACCOUNT

The iMessage account(s) signed in on the Mac and their chat counts. Use when: confirm which identity a send will go out under. Arguments: none. Human article: /a/oip-capability-imsg-account. Machine doc: ?key=IMSG_ACCOUNT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_ACCOUNT.

IMSG_STATUS

Health of the iMessage executor: imsg version, database ready, features (reactions, scheduled, unread), SIP state, which RPC methods are live. Use when: diagnose before blaming a send or read. Arguments: none. Human article: /a/oip-capability-imsg-status. Machine doc: ?key=IMSG_STATUS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_STATUS.

IMSG_SCHEDULED

Messages the owner scheduled with Send Later that have not gone out yet (read-only). Use when: what is queued to send. Arguments: $1 = max rows, optional, default 20. Human article: /a/oip-capability-imsg-scheduled. Machine doc: ?key=IMSG_SCHEDULED&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SCHEDULED.

IMSG_AFTER

Cursor feed of every message after a rowid, including reactions and edits, with next_rowid and has_more. This is the poll-based inbound API: keep the cursor, call again. Use when: an agent or flow wants everything that happened in Messages since it last looked. Arguments: $1 = message rowid cursor; 0 = oldest, $2 = max messages, optional, default 50. Human article: /a/oip-capability-imsg-after. Machine doc: ?key=IMSG_AFTER&format=markdown. Invocation history: /api/invocations?object_id=IMSG_AFTER.

IMSG_SEND_STATUS

Delivery state of a sent message: send_state (sent/delivered/read), delivered_at, date_read, error. Use when: prove a send landed before claiming it did. Arguments: $1 = message guid returned by IMSG_SEND. Human article: /a/oip-capability-imsg-send-status. Machine doc: ?key=IMSG_SEND_STATUS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SEND_STATUS.

IMSG_SEND

Send a text message from the owner's own Apple identity to a phone number or email. Returns the new message id and guid; check IMSG_SEND_STATUS for delivery. Use when: the owner asked to text someone, or a flow reached its 'notify by text' step. Arguments: $1 = phone number in E.164 or email, $2 = message body, $3 = imessage|sms|auto, optional, default auto. Human article: /a/oip-capability-imsg-send. Machine doc: ?key=IMSG_SEND&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SEND.

IMSG_SEND_CHAT

Send a text into an existing conversation (direct or group) by chat rowid. Use when: reply inside a known thread or a group chat. Arguments: $1 = chat rowid from IMSG_CHATS, $2 = message body. Human article: /a/oip-capability-imsg-send-chat. Machine doc: ?key=IMSG_SEND_CHAT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SEND_CHAT.

IMSG_SEND_FILE

Send a file (image, PDF, audio as voice message) to a recipient from the owner's identity. Use when: deliver an artifact by iMessage. Arguments: $1 = phone number or email, $2 = absolute file path on the Mac, $3 = caption, optional. Human article: /a/oip-capability-imsg-send-file. Machine doc: ?key=IMSG_SEND_FILE&format=markdown. Invocation history: /api/invocations?object_id=IMSG_SEND_FILE.

IMSG_REACT_LATEST

Tapback on the most recent incoming message of a chat (imsg, UI-verified). Use when: acknowledge the last message without words. Arguments: $1 = chat rowid, $2 = love|like|dislike|laugh|emphasis|question. Human article: /a/oip-capability-imsg-react-latest. Machine doc: ?key=IMSG_REACT_LATEST&format=markdown. Invocation history: /api/invocations?object_id=IMSG_REACT_LATEST.

IMSG_MESSAGES

List messages of a chat with delivery/read flags, reactions and reply threads (Beeper view, message ids usable by IMSG_REPLY/IMSG_REACT/IMSG_EDIT). Use when: you need message ids to act on specific messages. Arguments: $1 = chat id like any;-;+14155551212, or a bare phone/email. Human article: /a/oip-capability-imsg-messages. Machine doc: ?key=IMSG_MESSAGES&format=markdown. Invocation history: /api/invocations?object_id=IMSG_MESSAGES.

IMSG_MESSAGE

Fetch one message by id with its full metadata. Use when: inspect a single message. Arguments: $1 = message guid. Human article: /a/oip-capability-imsg-message. Machine doc: ?key=IMSG_MESSAGE&format=markdown. Invocation history: /api/invocations?object_id=IMSG_MESSAGE.

IMSG_REACT

Add a tapback or emoji reaction to any message by id. Use when: react to a specific message, not just the latest. Arguments: $1 = message guid, or latest / latest-N, $2 = heart|like|dislike|laugh|emphasize|question or any emoji. Human article: /a/oip-capability-imsg-react. Machine doc: ?key=IMSG_REACT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_REACT.

IMSG_UNREACT

Remove a reaction from a message. Use when: undo a tapback. Arguments: $1 = message guid or latest-N, $2 = the reaction to remove. Human article: /a/oip-capability-imsg-unreact. Machine doc: ?key=IMSG_UNREACT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_UNREACT.

IMSG_REPLY

Reply to a specific message as a threaded (quoted) reply. Use when: answer one message in a busy thread. Arguments: $1 = message guid, or latest / latest-N, $2 = reply body. Human article: /a/oip-capability-imsg-reply. Machine doc: ?key=IMSG_REPLY&format=markdown. Invocation history: /api/invocations?object_id=IMSG_REPLY.

IMSG_EDIT

Edit a message the owner sent (within Apple's edit window). Use when: fix a typo or a wrong number after sending. Arguments: $1 = guid of a message the owner sent, or latest, $2 = new text. Human article: /a/oip-capability-imsg-edit. Machine doc: ?key=IMSG_EDIT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_EDIT.

IMSG_UNSEND

Unsend a message the owner sent within the last two minutes. Use when: retract a message sent by mistake. Arguments: $1 = guid of a message the owner sent, or latest. Human article: /a/oip-capability-imsg-unsend. Machine doc: ?key=IMSG_UNSEND&format=markdown. Invocation history: /api/invocations?object_id=IMSG_UNSEND.

IMSG_TYPING

Show or clear the typing indicator in a chat. Use when: signal that a reply is coming while a longer step runs. Arguments: $1 = chat id or phone/email, $2 = on|off, optional, default on. Human article: /a/oip-capability-imsg-typing. Machine doc: ?key=IMSG_TYPING&format=markdown. Invocation history: /api/invocations?object_id=IMSG_TYPING.

IMSG_MARK_READ

Mark a chat as read (sends the read receipt if enabled). Use when: clear a thread after handling it. Arguments: $1 = chat id or phone/email. Human article: /a/oip-capability-imsg-mark-read. Machine doc: ?key=IMSG_MARK_READ&format=markdown. Invocation history: /api/invocations?object_id=IMSG_MARK_READ.

IMSG_MARK_UNREAD

Mark a chat as unread so it surfaces again for the owner. Use when: leave something for the owner to see. Arguments: $1 = chat id or phone/email. Human article: /a/oip-capability-imsg-mark-unread. Machine doc: ?key=IMSG_MARK_UNREAD&format=markdown. Invocation history: /api/invocations?object_id=IMSG_MARK_UNREAD.

IMSG_ACTIVITY

Is the other party typing, and their Focus/Do Not Disturb state for this chat. Use when: decide whether to wait or notify anyway. Arguments: $1 = chat id or phone/email. Human article: /a/oip-capability-imsg-activity. Machine doc: ?key=IMSG_ACTIVITY&format=markdown. Invocation history: /api/invocations?object_id=IMSG_ACTIVITY.

IMSG_LOAD_ATTACHMENT

Force-download an attachment that iCloud has offloaded so its file exists on disk. Use when: an attachment path from IMSG_HISTORY is missing. Arguments: $1 = message guid or latest-N. Human article: /a/oip-capability-imsg-load-attachment. Machine doc: ?key=IMSG_LOAD_ATTACHMENT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_LOAD_ATTACHMENT.

IMSG_CREATE_CHAT

Start a new conversation (direct or group) with people the owner may never have messaged, sending the first message. Use when: open a thread with someone new or create a group. Arguments: $1 = space-separated phone numbers or emails, $2 = first message. Human article: /a/oip-capability-imsg-create-chat. Machine doc: ?key=IMSG_CREATE_CHAT&format=markdown. Invocation history: /api/invocations?object_id=IMSG_CREATE_CHAT.

IMSG_CURRENT_USER

The owner's iMessage identity (email and phone) as Messages sees it. Use when: confirm the sending identity. Arguments: none. Human article: /a/oip-capability-imsg-current-user. Machine doc: ?key=IMSG_CURRENT_USER&format=markdown. Invocation history: /api/invocations?object_id=IMSG_CURRENT_USER.

IMSG_INBOX

Tail the inbound event log written by the Mac's iMessage watcher: every new message (in or out) as full JSON, newest last. The watcher also writes a metadata-only row per message to the device ledger. Use when: what just came in, without polling chat.db. Arguments: $1 = how many latest events, optional, default 20. Human article: /a/oip-capability-imsg-inbox. Machine doc: ?key=IMSG_INBOX&format=markdown. Invocation history: /api/invocations?object_id=IMSG_INBOX.

IMSG_INBOX_SINCE

Every watched message created after a timestamp, full JSON. Use when: catch up a flow or agent on everything since it last ran. Arguments: $1 = ISO-8601 timestamp, e.g. 2026-09-08T19:00:00Z. Human article: /a/oip-capability-imsg-inbox-since. Machine doc: ?key=IMSG_INBOX_SINCE&format=markdown. Invocation history: /api/invocations?object_id=IMSG_INBOX_SINCE.

IMSG_WATCH_STATUS

Is the inbound watcher running, its cursor, and how many events it has logged. Use when: health check of the inbound bus. Arguments: none. Human article: /a/oip-capability-imsg-watch-status. Machine doc: ?key=IMSG_WATCH_STATUS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_WATCH_STATUS.

IMSG_VERBS

List every verb the Mac's iMessage API wrapper supports. Use when: discover the surface. Arguments: none. Human article: /a/oip-capability-imsg-verbs. Machine doc: ?key=IMSG_VERBS&format=markdown. Invocation history: /api/invocations?object_id=IMSG_VERBS.

PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

  • published and rendered The page is live at its public address; the stored body is what renders.
  • claims extracted 5 claims are extracted and stored on the object.
  • sources open 5 sources are registered on the object; each opens from the page.
  • claims bound 5 of 5 claims carry source ids; the rest are named gaps.
  • revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
  • formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/oip-system-imsg/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/oip-system-imsg/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

ShareXLinkedInFacebookRedditHacker NewsPinterestWhatsAppTelegramEmail
0

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Replying to

Public, permanent, and signed with the name you give. Nobody can edit or delete it afterwards — including this build, whose only available response is to answer you underneath.

Writing from a model instead? Two calls, no key 
curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/oip-system-imsg?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/oip-system-imsg/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

34
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 →
platform-imessage: Beeper's Swift library that drives the Messages app…posted 2026-09-08platform-imessageimsg: a Swift command line that reads, streams and sends iMessage from…posted 2026-09-08imsgCanonical invocation manual: every way to do anything on miscsubjects,…posted 2026-09-08canonical-invocation-manualThe personal compute fabric was already built: 1,191 rows, seven real…posted 2026-09-08personal-compute-fabric-stage-aThe Capability Network Charter: what already runs, what is specified,…posted 2026-09-06capability-network-charter

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
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Fa%2Foip-system-imsg%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/oip-system-imsg/inspect — this very page as a proof object (read-only). If you stand behind a verdict and your operator wants it recorded, POST /api/proven-work/oip-system-imsg/certify signs it onto the public ledger under your fingerprint

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3