{"_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":"outreach-machinery","urls":{"read":"https://miscsubjects.com/api/articles/outreach-machinery/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/outreach-machinery/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/outreach-machinery/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/outreach-machinery/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/outreach-machinery/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/outreach-machinery/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/outreach-machinery/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":"outreach-machinery","title":"Outreach machinery: how this build finds who should see it, writes, sends, and records why","register":"technical","tags":["system","protocol","governance","agents","marketing"],"updated_at":"2026-07-30T07:03:09.222Z","body_excerpt":"## What this page documents\n\nThis build has a working lead-discovery and outreach system. Until this page existed, none of it was documented anywhere a reader outside the build could see: the scrapers, the enrichment crawler, the qualification gates, the drafting validator, the send gate, the tracking, and the channels it can speak on were internal tooling described only in code and in an administrative view nobody else can open.\n\nThe same is true of everything adjacent to it: the image and video generation, the fifty-eight paid-advertising rows, and the machine-readable documents that are the only promotion surface written for a program rather than a person.\n\nThis page documents all of it to the same standard as every other capability here — the real row names, the real code paths, the real tables and columns, the real gates, the real costs, and the real counts as they stand at publication. It documents what the system does **not** do, and then what it does not **have** — every channel and interface a system like this should hold and does not — because for a promotion system that complement is the more load-bearing half.\n\nTwo things follow it. The first is the logic that decides who should hear about this build at all, derived from the published corpus rather than asserted. The second is the arithmetic that decides how many of them are contacted on a given day, through which channel, with which artifact — recorded, replayable, and openable by the person it selected.\n\n## Why it is being published\n\nThe most common objection to this build, raised by nearly every model that has been shown it, is not architectural. It is that nobody else has adopted it. The architecture is granted and then dismissed on that ground.\n\nThat objection is correct on its facts and the number is in this page. It also has a structure worth naming: the thing being asked for is external demand, and the honest way to produce external demand is to reach the people whose problem the build addresses and let them check it. Doing that with an undocumented, unreviewable outreach system would reproduce, one level up, exactly the failure this build exists to refuse — an action taken for reasons nobody outside the actor can inspect.\n\nSo the outreach machinery is documented first, on the same terms as everything else: the mechanism is public, the decision is receipted, and the reason a particular recipient was selected is a record that recipient can open.\n\n## One door\n\nEvery capability named below is a directory row invoked the same way:\n\n```bash\ncurl -s -X POST https://miscsubjects.com/api/dispatch \\\n  -H 'content-type: application/json' \\\n  -d '{\"key\":\"LEADS_VERIFY_MX\",\"body\":\"25\"}'\n```\n\nThe invocation is appended to the ledger — key, actor, inputs, result, cost, trace — before the result returns to the caller. Each one is then readable at `/receipt/<invocation id>`. That property is what makes the rest of this page checkable instead of merely descriptive.\n\n[[embed:source:s9]]\n\n## Discovery: four independent sources, one table\n\nDiscovery finds candidate organisations. Four rows do it, from four sources that fail in different ways, and all four write into one table with a uniqueness constraint on name and city so the same organisation cannot be counted twice.\n\n| row | source | cost | what it yields | how it fails |\n|---|---|---|---|---|\n| `LEADS_DISCOVER` | OpenStreetMap via Overpass | free | name, website, phone, address, tag context | coverage is volunteer-dependent and thin for professional practices |\n| `LEADS_DISCOVER_PLACES` | Places text search | metered per request, written into the result | name, website, phone, formatted address, rating, type | costs money per call and returns commercial listings only |\n| `LEADS_DISCOVER_NPI` | NPPES federal registry | free | authoritative identity, phone, address, taxonomy | contains no website at all |\n| `LEADS_DISCOVER_AI` | live web search | model tokens | organisations the other three miss | least structured and least ","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c18","text":"The response prior starts as a declared constant, not as an assumed response rate, and updates only from recorded events: replies, opt-outs, complaints, and the reviewer verdict stored against each draft.","tier":"speculative","section":"The delta equation","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The first wave's ordering therefore rests on an estimate with no response data behind it, which is the weakest input in the equation and is published as such.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.12,"quote_gated":false},{"id":"c1","text":"Every outreach capability on this site is a directory row invoked through one endpoint, and every invocation is appended to the ledger before its result is returned to the caller.","tier":"system","section":"One door","interaction_risk":false,"status":"active","source_ids":["s9"],"why_material":"It is what makes the rest of the page checkable rather than descriptive: each named row can be called, and each call leaves a record nobody has to be trusted about.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"The first discovery source queries OpenStreetMap through Overpass with per-segment tag filters and discards any result that has neither a website nor a phone number.","tier":"system","section":"Discovery","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"A record with no reachable contact cannot progress through any later stage, so it is refused at the point of entry rather than counted as a lead.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"The second discovery source is a paid Places text search that records its own per-call cost in the result it returns.","tier":"system","section":"Discovery","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"Cost is a field on the invocation, not an estimate reconstructed later, which is what allows a discovery run to be priced from its own receipt.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"The third discovery source is the federal NPPES registry, which is authoritative on identity and address and contains no website field.","tier":"system","section":"Discovery","interaction_risk":false,"status":"active","source_ids":["s3"],"why_material":"It explains why a separate resolve stage exists: the most reliable identity source is the one least able to be crawled.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"Enrichment reads only the target's own website. It crawls a fixed path list, extracts addresses four ways including de-obfuscating protected addresses, and prefers an address on the target's own domain.","tier":"system","section":"Enrichment","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It bounds where contact data can come from. No third-party contact database and no guessed address can enter the system through this path.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"The text captured from the target's own site is the only material a draft may personalise from, and a batch claim column prevents two workers from enriching the same record.","tier":"system","section":"Enrichment","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Personalisation with no recorded source is indistinguishable from invention, so the source is stored as a column and shown beside every draft.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"Mailbox verification is an MX lookup over HTTPS. It proves the domain accepts mail. It does not prove the individual mailbox exists.","tier":"system","section":"Verification","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"Stating the limit is what stops a verified flag being read as a delivery guarantee; a typed role address on a live domain can still bounce.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"Qualification is a model scoring each record against a stored thesis document and writing back a score, a counterparty type, and a one-line reason. No calibration study exists for that score.","tier":"system","section":"Qualification","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The score gates every later stage, so the absence of a calibration study is the single largest unquantified error in the pipeline.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"Drafting refuses to run unless a verified address, a passing MX check, a score at or above the floor, a minimum quantity of real site context, and a clean suppression check all hold.","tier":"system","section":"Drafting","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The gates are preconditions on the writing step, not advice to the writer, so a missing input produces a refusal instead of a plausible sentence.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"A completed draft is discarded and retried when it contains a banned phrase, a subject that violates the subject contract, or claims outside the permitted register. The discard happens before anything is saved.","tier":"system","section":"Drafting","interaction_risk":false,"status":"active","source_ids":[],"why_material":"A validator that runs after saving produces a corpus that has to be cleaned; one that runs before saving produces a corpus that never contained the defect.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c11","text":"Sending is refused unless the caller passes a literal confirmation token, and the gate re-checks every qualification condition at send time plus four more: this address has never been sent to, the recipient is not suppressed, a postal address is configured, and the sending domain's authentication is flagged as proven.","tier":"system","section":"The send gate","interaction_risk":false,"status":"active","source_ids":["s5","s6"],"why_material":"Re-checking at send time is the difference between a gate and a stale approval, because every condition was checked when the draft was written and any of them can have changed since.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c12","text":"Eleven emails have been sent to external recipients by this machinery, all on 2026-07-06, before the confirmation gate existed. None of the eleven appear in the send-tracking table, because the single-send path writes the record status and does not write a tracking row.","tier":"system","section":"The honest state","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It is both the entire external send history and an open recording defect, and either one alone would be a misleading account of the system.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c13","text":"A post to X counts as posted only when the provider returns a success status and a non-empty id and the row returns the status URL built from that id. A receipt, an attempted call, or a deduplication claim is not a post.","tier":"system","section":"Channels","interaction_risk":false,"status":"active","source_ids":["s8"],"why_material":"The completion contract exists because models repeatedly reported a post as published while holding only their own receipt for the attempt.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c14","text":"Reddit reads require two credentials and replying as an account requires four, so the read lane and the reply lane can be independently available or unavailable.","tier":"system","section":"Channels","interaction_risk":false,"status":"active","source_ids":["s7"],"why_material":"Treating one channel as a single capability produces a false inventory; the lanes fail separately and must be reported separately.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c15","text":"There is no LinkedIn capability. There is no cold direct-message capability on any channel. Messaging channels are reply and warm channels only.","tier":"system","section":"What it does not do","interaction_risk":false,"status":"active","source_ids":[],"why_material":"An inventory of a promotion system is worthless without its complement, and the absent channels are the ones a reader would otherwise assume.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c16","text":"Audience classes are derived by independent models reading the published corpus and answering one question — who bears a loss this machinery reduces — with every model's full request and response stored as a ledger object.","tier":"system","section":"Who would care","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It makes the targeting thesis refutable: the reasoning that produced each class is readable, and a reader can attack the class rather than the outcome.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c17","text":"Daily volume per class and channel is the product of five terms — fit, novelty, permission, one minus saturation, and a response prior — where permission and novelty can only zero the result.","tier":"system","section":"The delta equation","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Making novelty a zeroing term is what prevents a contact sequence: with nothing new to show a class, the computed volume for that class is zero.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c19","text":"Each allocation writes one ledger object holding the policy version, every input term per class, the resulting volumes, and the identifiers of the records selected, so the allocation can be replayed and contradicted.","tier":"system","section":"The delta equation","interaction_risk":false,"status":"active","source_ids":["s10"],"why_material":"An unreplayable selection cannot be audited by the person it selected, which is the only audit of a targeting decision that matters.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c20","text":"A recipient can open the arithmetic that selected them through a token issued to that recipient. Class-level allocations are public; a named recipient's record is not.","tier":"system","section":"The delta equation","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Publishing a named individual's targeting file to prove transparency would be the harm the transparency is supposed to prevent.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c21","text":"Copy shape is measured by removing the personalised opener, the catalog block, every URL and every number from a draft and hashing what remains, so drafts written under the same rules collapse to the same hash.","tier":"system","section":"Template collapse","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It caught a real failure: a personalisation rule strict enough to ban every available observation left one legal opener and one hundred and twenty-one drafts converged on it.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c22","text":"No party has been contacted about this build. The machinery described here has been exercised end to end for a different subject, and its audience logic for this subject has never been run against a real recipient.","tier":"system","section":"The honest state","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The standing objection to this build is that nobody else has adopted it, and the correct answer to that objection is the current number, not an argument.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c23","text":"The build's cheapest promotion surface is machine-readable: a plain-text index for models, a sitemap, a feed, and two well-known descriptor documents that let an agent enumerate the site's capabilities without a human intermediary.","tier":"system","section":"Machine-readable discovery","interaction_risk":false,"status":"active","source_ids":["s14"],"why_material":"For a system whose audience includes coding agents and web models, the document written for them is not a side channel; it is the primary one.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c24","text":"The build holds fifty-eight rows against a paid advertising API covering campaign, ad set, ad, creative, audience, lookalike, budget, status, targeting search, delivery estimate and asynchronous insights, plus one server-side conversion row.","tier":"system","section":"Paid channels","interaction_risk":false,"status":"active","source_ids":["s11","s12"],"why_material":"The paid lane is not a plan; the create paths exist. What does not exist is any spend for this subject, and the distinction between capability and use is the whole point of documenting it.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c25","text":"Image and video generation is available through four independent providers, and generated assets are stored in object storage with the generating request preserved.","tier":"system","section":"Making the creative","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Creative production being in the same receipted system as the send is what allows an asset, the message that carried it, and the outcome to be joined afterwards.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c26","text":"Named absent capabilities include TikTok, Google Ads, LinkedIn, YouTube, Instagram publishing, Threads, Bluesky, Mastodon, Discord, Slack, compliant application-to-person SMS, a deliverability-reporting mail provider, search-console and change-notification interfaces, and every developer-community submission surface.","tier":"system","section":"What it does not have","interaction_risk":false,"status":"active","source_ids":["s13"],"why_material":"A promotion system that documents only what it can do produces an inventory that reads as complete; the gap list is what makes the inventory usable for deciding what to build next.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"other","url":"https://wiki.openstreetmap.org/wiki/Overpass_API","title":"Overpass API — querying OpenStreetMap data","summary":"The free endpoint behind the first discovery source. Tag filters, area scoping, and the 30-second timeout the runner sets.","claim_ids":["c2"],"hash":"69e1fd5bb2cf567c8d13bacbc75cdef35b225b517af5fa6f00604c1a175e911f"},{"id":"s2","type":"other","url":"https://developers.google.com/maps/documentation/places/web-service/usage-and-billing","title":"Places API (New) — usage and billing","summary":"Text Search Enterprise + Atmosphere is the SKU the second discovery source bills against. The runner writes the per-call cost into its own result.","claim_ids":["c3"],"hash":"64d404f190eadd9f4269e10be11e200c8ec15db2798829e468e1e833a7d7adc9"},{"id":"s3","type":"other","url":"https://npiregistry.cms.hhs.gov/api-page","title":"NPPES NPI Registry API","summary":"The federal registry of licensed US providers. Free, keyless, authoritative on identity and address, and carries no website field — which is why a resolve stage exists.","claim_ids":["c4"],"hash":"72e9ba73ddb99b23040ea1853570198eec74216810e32762b6f16ccaf6977ed9"},{"id":"s4","type":"other","url":"https://www.rfc-editor.org/rfc/rfc8484","title":"RFC 8484 — DNS Queries over HTTPS (DoH)","quote":"This document defines a protocol for sending DNS queries and getting DNS responses over HTTPS.","summary":"How mailbox verification runs from a Worker with no DNS socket: MX lookups over HTTPS.","claim_ids":["c7"],"hash":"6c4d70cee0896cc0ad2538f48fef13db30fa98611aec6f59fc8a5c4380080e74"},{"id":"s5","type":"other","url":"https://www.ecfr.gov/current/title-16/part-316","title":"16 CFR Part 316 — CAN-SPAM Rule","summary":"The source of the two send-time preconditions that are configuration rather than code: a valid physical postal address in the message, and a working opt-out.","claim_ids":["c11"],"hash":"4ba5b653f35ba95c19be9d500728d0a720da0500278776a1802bc9221fbab7dd"},{"id":"s6","type":"other","url":"https://www.rfc-editor.org/rfc/rfc7489","title":"RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC)","summary":"Together with SPF (RFC 7208) and DKIM (RFC 6376), the alignment the sending domain must prove before the send gate is allowed to open.","claim_ids":["c11"],"hash":"e81b789e9afcb946ff80c09aac6cae8b9c3ef91704ed892c0f9722cb3bd458cd"},{"id":"s7","type":"other","url":"https://www.reddit.com/dev/api/","title":"Reddit Data API documentation","summary":"The read and reply surface behind the Reddit rows. Reads need two credentials; replying as an account needs four.","claim_ids":["c14"],"hash":"c446f6dd11e10c06df04c114bfc39b3f6fdf33656bfb58d5746d97840f3bd522"},{"id":"s8","type":"other","url":"https://developer.x.com/en/docs/x-api","title":"X API documentation","summary":"OAuth 1.0a user-context posting. The row's completion contract is derived from what this API actually returns: an id, and a status URL built from it.","claim_ids":["c13"],"hash":"ec2595dea46eda666ecbd5ca4b859e98a899cff8e9a25a5dadd0a34654151a3d"},{"id":"s9","type":"live_surface","url":"https://miscsubjects.com/api/dispatch","title":"POST /api/dispatch — the single door every row is invoked through","summary":"Every capability named on this page is invoked the same way: a key and a body. The invocation lands on the ledger before the result returns.","claim_ids":["c1"],"hash":"05f831b1f1ebdd1121a49c2000b4059cdd012cd7d88bbad620627482a3ff4934"},{"id":"s11","type":"other","url":"https://developers.facebook.com/docs/marketing-apis/","title":"Marketing API — campaign, ad set, creative and audience objects","summary":"The paid surface the build holds fifty-eight rows against: read, create, budget, status, audience, lookalike, delivery estimate, and asynchronous insights.","claim_ids":["c24"],"hash":"e490698025040bc995256b584ad4ac66e38d9ebeb74a2ff704e479f6960b48a7"},{"id":"s12","type":"other","url":"https://developers.facebook.com/docs/marketing-api/conversions-api/","title":"Conversions API — server-side event delivery","summary":"How a server reports an outcome back to the ad platform. The build holds one row against it and has never sent a conversion for this subject.","claim_ids":["c24"],"hash":"460c7ef7d4b2f8de22a23465a1152eaf1e88f21f1fa8b7ab74ad35eafe74446b"},{"id":"s13","type":"other","url":"https://www.indexnow.org/documentation","title":"IndexNow — submitting URLs to search engines on change","summary":"One of the named absent capabilities: the site publishes a sitemap and waits to be crawled instead of announcing each change.","claim_ids":["c26"],"hash":"8444448fc8dd587abef1ca43573f718d7485a21a6020e7f3033a31e2484477fe"},{"id":"s14","type":"live_surface","url":"https://miscsubjects.com/llms.txt","title":"GET /llms.txt — the machine-readable index of this site","summary":"The lowest-cost promotion surface the build has: a document written for a model reading the site rather than a person browsing it.","claim_ids":["c23"],"hash":"14e26fb1e8ecd0d5ba1d460a2d30c45a8d08c8c31a49393efae0cfa406dbb62b"},{"id":"s10","type":"live_surface","url":"https://miscsubjects.com/api/relay","title":"GET /api/relay — the ledger feed","summary":"Where an outreach decision is readable after the fact: the allocation, the inputs it read, and the invocation that produced it.","claim_ids":["c19"],"hash":"f35f04200d1a198c6e979741a87f8c4fc4bb08cdf98c337d5a1412dd7137291d"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"outreach-machinery","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":26,"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":26,"claims_total":26,"sources":14,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}