polyphony-branch-model

Standardize Git branch naming by enforcing deterministic topology rules for feature, plan, merge-group, and evidence branches. This ensures workflow orchestration and pull request routing can be automated without brittle, type-specific logic.

Merge-group promotion is a gated process that standardizes PR lifecycle ordering using stable MG identity grammar and driver-enforced merge policies. It mandates specific head/base relationships and merge commits to safely advance code through topology layers.

Handle concurrent pull requests safely using parent-plan generations to block stale PRs and enforce auditable rebases. Ancestor restack protections and recorded rebase events prevent silent topology drift during concurrent renegotiation.

Resolve cross-sibling code dependencies by applying policy-driven remedies like promote-and-rebase. These dependency fixes are recorded in a run manifest to ensure branch topology remains stable and auditable across sibling merges.

A topology hash is an immutable input recorded in a run manifest that guarantees stable merge-group identity. You need it when authoring workflow YAML to derive deterministic routing decisions across feature planning and evidence capture.

Deterministic branch naming requires a run manifest to record immutable topology inputs and planner-declared MG ids. Without this manifest, workflow orchestration cannot reliably enforce merge gates or prevent silent topology drift across branch generations.