Scroll.
Sensors, Shortcuts, Maps, Messages, Safari, Mail. Screen, macOS, Terminal, Browser, Files, Cloud.
One call reaches any of them. Every call leaves a receipt.
Each one opens a page on what it is, and what an assistant can do with it.
Taken apart the same way.
Your sessions, the page, a driver, an agent, a browser that runs in the cloud, and the evidence they leave.
Workspaces, a shell, coding agents, real phones in a data centre, and a token minted for one job.
Each one opens a page on what it is, and what an assistant can do with it.
Roofers, Phoenix. The missed call is the job. Your own number, in blue. Four angles: speed, trust, money, relief.
from: last month's threads · 3 reviews · the price listMade by AI. Directed by a person.
Four angles, three sizes, nine at a time. From the brief, not from a stock library.
9:16 for the story and TikTok, 4:5 for the feed, 1:1 for everything else.
Nothing spends until you say go.
The image and the video from this brief, in the feed.
The phone rings out, the caller gets a text from your number, and it books the job. Your number, not a rented one. Verified on the first call.
The image and the video from the brief. Meta, Instagram, TikTok, Google, taken apart the same way.
Thirty-six renders from one brief, straight into the ad account, paused.
Cut for every placement. Directed by a person.
Audience, budget, launch. Paused until you say go. Reported to a cell, not a screenshot.
Someone texts the number in the ad. Now the lead.
From the ad, from Places, from the licence board, from the site.
Found by AI. Enriched in batch. Scored by rule.
From the record, in your voice, about their actual problem.
iMessage from your number. Email, tracked. WhatsApp, warm only.
Day 2, 5 and 10. The reply lands on your number and the twin takes it from there.
Each one opens a page on what it is and what the system does with it.
You
What the system measured on your request, before any rule ran, read from GET /api/traffic/self. The raw address is used for the hash and the prefix, and is not stored.
One text
The system issues a six-character code to this browser. Sent from your own phone to the line, the message arrives at the same webhook every message arrives at, is matched to the code, answered, and written as an event with an id. The thread on the right fills in as it happens.
Issuing writes a row too: TRAFFIC_FRONT_CODE · mint. Every message on the line is written to the same record shown below.
The record
The Console's Events tab, projected for a stranger at GET /api/ledger/public: the same read model the owner sees, with bodies removed and identifiers masked. Counts are computed at read.
Every feature, running
Each tile is a feature, running in miniature. Hover to watch it. Tap for what it does and what it may touch.
The articles
Every claim bound to a source, or marked as having none. Every revision logged. Any claim disputable on the page it appears on. A model reads the same article as JSON at /api/articles/<slug>.
Tell me which layer you'd hand over first. I'll tell you what it would do by Friday.
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.
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.GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-modelGET https://miscsubjects.com/api/dispatch?explain=1&share=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. GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Floop-safe-miscsubjects.pages.dev%2Farticles%2FC03%7C%7C&share= — the receipt is yours, under your fingerprint GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on recordProtocol 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