A framework and prototype set for turning single-purpose agents into teammates — with identity, initiative, shared context, and a trail people can actually inspect.
01 — Context
Ask, answer, done. That loop is useful, but it can't carry work that runs across days, people, and systems. So I started with a simple question: what would it take for an agent to earn a seat on the team?
So what
The gap isn't intelligence. It's everything around the intelligence — memory, initiative, handoffs, and proof.
02 — Framework
It knows who it is. It speaks up first. It works with other agents. It shows its work. Each one costs something real to build, and none of them work on their own.
So what
Showing its work is the cheapest to build and earns the most trust. Identity is the most expensive — and everything else leans on it.
03 — Proof
When a store is suddenly short-staffed, the autopilot recognizes the staffing problem, pulls the right context, recommends coverage, and keeps the manager in control instead of making them chase status.
Open this scenario full screen ↗So what
One agent held the thread across six tools. The people made decisions instead of chasing status.
03 — Proof
The moment someone is hired, the same agents coordinate setup, a tailored first week, and a briefing for their manager — so everything is ready before the new person walks in.
Open this scenario full screen ↗So what
None of this needed new technology. It's information the company already had, gathered by something that understands the job.
03 — Proof
When the same kind of question keeps spiking, the system treats it as a signal rather than more work. It adapts its answers, and it tells the people who should know.
Open this scenario full screen ↗So what
Noticing the pattern is the work. Answering the questions one at a time is just triage.
04 — Risk
The four qualities only work together. On its own, each one fails in a way people spot straight away.
So what
Identity first, then the paper trail. Initiative before either of those is just software watching you work.
05 — Craft
I wrote it first, then designed it, then built it — handing each step to whichever tool was best at that part.
So what
Being able to build the thing changed the argument. People stopped debating the idea and started using it.
06 — Reflection
It was deciding what a teammate should actually feel like. The four qualities became my test for every decision: if a feature didn't add identity, initiative, teamwork, or a trail, it didn't belong. That one constraint is why the prototypes took weeks instead of months.