Seven practical
AI patterns

What I do

navarre.ai

FileMaker
since 1987

Certified on every version.

Matt Navarre

FileMaker is the
source of truth

The system of record.

AI reads, sorts and writes words. It does not own your data.

The seven

A tool that runs
beside FileMaker

Almost nothing in your file

One container

100% of the code
is maintained by prompts
in Claude Code

Anywhere Docker runs

What this makes possible

Semantic search.
Then and now

Find what you meant, not what you typed.

All in FileMaker. Two paths

Easy

Fuller

Enrichment

One to one. Many to many

What you carry

Fly does the work in a Web Viewer

Docker · container · Fly

What it asks of you

Every step is a switch

Combine them per table. All on is not the goal.

Pro and con

Let’s install

It asks for a name, then it builds.

Unlimited extension.
It is your code

Mitos: unlimited new features

with Claude Code, or Codex, or any coding agent

What I will build, live

It reads the repo first. It waits for my word before any deploy.

It learns from clicks

Ask your data.
Reports are just the start

Beside the file

Pro and con

Let’s install

It asks for a name, then it builds.

Clio

Logs. Boring.
Let’s see what this AI thing is, though.

You commit
a record

One trigger.
The whole file

It hands you
the changes

{ "Sales" : {
    "Invoices" : [
      [ "Modified", 4211, { ... } ],
      [ "New",      4212, { ... } ],
      [ "Deleted",  4108, { ... } ]
] } }

The { ... } is yours

JSONSetElement ( "{}" ;
  [ "id" ;          Invoices::ID ;         JSONString ] ;
  [ "total" ;       Invoices::Total ;      JSONNumber ] ;
  [ "status" ;      Invoices::Status ;     JSONString ] ;
  [ "modified_by" ; Invoices::ModifiedBy ; JSONString ]
)

One script sends it

Pro and con

Or pick
your spots

Layout by layout. Field by field.

No trigger.
Just the call

Then the useful part

What you add
to your file

“Three, sir!”

Let’s install

It asks for a name, then it builds.

Deep in the record.
Up on the surface

It reads the whole tree and tells you what matters.

It never makes you wait

A fixed shape,
every time

{ "summary":  "one sentence a human would say",
  "odd":      ["values that do not fit the rest"],
  "missing":  ["fields a record like this usually has"],
  "next":     ["what to do about it"] }

Surfaces
useful info

A data entry assistant.
Paste, and it fills

Every field that can be set, is set. You check it.

Your fields drive it

It takes what is relevant.
It ignores the rest

Automation.
The Aletheia preview

Super early.

She runs the work you give her

Every run tracked. A super early preview.

Aletheia, as you type

And while nobody is there

A rule is data

{
  "field": "State",
  "check": { "type": "pattern", "pattern": "^[A-Z]{2}$" },
  "fix":   { "type": "map", "map": { "New Jersey": "NJ" } },
  "mode":  "auto",
  "minConfidence": 1
}

You pick the trust

Every run
leaves a reason

{ "at": "2026-08-25T09:41:02Z", "rule": "org-state-usps",
  "field": "State", "old": "New Jersey", "new": "NJ",
  "why": "known replacement", "confidence": 1, "mode": "auto" }

And five more jobs

Ideas, not built yet.

Remember
the build?

It worked while we talked.

Four tools, one shape

Same install, same posture: beside the file, never inside it.

Let me help you

navarre.ai