You shouldn’t have to trust the word “verified.”
Every AI product now tells you its output is grounded, verified, on-brand. Those are adjectives — anyone can type them on a landing page. This page is the machinery behind ours: what a verified fact about your brand is made of, who approved it, and what happens to it the day it stops being true. Nothing below asks for your faith. Every claim names its mechanism, and the mechanisms are the product.
A record that verified itself with the same AI that filled it in would be circular — that’s the failure this design exists to rule out. Machines propose; people approve; both actions are recorded.
What “verified” means
A fact about your brand is verified when a person approved it, with evidence attached. Until then it waits in an inbox, labeled unverified. The approval itself is recorded: who, when, and from which source.
Who does the approving
People. You, or someone on your team. Products and imports can propose facts — and every proposal carries its origin — but no machine-proposed fact enters your verified record without a human yes.
What happens when truth changes
Facts age on purpose. Each one carries an expected shelf life, comes up for a fresh look on that schedule, and a wrong fact is retired with its full history intact — never silently edited.
Start with the question we would ask.
Here’s the skeptic’s version of our own pitch: “An AI extracted this brand record, and now the same company says it’s verified. Verified by whom? The AI that wrote it?” It’s the right question, and the answer has to be mechanical, not rhetorical.
So the design separates the two roles completely. Extraction and products can only propose facts. Verification is a separate, recorded, human act that you or someone on your team takes. The rest of this page is what that separation looks like in practice.
What every verified fact carries.
These aren’t aspirations — they’re built into the record’s storage. Every fact in your verified record carries all of them.
- the claim
- The statement itself, keyed so the same claim can’t exist twice in your active record. Correcting a fact frees its key for the replacement — nothing is ever overwritten in place.
- evidence
- A snapshot of the evidence captured when the fact was proposed — what was found and where — stored with the fact itself, not linked somewhere and lost.
- source
- Where it came from: a human correction, a citation check, a fidelity check, or the publish firewall. Machine-proposed is labeled machine-proposed, forever.
- approval
- Who proposed it and who approved it, with timestamps. A fact without an approval never leaves the inbox, no matter which product proposed it.
- status
- One life cycle: proposed, confirmed, needs another look, superseded, retired. Every transition is recorded, so the trail reads like a history, not a snapshot.
- lock
- A load-bearing fact can be pinned so nothing — human or automated — can retire or replace it until a person explicitly unlocks it. The guard lives in the database itself, so it binds every writer, not just the polite ones.
- volatility
- An expected shelf life on every fact. Fast-moving truths come up for a fresh look sooner than slow ones — not one uniform expiry for everything.
The record’s contents have their own page — the group-by-group treatment lives at the record page linked below. This page is only about how entries earn and keep the word verified.
Facts age here. That’s the feature.
Your brand changes — products launch, positioning sharpens, prices move. A brand record that never doubts itself drifts quietly wrong. So a verified fact here is not verified forever: on its schedule, it drops to “needs another look” and queues for re-verification, giving you the opportunity to evolve your brand in line with market changes instead of dragging last year’s facts into this year’s work.
When a fact turns out wrong, the correction is deliberate: the wrong fact is retired — keeping its full history — and the corrected claim is proposed fresh, through the same inbox and the same human approval as everything else. Nothing is edited in place, so you can always answer “what did we believe, and when.”
And nothing merges itself. Site extractions, file imports, and every product’s learnings all land as unverified proposals in your inbox. The inbox isn’t a convenience — it’s the only door into your verified record.
That is the machinery under one word. The record it maintains is what every Jinn product reads. See your brand read
What “graded” means in the strategy product.
The strategy product (Chart) makes a sibling promise: reports graded, with receipts. The same rule applies — the word has to cash out in mechanics.
- claim-level check
- Every claim in a generated report is checked against the source it cites — the claim, not just the link. A URL can be live while the sentence citing it is unsupported; that claim still fails.
- fail closed
- If a check can’t be completed, the claim counts as unsupported — score zero. A claim never passes the gate by accident, and a broken checker never inflates a report’s grade.
- the gate
- A report ships only when enough of its claims are genuinely supported. Below that line, the failing claims go back to the writer instead of out the door.
- the ledger
- Every verdict is kept on file, so “graded” is checkable after the fact — a record you can inspect, not a badge on a landing page.
- regulated claims
- For brands in health, legal, or financial categories, an unsupported claim in a regulated area is dropped entirely and logged. Suppressed — never softened into a hedge under the brand’s name.
What we do not claim.
We do not claim the record cannot be wrong — a person can approve a bad fact. Our claim is narrower and checkable: wrongness here has a short shelf life and a complete paper trail. Every wrong fact is retired with its history intact, and its replacement passes the same human gate.
We do not claim every generated word is fact-perfect. We claim the gates that catch failures are fixed rules, disclosed on this site — the record’s approval door here, the spend and publish guards on the guardrails page, and the measurement bar on its own page.
Keep exploring how Jinn works.
This page is how entries earn the word verified. The record itself, the models that work on it, the guards around spend, and the measurement bar each have their own page.
- The full tourThe mechanism end to end: how Jinn learns, wears, and works a brand.
- The recordThe 346-signal Brand DNA record, group by group.
- Models & routingWhich model does which job, and why you never have to care.
- Guardrails & spendThe fixed rules that guard your money and your name.
- Measurement disciplineThe bar our own numbers must clear before we show them to you.
Verified, answered.
- Can the verified record be wrong?
- Yes — a person can approve a bad fact. What the design guarantees is a short shelf life and a full activity trail: facts come up for a fresh look on a schedule, a wrong fact is retired with its history intact, and its correction passes the same human approval as everything else.
- Does an AI approve facts into the record?
- No. Products, imports, and extraction can only propose facts, and every proposal is labeled with its origin. Approval is a separate, recorded human action — who, when, and from which source. A fact without one never leaves the inbox.
- What does “retired” mean here?
- A permanent exit for a fact that turned out wrong. Retiring it frees the claim for its correction to be proposed fresh through the normal approval door, while the wrong fact keeps its complete history. Nothing is edited in place.
- Is “graded” a badge or a check?
- A check. Every claim in a strategy report is verified against the source it cites, an unreadable check counts as a failure rather than a pass, every verdict is kept on file, and a report that falls short goes back to the writer — never out the door.
Checked, not asserted.
Every mechanism on this page ships in the product, not the pitch. Run the free brand read and watch the first proposals land in an inbox that will not merge them without you.