01 / STRATEGY
Set
direction.
Find the valuable problem. Decide where AI belongs, what to build, and what a better result looks like.
Find the opportunity JUDGMENT BEFORE TOOLSThink bigger.
Make it real.
AI strategy.
Working systems.
A partner who can lead and build.
Ideas, made real.
Products. Worlds. Working things.
Different ways to make an idea real.
From specification to sales tool
3D product visualization / client work
NASA / Machine Atlas
Interactive atlas / cinematic
Second Brain
Knowledge graph / tool
Bayit Brew
Cinematic website / concept
Coin-Op Revival
Editorial website / concept
CLAUDE · GPT-5.6 · GROK 4.7 · HERMES AGENTS · MCP SERVERS · EVALS · RAG · AGENT FLEETS · VOICE AGENTS · COMPUTER USE
Most companies don't have an AI problem. They have a clarity problem. I find the one workflow worth changing, build the system that changes it, and stay until your team runs it without me. Strategy you can act on. Systems that actually ship.
I don’t demo AI.
I run it.
Hermes agents, Grok bots, Claude Code, Codex, and ChatGPT share one context and work inside guardrails I set. This is how the system fits together, and, when the feed is live, what it is doing right now.
Illustrated system · live signals when available
Live feed offline · illustrated system
Explore the system using the node list below.
Every node, in words
The same system without the 3D view. The illustrated nuclei stand for five families of agents, not a measured headcount.
Agent families
- Hermes agents are my long-running workers. They carry context from one day to the next and keep a task moving.
- Grok bots get one defined job and clear boundaries: watch this, research that, report back.
- Claude Code plans, builds, and reviews changes in my codebases, then leaves a handoff for whoever picks it up next.
- Codex builds from a tight written plan and gives me a second opinion on risky work.
- ChatGPT is where I think out loud: questions, plans, and decisions worked through in conversation.
Shared system
- Every agent reads from and writes to one shared context: my notes, decisions, and handoffs. That is how a whole fleet stays one system.
- I route work across GPT-5.6, Claude Fable 5.1, Claude Opus 5.5, and Grok 4.7. The model reasons; the agent manages the task.
- Command Deck is my hub. Every agent logs its work there and reads the decisions I make.
- Tools connect through MCP, so an agent can take the actions I have allowed and nothing else.
- Risky work gets checked by a different model before it moves forward. Two sets of eyes catch different mistakes.
- I sign off on anything irreversible. An agent never gets to grant itself permission.
- Automated checks watch for defined failures and flag what needs my attention.
- Encrypted copies live off the machine, so recovery is part of the design, not an afterthought.
Request and checkpoints
- It starts with a clear request and a picture of what a useful result looks like.
- The agent gets a bounded task. It gathers context and coordinates the next steps.
- I decide what the agent can access and change. Those limits are enforced by the system, not requested in a prompt.
- I test the behavior on concrete examples, including the ways it could fail.
- It ships after the checks and approvals, with a handoff note so anyone can pick it up cold.
Business judgment.
Builder's hands.
20Years at Verizon
450+People led
CSOAt Netcom today
Different problems.
Work that speaks.
The best proof of how I think
is what I've put into the world.
The right direction.
Then the work.
Start with the business. Choose the shape of the work.
Set
02 / BUILD
Make
it real.
A product, agent system, or workflow your team can use. Build the first version, learn from it, and make it better.
Bring a build FROM POSSIBILITY TO USE03 / LEAD
Stay
involved.
Connect strategy, adoption, and the next decision. Ongoing advisory or embedded leadership, close to the work.
Talk about a partnership ONE ACCOUNTABLE PARTNERA focused build. A trusted advisor. An embedded strategy partner.
We choose what fits the problem.
PAUL TAKISAKISPOKANE, WASHINGTON
Business
judgment.
Builder’s hands.
I spent 20 years at Verizon, from a mall kiosk to leading a national organization of 450+ people. Today, I’m Chief Strategy Officer at Netcom.
I know the distance between a good idea and a business that can use it. My work connects the strategy, the build, and the people who make it matter.
A little more about meLet's build
what comes next.
Bring the business challenge.
Let's find the next move together.