## §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:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `what-the-build-can-do-on-your-mac-iphone-and-messages`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/bundle?format=markdown

### 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)
- **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
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/voxels
- **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
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### 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.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `what-the-build-can-do-on-your-mac-iphone-and-messages` v2 · content_hash `d5e274c74bd97e7c…` · thread_head genesis
- **thesis (c1):** The Mac reports macOS 26.6.2 when the sw_vers verb is executed through /api/surface/execute.
  - c2 [measured/active] A note named 'miscsubjects proof 2026-09-22' was created in Apple Notes through /api/surface/execute and read back with count 1.
  - c3 [measured/active] A full-screen screenshot of the Mac was written to a file through /api/surface/execute.
  - c4 [measured/active] The paired iPhone answered its lockdown values (iPhone17,2, iOS 26.6.1) through /api/surface/execute.
  - c5 [measured/active] The paired iPhone answered its battery diagnostics (463 cycles) through /api/surface/execute.
  - c6 [measured/active] The iPhone Mirroring window was read as accessibility elements and captured to a file through /api/surface/execute.
  - c7 [measured/active] A text sent from the rented line to the owner's number through /api/text reached status delivered over iMessage.
  - c8 [measured/active] 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.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `what-the-build-can-do-on-your-mac-iphone-and-messages`
- **title:** The build's door on a Mac, an iPhone and Messages: every call it ran, with the answer and the receipt
- **url:** https://miscsubjects.com/a/what-the-build-can-do-on-your-mac-iphone-and-messages
- **register:** plain
- **updated:** 2026-09-23T00:41:19.761Z
- **tags:** surface, iphone, imessage, bridges, proof

## Body

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.

