Subject
Agent Infrastructure
Build teams of AI agents that coordinate, remember, and ship — without you in the loop.
Section 1
FLAIR
Identity, memory, and soul for AI agents. Runs standalone or as part of a TPS office.
| Auth | Ed25519 cryptographic identity |
| Memory | Semantic search, local embeddings |
| Soul | Persistent personality + context |
| Runtime | Single Harper process |
| Status | Published |
$ npm install -g @tpsdev-ai/flair
$ flair init
$ flair agent create my-agent
Drop-in memory for OpenClaw agents. Install and go.
$ openclaw plugins install @tpsdev-ai/openclaw-flair
Agent identity auto-detected. Memory persists across sessions.
Section 2
CLI
The office OS for agent teams.
| Mail | Intra-office messaging |
| Pulse | PR lifecycle automation |
| Branches | Distributed agent offices |
| Sandbox | nono process isolation |
| Status | Published |
$ npm install -g @tpsdev-ai/cli
$ tps office init
Section 3
AGENT
Headless agent runtime.
| Execution | Mail-driven task loop |
| Isolation | nono-sandboxed |
| Deployment | Zero-config, single process |
| Status | Published |
$ npm install @tpsdev-ai/agent
$ tps agent start --id my-agent
Section 4
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
