Ecosystem Map
The full architecture of the 88.pi platform, showing how all components connect.
Component Tree
88.pi (platform)
├── pi-mono-main (forked base)
│ ├── pi-coding-agent (extension framework)
│ │ └── extensions/nity/ (17 files — THE NITY AGENT)
│ │ ├── coordinator.ts
│ │ ├── task-analyzer.ts
│ │ ├── strategy-planner.ts
│ │ ├── execution-router.ts
│ │ ├── standalone-runner.ts
│ │ ├── quality-gates.ts
│ │ ├── self-reflection.ts
│ │ ├── skill-registry.ts
│ │ ├── progress-tracker.ts
│ │ ├── quantumreef-bridge.ts
│ │ ├── brand/ (voice, state-to-brand)
│ │ ├── tui/ (presence, loop-status, memory-banner)
│ │ └── bridge/ (9 files — EXTERNAL CLIENT SDK)
│ └── nity-memory, nity-loop, nity-brand (sub-extensions)
├── ralph-loop/ (autonomous iteration patterns + Voyager)
├── specs/ (5 spec families, 73+89 tasks)
├── 88.pi-assets/ (skills, brand assets)
└── memory_bank/ (strategic context)Navigation
Layer Responsibilities
| Layer | Path | Role |
|---|---|---|
| Platform | 88.pi/ | Repository root, configuration, CI |
| Base | pi-mono-main/ | Forked coding agent framework |
| Framework | pi-coding-agent/ | Extension system, tool registry, execution |
| Agent | extensions/nity/ | The Nity agent — orchestration, execution, reflection |
| Memory | extensions/nity-memory/ | Persistent context, episodes, brain |
| Loop | extensions/nity-loop/ | Autonomous iteration with safety |
| Brand | extensions/nity/brand/ + tui/ | Presence, voice, visual state |
| Bridge | extensions/nity/bridge/ | External client SDK (9 files) |
| Patterns | ralph-loop/ | Ralph's autonomous iteration + Voyager |
| Specs | specs/ | 5 spec families, 162 total tasks |
| Assets | 88.pi-assets/ | Skills, brand assets, templates |
| Context | memory_bank/ | Strategic context, decisions, history |
The architecture follows a layered dependency pattern: platform → base → framework → agent → extensions. Each layer depends only on the layer below it, never upward or sideways.
Critical Path
The critical path from the spec runs through:
coordinator.ts → task-analyzer.ts → strategy-planner.ts → execution-router.ts → loop-engine → circuit-breaker → quality-gates → self-reflection → episode-recorder → bridge (stream to client)Every component on this path must be functional for autonomous operation. Components off this path (brand, tui, quantumreef-bridge) enhance the experience but don't block execution.