> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Our Definition of Done

> Quality is a hard gate at every phase, phrased as yes/no questions from the ICP's point of view, including a claims-safety gate you clear before publishing.

Quality is enforced as a hard gate at every phase, phrased as answerable yes/no questions the
operator has to pass, rather than a checklist you tick after the fact. Each stage (Discovery,
Product Bible, Keywords, Blog Post, Landing Page) has its own gate, and work isn't "done" until it
passes. The gates are written from the reader's and ICP's point of view ("can I *see* it?",
"would ChatGPT cite this?"), and they include a claims-safety gate: flag anything you can't say
publicly before it ships.

## Why gates, and why from the ICP's point of view

Gates make "done" objective and repeatable across operators and agents, and that repeatability is
the discipline gap between a self-serve account and an agency-run one (see
[3.6 — The Quality Gate](/sops/quality-gate)). Phrasing them as ICP-perspective
questions forces the operator to simulate the searcher or engine instead of grading their own
effort. The claims gate exists because programmatic pages scale fast: an unvalidated claim doesn't
sit on one page, it replicates across a whole pillar.

## The gates (verbatim)

**Discovery Gate**

> *"Can I see my ICP when I close my eyes? · Do I have >20 ways to describe my product? (if 20 is
> hard, try starting with 200) · Have I looked up those terms and verified I can win?"*

**Product Bible Gate**

> *"Do I know which feature is most important for which ICP? · Do I know what my ICPs are going to
> name those features? · Do I know what are my ICPs buying triggers?"*

**Keywords Gate**

> *"Does this look like they want to buy? · Does my company offer this? · Is the source credible? ·
> Can I win on this keyword?"*

**Blog Post Gate**

> *"Does this blog post look like what ChatGPT would search for and cite? · Does it have the
> potential to sell your product? · Can you win with this blog post? · Are the keyword/query exist
> in the blog post title?"*

**Landing Page Gate**

> *"Can I 'see' my landing page? · Does this make my ICP go 'THIS IS EXACTLY IT!'? · Does it target
> ONE search intent with ONE keyword? · Do I have >20 pages?"*

## The three technical things that matter most

If you can only get three things right on a page, get **Title, Description, H1** right:

> *"surprisingly important because both human & LLMs are looking at just these in the search
> results and ask 'which of these is more relevant or interesting for me?'"*

After that, in order: first paragraph, heading flow, robots.txt, sitemap.xml, JSON-LD, llms.txt.
And deliberately don't chase the long tail of automated "issues":

> *"Most technical SEO is just about improving experience for a human… \[tools give you] 100s of
> things to fix, they don't even improve the experience — **ignore those.**"*

## The claims-safety gate

Because a claim replicates across a whole pillar, you validate claims before they ship. In
**Hyperbound's** flow the Product Bible goes to the client to:

> *"Flag any claims we should NOT make (metrics, customer names, positioning)"*

and to confirm specific metrics such as *"50% faster ramp," "150% increase in DM→demo
conversion," "2x faster time to first won deal"* before any of them touches a landing page.

## Operationalize it

* The Definition of Done in production: [3.5 — Content production + Definition of Done](/sops/content-production-dod).
* The Quality Gate as an AM discipline: [3.6 — The Quality Gate](/sops/quality-gate).
* Technical DoD checks on a live site: [2.5.2 — Technical SEO audit](/platform/technical-seo-audit).
* Claims-safe compliance edits on landing pages: [2.3.5 — Landing-page refiners / compliance](/platform/landing-page-refiners).