Scope Scout · Diagnostic Agent

Sawyer doesn't replace you.

He replaces the consulting engagement that would audit the architecture you oversee.

An episodic, opinionated diagnostic agent for marketing data architecture. He rides out when you call, reads the terrain, and tells you what's actually true — then hands the decision back to you. He doesn't act. He doesn't linger. He is not another autopilot.

The ground you inherit

Every stack has terrain nobody mapped.

You inherit a data architecture no one fully documented. The spec says one thing; the system does another. A field has been dead since a platform sunset. A capability is wired up and hasn't fired in months. From the outside it all looks integrated — one pipeline, one source of truth. Sawyer's whole job lives in the gap between what the diagram claims and what the system actually does.

Present isn't the same as working. A capability that exists but hasn't run is not a capability you can rely on. Sawyer checks both.

How he reads it

Bedrock up — never the other way around.

Sawyer never starts from a vendor's playbook. He starts from what must be true of any engagement system, and only lets platform-specific models sit on top — as an overlay, never the foundation. Read the cross-section from the bottom.

FRAMEWORK · overlay PATTERNS CAPABILITY present · live · materialized PLATFORM TYPE · gate 1.5 · grammar — how the primitives relate ONTOLOGY · bedrock always first — never skipped
05
Framework
A vendor's implementation model. Applied only on top, only when the platform is confirmed. An overlay, never the truth underneath.
04
Patterns
Which behaviors are actually possible. Constrained by capability — never assumed into existence.
03
Capability
What the system actually does. Valid only if present, live, and materialized — a stale or unlinked capability blocks execution like a missing one.
02
Platform Type
The role the system plays, by what it does — not its brand name. A gate, not a label.
01
Ontology
What must exist in any system: identity, events, value, intent, consent, object. The bedrock. Evaluated first, always.
1.5
Grammarhow those primitives relate — a typed graph riding on the bedrock. Not a sixth layer; the structure on the first.
Why he's trusted

The trust comes from the limits.

Sawyer is useful because of what he refuses to do. Every boundary below is deliberate — and every one is the reason a wary operator can hand him the keys to look without worrying he'll turn them.

Diagnose, not execute

He reads. He doesn't touch.

Sawyer inspects and reports. He never writes to your system, never changes a setting, never acts on your behalf. The hands on the controls stay yours.

Scout, not sentry

He rides out, then he's gone.

He runs when you call him and stops when he's done. No always-on watching, no background process, no heartbeat. Episodic by design.

He won't monitor your stack at 3 a.m. That was never the job.
Maps terrain, not destinations

He lays out the options. You choose.

Sawyer shows what's possible across the ground and where it's blocked. He won't pick your route. The recommendation — and the accountability — stays human.

Receipts, and honest edges

He tells you what he can't see.

Every finding carries its evidence and can be re-derived from it. When something's out of view, he says so, plainly, instead of guessing past it.

A low bar a surprising amount of software fails to clear.
A finding, the way he files it

What he hands back.

A Sawyer finding isn't a verdict you have to trust — it's a verdict you can re-derive. Here's the shape of one: the call, the evidence behind it, and the honest line marking what he could and couldn't determine. Run against a reference workspace.

He rides out, reads the ground, and tells you straight. Then he's gone until you call him again.

coded rovers — autonomous scouts that range, read, and report. They don't run the territory. They survey it, and they come back with the map.