Follow-up is a gate, not a reflex.

1. sendInbound interest or gate date.Role source live, digest current, ledger verified, cold-read page published, and one new proof path. Action: prepare one short source-backed follow-up after the gate only. Rule nf-001 · score 5/5
2. sendWarm referrer asks for a compact proof link.Use the reviewer digest as the front door; do not attach private logs or unsourced claims. Action: route the referrer to the digest when the gate opens. Rule nf-002 · score 4/5
3. holdBefore May 26 with no reply.No current override, no inbound reply, and no proof failure requiring correction. Action: keep improving public proof, validators, graph evidence, and claim gates. Rule nf-003 · score 5/5
4. holdNew proof is not verified.Pack verifier, ledger verification, Pages QA, privacy scan, banned-claim scan, and live URLs must pass first. Action: regenerate and hash-chain the evidence before it becomes leverage. Rule nf-004 · score 5/5
5. do_not_sendThe draft overclaims.Affiliation, employment, endorsement, customer deployment, revenue, incorporation, funding, and production-result claims are hard stops. Action: refuse the message and rewrite as independent fixture-backed role-fit evidence. Rule nf-005 · score 5/5
6. do_not_sendThe draft adds no signal.Generic, repetitive, unsupported, wrong-recipient, or cold-read-failing messages spend attention without proof. Action: build a stronger proof branch or wait for a real reply. Rule nf-006 · score 4/5

• Public-safe dataPublic URLs and synthetic decision rules only.
• No private recipient dataNo email addresses, private inbox IDs, local paths, credentials, or account-specific handles.
• Date-gated follow-upSend lanes stay inactive until May 26, 2026 unless a real reply or explicit fresh override appears.
• Claim safetyDo-not-send criteria block target-company status, traction, legal-entity, and production-result overclaims.
• Repetition controlA follow-up must add a specific new proof path; generic repetition is a do-not-send lane.

• python3 tools/deployment_receipt.py validate-follow-up-kit --input examples/no_send_follow_up_decision_kit.json
• python3 tools/deployment_receipt.py follow-up-kit --input examples/no_send_follow_up_decision_kit.json
• python3 scripts/verify_public_pack.py
• python3 -m unittest tests/test_deployment_receipt.py

This page does not send, schedule, draft to a recipient, contact OpenAI, contact a recruiter, claim employment, claim affiliation, claim endorsement, claim customer deployment, or authorize legal/company formation. It is a public-safe verifier for deciding what should happen after the no-outbound gate.