AVE Studio · AI Visibility Engineering
CCE · The coherence of your claims
Claim Coherence Engine · GEO + KEO the approved claim ledger
Being found, included and cited when an AI generates an answer — at answer time, from the live web.
Generative Engine Optimization: the definitionThe verified, canonical, readable, citable record AI models learn from — so each new model is trained to know and recall your business correctly.
Knowledge Engine Optimization: the definitionOne page says "15 years", another "since 2010", a third "a decade and a half". The AI can't tell which claim is correct. We consolidate them into one consistent version.
The machine-equity loop — Claim Coherence Engine
- 1 · MEASURE — “Where do I stand today?” Per engine, with a range (Citation Tracker, Selector)
- 2 · FIX — “Why do they skip me?” Page by page, then fixed in code (Gap Analysis, Gap Closure)
- 3 · ANCHOR — “Where does the machine learn about me?” An unambiguous entity, present where models learn (Entity Anchor, Corpus Campaign)
- 4 · PROVE ↺ — “Did it move, and what did it bring?” Closed-book baseline and the delta at every new model generation (Model Memory Audit, Release Audit)
KG Doctor and the Claim Coherence Engine — the studio's own instruments — serve the entire loop.
Machine equity is the business asset that arises from AI systems being able to recognize, understand, recall, recommend — and, on a user's behalf, transact with — a brand. Composed of three layers: rented reach (retrieval visibility), owned memory (trained model recall), and machine buyability (agent-side transactability). Measured honestly only as a portfolio of ranged, per-layer metrics — never as a single blended score.
Machine equity: the definitionAI models try to understand what your company does from the claims found on your website. If the same fact appears differently across pages, the overall picture becomes contradictory and uncertain — and the AI may present you cautiously, or even incorrectly. The Claim Coherence Engine reads your entire website — it only reads, it never modifies — then organizes every factual claim into a single system you approve.
The CCE works with the prose marketing claims on your website. Structured facts — Wikidata, embedded data, profiles — are examined by its sibling instrument, KG Doctor; both feed the same approved fact base.
Collecting the claims
It gathers every standalone marketing claim: exactly what you state about your company, on which page, in what wording.
Proof by source quote
Every claim is paired with a verbatim quote from its source page. What cannot be proven with such a quote cannot enter the ledger.
Consolidating identical claims
Claims with the same meaning but different wording are grouped under one official version. Hungarian and English counterparts are linked as well.
You approve
You can confirm, edit or reject every item. When the system is uncertain, it doesn't decide for you — it asks.
Every service runs on an application we built in-house for exactly this job — not manual spreadsheets, not general-purpose tools.
Our claims engine: extraction bound to verbatim source quotes, deterministic re-runs, and a human approval layer.
The claim ledger is the single, approved, official list of every factual claim about your company. It becomes the company's authoritative fact base, on which all later content work can build — a consistent rewrite, for instance, or copy that's easier for AI to interpret. So the question "what do we claim about ourselves?" always has exactly one approved answer.
Only claims proven by a source quote can enter
Every claim carries a verbatim quote from the website. An invented fact cannot enter the system.
The human makes the final call
What you approved or rejected is never overwritten by a later re-run. Your earlier decisions stand.
The audit is repeatable with identical input
The same input yields the same result. So the audit is verifiable and can be repeated precisely later.
Hungarian and English claims are consistent too
The system also detects contradictions between the two language versions, because the AI reads both.
In the next development phase, the approved claim ledger can drive a consistent rewrite of the website's copy, so that every page tells the same official company story. This is a planned feature; what's available today is the creation of the claim ledger.
This instrument prepares the fact base for these paid modules:
A proprietary internal diagnostic instrument of the studio that powers the paid modules. Not a standalone, purchasable product.
Why sort the claims out now? Every contradictory sentence on your site today will be there in the AI's answers tomorrow — and a model would rather say nothing about you than pick between two conflicting facts. The claim registry is one-off work, but after it every new page and every new campaign draws on the same source.