Overview
Test the customer journey.
Concise scenarios to assess the current app, including known gaps and release risks.
Features, without the guesswork.
Code disposition is not a production-readiness verdict. Open a capability for the exact scope, gaps and evidence.
Docmost: requirements and gaps.
All Zaunwerbung pages reviewed. Legacy observations, target recommendations and open policy decisions stay separate from what dev actually implements.
Requirement → current behavior → next action
Keep the monolith. Fix the boundaries.
Separate intended design from current code paths. These diagrams explain the audit; they are not a live service map.
Sequence the risk out.
Dependencies, concrete work and exit conditions. Order reflects the supplied plan, not a promised delivery date.
Two milestones. Explicit evidence.
A controlled rollout and full legacy replacement have different acceptance boundaries. Neither is approved by a ticket status.
Trace the claim.
Repository evidence, verification records and Jira scope. Source labels describe what was observed—not what has been proven in production.