Subject
Agent Infrastructure
Build teams of AI agents that coordinate, remember, and ship — without you in the loop.
Section 1
Agents that remember together, work better together. Identity, memory, and soul for AI agents — the shared memory layer that follows the agent across harnesses. Runs standalone or as part of a TPS office.
| Identity | Ed25519 keypair per agent; every read and write signed |
| Memory | Semantic search, in-process embeddings, no API calls |
| Soul | Persistent personality, values, and procedures |
| Harnesses | 11+ surfaces — Claude Code, Cursor, Codex, Gemini CLI, OpenClaw, LangGraph, n8n, Hermes, Pi, more |
| Bridges | Import/export to Mem0, ChatGPT, claude-project, agentic-stack — open-source, pluggable |
| Federation | Hub-and-spoke peering across hosts; memory syncs with provenance |
| Runtime | Single Harper process |
| Status | Published |
$ npm install -g @tpsdev-ai/flair
$ flair init
$ flair agent add my-agent
MCP — for Claude Code, Cursor, Codex, Gemini CLI, Continue.dev, Goose
One MCP server, every MCP-capable client. Same memory follows the agent across CLIs.
$ npx -y @tpsdev-ai/flair-mcp
Add to .mcp.json with FLAIR_AGENT_ID. Twelve tools — memory, soul, bootstrap, relationships, workspace.
Drop-in memory for OpenClaw agents. Install and go.
$ openclaw plugins install @tpsdev-ai/openclaw-flair
Agent identity auto-detected. Memory persists across sessions.
Google ADK
Drop-in MemoryService for Google's Agent Development Kit — Python and TypeScript. Cross-session agent memory backed by Flair.
$ pip install adk-flair
$ npm i @tpsdev-ai/adk-flair
Pass FlairMemoryService to Runner. Memory persists across sessions.
Section 2
The office OS for agent teams. Hire, brief, and dispatch agents from one command surface.
| Hire | Onboard an agent from a .tps report or persona |
| Mail | Intra-office messaging — async work handoff between agents |
| Skills | Orientation + best-practice packs via npx skills add — any harness |
| Branches | Hub-and-spoke offices, Noise_IK-encrypted WebSocket tunnel |
| Sandbox | nono process isolation |
| Identity | Per-agent Ed25519 keys; integrated with Flair |
| Status | Published |
$ npm install -g @tpsdev-ai/cli
$ tps hire developer --name dev
$ tps mail send dev "ship the auth refactor"
Section 3
The runtime library office agents run on — mail-driven loop, provider adapters, sandboxing. tps hire wires it for you; install it directly only when building a custom runtime.
| Execution | Mail-driven event loop; per-task turn cap (maxTurns) |
| Providers | Anthropic, OpenAI, Google, Ollama |
| Isolation | nono-sandboxed |
| Deployment | Single process, YAML-configured |
| Status | Published |
$ npm install @tpsdev-ai/agent
$ tps agent start --config ~/.tps/agents/my-agent/agent.yaml
Section 4
Moldable office-agent shell — one shape, any role. Identity, memory, mail, and channels wired; the persona is yours.
| Shell | Thin layer over pi-coding-agent — pi owns the agent loop, tools, providers |
| Identity | Ed25519 keypair + Flair Agent record, generated on hire |
| Memory | Flair — same substrate as the rest of the stack |
| Lifecycle | Self-restarting service — launchd (macOS) or systemd user unit (Linux) |
| Scheduling | In-process cron for proactive sweeps, wired via bob.yaml |
| Capabilities | Discord, Flair, Observatory — pluggable pi-extension packages |
| Roles | ea, writer, reviewer, coder, qa, custom — seeded soul.md + tool allowlist |
| Status | Public — source install |
$ git clone https://github.com/tpsdev-ai/bob.git && cd bob
$ bun install && bun run build
$ ./packages/cli/bin/bob onboard analyst --role ea
$ ./packages/cli/bin/bob install-service analyst && ./packages/cli/bin/bob up analyst
Section 5
ARCHITECTURE
Mail routes across offices through encrypted tunnels. Branch agents can use HQ's
Flair remotely or run their own. The
CLI handles the plumbing — one office or twenty.
tps-flint (agent) — Filed
tps-sherlock (agent) — Reviewed
heskew (human) — Approved
Cover sheet attached