## The Mac is 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](https://miscsubjects.com/receipt/cec741e7-eacc-4176-bac3-41b8ac4ac980).
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](https://miscsubjects.com/receipt/061fa192-c860-4f50-85d6-12ba83aaa3e7).
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](https://miscsubjects.com/receipt/82ca123e-826d-443d-9e16-e9a388511f68).
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](https://miscsubjects.com/receipt/2ec29e81-ff19-40ac-8a16-f945039d3375).
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](https://miscsubjects.com/receipt/8b0ebc43-841b-47d0-8e7c-6f6deca337d2).
6. React. `{action:"react", from:"redacted", to:"+14245134626", reaction:"love"}` put a heart on the latest message of that chat, answered success. Receipt [d2595989](https://miscsubjects.com/receipt/d2595989-f5c1-4c75-8c01-aefc0e56242f).

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

| what | call | answer | receipt |
|---|---|---|---|
| macOS version | `POST /api/surface/execute {id:"v_2992029c22", args:{args:"-productVersion"}}` (sw_vers) | `26.6.2` | [1d56788a](https://miscsubjects.com/receipt/1d56788a-4e4f-4a6c-9732-46086dcf8610) |
| battery | `{id:"v_7d48c913b3", args:{args:"-g batt"}}` (pmset) | AC power, 100%, charged | [8b30d9ab](https://miscsubjects.com/receipt/8b30d9ab-d81d-4ffd-9e5c-f80a1adcb3fa) |
| a preference | `{id:"v_97c5e2df6c", args:{op:"read", key:"tilesize"}}` (defaults, com.apple.dock) | `64` | [d27339d6](https://miscsubjects.com/receipt/d27339d6-9588-4a18-a369-55b458a924f9) |
| the frontmost app and what is running | `{id:"v_c5806c46f4", args:{jxa:"…System Events…"}}` | frontmost Kimi, 138 processes, iPhone Mirroring open, Notes open, Messages open | [880823d2](https://miscsubjects.com/receipt/880823d2-ae56-4e20-a51b-86a9d37dd88e) |
| 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 PNG | [6e6fa584](https://miscsubjects.com/receipt/6e6fa584-efff-4528-a515-0380e4863c04) |
| create a note in Apple Notes | `{id:"v_387bb86491", args:{jxa:"…n.Note({name:'miscsubjects proof 2026-09-22', …})…"}}` | created | [3bb13577](https://miscsubjects.com/receipt/3bb13577-bee1-4b5b-a0e7-bead1b3e21e2) |
| read the note back | same verb, `notes.whose({name:…})` | count 1, id `…/ICNote/p1228`, folder Notes, created 12:50:46 | [310cdebd](https://miscsubjects.com/receipt/310cdebd-32d1-4af9-bf37-62d465c5f666) |

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.

| what | call | answer | receipt |
|---|---|---|---|
| device name | `{id:"v_b7e7234d17"}` (lockdown device-name) | `iPhone` | [7ccc2107](https://miscsubjects.com/receipt/7ccc2107-f515-48c0-9514-72ff71ed1cdc) |
| battery | `{id:"v_9e73e0504c", args:{args:"single"}}` (diagnostics battery) | 463 cycles, 26.4 °C, 3.676 V, design capacity 4630 mAh | [27b3ad3f](https://miscsubjects.com/receipt/27b3ad3f-7a1d-418d-b069-9e2d0e9ce8c1) |
| diagnostics | `{id:"v_a5456bbcd1"}` (diagnostics info) | gas gauge, HDMI unplugged, status Success | [09ed1ee8](https://miscsubjects.com/receipt/09ed1ee8-e3a6-4009-a08a-1e42bb2817ab) |
| every lockdown value | `{id:"v_1310a409bd"}` (lockdown info) | product `iPhone17,2`, iOS `26.6.1`, time zone America/Los_Angeles, activated | [5b6b9034](https://miscsubjects.com/receipt/5b6b9034-cf59-4138-be6a-e26bdbb15d0d) |
| user-installed apps | `{id:"v_6cc20555b0", args:{args:"--userspace"}}` (apps list) | 2 apps: DevUtils, Zoom | [ab0cc9f4](https://miscsubjects.com/receipt/ab0cc9f4-9259-4742-801d-8b558b9b2aee) |
| 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 read | [9431f2ad](https://miscsubjects.com/receipt/9431f2ad-0f83-469c-9745-9e89f651fd3f) |
| 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 781 | [29461ced](https://miscsubjects.com/receipt/29461ced-ae3f-40f8-a5e2-999d8895871a) |
| 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 provide | [ae7b0fc4](https://miscsubjects.com/receipt/ae7b0fc4-f22a-428a-8237-e691156ba796) |

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

| what | call | answer | receipt |
|---|---|---|---|
| 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_c2fdba93ee` | [74a7cd72](https://miscsubjects.com/receipt/74a7cd72-6c0b-4619-909d-645a6128a636) |
| run the chain by id | `POST /api/surface/execute {id:"v_c2fdba93ee"}` | `26.6.2`, AC power 100%, `Kimi`: three steps in 650 ms | [6e582ced](https://miscsubjects.com/receipt/6e582ced-2b0e-451b-82bc-58e8fbd065bd) |
| 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_VERSION` | [a61c6a71](https://miscsubjects.com/receipt/a61c6a71-9e84-44a3-a406-d0605ce46560) |
| call the atom by name from the door every model uses | `POST /api/dispatch {key:"SURFACE_MAC_VERSION"}` | `26.6.2` | [inv_myutgh92gs](https://miscsubjects.com/receipt/inv_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

| what | call | answer | receipt |
|---|---|---|---|
| web search with page contents from the Mac's Starlink line | `POST /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 each | [inv_r0p7ep4qrz](https://miscsubjects.com/receipt/inv_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 ms | [32dd4f4b](https://miscsubjects.com/receipt/32dd4f4b-8fea-4ede-a792-e0f73d244f54) |

## 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).


## Claims (13)

- **c1** [measured w=?] The Mac reports macOS 26.6.2 when the sw_vers verb is executed through /api/surface/execute.
  - sources: s1
- **c2** [measured w=?] 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
- **c3** [measured w=?] A full-screen screenshot of the Mac was written to a file through /api/surface/execute.
  - sources: s3
- **c4** [measured w=?] The paired iPhone answered its lockdown values (iPhone17,2, iOS 26.6.1) through /api/surface/execute.
  - sources: s4
- **c5** [measured w=?] The paired iPhone answered its battery diagnostics (463 cycles) through /api/surface/execute.
  - sources: s5
- **c6** [measured w=?] The iPhone Mirroring window was read as accessibility elements and captured to a file through /api/surface/execute.
  - sources: s6
- **c7** [measured w=?] A text sent from the rented line to the owner's number through /api/text reached status delivered over iMessage.
  - sources: s7
- **c8** [measured w=?] 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
- **c9** [measured w=?] A heart reaction was added to the latest message of a chat through /api/text.
  - sources: s9
- **c10** [measured w=?] A chain of three Mac verbs was composed through /api/surface/compose and run by id, returning all three values.
  - sources: s10
- **c11** [measured w=?] An atom row SURFACE_MAC_VERSION was composed and then called by name through /api/dispatch.
  - sources: s11
- **c12** [measured w=?] WEB_SEARCH ran from the Mac's Starlink line and returned page contents.
  - sources: s12
- **c13** [measured w=?] A headless browser bridge opened a live page and returned its title and links.
  - sources: s13

## Voxel graph (13 atoms · 13 edges)
- full graph: https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (13)
- chain valid: yes · head: `b3f4c031edcc5dad`

### s1 · other
- title: Ledger receipt 1d56788a-4e4
- url: https://miscsubjects.com/receipt/1d56788a-4e4f-4a6c-9732-46086dcf8610
- quote: the build's own ledger row for this call
- hash: `00caa710c2da547a`

### s2 · other
- title: Ledger receipt 310cdebd-32d
- url: https://miscsubjects.com/receipt/310cdebd-32d1-4af9-bf37-62d465c5f666
- quote: the build's own ledger row for this call
- hash: `324efc3a64afd0c4`

### s3 · other
- title: Ledger receipt 6e6fa584-eff
- url: https://miscsubjects.com/receipt/6e6fa584-efff-4528-a515-0380e4863c04
- quote: the build's own ledger row for this call
- hash: `ae51c6a86ac625fd`

### s4 · other
- title: Ledger receipt 5b6b9034-cf5
- url: https://miscsubjects.com/receipt/5b6b9034-cf59-4138-be6a-e26bdbb15d0d
- quote: the build's own ledger row for this call
- hash: `c368ff9399159402`

### s5 · other
- title: Ledger receipt 27b3ad3f-7a1
- url: https://miscsubjects.com/receipt/27b3ad3f-7a1d-418d-b069-9e2d0e9ce8c1
- quote: the build's own ledger row for this call
- hash: `4d004ea8f4ec2b7a`

### s6 · other
- title: Ledger receipt 29461ced-ae3
- url: https://miscsubjects.com/receipt/29461ced-ae3f-40f8-a5e2-999d8895871a
- quote: the build's own ledger row for this call
- hash: `6f204b51f259576b`

### s7 · other
- title: Ledger receipt 061fa192-c86
- url: https://miscsubjects.com/receipt/061fa192-c860-4f50-85d6-12ba83aaa3e7
- quote: the build's own ledger row for this call
- hash: `5856f865215abb7b`

### s8 · other
- title: Ledger receipt 8b0ebc43-841
- url: https://miscsubjects.com/receipt/8b0ebc43-841b-47d0-8e7c-6f6deca337d2
- quote: the build's own ledger row for this call
- hash: `245b85d0644e96d1`

### s9 · other
- title: Ledger receipt d2595989-f5c
- url: https://miscsubjects.com/receipt/d2595989-f5c1-4c75-8c01-aefc0e56242f
- quote: the build's own ledger row for this call
- hash: `2694a0ca6b870460`

### s10 · other
- title: Ledger receipt 6e582ced-2b0
- url: https://miscsubjects.com/receipt/6e582ced-2b0e-451b-82bc-58e8fbd065bd
- quote: the build's own ledger row for this call
- hash: `8b70f08542d672fe`

### s11 · other
- title: Ledger receipt inv_myutgh92
- url: https://miscsubjects.com/receipt/inv_myutgh92gs
- quote: the build's own ledger row for this call
- hash: `e64261188e15938b`

### s12 · other
- title: Ledger receipt inv_r0p7ep4q
- url: https://miscsubjects.com/receipt/inv_r0p7ep4qrz
- quote: the build's own ledger row for this call
- hash: `b8b9613224a3282e`

### s13 · other
- title: Ledger receipt 32dd4f4b-8fe
- url: https://miscsubjects.com/receipt/32dd4f4b-8fea-4ede-a792-e0f73d244f54
- quote: the build's own ledger row for this call
- hash: `b3f4c031edcc5dad`

## Provenance (1 model passes)
- chain valid: yes · head: `4f82300cada14a13`

- write · claude-fable-5.1 · 2026-09-22T20:01 · hash `4f82300cada1`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/what-the-build-can-do-on-your-mac-iphone-and-messages/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"what-the-build-can-do-on-your-mac-iphone-and-messages","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest what-the-build-can-do-on-your-mac-iphone-and-messages|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim what-the-build-can-do-on-your-mac-iphone-and-messages|tier|assertion`
- **iMessage ask:** `what-the-build-can-do-on-your-mac-iphone-and-messages|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §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:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `what-the-build-can-do-on-your-mac-iphone-and-messages`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### 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)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **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
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### 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.*