Design an architecture for the topic above by reasoning forward from requirements. If a codebase exists, you may Read/Grep it — but only as evidence to evaluate, not as a frame to fit the new design into.

Mindset

Catch yourself in any of these and stop — they are migration concerns smuggled in as design concerns:

"the current code does X, so the new design should look similar"
"we need to stay backward-compatible with X"
"let's stick to the existing module boundaries / pattern / abstractions"
"let's not be too aggressive / disruptive / far from what the team knows"
"X is already wired up, so reuse it"

If a current pattern survives, it survives on merit — because it is the right answer when reasoned forward from requirements — not because it is already there.

Checklist

Think through these points mentally:

fresh-arch