BusinessGovernance
Asset Ownership Model
Asset ownership records keep Prox OS operable if the founder is unavailable,
Purpose
Asset ownership records keep Prox OS operable if the founder is unavailable, if a contractor needs access, or if a future team needs a controlled handoff.
This document records categories and review rules only. It must not contain secrets, tokens, account IDs, recovery codes, or private legal documents.
Asset Categories
| Category | Examples | Primary owner | Backup owner | Risk |
|---|---|---|---|---|
| Identity | GitHub org, domain registrar, email domains | Founder / Product Architect | Ops Steward | High |
| Infrastructure | Cloudflare, Vercel/Netlify candidates, Neon, storage | Founder / Product Architect | Ops Steward | High |
| AI workspace | OpenAI/Codex workspace, prompt archives, model accounts | Founder / Product Architect | AI Workflow Librarian | Medium |
| Product analytics | PostHog, logging dashboards, research notes | Founder / Product Architect | Ops Steward | Medium |
| Commercial | Stripe/payment candidates, pricing docs, investor decks | Founder / Product Architect | Capital Partner when formalized | High |
| Legal/accounting | Company formation, tax/accounting contacts, trademark notes | Founder / Product Architect | Capital Partner or legal operator | High |
| Community | GitHub Discussions, Discord, newsletter, social channels | Growth & Community Lead | Founder / Product Architect | Medium |
Review Rhythm
- Critical assets: monthly review once production users exist.
- Medium assets: quarterly review.
- Public community assets: review during launch cycles.
- Every asset should eventually have owner, backup owner, access level, last reviewed date, and runbook link.
Storage Rule
Store the asset inventory structure in repo docs. Store secrets and recovery material only in approved secret managers or provider-native access controls.