What Navi is

Navi is the company’s governed AI-agent service.

Ask in plain language — in Slack, from a Jira ticket, or on a schedule — and a team of scoped AI specialists does real work across our own systems: code, the data warehouse, monitoring, tickets, Shopify. A human approves anything consequential; every step is on the record.

Not a chatbot that answers — a governed team that does the work, takes one sentence to a finished result, and is accountable for every step.

What it does

One sentence in; finished cross-system work out.

Real requests teams make every day — each would otherwise mean opening several tools, pinging colleagues, and waiting.

Engineering
  • What shipped to prod last week?Changes + linked tickets, in one reply.
  • What caused the 2pm alert?Logs, metrics, deploys → root cause.
  • Implement this change.Plan → code → PR to review.
Data & Analytics
  • GMV last month, top 10 customers?Warehouse query → numbers + chart.
  • Build this recurring report.Compiled and posted on a schedule.
  • Why did signups dip Tuesday?Cross-source pull, summarized.
Operations & SRE
  • Health-check this service, 24h.Heap, GC, CPU, threads → a verdict.
  • Triage this incident.Correlates signals, proposes a fix.
  • Plan the new-database change.Step-by-step plan for sign-off.
Customer Support
  • Reset this buyer’s password.Verifies identity, resets safely.
  • Summarize & update this ticket.Reads the thread, writes it back.
  • What’s this customer’s history?Orders & context in one view.
Triggered from Slack from a Jira ticket or on a schedule

The value add

Why it matters.

01 — Leverage

Hours of legwork, removed.

The cross-system “find it, switch tools, wait on a colleague” tax every team pays daily is cut sharply — you ask once, instead of chasing it across tools and people.

02 — Safe to scale

Governed by design.

Scoped access, human approval on risky moves, and a complete audit trail — so it’s safe to open to everyone, not just engineers.

03 — Compounds

A company asset.

New capabilities are added as configuration, not code, and improve for everyone at once. It outlasts any one person’s laptop.

How it fits — our data, workflows & third-party models

Navi is a layer. It replaces nothing; it governs what we already have.

Our data & systems

It reaches in; it never owns or moves the data.

The warehouse, GitHub, Datadog, Jira and Shopify stay exactly where they are. Navi reads and acts on them through standard connectors. It’s the hands that reach into our systems — not another data store, and not a migration.

Our workflows

It turns tribal know-how into governed, repeatable agents.

The “who do I ask, which tool, in what order” that lives in people’s heads becomes a specialist or a reusable skill — consistent, permissioned, and runnable on a schedule instead of from memory.

Third-party models (Claude, GPT, …)

The model is a commodity engine Navi rents — not what Navi is.

Navi isn’t tied to any one model — it can run on Claude, GPT, or another, and swap to a stronger one anytime. The model supplies reasoning; everything that makes it safe, reliable and governed inside our company is Navi — the harness around the engine.

The model is the engine; our data and systems are the roads and cargo; Navi is the whole governed vehicle. Take the metaphor apart — every part of the car maps to a part of Navi:
Engine
The model (Claude / GPT …)Supplies the reasoning “horsepower.” Off-the-shelf and swappable — drop in a stronger one anytime.
Driver / dispatcher
OrchestratorUnderstands what you want and decides who should do the job. It only routes — it never touches the controls itself.
Working parts & robotic arms
Sub-agents + Tool LayerThe specialists that do the actual work, one job each — reaching out through tools to each system.
Each part’s key
Scope (least privilege)Every part carries only its own key; it can’t open a door it isn’t allowed to.
Brakes
Approval gateBefore anything risky, a human can hit the brakes — it moves only once approved.
Dashcam / black box
Trace (audit)Every step is recorded, so any run can be replayed and accounted for.
Autosave / spare tire
Checkpoints + durable RuntimeStall mid-trip and it resumes from the last save — work is never lost or run twice.
Center console
Config CenterOne console to switch specialists on/off, set scope, swap the model, schedule work — without ever touching the engine.
The roads and cargo are our own data and systems — what the vehicle drives on and carries; Navi doesn’t own or move them, it just reaches them in place. Anyone can buy the engine; the whole vehicle — built around our systems, our permissions, our workflows — is the hard-to-copy part.
Navi is harness engineering, not a model wrapper: inputs from Slack, Jira and schedules flow into the Navi platform — the enterprise control plane that owns the work lifecycle — which calls the model only inside a controlled boundary that has no direct access to our systems.
Navi is harness engineering, not a model wrapper. Navi owns the engineering lifecycle — intent, context, policy, permissions, execution, recovery, audit. The model is a replaceable supplier it calls inside a controlled boundary, with no direct access to our systems.

The boundary & how it collaborates

Navi calls your business systems — it doesn’t replace them.

Business systems — IMS, the order service, and the rest — stay exactly what they are. The logic, the data, the source of truth all remain theirs. Navi doesn’t reimplement that logic, doesn’t hold that data, and never becomes a business system. When a request needs them, it simply calls the system’s own API.

Business systems (e.g. IMS)

Own the logic, the data, the truth.

Each service stays the system of record for its own domain — inventory, orders, payments. Navi never copies it, owns it, or overrides it.

Navi

Orchestrates — it doesn’t hold the business.

It understands the request, picks the specialist, and calls the service’s predeclared API through one governed tool (call_service_api) — then reports back. It has no business logic of its own.

Example — “How much stock is left for this product?”
  1. A Navi specialist calls IMS’s predeclared inventory API via call_service_api.
  2. IMS looks up its own inventory and returns the number — the source of truth stays inside IMS.
  3. Navi relays the result back to Slack.

Navi holds no inventory data and no inventory logic — it just asked IMS on your behalf. And it can only call operations a Skill predeclared (a whitelist); URLs and keys never appear in the conversation, the platform authorizes each call with a machine-to-machine credential, and every call is traced. Governed collaboration — not a takeover.

Navi data-flow diagram: requests enter on the left (Slack, Jira, schedule); Navi in the center — web, durable queue, worker, router, scoped sub-agent — orchestrates and calls each system across a governed boundary; on the right, engineering platforms, third-party business systems and our own business systems each keep their own data and logic.
The full data flow. Requests enter on the left; Navi (center) orchestrates and calls each system across the governed boundary; every system on the right keeps its own data, logic and source-of-record truth — Navi calls them, it never replaces them.

Navi vs. local Claude Code

A personal asset, or a company capability.

Some of us already use Claude Code on our laptops — and should keep doing so. It’s a great personal asset, but a personal asset by nature: it runs as one person, with their access, used by them alone. It can’t stretch to cover the company’s whole business. That’s a different scope — and it’s where Navi lives.

Personal scope
An employee’s local Claude Code — a personal asset
→
Company scope
Navi — AI across the whole company’s business
Claude Code — personal asset Navi — company capability
Who can use it The engineer who set it up Everyone, in Slack — zero setup
Whose access it uses The owner’s full access Scoped per specialist, enforced every action
Who approves a risky action The owner, themselves A human gate; who-asked kept separate from who-it’s-about
If something goes wrong No central trail Every run recorded & auditable
When the laptop’s off It stops Always-on — scheduled & triggered work
The know-how built Stays on the laptop; leaves with the person Shared — compounds and persists
In one line

Claude Code for the individual; Navi for the company. The same engine — made a governed capability the whole business can run on.