# Nora: second-client adaptation

**Synthetic change brief NORA-01..03. The HVE core uses the supplier-service boundary and relevant actual HVE artifacts where available. A deployed lab 05 application is needed only for the optional implementation extension.**

- **NORA-01:** Nora Services requires an additional `Service region` choice: North or South. It is required before a submission is accepted into review, including API/form bypass attempts, not just visually marked on the page. An invalid attempt can be retained as evidence but cannot create a review application.
- **NORA-02:** Supplier contacts see only their own applications, unchanged from RULE-05. Nora's test contacts are new identities; do not copy Zava contact rows.
- **NORA-03:** Procurement uses a different sandbox review team and a different training notification recipient. Both are configuration. Missing configuration must stop processing with an explicit operator-visible failure, not default to Zava.

No new customer data, site publication, bank details or ERP integration is authorized. In the core, the receiving consultant must find the accepted basis and obtain a credible adaptation handoff without private author coaching. Actual deployment/configuration tests are separate optional evidence.