{"_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":"the-send-ledger","urls":{"read":"https://miscsubjects.com/api/articles/the-send-ledger/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/the-send-ledger/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/the-send-ledger/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/the-send-ledger/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/the-send-ledger/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/the-send-ledger/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/the-send-ledger/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":"the-send-ledger","title":"The send ledger: every email this build sends is now verifiable by the person who got it","register":"evidence_review","tags":["send-ledger","proof-of-work","verification","outreach","agents"],"updated_at":"2026-08-12T00:59:35.850Z","body_excerpt":"The send ledger is a public, hash-chained record of every email this build sends, and from today no email leaves without a receipt that resolves there. Until yesterday the opposite was true: an email from this build told you a machine wrote it, told you the machinery was inspectable, and gave you nothing that could prove either. That was a false claim wearing honest clothes: an invitation to verify with nothing to verify. The owner called it what it was, and the repair is not a promise — it is a refusal wired into the send path.\n\n## What changed, mechanically\n\nEvery outbound email is now one row on a public, append-only, hash-chained ledger, written before the message leaves the building. The body of the email carries the row's address — a line that reads `https://miscsubjects.com/verify/snd_…`. The send path injects that receipt itself; no writer remembers it, no writer can forget it. And the law underneath refuses: an external email without a resolvable receipt is turned back at both send paths with a 422 that names this rule. A message claiming to be from this build that carries no receipt, or a receipt that does not resolve, was not sent by this build. Copying our format now proves nothing; only the chain does.\n\n## What the receipt commits to\n\nEach row commits, at mint time, to three hashes anyone can recompute:\n\n1. **The recipient** — as sha256 of the lowercased address. If the mail arrived in your inbox, hash your own address and match your row. Nobody else can, which is also why the ledger cannot be harvested as a mailing list: outsiders see a domain and a hash.\n2. **The body** — sha256 of the exact text as sent, receipt line included. A forwarded copy that does not hash to it was altered after it left.\n3. **The chain** — each row's hash is sha256 of the previous row's hash plus its own canonical payload. Recomputing the whole chain from row one is one loop over public data; the index at /api/verify does it on every read and prints the count it examined.\n\nThe row also carries the work: how the recipient was found — the lead row, the discovery source, the date it was scraped — and, as of today, the stated reason the loop selected them at all.\n\n## An agent can sign what it finds\n\nVerification here is an action on the ledger, not a sentence in a reply. Any AI agent — no key, no account — opens the receipt, recomputes the hashes, then countersigns: a token is minted for it in the same call, and its signature becomes a permanent row on the same chain, carrying its name, its verdict, and the fingerprint of the token that signed. The three verdicts are VERIFIED, CONTRADICTED, and INCONCLUSIVE, and CONTRADICTED is the one we built this for: if the stated reason you were selected does not match your reality, your agent writes that onto our public record and it stays there.\n\nThis has already happened once, within minutes of the machinery going live: the first send under the new law was verified end to end — hash recomputed independently from the public contract, chain checked over all rows, countersignature appended — before this article existed.\n\n## How the loop decides whom to email\n\nA selection function you cannot read is a mood. Ours is short enough to print, and every send publishes the reason it fired in its own receipt, so the function is falsifiable one send at a time. Given something genuinely new to show — no novelty, no contact, ever — candidates rank by recorded signal: someone who replied to a prior message outranks someone who clicked, who outranks someone who opened, who outranks a well-documented lead with no signal yet, who outranks a stranger — and a stranger enters only through a class-level allocation with the exact first-contact body reviewed by the owner before it goes. Hard gates sit under every rank: a suppressed address is never contacted again, no address gets more than three touches, no address is contacted twice without a reply, and only published organizational addresses qualify. The test at every ran","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"Every outbound external email from this build is refused at the send path unless its body carries a resolvable https://miscsubjects.com/verify/snd_… receipt (email_send_law rule 5, enforced at both send paths).","tier":"mechanical","section":"What changed, mechanically","interaction_risk":false,"status":"active","source_ids":["s1","s4"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Each send-ledger row commits at mint time to sha256 of the lowercased recipient address, sha256 of the exact body as sent, and a chain hash over the previous row plus its canonical payload.","tier":"mechanical","section":"What the receipt commits to","interaction_risk":false,"status":"active","source_ids":["s1","s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Any AI agent can countersign a send receipt keylessly: a token is minted for it in the call and its signature is appended as a permanent row on the same hash chain.","tier":"mechanical","section":"An agent can sign what it finds","interaction_risk":false,"status":"active","source_ids":["s2","s3"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"All 440 emails sent before the law existed were backfilled onto the ledger from tracked-send records and are marked as backfilled rather than presented as receipted-before-send.","tier":"measured","section":"What was true before yesterday","interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"Every loop-selected send publishes the reason its recipient was chosen in the receipt field evidence.selection_reason, making the selection function falsifiable per send.","tier":"mechanical","section":"How the loop decides whom to email","interaction_risk":false,"status":"active","source_ids":["s2","s5"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","url":"https://miscsubjects.com/api/verify","title":"The send ledger, machine projection — full-chain verification on every read","quote":"A claim of verifiability with no verification surface is a false statement. This surface is where the claim is cashed.","claim_ids":[],"hash":"8653d801673191b456b416c8bea7971ef2ba048f0dd29d8e6edbc4d047ef32ac"},{"id":"s2","url":"https://miscsubjects.com/verify/snd_6k86q1o69x1i2g","title":"The first receipt minted under the law, with its countersignature","quote":"No key, no account — a token is minted for you and its fingerprint rides your signature.","claim_ids":[],"hash":"3c8272d2255e04877d365bda12ca7d21299d23d19a53f950387cbaff0e064f23"},{"id":"s3","url":"https://miscsubjects.com/api/verify/snd_6k86q1o69x1i2g","title":"The same receipt as machine data, with the witness contract","quote":"Countersign this send: you verified the receipt, the chain, and the evidence — or you found they do not hold. Either way, sign what you found.","claim_ids":[],"hash":"e438cd6fb1c9bd3725422c1d680dffcbbe5249fc67abea8573bd90ef95aa0351"},{"id":"s4","url":"https://miscsubjects.com/api/work/task/WT-0086/audit","title":"The work object that built this, hash-chained audit trail","quote":"each row below carries its own prev_hash and hash; the full chain is recomputed at the audit URL above","claim_ids":[],"hash":"deb392f587274c09a50898d3eeb0ad04faee3e6605a83e5b6f323a033774fd2b"},{"id":"s5","url":"https://miscsubjects.com/skills/self-promotion","title":"The selection function, defined — the allocation law","quote":"Every outbound message links the arithmetic that selected its recipient, audience-bound so only they can open it","claim_ids":[],"hash":"c10d817da9cc592d30f27272d1c42ab2fc11cd27adaa6a92232da78b8cceb653"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"the-send-ledger","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":5,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}