<one-line change title>

Raised <date>. Follows the architecture change protocol.

Architecture evidence is insufficient to make this change recommendation yet

This template ships in the honest default state: every step insufficient_evidence, and therefore do_not_implement. That state PASSES the gate — which is the point. Fill each step as the evidence is actually gathered, and the recommendation becomes available only when nothing is left unanswered.

1 · Existing architecture

2 · Actual data model and relationships

⚠ Include nullability for every column named. A NOT NULL column cannot be SET NULL, and that omission has already produced an impossible recommendation once.

3 · Current implementation

Every consumer, enumerated. Distinguish must change from keeps compiling but changes meaning.

4 · Impact analysis

5 · Gaps

⚠ State the search space before claiming an absence. A prefix grep once missed a table whose name is a longer form of the string searched for, and produced a published false negative.

6 · Alternatives evaluated

7 · Proposed change

8 · Validation against all four customer types

Customer type	Verdict	Why, with citations
Consumer
Solo / SMB merchant
Car dealership
Enterprise

9 · Production-risk assessment

10 · Final recommendation

Not verified

❓ What remains unmeasured, and what would need inspecting.