YOU HAVE LEFT THE DRAWING. THIS IS THE MACHINE — AND I INSTALL IT FOR BUSINESSES LIKE YOURS. DETAIL B — OPERATOR CONSOLE · SCALE 1:1
guest@pn-os:~ $ evc --install your.business

AI systems for your business,
installed.

Your investors say "we need an AI strategy." I turn that mandate into running systems — brand canon your agents can't violate, content engines with human gates, quality hooks that catch slop before it ships. Built on EVC, my open-source framework. À la carte: I install it, train your team, and leave you owning it — or stay on retainer and run it.

B1

The content engine, traced.

one cycle · human gates marked

Every piece of outbound content runs this chain. The gates are the point: the machine drafts, the operator decides. Nothing auto-posts. Ever.

B2

À la carte, fixed scope, no retainer trap.

pick the mode · upgrade later

Most protocols don't need a head of AI in the marketing org — they need the systems that role would build, installed and documented. Start with an install; add operation only if you want it run for you.

MODE
Engagement
What you get
Terms
M-1
System installcontractor · fixed scope
Canon built, engine configured, hooks armed, team trained — you own everything when I leave
FIXED SCOPE · 4–12 WKS
M-2
Operate on retainerthe system, run for you
I run the installed engine — weekly production, QA gates, reporting to your exec team
MONTHLY RETAINER
M-3
Fractional CMOsystems + marketing leadership
The full operator: AI systems underneath, GTM and brand leadership on top
MONTHLY · 3–6 MO MIN
M-4
Full-timeprotocols & scale-ups
The whole drawing set, in-house
LET'S TALK

Rates are published — full schedule and process at The Desk →

B3

Field output — two systems, one operator.

real templates · real installs

Both built as M-1 installs: canon first, design system second, template library last. Two completely different brand languages, produced in parallel by one operator — the agents do the grunt work; the gates keep the brand safe.

INDEPENDENT INSTALLS — BUILT UNINVITED ON PUBLIC BRAND FOUNDATIONS TO PROVE THE METHOD · YOURS WOULD BE BUILT WITH YOU EACH: 1 CANON · 15+ TEMPLATES · WEEKLY CADENCE — INSTALLED IN WEEKS, NOT QUARTERS
B4

System readouts.

verified · inspect the source
42
Production commandsmarkdown playbooks, composable
8
Workflow chainsmulti-stage, gate-checked
6
Quality hookscanon · slop · commit · audit
3
Live deploymentsacross client brands

"Open source" isn't a slide claim — it's an invitation to audit. The framework is MIT-licensed and public: read the hooks, run the setup, fork it. An operator whose infrastructure survives inspection is the proof the drawing promised.

$ git clone github.com/SaigonXIII/evc ↗
Back — A4
FIAT Chrysler × Canada
Detail
B — OPERATOR CONSOLE
Scale
1:1 — FULL
License
MIT
Uptime
SINCE 2011
© 2026 Peter Nguyen The machine drafts — the operator decides Source ↗ · Sheet 1