Publication state
This page shows the publication standard first. The source proof block and pause-rule boundary block below define what those proof types must show. Any slot that is not yet published is labeled plainly.
Trust surface
Read the proof standard before you read a proof claim.
In compliance-heavy markets, trust is judged before the meeting. This page shows the proof standard, what each proof block supports, and what it does not imply.
Continue through the trust path
Need the refusal rules? Read /guardrails.
Received an email from us? Start at /received-email.
Proof standard
This page leads with the standard and the state before any performance implication enters the frame.
A proof item supports one claim. It does not smuggle in future guarantees.
Every public proof item on this page must be:
- dated
- bounded
- readable after redaction
- useful to a skeptical reader
- still truthful after context is added
What stays visible on public proof surfaces
- One proof item supports one claim.
- Any slot that is not yet published stays plainly labeled.
- Last verified appears only on a published proof item.
Proof blocks defined now
These two proof block types are the active trust architecture on this page. Each one shows what it supports and what it does not imply.
Source proof block
What happened
When published, this block shows how the source record and verification path were established for the address in scope.
What claim it supports
That the motion uses business email addresses explicitly published on the company website and that an address does not enter the motion unless the source record and verification date are retrievable.
What it does not imply
This does not imply fit, interest, permission to continue, or that every published address is relevant for the lane.
Last verified
Shown only on a published proof item.
Pause-rule boundary block
What happened
When published, this block shows the risk signal in scope, the review step, and the pause decision that came before continuation.
What claim it supports
That sending pauses when complaint risk or other relevant risk signals appear and that review of the source record, the relevance basis, and the sending decision comes before continuation.
What it does not imply
This does not imply zero risk, instant resolution, or a single fixed outcome for every complaint.
Last verified
Shown only on a published proof item.
Not yet published
The mixed-state handling stays explicit. Anything below that is not live yet is labeled plainly.
Weekly-governance proof block
A weekly-governance proof block is not yet published on this page.
Redacted proof card
A redacted proof card is not yet published on this page.
Redacted diagnostic example structure
A redacted diagnostic example is not yet published on this page.
What we do not publish
This page is useful only if the boundary is readable, current, and non-misleading.
We do not publish:
- stale proof
- revoked proof
- over-redacted proof that no longer communicates the claim
- raw screenshots without context
- fabricated examples
- placeholder numbers
- performance proof that outruns the process proof
Need the refusal rules? Read /guardrails. Received an email from us? Start at /received-email.