What this page covers
- What we refuse
- What triggers a pause
- Who owns what
- Continuation is not automatic
- Category boundary
Trust surface
See the refusal rules, pause triggers, and ownership split before scale.
The motion only runs while the rules hold. If the rules break, sending pauses first.
Why these rules exist
These guardrails are not marketing theater. They are operating rules designed to prevent trust leakage, sourcing ambiguity, and sloppy escalation.
What we refuse
The refusal set stays explicit because the motion only runs while the rules hold.
- No bought lists.
- No guessed patterns.
- No people databases as source authority.
- No directory sites as email-source proof.
- No blast volume.
- No meeting guarantees.
- No pipeline guarantees.
- No revenue guarantees.
- No outsourced reply ownership.
- No outsourced call handling.
- No compliance-delivery claims.
Safety reinforcement
No sender-reputation shortcuts.
What triggers a pause
Pause-first handling stays easy to scan because the trigger list is visible and specific.
Sending pauses first when any of the following appears:
- complaint
- hard bounce pattern
- opt-out issue
- QA failure
Sending pauses first when any of the following appears:
- deliverability warning
- sender-risk signal
- client reply-SLA failure
- monitoring gap that makes truth or control uncertain
Ownership and continuation
This page makes the split visible so the motion does not drift into vendor-owned replies or automatic continuation.
Who owns what
NotchForge governs the motion.
The client owns replies within 24 hours, qualified call ownership, truthful inputs, suppression compliance, and boundary compliance.
Continuation is not automatic
ForgeStart does not roll forward by default.
Day 45 ends with one of three states.
Continuation requires explicit approval.
Boundary and why these rules exist
The point of the guardrails is to keep trust, sourcing, and responsibility visible before scale ever enters the picture.
Category boundary
We do not deliver CMMC, DFARS / NIST SP 800-171, GCC High, or enclave implementation services. We run outbound for MSPs that do.
Why these rules exist
These guardrails are not marketing theater. They are operating rules designed to prevent trust leakage, sourcing ambiguity, and sloppy escalation.
Need the proof standard? Read /proof. Received an email from us? Start at /received-email.