02 · working software, not workflow slides

AI systems & consulting

Agents, retrieval, MCP servers, automation that survives contact with production. I build AI that does a job — scoped tight, instrumented, and cheap to run — and I'll tell you plainly when you don't need it.

the concierge answering below and the mcp server agents call are both running on this page's own stack · scroll — the instrument is live ↓

the instrument — the concierge — ask this site about the work

live — same stack this service sells

concierge — preview

> can an agent book a discovery call with you?

tool · calendar.check

next opening surfaced from the live calendar

tool · scope.draft

three-line brief drafted from your message

tool · call.book

booked — invite issued to both sides

that was the canned preview — the live seat is below

● live — the concierge holds this seat

the work — manifest

  • w-01

    Custom agents and assistants wired to your real systems — bookings, catalogues, support, operations.

  • w-02

    MCP servers that make your product usable by the agents your customers already run. This site is one — four live tools.

  • w-03

    Retrieval and content pipelines: your data, structured, queryable, and fresh.

  • w-04

    Guardrails as a first-class feature: grounding, rate buckets, spend caps, injection resistance — tested adversarially before launch.

  • w-05

    Sober consulting: model choice, cost ceilings, evals, failure modes — decided before the build, not after the bill.

method — how it runs

01

name the job

one week of discovery ending in a working prototype or a written 'don't build this'. The second outcome is cheaper and delivered just as proudly.

02

ground it

the system answers from your data and refuses beyond it. Facts documents, retrieval, and tool access are scoped before a single prompt is written.

03

cage it

rate buckets, spend ceilings, kill switches, adversarial testing. The failure modes are rehearsed before customers find them.

04

hand it over running

deployed, documented, instrumented — with the logs and budgets visible to you, not just to me.

manifest — what lands on your desk

jm/ai·02

  • 01

    a working system in production, not a proof-of-concept in a folder

  • 02

    an MCP surface where it earns one — your product, callable by agents

  • 03

    guardrail suite: caps, buckets, kill switch, injection tests

  • 04

    cost model + logs you can read without me

  • 05

    a written 'don't build this' when that's the honest answer

signed — one operator, no handoffs

05 items

proof — on the record

the concierge — live on this page

live

grounded in site facts, sealed identities held under direct injection, pricing routed to a human. Ask it something.

this site's mcp server

live

four tools live over streamable HTTP — grade_site, site_map, ask_concierge, contact_channel.

the bench

agent-ready grader

on record

the scoring instrument at /lab — engine, verdict model, and abuse guards all part of the exhibit.

run it

self-audit

agent-ready grader

live

run it at /lab

mcp tools

04

public — /api/mcp/

corpus

222→0

retired into the field

build

p5

hardening pass

your visit — measured on you, just now

ttfblcpinpawaiting inputcls

compiled from c2660ba · 2026-08-26 16:14 utc · push = ship


Jamie McKaye — technical SEO, AI systems, full-stack build, technical writing. One person, no handoffs.