Part 3 · Operate
Grounding and evidence
Every claim traces to a dated row, and the validator refuses the ones that do not.
01What it is
A rule enforced in code: any sentence referencing a company or a person must trace to a stored row with a URL and a date. The model never invents a trigger event.
02Why it exists
A message built on something that did not happen is worse than no message. The recipient knows their own company, and one invented detail ends the conversation and the relationship behind it.
This is also what makes the product defensible. Everything it says about a company can be shown with a source, which is a different position from a tool that infers interest and cannot say from what.
03How to use it
- 01Read the evidence beside a draft before approving it.
- 02Follow a source link when a claim surprises you.
- 03Add proof points in the brand brief with their sources so your own claims can pass the same rule.
04What good looks like
- You give it
- A draft referencing "the four platform roles you opened in August", with the job posting URLs stored.
- You get
- Passes. Each claim maps to a row with a date and a link.
- Why
- The claim is specific, dated and traceable to stored observations.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- A draft saying "I saw you are scaling the team".
- You get
- Refused for having no dated signal, because nothing in the sentence points at a row.
- Why
- The outreach contract requires a dated signal, and a vague paraphrase satisfies nothing.
Derived from the rules in the code