Gamri
The Gamri Grid

What every finished piece stands on.

Writing is easy now. Getting it right under your business's name is a different job. The Gamri Grid is the structure every piece of Gamri's work runs on. It works from what you approved, looks only where you said, checks every claim, waits for your yes, and keeps a record of what it stood on.

Ask for access See the five parts

In one paragraph

Work that goes out under your name has to be right, and a capable model on its own can't promise that. The Gamri Grid adds the five things it's missing: one approved version of what's true, sources you assigned, a check of every claim against the evidence, your approval before anything leaves, and a permanent record of what each piece stood on. Each part is enforced by the system itself, not requested in a prompt and hoped for.

The result is work you can hand to a customer, and an answer ready for the day someone asks why it said what it said.

1place for what your business stands behind, approved by you
0emails to customers sent without your approval
Everyspecific claim checked before you see it
Everyrun on the record, down to the exact version
Why it exists

Fluent is not the same as right.

Today's tools made your business's knowledge easy to reach. None of that decides which version is the real one, keeps it current, or shows afterward what a piece of work relied on.

Three versions of one price

Point an assistant at your files and it finds last year's rate card, this year's, and the special that ended in May. Finding them is easy. Knowing which one counts is the job.

A fact that quietly expired

Holiday hours, a promotion, a policy you changed. The old version keeps getting repeated, confidently, long after it stopped being true.

No answer to "why?"

When a customer disputes what they were told, "the assistant said so" isn't an answer. You need to see exactly what it was working from at the time.

Search finds things. It doesn't decide what's true.

The five parts

Five parts. One structure. Every piece of work.

Each part answers a question an owner would ask before putting their name on something. Each one is backed by a mechanism, not a promise.

01 · True

One approved version of what's true.

Your prices, policies and facts, approved by you and in front of every piece of work.

What you get
One place for what your business stands behind, read by every teammate on every job. A fact can carry an end date, so a promotion stops being quoted the day after it ends. If two of your facts disagree, you're told.
What holds it
Only a person approves a fact: you, or us when we run it for you. Nothing the team writes becomes one. Facts for one client stay inside that client's project. If your facts outgrow what one piece of work can carry, it says which ones were left out rather than dropping them silently.
02 · Sourced

It looks only where you said.

Each teammate works from the sources you assigned, and nothing else.

What you get
Answers drawn from your documents, your inbox, your apps, your form responses, and the web only if you allow it.
What holds it
When those sources don't have the answer, it asks you before looking anywhere else. It never fills a gap from general knowledge, and nothing it wrote can come back to it as a source.
03 · Checked

Every claim, read against the evidence.

A separate judgment model reads the work before you do.

What you get
Each requirement of the request, and each specific claim (a price, a date, a figure), checked against what was actually found and against your approved facts.
What holds it
Anything that doesn't hold up gets one more look or one revision. After that, the reply names plainly what's still open. A price, date or link with no source behind it is refused at the moment of sending.
04 · Held

Nothing leaves without your yes.

Every email to a customer, every post, every change in another system waits for you, showing the exact words.

What you get
One place for everything that's waiting on you, on screen or on your phone. The only steps that go ahead unasked are routine ones you chose to trust, such as clicking through a site you use every week.
What holds it
What you approve is what goes out, replayed exactly and never written again after you said yes. Anything destructive always asks, and no setting can turn that off.
05 · Recorded

A record of what it stood on.

Under every answer: which of your facts it used, and which it couldn't.

What you get
The answer to "why was this customer quoted that?" months later, as a lookup rather than a guess.
What holds it
Before the work starts, each run records the exact version of every fact, guideline and setting in front of it. Your facts and settings are kept with their full history, so every version can be traced to when it was approved, and by whom.
The record

Every piece of work comes with its evidence.

This is what one run keeps: the facts it worked from and their versions, where it looked, what the check found, and who said yes.

Quote for Blake Boats · Jim, CEOOct 3, 10:42 AM

Your facts in force

  • UsedRate cardversion of Sep 14
  • UsedAbout the businessversion of Aug 2
  • Ran out May 31Spring commissioning specialnot used

Where it looked

  • AssignedYour shared files: service menu

The check

  • SupportedAll 4 prices trace to the rate card

Your yes

  • ApprovedSent to Blake Boats exactly as you read it

An illustration of what one run's record holds. The record itself is kept with every conversation.

The difference

Most tools hope. The Gamri Grid holds.

The same request, handled the usual way and on the Gamri Grid.

The usual way
On the Gamri Grid
Finds text that looks relevant in your files.
Uses the version you approved, and says what it left out.
Follows the instructions in a prompt, most of the time.
Enforces what matters in the system itself: a gate, not a request.
Leaves the checking to you.
Checks every claim before you see it.
Sends when it thinks it's done.
Waits for your yes whenever something leaves.
Keeps a log of what happened.
Keeps a record of what each piece stood on, by exact version.
Found isn't approved.Your approval decides what counts.
Asked isn't enforced.The rules that matter are gates.
Logged isn't accountable.The record names what it stood on.
Plainly

What the Gamri Grid claims, and what it doesn't.

A system about being right should be exact about itself.

It does

  • Work only from the facts you approved and the sources you assigned.
  • Check each specific claim against what was found before you see it.
  • Hold every email, post and outside change for your yes.
  • Record, for every run, the exact versions it was working from.

It doesn't

  • Read a model's mind. The record shows what the work was given, and the check is what holds the work to it.
  • Ask you to learn a rules language. Facts are plain sentences you write.
  • Decide for you when two facts disagree. It tells you, and you choose.
  • Train a model on your work. Gamri trains nothing.
How we work with you

Accelerating your intelligence

Every organization on the Gamri Grid gets onboarded and aligned to your outcomes. We will support you every step of the way for ongoing success.

Included with every account

Managed support

You and your team work with it every day and approve what goes out. We look after everything underneath: the setup, the tuning, and keeping it running.

When you want more

Fully managed

We run the work as well: your inbox, quotes, reports and posts, on your Gamri Grid. You approve each piece in the app or on your phone, and get finished work without managing a thing.

Every account is supported!

Set up with youWe onboard you ourselves, so your prices, facts, voice and sources are in place before the first job.
Tuned to your businessWe adjust it until the work sounds like you and gets your details right.
Kept running smoothlyWe stay with you after launch, and when something needs attention, we take care of it.

Put your business on the Gamri Grid.

We're welcoming a few businesses at a time and setting each one up by hand. Tell us what you do and what you'd like to hand over.

Ask for access