preserve-existing-flow

Preserving existing flows in brownfield systems requires mapping ownership boundaries across producers, transport, state, and consumers. You must layer new behavior beside the current owner path and obtain explicit approval for ownership migration before making any edits.

Ownership-aware layering is an architecture-first approach that maps decision paths and respects boundaries across producers, transport, and state. It requires specifying discovery requirements and validation evidence before layering new behavior into existing queues or state machines.

Start by producing a concise working brief detailing the requested behavior, current flow, owners, evidence needed, and task scope. This brief determines whether your task is read-only, review-only, or implementation-approved before any edits to state machines begin.

No, directly overwriting current functionality risks unintended behavioral changes. You must layer new behavior beside the current owner path and require explicit approval for ownership migration before executing any implementation-approved edits on the codebase.

Validation evidence is required whenever changes are layered through current owners in transport paths or queues. You must specify whether the task is read-only, review-only, or implementation-approved, gathering evidence before any edits to prevent risk-management failures.