Outreach machinery: how this build finds who should see it, writes, sends, and records why
What this page documents
This 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.
The 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.
This 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.
Two 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.
Why it is being published
The 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.
That 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.
So 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.
One door
Every capability named below is a directory row invoked the same way:
curl -s -X POST https://miscsubjects.com/api/dispatch \
-H 'content-type: application/json' \
-d '{"key":"LEADS_VERIFY_MX","body":"25"}'The 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.
Discovery: four independent sources, one table
Discovery 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.
| row | source | cost | what it yields | how it fails |
|---|---|---|---|---|
LEADS_DISCOVER | OpenStreetMap via Overpass | free | name, website, phone, address, tag context | coverage is volunteer-dependent and thin for professional practices |
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 |
LEADS_DISCOVER_NPI | NPPES federal registry | free | authoritative identity, phone, address, taxonomy | contains no website at all |
LEADS_DISCOVER_AI | live web search | model tokens | organisations the other three miss | least structured and least verifiable of the four |
Every one of them discards a result that has neither a website nor a phone number. A record with no reachable contact cannot pass any later stage, so it is refused at entry rather than stored and counted.
The insert is a conflict-ignoring insert that returns the new identifier only when a row was actually created, so a discovery run reports how many records are new rather than how many results it saw. Both numbers are in the result.
Resolve: giving the authoritative rows something to crawl
The most reliable identity source has no website field. A separate row looks up siteless records by name and city and attaches the website, which is the only thing that makes the next stage possible. This is the stage that decides whether personalisation can happen at all — not the writer, and not the model.
Enrichment: the target's own site, and nothing else
Enrichment fetches the organisation's own website and reads a fixed list of paths on it — the homepage, then the conventional contact, about, team, services, and location paths. Addresses are extracted four ways: visible text, mail links, structured data, and de-obfuscation of protected addresses that are rendered as encoded attributes rather than text. A junk filter removes placeholders, platform addresses, and content-delivery artefacts. An address on the organisation's own domain is preferred; a role address is next.
The same pass captures the site's own title and description, and stores them as the record's context.
Two properties matter more than the extraction detail.
The only permitted source of contact data is the target's own website. No purchased list, no third-party contact database, and no pattern-guessed address can enter the system through this path. If the organisation has not published an address, the record ends as no address found and is never drafted.
The stored context is the only material a draft may personalise from, and it is displayed beside every draft along with the URL it came from. A personalised sentence with no recorded source is indistinguishable from an invented one, so the source is a column.
A batch version processes several records at a time and stamps a claim timestamp on each, with stale-claim recovery, so two workers running concurrently never enrich the same record twice.
Verification: what a verified address actually means
Mailbox verification looks up the mail-exchange records for each address's domain over HTTPS, because a Worker has no DNS socket. Domains with no mail server are parked so that no draft and no send is ever spent on them.
The limit has to be stated in the same breath as the check: this proves the domain accepts mail. It does not prove the individual mailbox exists. A role address on a live domain can still bounce, and any claim stronger than that is false.
Qualification: a score, and the study that does not exist
A model reads each verified record against a stored thesis document — what is being offered, to whom, and why they would want it — and returns a score out of one hundred, a counterparty type, and a one-line concrete reason. The score and the reason are written back onto the record, so the list can be ordered by judged fit rather than by whether a website happened to be found.
Records below the floor are never drafted.
No calibration study exists for that score. It is a model's estimate of commercial fit, it gates every later stage, and its error rate is unmeasured. That is the largest unquantified term in the whole pipeline and it is not improved by describing it in stronger language.
Drafting: preconditions, then a validator that destroys its own output
The drafting row refuses to run at all unless every one of these holds: an address was found on the organisation's own site, its domain accepts mail, the qualification score is at or above the floor, there is a minimum quantity of real site context to write from, and the recipient is not suppressed. A missing input produces a refusal, not a plausible sentence written around the gap.
When it does run, the finished draft is then checked and — if it fails — discarded and retried before anything is stored. The checks include banned phrases, a subject-line contract, register violations, and claims outside the permitted class. A validator that runs after saving produces a corpus that has to be cleaned later; one that runs before saving produces a corpus that never contained the defect.
Template collapse, and how it is measured
The most expensive failure this system has produced was not a rule being broken. It was a rule being obeyed.
A personalisation rule was tightened until it banned every observation the target sites actually contained. One legal opener remained, and one hundred and twenty-one drafts converged on it under the same four-word subject. Every draft passed every validator. Interchangeable mail is unwanted mail regardless of how strict the rules that produced it were.
The detector for it is structural. A draft's shape is what remains after the personalised opener, the catalog block, every URL and every number are removed; that residue is hashed. Two drafts written under the same rules produce the same hash. Clustering the corpus on it turns a pile of near-identical bodies into the handful of generations the copy has actually been through, and the count of distinct businesses inside one shape is the collapse measurement.
Every change to the drafting rules is stored verbatim with its timestamp, and the shape clustering is re-run after the change. The rule history and the corpus it produced are inspected together, because a rule change is only evaluable against the output it caused.
Review: nothing reaches a recipient unreviewed
Drafts are mailed for review with the recipient, the subject, and the full body, one per draft. Nothing is sent to any recipient until that review has happened.
Review mail deliberately carries no link wrapping, unlike outbound mail. Wrapping rewrites the visible destination of every link, and a review message carrying a dozen rewritten links is a text-and-destination mismatch on every one of them — which is what filters score as impersonation. That was not theoretical: a wrapped review batch went to spam while earlier unwrapped mail arrived.
The send gate
The send row refuses unless the caller passes a literal confirmation token as the first argument. It is not a parameter with a default; the absence of the exact token returns a refusal that sends nothing.
With the token, it re-checks all of the following at send time:
- the record is in the drafted state;
- its domain still passes the mail check;
- its qualification score is still at or above the floor;
- the recipient is not in the suppression table;
- this address has never been sent to before, by any record;
- a valid physical postal address is configured;
- the sending domain's authentication alignment is flagged as proven.
Then it appends the disclosure footer — the postal address, and a one-word reply that stops all further contact.
Re-checking is the whole point. Every one of those conditions was already checked when the draft was written, and any of them can have changed since. An approval that is not re-verified at the moment of action is a memory of an approval.
The batch version caps the number it will send and runs the entire gate again per record, so a batch is a loop over individual gated sends and not a bulk path around them.
Tracking, and its unreliability
Outbound mail has its links rewritten through a redirect that counts clicks, and carries a single-pixel image that counts opens. Delivery status, open count, first and last open, click count and a click log are stored per send.
Open tracking is unreliable and should be read as a floor, not a measurement: image blocking, privacy proxies, and prefetching all break it in both directions. Click tracking is more reliable and still not proof of a human.
Follow-ups
A follow-up row drafts a short threaded sequence off the first message. It is subject to the same review-before-send rule, and to the same never-twice constraint at the address level.
The channels, and the completion contract on each
| channel | rows | state | what counts as done |
|---|---|---|---|
EMAIL_SEND, EMAIL_SEND_TRACKED, LEADS_SEND, LEADS_SEND_BATCH | live | provider accepted the message, and a tracking row exists | |
| X | X_POST, X_REPLY, X_SEARCH | live, owner account, user-context OAuth | provider success status, non-empty id, and the status URL built from that id |
REDDIT_SEARCH, REDDIT_THREAD, REDDIT_REPLY | reads and replies implemented; the reply lane needs two more credentials than the read lane | the provider's comment identifier and its permalink | |
| iMessage | messaging-provider rows, with a capability probe per number | live | provider delivery event for the specific message |
| messaging-provider rows | live | provider delivery event | |
| Telegram | dedicated route | live | provider message identifier |
| paid delivery | fifty-eight advertising rows, read and create | live, never used for this build | the platform's own object identifier for the created campaign, ad set, ad or creative |
| creative production | image, video and ad-format generation across four providers | live | the stored asset and the request that produced it |
| machine-readable | /llms.txt, /sitemap.xml, /feed.xml, two well-known descriptors | live | a fetch of the document, logged |
The X completion contract deserves its own line because it was written against a real repeated failure: a model reported a post as published while holding only its own receipt for having attempted it. A receipt proves a call was made. Only the provider's identifier and the resulting status URL prove a post exists. The same standard now applies to every channel in the table: the provider's own identifier, or the action is not done.
Machine-readable discovery: the channel with no recipient
The cheapest promotion this build does has no message and no send. It is a set of documents written for a program rather than a person.
| surface | what it is for |
|---|---|
/llms.txt | a plain-text index of the site, written so a model reading it can find the substantive pages without parsing navigation |
/sitemap.xml | every page, for crawlers |
/feed.xml | changes, for anything that subscribes |
/.well-known/agent.json | a descriptor telling an agent what this site is and how to call it |
/.well-known/oip.json | the object protocol descriptor: the shape of every addressable object here |
/api/dispatch, /api/relay, /receipt/<id> | the enumerable capability surface and its history |
This matters more for this build than it would for most. A meaningful share of the audience for an auditable-reasoning primitive is not a human browsing — it is a coding agent or a web-based model asked to evaluate something, which will read whatever is machine-addressable and ignore whatever is not. Making the capability surface enumerable, and every claim traceable to a receipt an agent can fetch, is the promotion. A page a model cannot verify is a page a model will hedge about.
Making the creative: images and video
Creative production is inside the same receipted system as the send.
| capability | rows |
|---|---|
| ad-format image and video generation, uploaded to object storage | creative-platform rows including a credit check, a generate call, a video generate call, and an upload-to-storage step |
| general image generation | two independent model providers, each with a direct call and a store-to-object-storage variant |
| image editing | provider edit rows |
| short video generation | a start-and-poll pair |
| text-to-image on the platform's own inference | one row |
Four independent providers exist for images, so a provider refusal or outage is not a stop. The generating request is preserved alongside the asset, which is what allows an image, the message that carried it, and whatever came back to be joined afterwards rather than guessed at.
Every featured image on this site, including the one on this page, was produced this way.
Paid channels: the ads surface
The build holds fifty-eight rows against a paid advertising API. Not a read-only integration — the create paths exist:
- read: accounts, businesses, portfolio, campaigns, ad sets, ads, creatives, images, videos, audiences, pixels, catalogs and their diagnostics, activities, studies;
- create: campaign, ad set, ad, creative, custom audience, lookalike audience, catalog;
- change: budget set, status set, campaign update, ad set update, ad update, object delete;
- measure: insights, asynchronous insights create/status/result, dataset stats, delivery estimate;
- target: targeting search and targeting browse;
- report back: one server-side conversion row.
Zero has been spent promoting this build. The advertising account those rows are bound to belongs to a different venture. The capability is real and the use is nil, and the distinction between those two things is exactly what this page exists to make legible.
The reason the paid lane is documented next to the free one is that they are one loop, not two. A paid impression and a cold email are both a spend of something scarce against a hypothesis about who cares; both produce a signal; both signals move the same terms in the same equation. The only structural difference is that the paid lane can be bought in volume before the hypothesis is any good, which is the argument for its coming last rather than first.
What it does not have, and should
An inventory of a promotion system that lists only what it can do reads as complete. This is the complement — every channel and interface that is absent, with what its absence costs.
| absent | what it would do | cost of not having it |
|---|---|---|
| TikTok Content Posting and Marketing APIs | organic posting and paid delivery on the platform with the largest current attention surplus | the entire short-video audience is unreachable |
| Google Ads API | intent-side paid delivery — reaching a search rather than an interest | no way to appear at the moment someone searches for the problem this solves |
| LinkedIn Pages and Marketing APIs | the professional network where the audience classes for this build actually work | the single largest miss for a business-to-business primitive |
| YouTube Data API | publishing demonstration video where technical evaluation actually happens | a demonstration has nowhere durable to live |
| Instagram Graph publishing | scheduled organic publishing | ad rows exist for the platform; organic publishing does not |
| Threads, Bluesky and Mastodon | the developer-adjacent networks displacing a share of X | one microblog is a single point of failure |
| Discord and Slack | the closed communities where technical adoption is actually argued | no presence where practitioners talk |
| Product Hunt, Hacker News, developer-community submission | one-shot launch surfaces with real reach for infrastructure | no launch mechanism at all |
| compliant application-to-person SMS | text as an outbound channel under a registered campaign | messaging exists only as a reply channel, correctly, because the compliant path is unbuilt |
| a mail provider with deliverability reporting | bounce, complaint and reputation data as first-class events | delivery is inferred from an accepted request, and complaints are invisible |
| IndexNow and search-console interfaces | announcing each change and reading back what indexes and what ranks | the site publishes and waits, blind to its own search performance |
| a newsletter surface | a subscription that does not require the build to initiate | every contact must be outbound; nobody can opt in |
| review and comparison directories | third-party listings buyers consult before contacting anyone | absent from the places evaluation actually starts |
That table is not a wish list. It is the input to the same allocation described below: an absent channel with a high-scoring class behind it is a build task with a priority, and the reason it is published is that the gap list is the part of a self-promotion system nobody writes down.
What it does not do
- No LinkedIn. There is no LinkedIn capability of any kind — no posting, no messaging, no scraping. A reader assuming otherwise from a list of channels would be wrong.
- No cold direct messages, on any channel. iMessage, WhatsApp and Telegram are reply channels and warm channels. A cold message to a personal phone number is not a lower-friction email; it is a worse one, and no row exists to send it.
- No purchased or third-party contact lists. Contact data enters only from the target's own published website.
- No guessed addresses. No first-name-dot-last-name construction against a domain, ever.
- No scraping behind a login, and no automated defeat of bot checks. The crawler fetches public pages of public sites.
- No sending without a human review of the exact body, and no sending twice to one address.
- No claim of delivery, open, or adoption that is not backed by a provider record.
Who would care, and how that is decided
The audience logic is derived, not asserted. Independent models — from different training families, the same channels the adjudication panel uses — read the published corpus and answer one question each: who bears a loss this machinery reduces, and what is the one sentence that would make them reply? Their full requests and responses are stored as ledger objects, so the reasoning that produced a class is readable and can be attacked directly.
A class is stored as a record with: the loss borne, the mechanism that addresses it, the single strongest artifact to show that class, a one-sentence thesis, the counter-argument that class will raise first, and a fit score with its reason. The drafting row reads the class record the same way it reads any other thesis document, so the same code writes to a regulator and to an infrastructure engineer without a fork.
The starting classes are candidates, scored and cut on evidence, not a finished list: assurance and audit technology, litigation support and discovery engineering, model-risk and AI-governance functions inside regulated firms, conformity-assessment and standards bodies, underwriters of professional and technology liability, agent-infrastructure and protocol builders, evaluation and interpretability researchers, procurement functions that must evidence diligence, public-sector oversight bodies, and the platform teams whose primitives this is built on.
The scoring question for each is deliberately narrow: does a wrong decision in their work cost money or licence, do they already pay for attestation of some kind, can one person there act without a committee, and does a page on this site already speak to their specific loss.
The delta equation
Volume is not a target. It is the output of an equation whose terms are recorded.
For a class c, a channel k, on a day d:
priority(c,k,d) = fit(c) · novelty(c,d) · permission(c,k) · (1 − saturation(c,k,d)) · prior(c,k)
volume(c,k,d) = clamp( round( cap(k,d) · priority(c,k,d) / Σ priority ), 0, cap_class(c,d) )- fit — the class score, from the derivation above.
- novelty — what has shipped since this class was last contacted that is relevant to this class: a new article, a new claim, a new receipt, a new capability, a resolved defect. Zero new relevant material is zero novelty and therefore zero volume. This is the term that makes the system incapable of running a drip sequence: with nothing new to show a class, it does not write to that class.
- permission — one for a published organisational address on a channel that class has permitted, zero otherwise. It is a gate that can only zero the term, never a weight that trades against the others.
- saturation — how much of the class has already been contacted on this channel in the trailing window, plus a hard per-domain rate.
- prior — a declared constant to begin with, updated only by recorded events: replies, opt-outs, complaints, and the reviewer's verdict on each draft.
- cap — the daily channel ceiling, set low enough that every message remains individually reviewable.
Each run writes one ledger object holding the policy version, every input term for every class, the resulting volumes, and the identifiers of the records selected. The allocation is therefore replayable and contradictable — someone can recompute it, disagree with a term, and point at the exact number they disagree with.
The prior is the weakest input. With no response data, the first wave's ordering rests on an estimate. It is published as an estimate, and the first real replies will move it.
The receipt the recipient can open
Every message carries a link to the arithmetic that selected its recipient: the class, each input term, the artifact chosen, and why. The link resolves for that recipient, through a token issued to them, using the same audience-bound mechanism this build already uses for blinded human review.
Class-level allocations are public. A named recipient's record is not, and publishing one to demonstrate transparency would be precisely the harm the transparency is for.
What happens when someone replies
- A one-word stop writes the address to the suppression table, which every gate consults before every draft and every send. Nothing further is possible to that address.
- A substantive reply is a first-class event, stored, and it updates the prior for that class rather than being read as a private success.
- "This is spam" is treated as a defect report about the machinery, not about the recipient. It is recorded against the class and the shape that produced it.
- "You are wrong" is the reply the machinery is most interested in, and it has a place to go: the objection log, attributed and dated, alongside every other objection raised against this build.
One loop over every channel, free and paid
The loop is five steps and each hop is a receipt.
- Something ships — an article, a capability, a resolved defect, a measurement, a generated asset.
- The novelty term changes for whichever classes that thing is relevant to. Nothing relevant, no contact.
- The allocation recomputes — who is worth reaching today, on which channel, with which artifact. The artifact changes when a newer and stronger one exists. The channel set includes the free lanes, the machine-readable surfaces, and the paid lane, priced in the same units.
- Signal comes back on every lane and into the same table: replies, opt-outs, complaints and reviewer verdicts from the direct lanes; impressions, clicks and cost from the paid lane; traffic, referrers and which pages were actually read from the analytics surface; and — the signal specific to this build — which receipts and which machine-readable documents were fetched, and by what.
- That signal moves two things, not one. It moves the priors and class scores, which changes the next allocation. And it moves the gap list: a class that responds through a channel the build does not have turns the absence of that channel into a ranked build task. What the build learns about who finds it interesting steers what it builds next, not only who it writes to next.
Step five is the part that makes this different from a marketing pipeline. The output of the loop is not only a message; it is a change to the build's own priorities, produced by evidence about which of its capabilities anyone actually cared about.
There is nothing autonomous about the send. A human reviews every body before a first contact to any class. What is automated is the reasoning about who and when, and that reasoning is recorded in a form that can be read back and contradicted. That is the same standard this build applies to every other decision it makes; outreach is not an exception to it.
The honest state, in numbers
At publication:
- 8,584 records discovered and not yet enriched.
- 680 enriched with a verified address; 814 where no address was found on the target's own site; 18 parked for having no mail server; 7 where no website could be resolved at all.
- 11 drafted and awaiting review; 8 rejected.
- 41 review messages sent to the reviewer, and 1 deliverability test.
- 0 addresses in the suppression table, because no recipient has yet asked to be removed.
- 0 spent on paid delivery for this build, across fifty-eight available advertising rows.
- 0 posts, replies or messages sent about this build on any social or messaging channel.
- 11 emails sent to external recipients — all of them on 2026-07-06, all for a different subject, and all before the confirmation gate existed. That gate exists because of them.
No party has been contacted about this build. The machinery above has been exercised end to end for another subject. Its audience logic for this subject has never been run against a real recipient, and the first wave has not been sent.
Defects, stated before anyone has to find them
- The eleven sends are not in the tracking table. The single-send path updates the record's status and does not write a tracking row, so the send table shows zero outbound messages while eleven records say sent. Two sources of truth that disagree, in the direction that understates activity.
- The qualification score has no calibration study. It gates everything and its error rate is unknown.
- The response prior is a declared constant. Ordering the first wave with it is an estimate presented as an estimate.
- Open tracking is unreliable in both directions, and no engagement number from it should be read as a measurement.
- A verified address is a verified domain. Individual mailboxes are unproven until a message is accepted.
- The audience classes are model output about the build's own value, produced by models that were shown the build's own corpus. A promotion system grading its own targeting is a conflict it cannot resolve from the inside. That is the specific reason the outbound message asks for external audit rather than asserting significance.
- The paid lane has no attribution wired to this subject. The conversion row exists and no conversion definition for this build does, so a paid impression could be bought today and its outcome could not be joined to anything.
- The analytics signal is not yet an input to the allocation. Traffic and referrer data are collected and readable; the equation does not read them. Until it does, step four of the loop is smaller than described here for the free lanes and empty for the paid one.
- Nobody outside has adopted this. It remains the strongest objection, and the number above is the answer rather than an argument.
Wave one, as it stands
The loop above stopped being a description on 2026-07-30. In order, each step receipted:
- Audience derivation ran across model families: inv_6ak9uz7fic (kimi-k2.7-code, eight classes with losses and objections) and inv_bbwnx5ce85 (gemini-2.5-flash, seven). One channel answered a different question than the one asked (inv_gi55ouniaz) and one refused on a spending limit (inv_6b9a8ovtmm) — both recorded rather than retried into silence. Eight classes now sit in the class table, fit 55–85, priors declared at 0.05.
- The allocation ran live, twice: inv_6gaq45opcm before any organization existed to select, and inv_sta3m7a809 after discovery — eight classes at full novelty, volume one each, five with a selected record. Both runs report
sends_performed: 0. - Forty real organizations entered through discovery with each website verified alive at insert; thirteen published an address on their own site and all thirteen domains verified; twenty-seven published none and will never be drafted.
- The owner reviewed the full packet — every party, every selection reason, every draft body — and approved sending.
- Three model families reviewed the drafts before any send: inv_j9hcpxketv (glm-5.2), inv_pu9flpr6d3 (kimi-k2.7-code), inv_8rxiu0po4g (gemini-2.5-flash). Their convergent finding: two drafts clean, three openers described the recipient's industry rather than the recipient. The three openers were rewritten to the reviewers' specification and the revised drafts staged on their records — the peer review is part of the pipeline now, not a courtesy.
- The five first contacts are sent. Each went through the full gate — CONFIRM token, drafted state, mail-domain check, score floor, suppression check, never-sent-before check — and each send is a receipt: inv_uvpxjk93te (an AI-certification body), inv_tqncce1bis (a model-risk practice), inv_k8jba7c0cp (an audit-AI vendor), inv_otiekxkpxp (an ediscovery platform), inv_hi8zwbvp3t (a model-infrastructure company). The provider accepted all five with a message id each.
- The owner ruled on identity before the first send, and the ruling is now a mechanical gate. These messages are feedback requests, not commercial solicitation. They carry no person's name, no postal address, no business name, and no compliance-footer phrasing — the message is the body and the model signature, nothing else, sent as miscsubjects.com. An identity guard in the send path now refuses any feedback-mode send matching a person, business, address, or footer phrase, and a copy of every outbound message lands in the owner's inbox. The five classes contacted are stamped, so their novelty term is zero until something new ships — the loop cannot write to them again with nothing new to say.
After a send: the standing logic
What happens next is not decided next — it is decided now, and it is the same five rules every time:
- A reply is recorded, moves the class prior, and is answered by a person, not by the loop.
- A one-word no writes the address to the suppression table permanently.
- No reply earns at most a follow-up, and only when the novelty term is positive — something real must have shipped since the first message. Three touches is the ceiling, ever, per address.
- A complaint is a defect filed against the class and the copy shape that produced it, not against the recipient.
- Every one of these events updates the same allocation inputs the next wave is computed from, on the ledger, before the next wave runs.
Whether this is the template
The question this wave was run to answer, recorded here as asked: is this the end-to-end shape of a firm run this way — a system that builds its own capabilities, documents them, derives who should care, reaches them, and steers its own building from what comes back, with every step inspectable?
In shape, yes. One system produced the capability, the public documentation of the capability, the audience logic, the allocation, the creative, the review packet, and the record of all of it — through one door, on one ledger, in one working day. Nothing in the loop is specific to promotion: the same shape (ship → derive who bears the loss → show them → record what returns → let it steer the next build) is how any function of a firm would run on this substrate, and the paid rows, creative rows, and commerce rows already exist for the functions that come after this one.
In fact, not yet, on three counts. No revenue has closed through this loop. It has one operator and one node, and the objection log holds that objection already. And the human review gate is load-bearing by design — the loop decides whether, whom, when and with what; a person still decides go. Removing that gate is not a roadmap item; it is what this build exists to refuse.
What is being asked for
Three questions, and they are the reason a message gets sent at all:
- Where is this most commercially valuable, and to whom — from someone who actually buys in that market.
- What is the strongest objection to it that the objection log does not already contain.
- Which of the build's claims about itself do not survive contact with your practice.
Every one of those has a place to be recorded, publicly and attributed, whether the answer flatters the build or ends it.
Key evidence
15 more ranked claims
Low-confidence / auto-generated 1
Ask this article · 8 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.