Development

Purpose

This section is the day-to-day development entry for Prox OS. It explains how humans, AI agents, branches, pull requests, docs, and quality gates cooperate while preserving the shape of the browser-based OS shell.

Use this section for development workflow decisions. Use docs/operations/deployment/ for deployment targets, environments, release commands, and Cloudflare safety. Use docs/development/ai-control-plane/ only for opt-in task graphs, multi-agent orchestration records, run logs, and integration reports.

Start Here

1. OS Collaborative Development Model
2. Branch and Merge Rules
3. Quality Gates
4. Local Dev Workbench
5. AI Prompt Batching
6. GitHub Issues and PRs Agent Workflow

Development Flow

Read the relevant boundary docs
  -> run the agent pre-flight impact check
  -> choose serial or parallel execution
  -> create a scoped branch or worktree
  -> make the smallest coherent change
  -> update docs and stories when behavior changed
  -> run the relevant quality gates
  -> open or summarize a PR with risks and follow-ups
  -> human owner decides merge order

What Belongs Here

• Local development workflow.
• Local-only /dev workbench and hidden prototype surface rules.
• Human and AI agent responsibility boundaries.
• Branch, worktree, PR, and merge rules.
• Parallel Codex, Cursor, terminal agent, or future local agent workflows.
• Pre-flight impact checks and prompt batching.
• Development-time quality gates.

What Belongs Elsewhere

Default Posture

Direct Implementation Mode remains the default for ordinary docs, UI incubation, app surfaces, Storybook stories, copy, routing, and non-destructive refactors. The development model here adds pre-flight discipline and merge structure; it does not make every task a gated RFC or task graph.