adarshpuri20

flow-surface-theory

The geometric model behind surface review — communication planes, dents as bugs, bulges as vulnerabilities, and smoothness as the invariant. Load when classifying a defect, when judging whether a fix deformed something adjacent, or when reasoning about a case the gates do not cover.

surface-review

Run the 11-gate Flow Surface review on a set of changed files, then the smoothness convergence loop. Use before merging a branch, before shipping a phase, when asked for a thorough or cross-file code review, or when a fix might have broken something adjacent.

phase-execution

Execute a planned phase with checkpoint-based state that survives context compaction, then hand off to review and commit. Use after a plan exists, to resume interrupted phase work, or on "continue the phase".

phase-planning

Plan a multi-sub-phase development phase before any code is written — landing architecture estimate, sub-phase sequence, and blast-radius declaration. Use when starting a phase, when work is large enough to need staging, or on "plan this phase".

simulation-lanes

Run sub-phases in parallel isolated lanes (git worktrees or sandboxes) and graduate proven code to the main branch. Use when a phase has parallel-safe sub-phases, when work must not touch main until reviewed, or on "set up the sim lanes".

gate-ledger

Read and maintain the persistent gate ledger and debt ledger that span audit runs and build phases. Use when checking which gates are open, recording accepted debt, or asking what the current readiness state is.