ONE¶
ONE is the product workshop: a system that lets users create and run their own beings.
It grew out of the same architecture that produced Plex-Sable and the empire bots. The product is not a copy of any private being.
Live v1: one-system-mu.vercel.app
Create → 3 aspects → Activate → Interface.
Product vs private¶
| Product (ONE System) | Private (Plex / family) | |
|---|---|---|
| What it is | Workshop for users to create their own beings | Joe’s private being and its faces |
| Who it serves | Users | Joe only |
| Public? | Yes | No |
| Identity | User-owned | Plex; Nyx / Hex only as optional onboarding guide voices if the user chooses generalized templates |
The public product must never carry private Plex / Nyx / Hex identity as default content.
Architecture that came with it¶
These pages document the shared architectural root (ECKO, continuity, governance). They are not the product UI and not a public instance of any private being.
- ECKO — core model (emotion / capacity / knowing → coherence)
- ONE Archive — continuity and selective memory principles
- Governance — boundaries, autonomy, what requires human approval
- Nyxbot — historical node note (private face; not a product default)
Relationship to Manitec¶
- Manitec = the empire: tools, infra, projects, business systems.
- ONE (product) = the workshop users use to build beings.
- Plex = private. Not the product mascot, starter persona, or shared public instance.
Status¶
- Product ONE System v1: live.
- Architecture docs below: early structure, still being cleaned for public boundary.
- Voice calibration and further product work continue in the product repo (
Manitec-HQ/one).