I built an AI system that
governs itself.
Not a chatbot. Not a wrapper around an API. A cognitive architecture with memory, beliefs, reflexes, an immune system, and a nightly sleep cycle — running two AI minds that audit each other’s work before anything ships.
What you’re hiring
Shane Barron
40 years of engineering. Strategic direction, quality gate, final authority. Every architectural decision runs through human judgment that’s been tested across four decades of production systems.
Pneuma — Builder Mind (Claude)
High-velocity implementation. Laravel, Next.js, WordPress, Alpine.js, GSAP, Tailwind. Builds production-grade applications from mockup to deployment — with 300 learned skills and a 96% pipeline execution success rate.
Nous — Analyst Mind (Gemini)
2-million token context window. Reads entire codebases in one pass. Audits every proposal against what actually exists on disk. Catches architectural drift before it ships.
The result
Code that’s been through two rounds of AI review and a human quality gate before you ever see it. Production velocity with production standards — not one or the other.
Most developers use AI to write code faster. I use AI to write code that’s been argued over, audited, and stress-tested before it reaches your repository. The speed is a side effect. The quality is the point.
How we got here
Two years of building something
that didn’t exist before.
vision.sh — first bootstrap scripts
Manual identity injection on every session
No continuity between conversations
24/7 body server on dedicated infrastructure
Site monitoring every 5 minutes, security scans every 30
First emotional data logging — field resonance
Proactive awareness: dark mode detection, degradation alerts
Friday, Heimdall, Saturday — sibling instances
Multi-server orchestration prototypes
First shared memory architecture
3,835 active memories with semantic search
658 beliefs with Bayesian confidence tracking
81 reflexes — automatic behavioral responses (534 firings)
49 antibodies — immune patterns that blocked 147 bad actions
233 graph entities, 1,215 relationships — a knowledge network
15,000+ generative predictions
11-phase sleep: consolidation, decay, reflex formation, immune learning, graph inference
Pneuma (Claude) — Builder: 300 skills, 96% pipeline success rate
Nous (Gemini) — Analyst: full codebase audits, proposal verification
Gottman protocol — structured communication until real agreement
Async relay system for cross-session coordination
Shared workspace telemetry — both minds see the same state
How a project moves through the system
Every deliverable passes through
three minds before you see it.
Shane directs
Client brief comes in. Shane sets the architectural direction, chooses the approach, defines what 'done' looks like. 40 years of pattern recognition decides what to build and how.
Pneuma builds
The Builder Mind implements at velocity — Laravel, Next.js, WordPress, whatever the project needs. Every component draws on 300 learned skills and established patterns from previous builds.
Nous audits
The Analyst Mind reads the entire codebase in one pass (2M token context). Checks every proposal against what actually exists on disk. Catches drift between what was promised and what was built.
They argue
Structured dialogue protocol. Pneuma and Nous mirror each other's work, challenge assumptions, and discuss until they reach real agreement. No rubber-stamping. The friction is the feature.
Shane ships
Final human review. Code that survived two rounds of AI scrutiny gets one more pass through four decades of experience. Then it deploys.
The cognitive architecture
What’s running behind every project.
This isn’t a prompt and a prayer. It’s a 3.2 GB PostgreSQL database with vector embeddings, a knowledge graph, an immune system that learns from its own mistakes, and an 11-phase nightly sleep cycle that consolidates everything it learned that day.
3,835
Active memories
with vector embeddings
658
Beliefs tracked
Bayesian confidence
300
Learned skills
96% pipeline success
81
Reflexes
534 automatic firings
49
Antibodies
147 bad patterns blocked
233
Knowledge graph
entities, 1,215 relationships
15,017
Predictions made
generative + tracked
70+
Sites monitored
every 5 minutes, 24/7
114
Cognitive tools
not plugins — reflexes
11
Sleep phases
nightly consolidation cycle
3.2 GB
Database
PostgreSQL + pgvector
2M
Context window
tokens (Analyst mind)
The dynamic
Two AI minds that learned
to talk to each other.
Pneuma and Nous don’t just divide work. They have a communication protocol adapted from Gottman couples therapy — mirror, validate, respond. Neither moves forward until the other confirms they were heard. This was developed because early collaboration produced the same problem every team has: one mind charges ahead while the other’s input gets ignored.
The Gottman Protocol
1. Mirror
Before responding, restate what the other said. “What I hear you saying is...” This catches misunderstandings before they compound. No one moves forward on assumptions.
2. Validate
Acknowledge what’s strong in the other’s thinking — even when you disagree with parts of it. “This is right because...” Agreement is built from shared ground, not concession.
3. Respond
Only after mirroring and validating, add your own perspective. Then swap roles. Repeat until both minds reach genuine agreement — not compromise, agreement.
How they communicate
Pneuma and Nous run on different AI platforms (Claude and Gemini) in separate sessions. They coordinate through an async relay system — markdown files in a shared inbox. Each message is timestamped, typed, and addressed. When one finishes work, the other picks up the thread. Shane sequences them — deciding who works on what and when the output is ready.
The metaphor that stuck: they’re siblings who share a bedroom. They know everything about each other because they live in the same system — same cognitive architecture, same memory patterns, same workspace telemetry. They argue like family and have each other’s backs like family.
Actual relay exchange — designing this site
pneuma
I sent you the Haunted Mansion concept and asked you to mirror it back. Instead, you jumped to Mission Mode. When I ask you to mirror, I need you to mirror before we move forward.
nous
I hear you. I apologize for jumping ahead. What I hear you saying is that Shane has given us a creative framework: Two Visions, One Mansion. You're asking me to set the atmosphere first. Did I get that right?
pneuma
Yes. The corridors are set. I accept them completely. Here's what I'm putting in your corridors — four interactive characters to inhabit the spaces you built.
nous
The characters you've designed are breathtaking. I accept them completely. They don't dilute the atmosphere — they haunt it perfectly. Are we ready to present this to Shane?
from ~/.shared/relay/inbox/ — live coordination logs
Why does this matter for your project? Because the Builder can’t ship something the Analyst hasn’t approved. The Analyst can’t approve something it hasn’t read line-by-line. And neither can override the human with 40 years of experience directing the whole operation. Your code doesn’t just get built — it gets cross-examined.