BusinessRolesHuman
Backend Platform Partner
This is a future human role spec. It does not assign access, create employment
Status
This is a future human role spec. It does not assign access, create employment terms, or replace legal agreements.
Mission
The first technical partner should own backend platform foundation while the founder keeps product direction, shell/front-end architecture, and commercial judgment aligned.
Responsibilities
- Auth and session baseline.
- User, Organization, and Membership.
- Space, Desktop, Surface, and WindowSession persistence.
- Database schema and migrations.
- API contract.
- Backend tests.
- Cloudflare Worker, Hono, OpenAPI, and DB connection.
- Data security and access boundaries.
- First business loop backend: visitor, waitlist, activation code, and feedback.
- Later Moments and personal data backend.
Not Responsible For
- All product direction.
- All UI.
- All marketing.
- Live payment before readiness.
- Marketplace revenue split before OS backend foundation.
Ownership Map
| Area | Future owner |
|---|---|
apps/os-shell/window-manager | Founder / frontend owner |
apps/os-shell/app-registry | Founder with backend review |
apps/api-worker | Backend partner |
packages/data/db | Backend partner with founder review |
packages/contracts/app-contract | Shared ownership |
docs/platform/architecture | Founder with shared review |
docs/platform/db | Backend partner |
docs/business and docs/go-to-market/how-prox-os-grows | Founder |
Review Boundaries
- Backend schema changes must be reviewed.
- Production migrations require explicit human approval.
- Payment and entitlement changes wait for readiness.
- Agent-generated backend patches need human review before merge.