Development Workflow

Every change starts with a clear problem statement and ends with verified customer value.

Before coding

1. Confirm the expected behavior and acceptance criteria.
2. Identify the owning service using the architecture overview.
3. Note rollout or migration risks on the issue.

Branch and review

git switch -c feature/short-description
npm test
git push -u origin feature/short-description

Pull requests should be small enough to review in one sitting. Include:

• What changed and why
• Screenshots or API examples when relevant
• Test evidence
• Rollout and rollback notes

Definition of done

A change is done when tests pass, review feedback is resolved, documentation is updated, and the release can be observed and reversed. Continue with the release process.