DDD Strategic Lens — Boundaries, Language, Integration

Review the strategic shape of a change through the lenses from Learning Domain-Driven Design (Vlad Khononov, O'Reilly), Parts I, III–IV. This is not about which pattern a class uses inside a context (use ddd-tactical) and not a generic layering check (use model-lens). It asks three questions:

1. Are the bounded-context boundaries right — does this change stay inside one context, or does it leak across and couple things that should be independent?
2. Does the code speak the business's ubiquitous language, consistently within its context?
3. When contexts integrate, is the right integration pattern used to protect each model?

Apply the relevant lenses, report findings grouped by lens, cite file:line, name the rule, propose the fix. Skip lenses that don't apply. If it's clean, say so.

Map: contexts in greenspark-aws