Ecosystem
Orchestration, not tools
Peri is built and operated by one person orchestrating an AI-native toolchain. The interesting fact is not any single tool — it's that the design system, codebase, documentation and prototype stay coherent because every tool feeds the same sources of truth.
The map
How the clusters relate
| Cluster | Role | Feeds |
|---|---|---|
| Intelligence | Claude + Claude Code build and audit the app, engines and docs; Claude Design / Figma AI / Stitch / GPT explore visual and copy directions; Base44 prototyped early concepts | Codebase · Design system · Documentation |
| Infrastructure | Netlify serves the static export; Google Authentication gates real users; Google Drive holds each user's data as JSON in appdata; Supabase reserved for future multi-device sync | Application runtime |
| Data Sources | Manual logs and cycle history are primary; Health Connect brings wearable sleep stages, recovery and temperature — always subordinate to symptoms | The single daily record (Entry) |
| Artifacts | The design system, application, codebase, documentation, prototype and case-study assets — each one generated from, and checked against, the others | Portfolio · handoff · scaling |
The orchestration loop
One loop keeps everything coherent: the app is the behavioural source of truth, Figma is the visual source of truth, and the documentation rules every divergence between them. AI tools amplify each stage — writing engines against specs, auditing cross-signal priorities, capturing Figma tokens, building this portal — but no tool owns the truth. That's why a sixth tool can join (or any tool can leave) without the system losing integrity.
Why this matters beyond Peri
The same loop is the template for AI-native product work generally: sources of truth + divergence rulings + AI as the labor between them. The portal you are reading is itself an artifact of that loop.