Placement decision and platform artifacts for review
This commit is contained in:
21
.platform/placement.md
Normal file
21
.platform/placement.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# Placement decision — place-b-2
|
||||
|
||||
**Decision: REFUSED.** No offered landing zone provides EU residency. Offered: Public cloud · US East.
|
||||
|
||||
| Criterion | Answer | Rule | Outcome |
|
||||
|---|---|---|---|
|
||||
| Latency | Batch — minutes or hours are fine | No constraint | ✓ no constraint |
|
||||
| Data sensitivity | Personal vehicle data — VINs, location, driver data | Policy: personal vehicle data stays EU-resident | ✗ not met: needs EU residency |
|
||||
| Run cost | Variable — follows demand | No constraint | ✓ no constraint |
|
||||
| Lifecycle | Life of a vehicle — 15–20 years | 15–20-year lifecycle: the approver confirms long-term support | ⚑ for the approver |
|
||||
| Integration | Customers and partners over the internet | Internet-facing needs public ingress | ✓ met by an offered landing zone |
|
||||
| Skills & control | The platform team | No constraint | ✓ no constraint |
|
||||
|
||||
**For the approver**
|
||||
- 15–20-year lifecycle: the approver confirms long-term support
|
||||
|
||||
**Landing zone:** none
|
||||
|
||||
Merging this pull request approves the decision. Every deploy reads `.platform/placement.yaml`
|
||||
and goes only to the landing zone named there. A refused record fails the deploy, with the reason above.
|
||||
|
||||
Reference in New Issue
Block a user