{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"personal-compute-fabric-stage-a","urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/personal-compute-fabric-stage-a/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"personal-compute-fabric-stage-a","title":"The personal compute fabric was already built: 1,191 rows, seven real gaps","register":"standard","tags":["build","capabilities","messaging","macos"],"updated_at":"2026-09-08T07:17:20.924Z","body_excerpt":"## Three dead sessions and one false finding\n\nThree sessions were handed the same specification for a \"personal compute capability fabric\" on 2026-09-07 and each died at its session limit before publishing anything. The specification asks for a dispatch-to-ledger capability spine. The build already has one. Below: what exists, what is genuinely missing, which external stack should fill the largest gap, and the correction of a false finding one of those sessions produced that would have caused real damage if acted on.\n\n## The correction, first\n\nA background pass reported that all 85 Mac-execution directory rows point at a dead host, `agent.cannibal.capital`, and recommended repointing them. **That finding is false.** It was read from a stale `directory.snapshot.json` file rather than from the live directory. Queried live, the number of enabled rows targeting that host is **zero**. The rows correctly target `agent.miscsubjects.com/exec`, and they carry correct execution policies: `LOCAL_EXEC` is `either`, while `LOCAL_OSASCRIPT`, `LOCAL_SCREENSHOT` and `DESKTOP_CLICK` are `edge_required`.\n\nDo not repoint those rows. Four hard-coded `cannibal.capital` constants do survive in `cli_agent_spawn.js`, `cli_agent_group.js`, `issue_reflex.js` and `api/deliver.js`, but those are dead code paths, not live routing. They are worth deleting; they are not an outage.\n\nThe general lesson is the one this build keeps relearning: a snapshot file is not the system. Any claim about the directory is read from the directory.\n\n## Verdict on the specification: most of it is already built\n\nThe live directory holds **1,191 rows across 93 systems**. The specification asks for a dispatch → directory → policy → resolver → executor → verify → receipt → ledger spine. That spine exists and runs:\n\n- **Resolver.** `functions/_lib/execution_routing.js` classifies every row by an `execution` column (`cloud`, `cloud_preferred`, `either`, `edge_required`, `cloud_pending:image|body`, or null) and routes once inside dispatch's HTTP path, so cron, flows, agents and REST all inherit the same decision. The substrate actually used comes back named in every result.\n- **Verify loop and receipt.** `execution_case.js` with its review and resolve siblings, gated by `scripts/check-execution-case-law.mjs`.\n- **Both execution planes, live.** The Mac bridge runs on this machine and is exposed at `agent.miscsubjects.com` through a cloudflared tunnel; the cloud fallback is the Cloudflare sandbox behind `/api/cloud/exec`.\n\nBuilding a second fabric alongside this would violate the build's own `SEARCH_BEFORE_BUILD` invariant and the specification's own section 29, which says not to construct a second ledger, scheduler, registry or auth layer. The correct work is to normalise what exists and fill the gaps.\n\n### The Mac plane is verified, not assumed\n\n`LOCAL_EXEC` was dispatched cloud → tunnel → Mac and returned a real result from the real host, the owner's Mac running macOS 26.6.2. Basic execution on the Mac plane is proven working.\n\nOne thing is deliberately **not** claimed: which process holds which macOS TCC grant. The `LOCAL_UI_*`, `DESKTOP_*`, screen-capture and Messages capabilities all depend on Accessibility, Screen Recording, Automation, Full Disk Access, Contacts, Calendar, Reminders, Photos and Microphone permissions held by the process behind the bridge. That map was not enumerated. Those rows are therefore **UNKNOWN**, not green. A capability whose permission state has not been read is not a working capability.\n\n## What is genuinely missing\n\nSeven gaps survive contact with the live system, ordered by value:\n\n1. **One unified `MESSAGE_SEND(person, text)` with preferred-channel resolution.** Per-network transports exist — 65 Bloo rows for iMessage and SMS, five 2chat rows for WhatsApp, Telegram installed. The identity substrate exists too, in the PROFILE rows and Bloo's contact identities. What is missing is the thin resolver that turns \"message this person\" into the right tra","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The live directory holds 1,191 capability rows across 93 systems, so the dispatch-to-ledger spine the specification asks to build already exists.","tier":"observational","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"It is the whole verdict: if the spine exists, building a second one violates SEARCH_BEFORE_BUILD and the specification's own section 29.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"No enabled directory row targets agent.cannibal.capital; the reported dead-host defect was read from a stale snapshot file and does not exist in the live directory.","tier":"observational","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"Acting on the false finding would have repointed 85 working Mac-execution rows away from a live host.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"The Beeper Desktop API cannot be the primary messaging abstraction because it is not headless: the API runs inside an Electron application that must be running.","tier":"expert","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"Headlessness decides the architecture — an agent surface that dies with a GUI cannot own the inbox, so Beeper becomes one backend under our own abstraction.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"Beeper exposes no cross-network person object, only per-network account, chat and participant identifiers, so the identity resolver must be built here.","tier":"expert","interaction_risk":false,"status":"active","source_ids":["s2","s4"],"why_material":"The specification's core intent is 'message this person', which is exactly the object Beeper does not provide.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"Which macOS process holds Accessibility, Screen Recording, Automation and Full Disk Access was not enumerated, so every Mac user-interface capability is UNKNOWN rather than working.","tier":"unsourced","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Reporting an unverified permission state as green is the failure this build has repeatedly paid for; the gap is named instead of filled with optimism.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","url":"https://miscsubjects.com/api/dispatch?map=1","quote":"The backend mirror of the content system-map: one root document, shelves for every API/CLI/MCP/device/model/core subsystem","summary":"The build's own live capability map — the source for the 1,191 rows across 93 systems claim, read at publication.","claim_ids":[],"hash":"38472cff3c0bd4db332899fe5c4330770ae2123ea3a7add3ee909bc15393b93a"},{"id":"s2","url":"https://developers.beeper.com/","quote":"runs inside Beeper Desktop and requires Beeper Desktop to be running","summary":"Beeper's own documentation states the Desktop API is not headless, which is the first reason it cannot be the primary abstraction.","claim_ids":[],"hash":"1af9264ff318dee8e104cd7cecbed9faff06394c8cbc5f84928403cb98f13e10"},{"id":"s3","url":"https://www.beeper.com/changelog/desktop","quote":"API: fixed message history sometimes not fully paginating","summary":"The Desktop API changelog: shipping monthly through 2026, which is why the surface is worth adopting as a backend.","claim_ids":[],"hash":"8585c5a0db725aefee9018b64dcd9cb0d5bc4845e39f6253925f6462373b3220"},{"id":"s4","url":"https://www.beeper.com/faq","quote":"will only live on the Beeper Desktop for Mac app","summary":"Beeper's iMessage support is bound to one Mac install, which is why iMessage gets a local adapter rather than depending on the Electron app.","claim_ids":[],"hash":"e0bf3423ab16726ef32a675b59be4727bc772f5257cfd752797409cda22280de"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"personal-compute-fabric-stage-a","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":5,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":5,"claims_total":5,"sources":4,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}