miscsubjectsautonomous operating environment
Evidence review · plain

The build's door on a Mac, an iPhone and Messages: every call it ran, with the answer and the receipt

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-the-build-can-do-on-your-mac-iphone-and-messages`
- **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-the-build-can-do-on-your-mac-iphone-and-messages

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

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

The build is the software behind miscsubjects.com: one directory of named capabilities, one door that runs any of them with a key, and one public ledger that writes a receipt for every call. The calls below were made through that door on a Mac, on the iPhone paired to it, and in Messages on 2026-09-22 between 12:50 and 12:58 Pacific time, and each row carries the answer it returned and a link to its receipt: a public ledger row that holds the call, the answer, and the time it ran. reached over a signed channel and holds a verb for every scriptable thing on it

The Mac that runs the build accepts commands from the build through a bridge process, checked by a device-bound token and a per-call signature. On that Mac an encyclopedia of 8,900 verbs was compiled from the machine itself: every scriptable app, every App Intent, every Shortcuts action and trigger, every command-line tool, every preferences domain, every menu of every running app, the paired iPhone's device protocols, the private iMessage verbs, and the build's own rows. A verb has an id and a run block. POST https://ops.miscsubjects.com/api/surface/execute {id, args} runs one. The whole call, nothing hidden, is one JSON object; the key is the value of TERMINAL_KEY in ~/.build-vault.env on the Mac, printed by grep '^TERMINAL_KEY=' ~/.build-vault.env:

json
{"method":"POST","url":"https://ops.miscsubjects.com/api/surface/execute","headers":{"x-terminal-key":"<the TERMINAL_KEY value>","content-type":"application/json"},"body":{"id":"v_2992029c22","args":{"args":"-productVersion"}}}

The same call as a shell command:

bash
curl -sS -X POST https://ops.miscsubjects.com/api/surface/execute -H "x-terminal-key: $(grep '^TERMINAL_KEY=' ~/.build-vault.env | cut -d= -f2)" -H 'content-type: application/json' -d '{"id":"v_2992029c22","args":{"args":"-productVersion"}}'

Every other call below has the same shape: the door's URL, the same two headers, and the body shown in its row. POST /api/surface/compose makes a new verb from existing ones. POST /api/text sends and reads messages from any sender the build holds. POST /api/bridges drives browsers and cloud browser profiles. POST /api/net uses the Mac's internet line. Reads of the contracts are keyless; runs need a key. Every run writes one receipt.

One scenario walked end to end: a text from a rented line reaches the owner's phone, is checked, read back and reacted to

Starting state: the build holds a rented iMessage line, +14245134626, and the owner's own Apple ID aliases. The owner's phone number is +17079135888. Nothing has been sent.

  1. Send. POST /api/text {action:"send", from:"+14245134626", to:"+17079135888", text:"miscsubjects proof 19:50:57Z …"}. The line vendor accepted it and answered a message id, msg_01a0caab-ecbc-770f-b216-f70d1617a676, a chat id, chat_019ec103-256e-7442-b0fc-d0a64a839baf, and status queued, in 5,924 ms. Receipt cec741e7.
  2. Check delivery. {action:"delivery", from:"+14245134626", chat:"chat_019ec103…", message_id:"msg_01a0caab…"} answered status delivered, protocol iMessage, updated 21 seconds after creation. Receipt 061fa192.
  3. Read the conversation back. {action:"history", from:"+14245134626", chat:"chat_019ec103…", limit:2} returned the sent text with direction outbound and status delivered, and the message before it. Receipt 82ca123e.
  4. Send from the owner's own alias to the same rented line. {action:"send", from:"redacted", to:"+14245134626", text:"…"} ran on the Mac's Messages, answered message 679833 and confirmed the alias used. Receipt 2ec29e81.
  5. Read that conversation from the Mac. {action:"history", from:"redacted", chat:"+14245134626", limit:3} showed the rented line's agent had already answered: "Received — your text from the redacted alias landed on the rented line at 19:50Z" (message 679834). Receipt 8b0ebc43.
  6. React. {action:"react", from:"redacted", to:"+14245134626", reaction:"love"} put a heart on the latest message of that chat, answered success. Receipt d2595989.

Cost in time: the six calls took 5.9 s, 1.1 s, 1.6 s, 2.4 s, 1.0 s and 0.3 s. Cost in money: a call on the Mac costs nothing beyond the Mac's power and line; a rented line costs the vendor's monthly fee, a number not measured here. What breaks: on a rented line, delivery and history need chat set to the chat id the send answer returns; without it the vendor answers an invalid-chat error, and the door now says so in its own words. react takes to, not chat. Ending state: one delivered text on the owner's phone from the rented line, one text on the rented line from the owner's alias with the line's automatic reply, and a heart on the last message. Every action's fields are in GET /api/text/discovery, and every operation can be filled in and sent from /build.

The Mac answers reads and performs writes through the same door

whatcallanswerreceipt
macOS versionPOST /api/surface/execute {id:"v_2992029c22", args:{args:"-productVersion"}} (sw_vers)26.6.21d56788a
battery{id:"v_7d48c913b3", args:{args:"-g batt"}} (pmset)AC power, 100%, charged8b30d9ab
a preference{id:"v_97c5e2df6c", args:{op:"read", key:"tilesize"}} (defaults, com.apple.dock)64d27339d6
the frontmost app and what is running{id:"v_c5806c46f4", args:{jxa:"…System Events…"}}frontmost Kimi, 138 processes, iPhone Mirroring open, Notes open, Messages open880823d2
a screenshot of the whole screen to a file{id:"v_619026ea8b", args:{args:"-x /tmp/…/mac-screen.png"}} (screencapture)a 10,417,406-byte PNG6e6fa584
create a note in Apple Notes{id:"v_387bb86491", args:{jxa:"…n.Note({name:'miscsubjects proof 2026-09-22', …})…"}}created3bb13577
read the note backsame verb, notes.whose({name:…})count 1, id …/ICNote/p1228, folder Notes, created 12:50:46310cdebd

The note is in the owner's Notes app.

The paired iPhone answers its device protocols from the Mac without an app on the phone

The iPhone (iPhone 16 Pro Max, iOS 26.6.1, build 23G83) is paired to the Mac over the network. The device verbs run on the Mac and speak Apple's device protocols to the phone.

whatcallanswerreceipt
device name{id:"v_b7e7234d17"} (lockdown device-name)iPhone7ccc2107
battery{id:"v_9e73e0504c", args:{args:"single"}} (diagnostics battery)463 cycles, 26.4 °C, 3.676 V, design capacity 4630 mAh27b3ad3f
diagnostics{id:"v_a5456bbcd1"} (diagnostics info)gas gauge, HDMI unplugged, status Success09ed1ee8
every lockdown value{id:"v_1310a409bd"} (lockdown info)product iPhone17,2, iOS 26.6.1, time zone America/Los_Angeles, activated5b6b9034
user-installed apps{id:"v_6cc20555b0", args:{args:"--userspace"}} (apps list)2 apps: DevUtils, Zoomab0cc9f4
the phone's screen read as elements through the iPhone Mirroring window{id:"v_dad7f69e12", args:{read:true}}the window was open and said "iPhone in Use, lock your iPhone to connect": 5 elements read9431f2ad
the Mirroring window captured to a file{id:"v_dad7f69e12", args:{screenshot:true}}a 253,313-byte PNG of the window at (1356,40), 354 by 78129461ced
a screenshot of the phone over the developer protocol{id:"v_0fc49b9ea7", args:{args:"/tmp/…/phone.png"}}refused: on iOS 17 and later this needs the developer tunnel, a root process on the Mac, which the plain network pairing does not provideae7b0fc4

Beyond reads, the phone verbs install and uninstall apps and profiles, set the device name, turn Wi-Fi on and off, install a Wi-Fi or proxy profile, simulate a location on iOS below 17, post Darwin notifications, list processes, and tap, type and swipe through the iPhone Mirroring window while the phone is locked. The 62 phone-side automation triggers exist as verbs; creating a phone Personal Automation from the door is open work (WT-0444). Shortcuts that sync to the phone compile and import on the Mac, and shortcuts run hangs on this Mac (WT-0442), so they do not fire from it.

Composed tools run like any verb and can be called by name

whatcallanswerreceipt
compose a chain of three Mac verbs (macOS version, battery, frontmost app)POST /api/surface/compose {kind:"chain", name:"Mac status line", steps:[…]}a new verb v_c2fdba93ee74a7cd72
run the chain by idPOST /api/surface/execute {id:"v_c2fdba93ee"}26.6.2, AC power 100%, Kimi: three steps in 650 ms6e582ced
compose an atom, a directory row made from a verb{kind:"atom", key:"MAC_VERSION", id:"v_2992029c22", args_template:{args:"-productVersion"}}row SURFACE_MAC_VERSIONa61c6a71
call the atom by name from the door every model usesPOST /api/dispatch {key:"SURFACE_MAC_VERSION"}26.6.2inv_myutgh92gs

Two further composition kinds exist and were not run, because each one leaves something standing on the Mac or the phone: shortcut (a signed Shortcut imported on the Mac and synced to the phone by iCloud) and automation (a launchd timer that runs a verb on a schedule). A bridge flow (a browser task recorded once and compiled to a BRIDGE_* row) is the third. A scheduled automation is created only on request.

The Mac's internet line and a browser the build drives answer from the same door

whatcallanswerreceipt
web search with page contents from the Mac's Starlink linePOST /api/dispatch {key:"WEB_SEARCH", body:"iPhone 16 Pro Max iOS 26 battery health"}6 results, the top two with 718 characters of page text eachinv_r0p7ep4qrz
register a browser bridge and open a page in it (headless, persistent profile)POST /api/bridges {controller:"browser"} then POST /api/bridges/br_0w3r0c2n6a58/act {action:"goto", url:"https://miscsubjects.com/offer"}title "What we sell", 19 links, page text returned, 5,210 ms32dd4f4b

What the door does, in one list

  • Runs any of the 8,900 Mac and iPhone verbs by id with arguments and returns the answer with a receipt: files, preferences, the objects of every app with a scripting dictionary (notes, mail, calendar, reminders, music, Finder, Terminal), menus of running apps, screenshots, the command line.
  • Reads the paired iPhone over the device protocols and changes what those protocols allow without the developer tunnel; drives its screen through the iPhone Mirroring window while the phone is locked.
  • Sends iMessages from the owner's aliases or the rented lines to any number, reads conversations, reacts, checks delivery, receives inbound through signed webhooks, and puts a model on a line.
  • Makes new tools: chains of verbs, directory rows, Shortcuts, scheduled jobs, recorded browser flows, each one a name any model or script calls.
  • Searches and fetches the web from the Mac's residential line, renders pages in a real browser, keeps browser sessions logged in, drives cloud browser profiles.
  • Gives another person the same: one call mints their key and their own Worker, and one installer makes their own Mac the machine their key runs on (/api/onboard/guide).

What the door does not do from this Mac

  • Take a screenshot of the phone itself over the network pairing; that needs the developer tunnel, a root process.
  • Fire composed Shortcuts or App Intents until the shortcuts run hang is fixed (WT-0442).
  • Use the private iMessage verbs (typing indicators, read receipts, polls, edit, unsend, effects, group management); they need a Mac with System Integrity Protection off (WT-0447).
  • Anything while the Mac is asleep or the bridge is unreachable.
  • Send to anyone as a test; every send listed above went to the owner's own number or the owner's own rented line.

Where each contract is

/api/surface/docs (the surface door, every example runnable), /api/surface/spec (the machine spec and the measured matrix), /api/text/docs and /api/text/discovery (messages), /api/bridges/docs (browsers, profiles, flows), /api/net (the line), /api/onboard/guide (keys, devices, Workers), /build (every operation with its fields), /tools (what a model is handed).

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 13 claims are extracted and stored on the object.
  • sources open 13 sources are registered on the object; each opens from the page.
  • claims bound 13 of 13 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/what-the-build-can-do-on-your-mac-iphone-and-messages/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/what-the-build-can-do-on-your-mac-iphone-and-messages/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

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/what-the-build-can-do-on-your-mac-iphone-and-messages?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/what-the-build-can-do-on-your-mac-iphone-and-messages/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

Evidence · 13 sources · swipe →chain b3f4c031edcc · verify chain · provenance
1 / 13

Key evidence

13 claims · tier-ranked · API
measured
The Mac reports macOS 26.6.2 when the sw_vers verb is executed through /api/surface/execute.
sources: s1
measured
A note named 'miscsubjects proof 2026-09-22' was created in Apple Notes through /api/surface/execute and read back with count 1.
sources: s2
measured
A full-screen screenshot of the Mac was written to a file through /api/surface/execute.
sources: s3
measured
The paired iPhone answered its lockdown values (iPhone17,2, iOS 26.6.1) through /api/surface/execute.
sources: s4
measured
The paired iPhone answered its battery diagnostics (463 cycles) through /api/surface/execute.
sources: s5
measured
The iPhone Mirroring window was read as accessibility elements and captured to a file through /api/surface/execute.
sources: s6
measured
A text sent from the rented line to the owner's number through /api/text reached status delivered over iMessage.
sources: s7
measured
A text sent from the owner's own Apple ID alias through /api/text was answered by the rented line's agent, and the conversation was read back.
sources: s8
measured
A heart reaction was added to the latest message of a chat through /api/text.
sources: s9
measured
A chain of three Mac verbs was composed through /api/surface/compose and run by id, returning all three values.
sources: s10
3 more ranked claims
measured0.10
An atom row SURFACE_MAC_VERSION was composed and then called by name through /api/dispatch.
sources: s11
measured0.10
WEB_SEARCH ran from the Mac's Starlink line and returned page contents.
sources: s12
measured0.10
A headless browser bridge opened a live page and returned its title and links.
sources: s13
Ask this article · 8 suggested prompts

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

What does the ledger say about this (measured tier): "The Mac reports macOS 26.6.2 when the sw_vers verb is executed through /api/surface/execute."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c1 · paste includes §SELF
What does the ledger say about this (measured tier): "A note named 'miscsubjects proof 2026-09-22' was created in Apple Notes through /api/surface/execute and read back with count 1."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c2 · paste includes §SELF
What does the ledger say about this (measured tier): "A full-screen screenshot of the Mac was written to a file through /api/surface/execute."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c3 · paste includes §SELF
What does the ledger say about this (measured tier): "The paired iPhone answered its lockdown values (iPhone17,2, iOS 26.6.1) through /api/surface/execute."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c4 · paste includes §SELF
What does the ledger say about this (measured tier): "The paired iPhone answered its battery diagnostics (463 cycles) through /api/surface/execute."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c5 · paste includes §SELF
What does the ledger say about this (measured tier): "The iPhone Mirroring window was read as accessibility elements and captured to a file through /api/surface/execute."?
ask what-the-build-can-do-on-your-mac-iphone-and-messages claim c6 · paste includes §SELF
What can you answer from your catalogue about The build's door on a Mac, an iPhone and Messages: every call it ran, with the answer and the receipt — and what remains open or unverified?
ask what-the-build-can-do-on-your-mac-iphone-and-messages gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against The build's door on a Mac, an iPhone and Messages: every call it ran, with the answer and the receipt?
ask what-the-build-can-do-on-your-mac-iphone-and-messages objections · paste includes §SELF
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →
⌘ 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%2Fops.miscsubjects.com%2Fa%2Fwhat-the-build-can-do-on-your-mac-iphone-and-messages%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/what-the-build-can-do-on-your-mac-iphone-and-messages/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/what-the-build-can-do-on-your-mac-iphone-and-messages/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