Analytics engineering needs a safe customer-region cleanup release. Deliver a staging model, a consumer mart, key tests, a documented NULL rule, and a targeted state selection. Preserve customer identifiers and unrelated models.
The Harbor Cart reporting team wants a smaller release that standardizes customer region codes without rebuilding unrelated work. You'll build a readable parent model, add a consumer, test its grain, and document the release contract. Then you'll choose a state-based selected set for a supplied change. Each step extends the same project.
Keep the output interface stable while you change its implementation. An identifier rename or a dropped NULL region can break consumers even when the model compiles.
The final artifact combines code and validation evidence. This simulator runs the local transformation and selection; it doesn't create a remote branch, schedule a production job, or store deployment credentials. Treat those external workflow decisions as explicit handoff choices rather than pretending the project has already been released to a live warehouse.