ralphinho-rfc-pipeline

Decompose the feature RFC into units each defining id, depends_on, scope, acceptance_tests, risk_level, and rollback_plan. Order units in a DAG so dependencies complete first, then validate each unit independently before merging.

A merge queue serializes unit integration by blocking merges with unresolved dependency failures, rebasing unit branches on the latest integration branch, and re-running integration tests after each queued merge.

Units fall into three tiers: Tier 1 covers isolated file edits with deterministic tests, Tier 2 covers multi-file behavior changes with moderate integration risk, and Tier 3 covers schema, auth, performance, or security changes.

Stalled units are evicted from the active queue, their findings are snapshotted, and a narrowed unit scope is regenerated. The unit is then retried with updated constraints rather than blocking the pipeline.

Use RFC decomposition when a feature is too large for one agent pass to implement and verify reliably. Single-pass execution suits small isolated changes, while decomposition fits multi-file or cross-cutting features needing staged validation.