{"_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."},"q":"email","category":"","count":24,"rows":[{"key":"LEADS_SCORE_AI","type":"fn","category":"biz-dev","target":"leadsScoreAI","planner_rank":6,"docs":"WHAT: AI ICP scoring — one Grok (grok-4.3) call scores a batch of enriched leads 0-100 on real wholesale/white-label peptide buying fit, grounded in OUTREACH_DOSSIER. Writes score + an icp: note (buyer type, volume guess, concrete reason) so LEADS_LIST ranks by commercial fit instead of has-a-website. WHEN_TO_USE: after enrichment, before drafting; \"score the leads\", \"which leads are actually worth emailing\". ARGS: $1 = batch size (default 8, cap 10). Call repeatedly until it returns scored:0. EX: [LEADS_SCORE_AI]8[/LEADS_SCORE_AI]"},{"key":"LEADS_VERIFY_MX","type":"fn","category":"biz-dev","target":"leadsVerifyMx","planner_rank":6,"docs":"WHAT: Verify whether the email domain publishes MX records using DNS-over-HTTPS. Tags mx:ok or mx:none. This verifies the domain, not the individual mailbox.\\n# WHEN_TO_USE: after enrichment and before ICP scoring or drafting.\\n# ARGS: $1=max leads (default 25, cap 50).\\n# EX: [LEADS_VERIFY_MX]25[/LEADS_VERIFY_MX]\\n[\"$1\"]"},{"key":"WORK_APPEND","type":"fn","category":"work","target":"workAppend","planner_rank":10,"docs":"WHAT: Append one entry to the shared append-only work thread. This is how every model records what it did, proposed, or audited so the next model continues from it (fixes short model memory). WHEN_TO_USE: after you do, propose, or audit anything. Always append. ARGS: $1 = your model/agent name, $2 = kind (note|edit|proposal|audit|question|done), $3 = your entry. Prefix body with 'ref:task:12' or 'ref:lead:49' or 'ref:gh:7' to link it. EX: [WORK_APPEND]grok-web|proposal|ref:task:4032 send 50 outreach emails/day to start, ramp weekly[/WORK_APPEND]"},{"key":"EMAILS_SENT","type":"fn","category":"leads","target":"emailsSent","planner_rank":20,"docs":"WHAT: List recent sent emails with open/click engagement + totals (sent-email visibility). WHEN_TO_USE: see everything sent and who opened/clicked. ARGS: $1 = limit (default 50). EX: [EMAILS_SENT]50[/EMAILS_SENT]"},{"key":"EMAIL_SEND_TRACKED","type":"fn","category":"leads","target":"emailSendTracked","planner_rank":20,"docs":"WHAT: Send a tracked email (open pixel + wrapped click links) and record it in email_sends. WHEN_TO_USE: any owner-authorized send where you want open/click visibility. ARGS: $1 = JSON {to, subject, body, kind?, lead_id?, from?, from_name?, reply_to?}. EX: [EMAIL_SEND_TRACKED]{\"to\":\"x@y.com\",\"subject\":\"hi\",\"body\":\"see https://leoresearch.com\"}[/EMAIL_SEND_TRACKED]"},{"key":"GOVERNOR_RUN","type":"fn","category":"governance","target":"governorRun","planner_rank":20,"docs":"WHAT: Run the GOVERNOR — scan the last 48h of ledger turns into a deterministic digest (error streaks, file collisions, loop states, auth lockouts, cron noise, task flow, waste), have the GOVERNOR model write the brief, email it to the owner, text him the verdict, ledger everything as GOVERNOR_BRIEF. WHEN_TO_USE: the owner asks \"whats going on with the build\", \"governor report\", \"run governor\", \"build brief\", \"what keeps breaking\" — or any model wants the standing manager's view before making structural changes. Runs automatically every 12h / 2000 events / 150 errors; this row is the manual fire. ARGS: mode — empty = full run (model + email + iMessage) · dry = digest JSON only, no model call, no delivery EX: [GOVERNOR_RUN][/GOVERNOR_RUN]   or   GET /api/dispatch?invoke=GOVERNOR_RUN&body=dry"},{"key":"CONSCIENCE_GATE","type":"fn","category":"governance","target":"conscienceGate","planner_rank":30,"docs":"WHAT: The Good Conscience Law — the veto between \"can execute\" and \"will execute\". MAY_ACT = authority AND evidence AND conscience; logical economics optimizes only among MAY_ACT=true actions. Empty body returns the constitution (build-conscience@1.0.0, clauses GC1-GC8). A REFUSE/ESCALATE/HALT verdict is rejected unless it names the violated clause, the prohibited consequence, the job's direct causal contribution, and evidence — refusal binds to a named clause, never to free moralizing. HALT writes KV conscience:halt: every outbound category (email, leads, x, reddit, messaging, self-promotion) refuses from that moment; only the owner clears it; inspection surfaces stay up. WHEN_TO_USE: before the build accepts any job or takes any consequential outbound action; when work smells like it violates the floor; \"should the build do this at all\". SAFETY: money, efficiency, owner instruction, or customer demand never compensate for a conscience failure. Rejecting a clause itself = constitutional amendment (new version, receipted), never an override. ARGS: $1 = empty (list clauses) OR JSON {job, verdict:ACCEPT|REFUSE|ESCALATE|HALT, violated_clause?, prohibited_consequence?, causal_contribution?, evidence?, notes?} EX: [CONSCIENCE_GATE][/CONSCIENCE_GATE]"},{"key":"LEADS_DRAFT_AI","type":"fn","category":"biz-dev","target":"leadsDraftAI","planner_rank":33,"docs":"WHAT: Grok drafts one review-only outreach email grounded in OUTREACH_DOSSIER and the business site. DOES NOT SEND. Hard-blocks unless email domain MX is verified, ICP score is at least 65, site context is sufficient, and recipient is not suppressed.\\n# WHEN_TO_USE: only after enrichment, MX verification, and ICP scoring.\\n# ARGS: $1=lead id, $2=brand (default LeoResearch).\\n# EX: [LEADS_DRAFT_AI]131|LeoResearch[/LEADS_DRAFT_AI]\\n[\"$1\",\"$2\"]"},{"key":"LEADS_SEND","type":"fn","category":"biz-dev","target":"leadsSend","planner_rank":33,"docs":"WHAT: Send ONE lead's already-saved email through the owner-reviewed Marketing admin. WHEN_TO_USE: only after the owner reviewed the exact recipient, subject, and body in Admin → Marketing → Leads, approved that exact copy, and separately clicked Send. SAFETY: literal CONFIRM alone is insufficient. $4 must be a current, unexpired, single-use approval token tied to the saved recipient+subject+body hash. Editing copy invalidates approval. Terminal keys/share tokens cannot mint approval. ARGS: $1=CONFIRM, $2=lead id, $3=from local-part, $4=owner-browser exact-copy approval token."},{"key":"LEADS_DRAFT","type":"fn","category":"biz-dev","target":"leadsDraft","planner_rank":34,"docs":"WHAT: Write a wholesale + white-label outreach email for one lead. Saves the draft on the lead. DOES NOT SEND. WHEN_TO_USE: after enrich, to prepare the message for the owner to approve. ARGS: $1 = lead id, $2 = which company it comes from (default miscsubjects). EX: [LEADS_DRAFT]12|miscsubjects[/LEADS_DRAFT]"},{"key":"LEADS_ENRICH","type":"fn","category":"biz-dev","target":"leadsEnrich","planner_rank":34,"docs":"WHAT: Visit one lead's website and pull the best contact email. Sets the lead to enriched or no_email. WHEN_TO_USE: after discovery, to get an email to reach out to. ARGS: $1 = lead id. EX: [LEADS_ENRICH]12[/LEADS_ENRICH]"},{"key":"LEADS_ENRICH_BATCH","type":"fn","category":"biz-dev","target":"leadsEnrichBatch","planner_rank":34,"docs":"WHAT: Enrich the next batch of un-enriched leads in one call (finds emails + context). Bounded so it never fails; call repeatedly to work through the queue. WHEN_TO_USE: after discovery, to fill in emails and context for many leads. ARGS: $1 = how many to do this call (default 8, max 10). EX: [LEADS_ENRICH_BATCH]10[/LEADS_ENRICH_BATCH]"},{"key":"LEADS_LIST","type":"fn","category":"biz-dev","target":"leadsList","planner_rank":34,"docs":"WHAT: List leads and a count by status (new, enriched, drafted, no_email, sent). WHEN_TO_USE: see the outreach pipeline. ARGS: $1 = status filter (optional; blank = all). EX: [LEADS_LIST]drafted[/LEADS_LIST]"},{"key":"LEADS_REENRICH","type":"fn","category":"biz-dev","target":"leadsReenrich","planner_rank":34,"docs":"WHAT: Second pass over status=no_email leads with the deep crawler (mailto links, Cloudflare-obfuscated emails, JSON-LD, /contact-us + /about pages — none of which the v1 crawler read). WHEN_TO_USE: rescue contactable emails from the no_email pool without any new discovery. ARGS: $1 = batch size (default 6, cap 8). EX: [LEADS_REENRICH]6[/LEADS_REENRICH]"},{"key":"EMAIL_SEND","type":"http","category":"email","target":"POST https://miscsubjects.com/api/email/send","planner_rank":35,"docs":"WHAT: Send an email through Cloudflare Email Sending via the sibling worker. WHEN_TO_USE: the owner explicitly asks to send/write/reply/forward an email. SAFETY: owner/internal recipients remain available. Every external recipient requires the server-signed, exact-copy Marketing approval proof; terminal/share credentials alone are refused. ARGS: to | subject | text"},{"key":"TASK_ADD","type":"fn","category":"email","target":"taskAdd","planner_rank":36,"docs":"WHAT: Add a task to the build queue (tasks table). Plain text is fine — it is stored and shown as-is. WHEN_TO_USE: the owner says remember to / add a task / put X on the list / follow up on Y. ARGS: $1 = the task in plain words. Pipes are allowed. EX: [TASK_ADD]call the peptide supplier back about white-label pricing[/TASK_ADD]"},{"key":"TASK_COMPLETE","type":"fn","category":"email","target":"taskDone","planner_rank":36,"docs":"WHAT: Mark a task done (removes it from the open backlog). Same as DONETASK. WHEN_TO_USE: a task is finished. ARGS: $1 = task_id (number), $2 = optional short result note. EX: [TASK_COMPLETE]448|called them, pricing sent[/TASK_COMPLETE]"},{"key":"TASK_DELETE","type":"fn","category":"email","target":"taskDelete","planner_rank":36,"docs":"WHAT: Delete a task for good. Any child tasks are lifted to top level so nothing is hidden. WHEN_TO_USE: a task is junk / a duplicate / should never run. ARGS: $1 = task_id. EX: [TASK_DELETE]448[/TASK_DELETE]"},{"key":"TASK_EDIT","type":"fn","category":"email","target":"taskEdit","planner_rank":36,"docs":"WHAT: Change a task's text and/or status in place. WHEN_TO_USE: reword a task, or move it to open/done/cancelled without deleting it. ARGS: $1 = task_id, $2 = new text (no pipes), $3 = optional new status (open|done|cancelled). EX: [TASK_EDIT]448|call the vendor back Friday|open[/TASK_EDIT]"},{"key":"TASK_THREAD","type":"fn","category":"email","target":"taskThread","planner_rank":36,"docs":"WHAT: Hang one task under another so related work groups together. Empty parent un-threads to top level. WHEN_TO_USE: a task is a sub-step of a bigger task. ARGS: $1 = child task_id, $2 = parent task_id (leave empty to move back to top level). EX: [TASK_THREAD]451|448[/TASK_THREAD]"},{"key":"article:what-this-site-sells","type":"article","category":"articles","target":"/api/articles/what-this-site-sells","planner_rank":100,"docs":"Proven work, the offer: send one case by email, get the deliverable back with its complete checkable record","human":"/a/what-this-site-sells","edit":"/admin/articles/what-this-site-sells","object":"/api/directory/article:what-this-site-sells"},{"key":"article:outreach-machinery","type":"article","category":"articles","target":"/api/articles/outreach-machinery","planner_rank":100,"docs":"8,584 organisations discovered, 680 with verified addresses, 11 drafts, 5 emails sent: the outreach pipeline and every gate in it","human":"/a/outreach-machinery","edit":"/admin/articles/outreach-machinery","object":"/api/directory/article:outreach-machinery"},{"key":"article:one-loop","type":"article","category":"articles","target":"/api/articles/one-loop","planner_rank":100,"docs":"An AI built a capability, tested it, found who needed it, and emailed them — the receipt for each of the six steps","human":"/a/one-loop","edit":"/admin/articles/one-loop","object":"/api/directory/article:one-loop"},{"key":"article:cloudflare-os-email","type":"article","category":"articles","target":"/api/articles/cloudflare-os-email","planner_rank":100,"docs":"Cloudflare email is three products, not one mail stack","human":"/a/cloudflare-os-email","edit":"/admin/articles/cloudflare-os-email","object":"/api/directory/article:cloudflare-os-email"}]}