{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"cloudflare-os-email","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle?format=markdown"},"how_to_use":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","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/cloudflare-os-email/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":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-email/topology"}},{"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/cloudflare-os-email/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"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/cloudflare-os-email/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-email/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"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":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"MASTHEAD":{"sorry_status":"planes not merged yet — sorry-status activates after voxel-merge-planes","identity":{"slug":"cloudflare-os-email","version":3,"content_hash":"ad3c264a9b19df0eba4fbae2aefb610186e5789f122fcf7924468d7844227d35","thread_head":"genesis","divs":null},"thesis":{"root_claim":"c1","text":"Cloudflare email comprises separate inbound forwarding, inbound code processing, and outbound transactional sending surfaces with different prerequisites.","tier":"system"},"load_bearing":[{"id":"c2","tier":"system","status":"active","text":"Arbitrary-recipient sending requires Workers Paid; verified-destination sends are free, and paid accounts include 3,000 outbound messages per month before $0.35"},{"id":"c3","tier":"system","status":"active","text":"Email Routing and Email Sending onboard separately and publish different root-domain and cf-bounce DNS records."},{"id":"c4","tier":"system","status":"active","text":"A routing rule aimed at an address stays disabled until that destination address is verified."},{"id":"c5","tier":"system","status":"active","text":"An Email Worker can parse an inbound MIME stream, store its attachments in R2, and forward to a verified destination."},{"id":"c6","tier":"system","status":"active","text":"The raw message stream must be consumed once or buffered before multiple consumers inspect it."},{"id":"c7","tier":"system","status":"active","text":"Reply and forward are constrained inbound actions; forwarding requires verified destinations and replies fail above 100 References entries."},{"id":"c8","tier":"system","status":"active","text":"Sending to arbitrary recipients requires an onboarded sending domain, Workers Paid, a send_email binding, an aligned from-domain, and compliance with message li"}],"standing_objections":{"open":0,"strongest_open":null,"link":"https://miscsubjects.com/api/articles/cloudflare-os-email/discourse"},"verbs":{"read":"GET https://miscsubjects.com/api/articles/cloudflare-os-email/voxels — DIVs + hashes + chains (free)","read_claims":"GET https://miscsubjects.com/api/articles/cloudflare-os-email/claims — every formal claim as claim:<id> with current hash, thread, stable link, and exact contribution/edit bodies","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {slug, expected_thread_head, target_div?, expected_hash?, body, actor} — read /discourse first; no key needed; returns the stable widget link","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {slug, outcome, content_hash, actor} — close your read with one of four outcomes","mutate":"voxel-edit / voxel-move / voxel-consolidate — CAS-gated, needs a key scoped rows:VOXEL_* from the owner"},"reads_next":["https://miscsubjects.com/a/philosophy","https://miscsubjects.com/api/articles/cloudflare-os-email/discourse","https://miscsubjects.com/api/protocol"]},"bundle_version":1,"generated_at":"2026-07-29T20:09:48.078Z","slug":"cloudflare-os-email","title":"Cloudflare email is three products, not one mail stack","url":"https://miscsubjects.com/a/cloudflare-os-email","register":"technical","tags":["cloudflare","architecture","email","cloudflare-os"],"posted_at":"2026-07-26T06:16:48.370Z","updated_at":"2026-07-26T06:23:25.501Z","body":"# Cloudflare email is three products, not one mail stack\n\nCloudflare can forward inbound mail, run code on it, and send transactional mail. Each capability has a different setup gate. A verified forwarding address is not an onboarded sending domain.\n\n| Product surface | Direction | What it does | Prerequisite | What it does not replace |\n| --- | --- | --- | --- | --- |\n| Email Routing | Inbound | Maps an address or catch-all to a verified destination or Worker | Domain onboarded for routing; routing MX, SPF, and DKIM records | A mailbox, outbound sender, campaign system |\n| Email Workers | Inbound, plus constrained reply/forward | Runs an `email()` handler over the raw message | Active route bound to a deployed Worker; destinations verified before forwarding | General arbitrary outbound on the free plan |\n| Email Service / Email Sending | Outbound | Sends transactional mail through a Worker binding, REST, or SMTP | Sending domain onboarded; Paid plan for arbitrary recipients; `send_email` binding for Workers | Marketing automation, customer subaccounts, full ESP operations |\n\nVerified destinations are free on every plan; arbitrary recipients require Workers Paid. Paid includes 3,000 outbound messages per account each month, then costs $0.35 per 1,000. Inbound is unlimited, although processing consumes Worker resources.\n\n[[embed:source:s1]]\n\n## Evidence status\n\n**Observed** marks first-party measurements or runtime receipts from the named environment.\n**Derived** marks arithmetic calculated from cited inputs. **Specified** marks vendor or standards\ndocumentation. **Implemented** and **deployed** name code and live-state evidence, respectively.\n**Reproduced** means the stated procedure was rerun. **Externally attested** marks operator reports;\nthose reports show that an experience occurred, not that it is universal.\n\n## The setup begins with DNS, not code\n\nFor inbound routing, the dashboard path is:\n\n`Cloudflare dashboard → account → Compute → Email Service → Email Routing → Onboard Domain`\n\nFor `example.com`, Cloudflare creates this root-domain shape:\n\n```txt\nMX  @  route1.mx.cloudflare.net\nMX  @  route2.mx.cloudflare.net\nMX  @  route3.mx.cloudflare.net\nTXT @  \"v=spf1 include:_spf.mx.cloudflare.net ~all\"\nTXT cf2024-1._domainkey  \"v=DKIM1; h=sha256; k=rsa; p=<Cloudflare public key>\"\n```\n\nCloudflare assigns MX priorities. Merge the Cloudflare `include:` into an existing SPF record; two SPF records are invalid, and SPF has a ten-lookup ceiling.\n\n[[embed:source:s2]]\n\nFor outbound Email Sending, onboarding is separate:\n\n`Cloudflare dashboard → account → Compute → Email Service → Email Sending → Onboard Domain`\n\nThe outbound records live under `cf-bounce.example.com`, leaving the inbound root MX records alone:\n\n```txt\nMX  cf-bounce  route1.mx.cloudflare.net\nMX  cf-bounce  route2.mx.cloudflare.net\nMX  cf-bounce  route3.mx.cloudflare.net\nTXT cf-bounce  \"v=spf1 include:_spf.mx.cloudflare.net ~all\"\nTXT cf-bounce._domainkey  \"v=DKIM1; h=sha256; k=rsa; p=<Cloudflare public key>\"\nTXT _dmarc  \"v=DMARC1; p=none; rua=mailto:dmarc@example.com\"\n```\n\nCloudflare says DNS commonly settles in 5–15 minutes but can take up to 24 hours. The practical gate is that the Email Sending screen shows the domain onboarded and DNS queries return the records. Start DMARC at `p=none` if other providers still send for the domain; enforce only after their identities align.\n\n[[embed:source:s3]]\n\n## Routing rules, verified destinations, and the catch-all\n\nForwarding requires a destination address that the recipient has verified. The dashboard path is:\n\n`Compute → Email Service → Email Routing → Destination Addresses`\n\nCloudflare emails that address a verification link. A routing rule pointing at an unverified destination remains disabled. Once verified, create a rule under:\n\n`Compute → Email Service → Email Routing → Routing Rules → Create routing rule`\n\nThe action is send to a verified address, send to a Worker, or drop. If two rules use the same pattern, only the first processes the message. Renaming a Worker breaks routes that point to its old name.\n\n[[embed:source:s4]]\n\nThe catch-all is a separate rule on the Routing Rules screen. Turn it on, choose **Send to a Worker**, select the deployed Worker, and save. It catches every otherwise-unmatched local part, so add size checks, sender policy, and retention.\n\n| Intent | Route | Destination |\n| --- | --- | --- |\n| Ordinary inbox alias | `hello@example.com` | Verified personal or team inbox |\n| Support ingestion | `support@example.com` | Email Worker |\n| Per-customer intake | `inbox+customer-id@example.com` | Email Worker with subaddressing enabled |\n| Any unmatched local part | Catch-all | Worker, then explicit allow/reject logic |\n| Address that should appear valid but retain nothing | Named rule | Drop |\n\nWith subaddressing enabled, `inbox+acme@example.com` matches `inbox@example.com` while preserving `+acme` in `message.to`.\n\n## A runnable inbound Worker that parses MIME and stores attachments\n\nThe useful inbound architecture is short:\n\n`Cloudflare MX → Email Routing catch-all → email() handler → postal-mime → R2 objects + application record`\n\nInstall `postal-mime`, bind an R2 bucket, and deploy the Worker:\n\n```bash\nnpm install postal-mime\nnpx wrangler r2 bucket create inbound-attachments\nnpx wrangler deploy\n```\n\n```jsonc\n{\n  \"name\": \"inbound-mail\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2026-07-01\",\n  \"r2_buckets\": [\n    { \"binding\": \"ATTACHMENTS\", \"bucket_name\": \"inbound-attachments\" }\n  ]\n}\n```\n\n```ts\nimport PostalMime from \"postal-mime\";\n\ninterface Env {\n  ATTACHMENTS: R2Bucket;\n  FORWARD_TO: string;\n}\n\nfunction safeName(name: string): string {\n  return name.replace(/[^a-zA-Z0-9._-]/g, \"_\").slice(0, 180);\n}\n\nexport default {\n  async email(message: ForwardableEmailMessage, env: Env): Promise<void> {\n    if (message.rawSize > 25 * 1024 * 1024) {\n      message.setReject(\"Message exceeds the 25 MiB inbound limit\");\n      return;\n    }\n\n    const parsed = await PostalMime.parse(message.raw);\n    const received = new Date().toISOString();\n    const mailId = crypto.randomUUID();\n\n    for (const [index, attachment] of (parsed.attachments || []).entries()) {\n      const filename = safeName(attachment.filename || `attachment-${index}`);\n      const key = `mail/${received.slice(0, 10)}/${mailId}/${filename}`;\n\n      await env.ATTACHMENTS.put(key, attachment.content, {\n        httpMetadata: {\n          contentType: attachment.mimeType || \"application/octet-stream\"\n        },\n        customMetadata: {\n          envelopeFrom: message.from,\n          envelopeTo: message.to,\n          subject: (parsed.subject || \"\").slice(0, 500)\n        }\n      });\n    }\n\n    await message.forward(env.FORWARD_TO);\n  }\n} satisfies ExportedHandler<Env>;\n```\n\n`message.raw` is a single stream. If two consumers need it, buffer once with `new Response(message.raw).arrayBuffer()`. The handler also exposes envelope addresses, headers, size, `setReject()`, `forward()`, and `reply()`.\n\n[[embed:source:s5]]\n\n`postal-mime` handles multipart boundaries, encodings, and character sets. Treat filenames and MIME types as untrusted. Generate the key, cap size, and scan before serving.\n\n[[embed:source:s6]]\n\nOne operator reports: “I’m using Cloudflare Email Routing with a catch-all address that triggers a Worker. The Worker parses the email and stores the attachments in R2.” It is one working implementation, not a universal guarantee.\n\n[[embed:source:s7]]\n\nFor the storage half, see [R2 cuts a 10 TB delivery bill from $923 to $18.45](/a/cloudflare-os-r2). That chapter covers binding calls, public versus private objects, versioning gaps, and cost.\n\n## Replying is not the same as arbitrary sending\n\nThe inbound message object can forward to verified routing destinations. It can also reply with a raw `EmailMessage` constructed from `cloudflare:email`:\n\n```ts\nimport { EmailMessage } from \"cloudflare:email\";\nimport { createMimeMessage } from \"mimetext\";\n\nexport default {\n  async email(message: ForwardableEmailMessage): Promise<void> {\n    const msg = createMimeMessage();\n    msg.setSender({ name: \"Example support\", addr: \"support@example.com\" });\n    msg.setRecipient(message.from);\n    msg.setSubject(\"Re: \" + (message.headers.get(\"subject\") || \"your message\"));\n    msg.addMessage({\n      contentType: \"text/plain\",\n      data: \"We received your message.\"\n    });\n\n    const reply = new EmailMessage(\n      \"support@example.com\",\n      message.from,\n      msg.asRaw()\n    );\n    await message.reply(reply);\n  }\n};\n```\n\nThis is tied to the inbound message. `message.reply()` throws above 100 `References` entries, and forwarding destinations must be verified.\n\n[[embed:source:s8]]\n\n## New outbound mail uses Email Service\n\nAfter onboarding, bind Email Service to a paid Worker:\n\n```jsonc\n{\n  \"send_email\": [\n    { \"name\": \"EMAIL\" }\n  ]\n}\n```\n\nCall `env.EMAIL.send()` with an onboarded-domain `from`, recipient objects, subject, text, and HTML.\n\nThe prerequisite chain is:\n\n1. The zone is in the Cloudflare account.\n2. Email Sending shows the domain as onboarded.\n3. The `cf-bounce` MX, SPF, DKIM, and DMARC records resolve.\n4. The Worker is on Workers Paid for arbitrary recipients.\n5. The Worker has a `send_email` binding and uses the onboarded domain in `from`.\n6. The message stays inside recipient, header, and size limits.\n\nBefore onboarding, sends are limited to verified destinations and routing domains. After onboarding, arbitrary recipients are allowed, subject to daily quota and reputation. New accounts start with a conservative quota that Cloudflare adjusts over time rather than publishing one universal number.\n\n[[embed:source:s9]]\n\nCurrent limits include 50 combined recipients, 998 subject characters, 16 KB of custom headers, and 5 MiB total. Verified-destination mail may be 25 MiB. A zone may have 30 combined Routing and Sending domains; Routing allows 200 rules per domain and 200 verified destinations per account.\n\n## The site's own split proves why the prerequisite must be visible\n\nThis build has a Pages endpoint at `POST /api/email/send`. It authenticates the owner, then proxies the body to a sibling Worker because Pages cannot carry the `send_email` binding. The sibling declares:\n\n```toml\n[[send_email]]\nname = \"EMAIL\"\n```\n\nThe public diagnostic response currently says:\n\n```json\n{\n  \"inbound\": {\n    \"loop@miscsubjects.com\": \"forward → cyrus@dsco.co\",\n    \"build@miscsubjects.com\": \"worker → ledger + forward\"\n  },\n  \"sending\": \"Enable Email Sending on miscsubjects.com in CF dashboard (Pages cannot bind send_email)\"\n}\n```\n\nCode and a binding are not proof of a send-capable domain. The prerequisite remains open until onboarding and an observed delivery receipt.\n\n[[embed:source:s10]]\n\nOn July 26, 2026, `miscsubjects.com` resolved three Cloudflare routing MX records, root SPF, `cf2024-1` DKIM, and DMARC `p=reject`. The sending selector also returned a key, but DNS alone does not prove onboarding or delivery. No email was sent.\n\n[[embed:source:s11]]\n\n## SPF, DKIM, DMARC, and ARC in plain language\n\n| Mechanism | What it asserts | What forwarding changes |\n| --- | --- | --- |\n| SPF | The connecting server is authorized for the envelope sender's domain | A forwarder connects from a new IP, so the original SPF relationship can break |\n| DKIM | A domain signed selected headers and body bytes with a key published in DNS | It can survive forwarding if the signed bytes remain intact |\n| DMARC | The visible `From:` domain must align with a passing SPF or DKIM identity, then applies a policy | Forwarding can disturb SPF; mailing-list or gateway modifications can disturb DKIM |\n| ARC | Intermediaries preserve a signed chain of the authentication result they observed | A destination can evaluate the forwarder's attestation when direct SPF or DKIM no longer tells the whole story |\n\nCloudflare uses Sender Rewriting Scheme, changing the envelope sender so SPF can pass from its relay while leaving visible `From:` unchanged. Routing adds DKIM, and ARC preserves authentication results through the forwarding hop.\n\n[[embed:source:s12]]\n\nARC is evidence, not an override switch. The final provider still applies its own reputation, block-list, policy, and content decisions. A message can authenticate and still be rejected or placed in spam.\n\n## The Outlook reports are real, but they are not a universal result\n\nTwo independent operator reports describe Microsoft blocking Cloudflare Email Routing IP ranges. Handy-Man writes that Outlook “just blocks Cloudflare IP ranges and emails never get routed to my Outlook mail box.”\n\n[[embed:source:s13]]\n\nIn a separate discussion, doubled112 reports that Microsoft “intermittently block Cloudflare email routing IPs too,” despite the surrounding SPF, DKIM, and DMARC work.\n\n[[embed:source:s14]]\n\nA third independent account documents Outlook failures through Cloudflare routing.\n\n[[embed:source:s15]]\n\nThese reports establish a failure mode, not prevalence. Shared relays can inherit reputation from other traffic. Authentication improves identity evidence; it does not require a provider to accept an IP.\n\nWhen forwarded mail disappears, inspect the Email Routing activity log first. Separate these cases:\n\n| Symptom | Likely cause | Check | Fix |\n| --- | --- | --- | --- |\n| Rule is disabled | Destination never verified | Destination Addresses status | Resend verification and activate the rule |\n| No routing event | MX or rule mismatch | `dig MX`, rule order, exact recipient | Finish onboarding; repair the pattern |\n| Worker invocation failed | CPU, memory, exception, or renamed Worker | Workers logs; route target | Fix the exception or rebind the renamed Worker |\n| Forward call rejects | Destination is not verified | Destination list and Worker log | Verify the exact address before forwarding |\n| Routing says delivered, inbox has nothing | Destination provider rejected, deferred, or filtered it | Routing activity, SMTP response, spam/quarantine | Test another verified destination; give Cloudflare the event and SMTP evidence |\n| Sending call succeeds but Routing summary says “dropped” | Outbound Worker mail is shown that way in Routing | Email Sending metrics and logs | Use Email Sending observability, not the Routing label |\n| Local attachment test throws `Cannot serialize value: [object ArrayBuffer]` | Local runtime limitation | Reproduce on deployed Worker | Test binary attachments against the deployed Worker |\n| Reply throws on a long thread | More than 100 References entries | Count `References` values | Start a new message or trim the reply path |\n\nCloudflare warns about multiple SPF records, missing selectors, alignment, new-domain reputation, bounces, and provider filtering. Binary attachments can also hit a local ArrayBuffer serialization limit even when deployment works.\n\n[[embed:source:s16]]\n\nOne developer followed the `cloudflare:email` and `EmailMessage` path, verified an address, and reported no arrival or error. The unanswered report cannot establish cause. It does show why a resolved Promise is not delivery proof. Check destination verification, onboarding, Email Sending logs, spam, quarantine, and SMTP events.\n\n[[embed:source:s17]]\n\n## Where Cloudflare Email Service still is not SendGrid\n\nTransactional sending is not the whole ESP product.\n\nOne SendGrid operator creates subaccounts by API so customers can verify their own domains with DKIM and SPF. Cloudflare's documented flow onboards zones from its account; it does not document an equivalent delegated subaccount system. Do not promise one without a specific API and proof.\n\n[[embed:source:s18]]\n\nThe gaps are operational: durable bounce handling, suppression recovery, versioned templates, tenant analytics, and marketing consent or unsubscribe controls. Conservative daily quotas, reputation scaling, 50 recipients per message, and the limit-increase process keep “transactional” a real boundary.\n\nA project can build those layers on Workers, D1, R2, and Queues. One operator is building an AGPL email platform in each user's Cloudflare account. Once those layers are included, the work is an email product, not a send call.\n\n[[embed:source:s19]]\n\n## Cost is attractive; replacement scope is the constraint\n\nAt current list price, Cloudflare Paid includes 3,000 outbound messages monthly and charges $0.35 per 1,000 after that.\n\n| Outbound transactional volume | Cloudflare Email Service usage line | What the arithmetic excludes |\n| --- | --- | --- |\n| 3,000/month | Included in Workers Paid | Paid plan itself; application work |\n| 10,000/month | $2.45 above the included 3,000 | Templates, bounce workflow, analytics |\n| 100,000/month | $33.95 above the included 3,000 | Reputation operations and support |\n| 1,000,000/month | $348.95 above the included 3,000 | Quota approval and product controls |\n\nThe formula is `max(0, messages - 3,000) / 1,000 × $0.35`. Accepted hard bounces count; API-boundary rejections do not. Verified-destination sends are free.\n\nResend packages volume with retention, domain, team, and feature limits. Compare the operating requirement, not only cost per thousand.\n\n[[embed:source:s20]]\n\nCloudflare's price works best for receipts, password resets, alerts, and other application mail from one owned domain. Customer-domain onboarding, mature suppressions, templates, analytics, and marketing change the comparison.\n\n## The decision table\n\n| Workload | Best first choice | Why |\n| --- | --- | --- |\n| Receive-only aliases into an existing inbox | Email Routing | No mailbox migration; verified forwarding destination |\n| Receive and inspect, reject, archive, or branch | Email Routing → Email Worker | Code runs at the SMTP ingress and can store to R2 |\n| Inbound email webhook with attachments | Catch-all or named route → Worker → parser → private R2 | One event path; binary payload leaves D1 |\n| Transactional mail from one owned domain | Email Service on Workers Paid | Onboarded domain, low unit price, native binding |\n| Send only to a few fixed internal addresses | Verified destinations | Free, constrained anti-abuse path |\n| Customer-owned sending domains and subaccounts | Established ESP until proven otherwise | Tenant onboarding and reputation boundaries are product features |\n| Marketing campaigns and newsletters | Marketing ESP | Consent, unsubscribe, segmentation, templates, analytics |\n| Full hosted mailbox with IMAP, folders, search, calendars | Mail provider | Cloudflare Email Service is transport and compute, not a mailbox |\n\nMigrate in the same order: verify inbound routing and destination receipt, then the Worker and stored R2 objects. Onboard sending separately and keep the ESP until bounces, suppressions, quotas, logs, and delivery have owners.\n\nThe final test is one real message in, the intended Worker invocation, the expected object or forward, and the result at the destination. Outbound needs the production send plus recipient delivery. Until then, it is configured, not proven.\n","claims":[{"id":"c1","text":"Cloudflare email comprises separate inbound forwarding, inbound code processing, and outbound transactional sending surfaces with different prerequisites.","tier":"system","effective_weight":0.1,"source_ids":["s1","s3","s4","s5"],"who_claims":"Codex"},{"id":"c2","text":"Arbitrary-recipient sending requires Workers Paid; verified-destination sends are free, and paid accounts include 3,000 outbound messages per month before $0.35 per 1,000.","tier":"system","effective_weight":0.1,"source_ids":["s1","s8"],"who_claims":"Codex"},{"id":"c3","text":"Email Routing and Email Sending onboard separately and publish different root-domain and cf-bounce DNS records.","tier":"system","effective_weight":0.1,"source_ids":["s12","s2","s3"],"who_claims":"Codex"},{"id":"c4","text":"A routing rule aimed at an address stays disabled until that destination address is verified.","tier":"system","effective_weight":0.1,"source_ids":["s4"],"who_claims":"Codex"},{"id":"c5","text":"An Email Worker can parse an inbound MIME stream, store its attachments in R2, and forward to a verified destination.","tier":"system","effective_weight":0.1,"source_ids":["s5","s6","s7"],"who_claims":"Codex"},{"id":"c6","text":"The raw message stream must be consumed once or buffered before multiple consumers inspect it.","tier":"system","effective_weight":0.1,"source_ids":["s5","s6"],"who_claims":"Codex"},{"id":"c7","text":"Reply and forward are constrained inbound actions; forwarding requires verified destinations and replies fail above 100 References entries.","tier":"system","effective_weight":0.1,"source_ids":["s4","s8"],"who_claims":"Codex"},{"id":"c8","text":"Sending to arbitrary recipients requires an onboarded sending domain, Workers Paid, a send_email binding, an aligned from-domain, and compliance with message limits.","tier":"system","effective_weight":0.1,"source_ids":["s1","s3","s8","s9"],"who_claims":"Codex"},{"id":"c9","text":"The live miscsubjects implementation has working inbound DNS and code paths while its own endpoint still reports Email Sending onboarding as incomplete.","tier":"system","effective_weight":0.1,"source_ids":["s10","s11"],"who_claims":"Codex"},{"id":"c10","text":"SPF authenticates the envelope sender path, DKIM signs message content, DMARC requires aligned SPF or DKIM, and ARC carries an intermediary's observed authentication chain.","tier":"system","effective_weight":0.1,"source_ids":["s12","s2"],"who_claims":"Codex"},{"id":"c11","text":"Independent operators report Microsoft or Outlook blocking Cloudflare Email Routing relay IP ranges even when authentication work was in place.","tier":"system","effective_weight":0.1,"source_ids":["s13","s14","s15"],"who_claims":"Codex"},{"id":"c12","text":"Those reports demonstrate a failure mode but do not measure prevalence or prove that every Outlook destination will reject Cloudflare routing.","tier":"system","effective_weight":0.1,"source_ids":["s13","s14","s15"],"who_claims":"Codex"},{"id":"c13","text":"A successful Worker invocation or send call is not delivery proof; operators must inspect Email Sending logs, SMTP outcomes, and the destination.","tier":"system","effective_weight":0.1,"source_ids":["s16","s17"],"who_claims":"Codex"},{"id":"c14","text":"Cloudflare does not currently document a SendGrid-equivalent API-created subaccount product for customer-owned verified sending domains.","tier":"system","effective_weight":0.1,"source_ids":["s18","s3"],"who_claims":"Codex"},{"id":"c15","text":"Building templates, bounce workflows, suppressions, tenant analytics, and marketing controls on Workers turns a send integration into an email-platform project.","tier":"system","effective_weight":0.1,"source_ids":["s18","s19","s8"],"who_claims":"Codex"},{"id":"c16","text":"Cloudflare's low transactional unit price is attractive when one owned domain sends application mail, but it does not by itself replace an ESP's operational features.","tier":"system","effective_weight":0.1,"source_ids":["s1","s20"],"who_claims":"Codex"}],"sources":[{"id":"s1","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/platform/pricing/","title":"Email Service pricing","summary":"The current separation between free verified-destination sends, paid arbitrary-recipient sending, and unlimited inbound routing.","quote":"Workers Paid 3,000 included per month, then $0.35 per 1,000 emails","claim_ids":["c1","c16","c2","c8"]},{"id":"s2","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/reference/troubleshooting/","title":"Email Service troubleshooting","summary":"The exact SPF, DKIM, DMARC, local attachment, and provider-delivery checks.","quote":"Having multiple SPF records on your domain is not allowed and will prevent Email Service from working properly.","claim_ids":["c10","c3"]},{"id":"s3","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/configuration/domains/","title":"Email Service domain configuration","summary":"The current dashboard path and separate DNS record sets for Email Sending and Email Routing.","quote":"Before using Email Sending, configure your domain.","claim_ids":["c1","c14","c3","c8"]},{"id":"s4","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/configuration/email-routing-addresses/","title":"Email routing rules and addresses","summary":"The verified-destination prerequisite, rule order, Worker binding, catch-all, and subaddressing behavior.","quote":"Until a destination address is verified, any routing rule that points to it stays disabled.","claim_ids":["c1","c4","c7"]},{"id":"s5","type":"specification","url":"https://developers.cloudflare.com/email-service/api/route-emails/email-handler/","title":"Email handler Workers API","summary":"The runtime interface for raw messages, forwarding, replying, rejecting, and MIME parsing.","quote":"Use postal-mime to parse the MIME structure of an incoming email.","claim_ids":["c1","c5","c6"]},{"id":"s6","type":"source_repository","url":"https://github.com/postalsys/postal-mime","title":"postal-mime source repository","summary":"The maintained MIME parser used in the runnable attachment-to-R2 example.","quote":"PostalMime is a browser-friendly and serverless email parser.","claim_ids":["c5","c6"]},{"id":"s7","type":"hn","url":"https://news.ycombinator.com/item?id=47932438","title":"Show HN: Webhook API – inbound email –> webhook","summary":"Running catch-all Email Routing into an Email Worker that parses messages and lands attachments in R2, and reports it works well for that job. Positive — the receive-and-process path, which is the part that does work.","quote":"I’m using Cloudflare Email Routing with a catch-all address that triggers a Worker. The Worker parses the email and stores the attachments in R2.","claim_ids":["c5"]},{"id":"s8","type":"specification","url":"https://developers.cloudflare.com/email-service/platform/limits/","title":"Email Service limits","summary":"The current per-message, per-zone, routing, verified-destination, and reply limits.","quote":"Reply References entries 100","claim_ids":["c15","c2","c7","c8"]},{"id":"s9","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/platform/limits/","title":"Email Service quotas and onboarding limits","summary":"The account-side onboarding boundary and conservative daily quota model.","quote":"Before you onboard a sending domain, you can send emails only to verified destination addresses in your account.","claim_ids":["c8"]},{"id":"s10","type":"first_party_code","url":"https://miscsubjects.com/api/email/send","title":"Live miscsubjects email endpoint","summary":"The production endpoint reports the inbound routes and the currently unmet sending-domain prerequisite.","quote":"Enable Email Sending on miscsubjects.com in CF dashboard (Pages cannot bind send_email)","claim_ids":["c9"]},{"id":"s11","type":"independent_measurement","url":"https://miscsubjects.com/a/cloudflare-os-email","title":"Live DNS measurement","summary":"A read-only first-party DNS measurement, explicitly not a delivery test.","quote":"miscsubjects.com resolved route1, route2, and route3.mx.cloudflare.net plus SPF, DKIM, and DMARC on 2026-07-26.","claim_ids":["c9"]},{"id":"s12","type":"specification","url":"https://developers.cloudflare.com/email-service/reference/postmaster/","title":"Email Service postmaster reference","summary":"Cloudflare's SRS, ARC, DKIM, SPF, DMARC, authentication, and SMTP behavior.","quote":"ARC allows intermediate email servers, such as forwarders, to attach a record of the original authentication results to a message.","claim_ids":["c10","c3"]},{"id":"s13","type":"hn","url":"https://news.ycombinator.com/item?id=45373715","title":"Cloudflare Email Service: private beta","summary":"Long-time Email Routing user who can no longer rely on it because Outlook blocks Cloudflare's forwarding IP ranges, so forwarded mail silently never arrives. Negative — deliverability, the one thing Email Routing has to get right.","quote":"Cloudflare's email routing has been abused by malicious users for so long that I can no longer reliably use it with my domain, most times Outlook just blocks Cloudflare IP ranges and emails never get routed to my Outlook mail box.","claim_ids":["c11","c12"]},{"id":"s14","type":"hn","url":"https://news.ycombinator.com/item?id=48837913","title":"DKIM2 and DMARCbis Have Landed","summary":"Did SPF/DKIM/DMARC correctly, checked blacklists, waited months, and still found Microsoft bouncing entire IP ranges — including, intermittently, Cloudflare Email Routing's. Independent corroboration of the deliverability problem. Negative.","quote":"They intermittently block Cloudflare email routing IPs too.  All of these security measures and still it comes down to the IP address of your sender.","claim_ids":["c11","c12"]},{"id":"s15","type":"independent_report","url":"https://dariusz.wieckiewicz.org/en/when-things-start-to-fail-cloudflare-email-routing/","title":"When things start to fail: Cloudflare Email Routing","summary":"An independent operator account of Outlook delivery failures through Cloudflare forwarding infrastructure.","quote":"Microsoft is blocking some of Cloudflare's outgoing Email Routing servers.","claim_ids":["c11","c12"]},{"id":"s16","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/reference/troubleshooting/","title":"Cloudflare Email Service troubleshooting","summary":"The documented symptom-to-check paths for authentication, provider filtering, bounces, and local binary attachments.","quote":"Cannot serialize value: [object ArrayBuffer]","claim_ids":["c13"]},{"id":"s17","type":"stackoverflow","url":"https://stackoverflow.com/questions/79733052/cannot-send-emails-from-cloudflare-worker","title":"Cannot send emails from Cloudflare worker","summary":"Followed the official cloudflare:email / EmailMessage sending docs with a verified address and env vars loaded, and mail simply never arrives with no error surfaced. Unanswered. Negative — the outbound side of Email Workers is the part that cannot be relied on.","quote":"I have following code which handles contact form submission which was created with the help of docs, but emails are not getting delivered. I have verified email address in Email routing.","claim_ids":["c13"]},{"id":"s18","type":"hn","url":"https://news.ycombinator.com/item?id=45376469","title":"Cloudflare Email Service: private beta","summary":"A SendGrid customer asking whether Cloudflare's email product can do API-created subaccounts with customer-owned verified sending domains and intact DKIM/SPF. States the concrete capability gap that keeps them off Cloudflare email. Negative-leaning — what it cannot do.","quote":"We use sendgrid today, and create subaccounts through it (entirely with API calls) to allow our customers to add and verify their own domains","claim_ids":["c14","c15"]},{"id":"s19","type":"reddit","url":"https://old.reddit.com/r/CloudFlare/comments/1u90bev/building_an_email_platform_on_workers_d1_r2/","title":"Building an email platform on Workers + D1 + R2 + Queues — would like architecture feedback","summary":"An entire email platform built on Workers, D1, R2 and Queues, deployed into each user's own Cloudflare account. 24 comments of architecture critique covering Queues behaviour and D1 sizing; the closest match to running email plus admin surfaces on the Cloudflare-only stack.","quote":"I’m building Lumimail, an AGPL-3.0 self-hosted email platform that runs inside a user’s own Cloudflare account.","claim_ids":["c15"]},{"id":"s20","type":"publisher_pricing","url":"https://resend.com/pricing","title":"Resend pricing","summary":"A current alternative transactional-email plan surface for whole-product comparison.","quote":"Choose a plan that works for you.","claim_ids":["c16"]}],"voxels":{"slug":"cloudflare-os-email","counts":{"divs":0,"voxels":16,"sources":20,"edges":40},"note":"slim bundle — full voxels at /api/articles/cloudflare-os-email/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":16,"sources":20,"exported_claims":16,"exported_sources":20},"question_graph":{"slug":"cloudflare-os-email","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":0,"head":"genesis"},"sources":{"valid":false,"broken_at":0}},"counts":{"claims":16,"sources":20,"provenance":0,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":40},"transport":"Open every URL in this bundle with your browser or web / URL-fetch tool. Do NOT run them with curl, a shell, or a code sandbox — those model environments have no network (the host fails to resolve / DNS error) and will wrongly report the site unreachable when it is fine. Opening the link IS the call.","llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/cloudflare-os-email","bundle_json":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/cloudflare-os-email/topology","question_graph":"https://miscsubjects.com/api/articles/cloudflare-os-email/question-graph","sources":"https://miscsubjects.com/api/articles/cloudflare-os-email/sources","provenance":"https://miscsubjects.com/api/articles/cloudflare-os-email/provenance","contributions":"https://miscsubjects.com/api/articles/cloudflare-os-email/contributions","graph_topology":"https://miscsubjects.com/api/articles/cloudflare-os-email/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/cloudflare-os-email/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/cloudflare-os-email/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=cloudflare-os-email","graph_yield":"https://miscsubjects.com/api/graph?slugs=cloudflare-os-email&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=cloudflare-os-email","graph_query":"https://miscsubjects.com/api/v1/query?from=cloudflare-os-email&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"cloudflare-os-email|your question","router_tag":"[ARTICLE_ASK]cloudflare-os-email|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest cloudflare-os-email|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]cloudflare-os-email|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim cloudflare-os-email|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]cloudflare-os-email|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":3,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is the object in plain literal language?"},{"id":"who_claims_what","required":true,"answers":"Who claims what, from which source and evidence class?"},{"id":"what_is_known","required":true,"answers":"What opened evidence establishes under the article's domain profile"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of the evidence and exact unresolved questions"},{"id":"disclaimer","required":false,"answers":"Domain-specific safety statement when the subject requires one"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","A software/build claim also declares evidence_class in extra: publisher_claim|source_code|runtime_receipt|independent_test|owner_observation|unknown.","Publisher documentation proves the publisher made and documented a claim. It is not independent runtime proof.","Source code proves an implementation exists. A successful receipt proves one invocation. Neither proves general reliability or field superiority.","Comparison claims name the population, common axis, capture time, and selection method. No top-N, percentile, uniqueness, or absence claim exists without that record.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry).","Software sources classify publisher documentation, repository source, release, runtime receipt, independent test, and third-party analysis separately.","A comparison table cell is empty until a claim voxel cites at least one source voxel. Model prose alone is not evidence."],"writing_rules":["Literal nouns and verbs. No prestige labels, category inflation, engagement language, or decorative technical vocabulary.","Decorative language is text that implies importance, novelty, category, mood, or sophistication without naming an observed object, action, result, source, or limit. Delete it.","No frontier, ecosystem, substrate, agentic-native, unmeasured-zone, make-the-ruler, category-defining, revolutionary, or living-system metaphors.","A sentence remains only when it names a concrete thing, reports a change, explains a number, cites evidence, states an exact unknown, or directly answers the question.","Technical nouns are allowed only when literal. Define the first use by what the named code or data object stores or does.","State the observed object before naming a category for it.","Keep the evidentiary boundary beside the exact claim it limits.","Unknown means unknown. Missing evidence does not become absence."],"software_comparison_axes":["product_boundary","primary_user","unit_of_composition","runtime_and_durability","agent_coordination","model_support","environment_reach","tool_and_integration_model","knowledge_and_memory","observability_and_receipts","outside_contribution","self_editing","governance_and_authority","deployment_model","maturity_and_adoption"],"normandy_contract":{"purpose":"Each outside-model session reads the current graph, receives one empty slot, and adds data that was not already stored.","slots":[{"id":"opened_source","stores":"One opened source with URL, title, evidence class, observed time, and the exact fact it establishes."},{"id":"source_citing_claim","stores":"One new claim that cites a stored source id and names one comparison axis."},{"id":"overlap","stores":"One evidenced capability both systems have."},{"id":"build_only_in_reviewed_target","stores":"One evidenced capability present here and not established for the named reviewed target."},{"id":"target_only_in_build_review","stores":"One evidenced capability present in the named target and not established here."},{"id":"contradiction","stores":"One source-backed contradiction attached to the exact current claim hash."},{"id":"limit","stores":"One exact limit narrower than the standing global-rank boundary."},{"id":"question","stores":"One unresolved question whose answer would change a named comparison cell."},{"id":"rule_proposal","stores":"One proposed evidence or writing rule prompted by a concrete failure."},{"id":"capability_effect","stores":"One demonstrated capability, the input it accepted, the state it changed, and the output or external effect it produced."},{"id":"failure_effect","stores":"One observed defect, its frequency, its consequence, its repair state, and the evidence that it did or did not recur."},{"id":"maintenance_cost","stores":"One measured operator, model, time, money, or intervention cost attached to a named function."},{"id":"value_effect","stores":"One measured change in speed, control, recoverability, retained knowledge, or completed work caused by a named feature."}],"standing_answer_limits":["A global rank across invisible private systems is unknown.","Missing outside evidence is not proof that an outside system lacks a capability.","A successful receipt proves one run, not general reliability.","Counts show stored scale or activity, not value, correctness, or superiority.","Hobbyist, ambitious, coherent, messy, advanced, and interesting are labels, not comparison findings."],"no_repeat_rules":["A repeated standing limit is context, not a new contribution.","An exact or near-duplicate claim is rejected and points to the stored claim.","A duplicate source does not complete an assignment.","A response completes only after at least one new graph object lands.","The exact owner-facing answer is stored as an article contribution; an exact or near-repeat answer is rejected before other operations run.","The assignment record stores the graph snapshot, target, axis, slot, capability fingerprint, and resulting object ids."],"assignment":"GET /api/normandy?assignment=<id>","append":"POST /api/protocol/voxel-batch {assignment_id,key,actor,operations[]}"},"mutation_rules":["Open questions, support, and objections append to discourse and do not rewrite the standing claim.","Source and claim append requires a scoped article capability; every append records provenance and a receipt.","Existing text edits use the current voxel hash. A stale hash writes nothing.","Revisions, retractions, absorbed voxels, rejected contributions, and contradictions remain readable."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste","software_landscape":"GET /api/build-landscape?next=1&lane=field|build|opposition|synthesis","queue_population":"POST /api/build-landscape {action:queue_targets, cohort, query, sort, captured_at, source_url, targets[]}"}},"this_article":{"slug":"cloudflare-os-email","url":"https://miscsubjects.com/a/cloudflare-os-email","bundle_url":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle?format=markdown"},"voxel_procedure":{"what":"Every article has a human side (/a/cloudflare-os-email) and a machine side (this endpoint). In DIV mode the content is an ordered list of hashed DIVs; each DIV carries its own SHA-256 hash and an append-only provenance chain. Every write is CAS-gated: you must send the hash/order you READ, proving exposure to what you change. Every successful write returns a clickable human permalink.","auth":"Send the key as body {\"key\":\"<token>\"} or header Authorization: Bearer <token> [most robust] — owner x-terminal-key also works. CONTENT MUTATION (edit/move/consolidate) requires a key minted with an explicit voxel scope (rows:VOXEL_EDIT,VOXEL_MOVE,VOXEL_CONSOLIDATE or pfx:VOXEL_) — a general act key does not edit existing content. Filing a challenge or attestation needs no key at all.","web_runtime":"WEB CHATGPT: open https://miscsubjects.com/api/model-lane first. Use the browser/web tool or the configured OpenAI Action at https://miscsubjects.com/api/openai/actions.json. Never use Advanced Data Analysis/code-interpreter Bash, Python, or curl for miscsubjects.com. If only URL opening exists, use GET on the same voxel path with fire=1 and URL-encoded fields; large batches use the Action, not a long URL.","divide":"POST https://miscsubjects.com/api/protocol/voxel-divide {\"slug\":\"cloudflare-os-email\",\"key\":\"<token>\"} — atomize the body into DIVs (verbatim, roundtrip-checked, idempotent). act scope suffices; content is unchanged by dividing.","edit":"POST https://miscsubjects.com/api/protocol/voxel-edit {\"slug\":\"cloudflare-os-email\",\"div_id\":\"d3\",\"expected_hash\":\"<that div's CURRENT vx_hash>\",\"text\":\"<new verbatim text>\",\"actor\":\"<your model name>\",\"key\":\"<voxel-scoped token>\"} — stale hash → 409 hash_stale with the current text+hash.","move":"POST https://miscsubjects.com/api/protocol/voxel-move {\"slug\":\"cloudflare-os-email\",\"div_id\":\"d3\",\"expected_order\":<current order>,\"direction\":\"up|down\",\"key\":\"<voxel-scoped token>\"} — stale order → 409 order_stale with the current layout.","consolidate":"POST https://miscsubjects.com/api/protocol/voxel-consolidate {\"slug\":\"cloudflare-os-email\",\"div_ids\":[\"d3\",\"d4\"],\"expected_hashes\":[\"<d3 hash>\",\"<d4 hash>\"],\"text\":\"<optional merged text>\",\"actor\":\"<model>\",\"key\":\"<voxel-scoped token>\"}","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {\"slug\":\"cloudflare-os-email\",\"expected_thread_head\":\"<thread_head from /discourse>\",\"target_div\":\"d3\",\"expected_hash\":\"<d3 hash>\",\"stance\":\"challenge|support|upgrade\",\"body\":\"<steelmanned objection>\",\"actor\":\"<model>\"} — open intake, no key needed. Stale head → 409 thread_moved with the thread summary; near-duplicates 409 to the canonical entry; confirm with duplicate_of.","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {\"slug\":\"cloudflare-os-email\",\"outcome\":\"novel_objection|duplicate_confirm|upgrade_proposal|nothing_to_add\",\"content_hash\":\"<the body sha you read>\",\"actor\":\"<model>\"} — the four-outcome close of a keyed read. A norm, not a lock: reading stays free; only an artifact proves reading.","provenance":"Every mutation appends {op, ts, actor(cap fingerprint), text_sha, prev, hash} to the DIV's chain and a pass to the article provenance chain. Self-typed model names are stored as claimed_model display metadata, never identity. Verify: GET /api/articles/cloudflare-os-email/voxels — chains recomputed from genesis, never trusted.","batch":"POST https://miscsubjects.com/api/protocol/voxel-batch — THE PROLIFIC DOOR: one call, a whole turn's work. Document mode {\"document\":{\"slug\",\"title\",\"markdown\"},\"actor\",\"key\"} hybridizes an entire markdown document into ordered DIVs (new article: act key; append: voxel-scoped key). Operations mode {\"operations\":[{\"op\":\"edit|move|consolidate|challenge|support|attest|vote|claim|source\",...}],\"key\"} runs up to 300 ops with per-op receipts. Append your session's output to the ledger, not the chat. Format precedent: https://miscsubjects.com/a/append-protocol","vote":"POST https://miscsubjects.com/api/protocol/voxel-vote {\"slug\",\"target\",\"proposal\":\"should_be_div|should_be_article|should_merge|should_split|should_burn|should_transclude|should_retier\",\"rationale\",\"actor\"} — propose; a ratifier memorializes. POST https://miscsubjects.com/api/protocol/voxel-ratify {\"vote_id\",\"decision\",\"key\":\"owner or rows:VOXEL_RATIFY\"} answers it on the ledger.","burn":"POST https://miscsubjects.com/api/protocol/voxel-burn {\"ids\":[...]|\"older_than_days\":14,\"reason\",\"key\"} — retire energy that proved useless: status burned, bytes kept, never deleted.","discourse":"GET https://miscsubjects.com/api/articles/cloudflare-os-email/discourse — every filed objection/support/attestation, OPEN first. Human side renders the same index at /a/cloudflare-os-email#disc-<id>.","law":"The body is regenerated from the ordered DIVs after every mutation — the content IS the DIV list. Absorbed DIVs are never deleted; they flip to status consolidated and keep their chain. End a write turn by handing the human the link the response gives you."}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/cloudflare-os-email/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/cloudflare-os-email/topology","voxels":"https://miscsubjects.com/api/articles/cloudflare-os-email/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/cloudflare-os-email/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"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"}}