How it works

Governance built in from the very first word.

GAIA doesn’t scan content once it’s written. Your standards shape each piece as it’s created, anything that falls short is held back, and how it was made is recorded.

01The pipeline

How a piece moves through GAIA.

Your eight areas of governance are set up once. Every piece then follows the same route, from who it’s for to the record that proves how it was made.

02Set up and plan

Every choice is locked in turn.

You choose who the piece is for, and GAIA offers only the options that make sense for that reader. The angle is shaped by what’s genuinely new in your piece and checked against what you’ve already published.

Choosing a persona in GAIA for a financial services blog: the prospective mortgage borrower is selected, with modifiers for financial sophistication and customer vulnerabilityClick to enlarge
A financial services piece written for a first-time mortgage borrower, with the vulnerability lens set.
Three candidate angles for a life sciences article in GAIA: conservative, balanced and innovative, each showing its archive overlapClick to enlarge
Three angles for a life sciences article, each showing how much it overlaps with what’s already been published.
03Write

Checks run while the piece is written.

As the draft takes shape, GAIA tracks readability, similarity to your archive and the risk of generic AI phrasing. Claims that go further than your evidence are marked in place, so they can be fixed before the gate ever sees them.

A draft blog article in GAIA comparing two foundation design codes, with an overstated claim about which code governs highlighted for reviewClick to enlarge
An engineering consultancy’s draft. Two claims that overreach are already marked.
04The gate

Anything that falls short waits at the gate.

Content that doesn’t meet your standard is held at the gate until it does, or until a person releases it with a recorded reason. Nothing reaches “approved” without clearing the checks or leaving a trace of who decided otherwise, and why.

The GAIA publication gate holding a savings article: findings for an unsubstantiated comparative claim and an overstated capital safety claim, each with a jump-to-passage buttonClick to enlarge
Findings are graded by severity, linked to the passage and fixable in place.

A person can always overrule it, on the record.

Sometimes a finding is right to set aside. When it is, the person releasing the piece chooses a reason code and writes a short rationale. Both are added to the audit trail with their name, so every exception can be explained later.

The override dialogue in GAIA, requiring a reason code and a rationale before an override is recorded to the audit trailClick to enlarge
An override needs a reason code and a rationale.
05Sources

Bring a source. Keep it at arm’s length.

You can give GAIA a web page or document to work from. It’s used as background or as something to respond to, never quoted or treated as evidence, and the draft is checked against it for anything repeated word for word.

Adding a reference source to a web page in GAIA, with options to use it as background or respond to itClick to enlarge
Adding a reference source, used as background or to respond to.
06The record

Proof of how every piece was made.

Every approved piece keeps its findings, decisions and rule versions, linked by a chain of cryptographic hashes. It stays with the piece in your archive long after the session that made it.

More on provenance →
An approved web page in the GAIA content archive, showing its persona, tone register, word count, approval date and a link to the full provenance recordClick to enlarge
An approved piece in the archive, with its full provenance record one click away.
07Onboarding

Set up with you, then tested before you rely on it.

GAIA isn’t a blank tool you configure alone. We run a structured intake and hand you a governance configuration that’s been built and tested against your own material.

1

Discovery

A structured questionnaire and your source material: what you publish, the standards it’s held to and the claims you can make.

2

Configuration

We write your governance rules across all eight areas: your voice, your claims framework, your standards.

3

Testing

The configuration is run against your own content and tuned until it holds.

4

Calibration

We review it with you, then lock the version so you know exactly which rules are in force.

Typically two to four weeks, depending on how complex your standards are.

See it working on your kind of content.

Tell us what you publish and what it costs when it’s wrong, and we’ll walk you through how GAIA would govern it.

Book a walkthrough