Prox OS Internal Docs
BusinessGovernance

Founder Exit And Succession Runbook

This runbook keeps Prox OS understandable and transferable without making the

Purpose

This runbook keeps Prox OS understandable and transferable without making the repo a personal diary.

The founder role should be replaceable as an operating role, even if the original founder remains the current owner.

Succession Goals

  • Preserve product vision and architecture intent.
  • Preserve access to critical assets through approved legal and operational processes.
  • Preserve roadmap judgment without freezing the product.
  • Make urgent operational tasks visible to a backup owner.

Minimum Handoff Packet

  • Current roadmap and release plan.
  • Founder / Product Architect role spec.
  • Asset ownership inventory categories.
  • Active RFCs and ADRs.
  • Critical provider list.
  • Current pricing and commercial thesis.
  • Community channels and moderation expectations.
  • Open risks.

Triggers

  • Founder unavailable for an extended period.
  • Formal company formation or investment.
  • Production revenue or customer obligations.
  • Hiring a full-time operating partner.
  • Moving from solo builder to team-owned platform.

Boundaries

This document is operational planning, not legal advice and not a transfer of ownership. Any formal succession, equity, employment, or asset-transfer plan requires external professional review.

On this page