From fb8c1fad910417aed50ad3edfce75fe6ec8e812d Mon Sep 17 00:00:00 2001 From: demo-bot Date: Mon, 12 Oct 2026 19:25:11 +0000 Subject: [PATCH] Placement decision: REFUSED, no compliant landing zone - for review --- .platform/placement.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .platform/placement.md diff --git a/.platform/placement.md b/.platform/placement.md new file mode 100644 index 0000000..f969cef --- /dev/null +++ b/.platform/placement.md @@ -0,0 +1,21 @@ +# Placement decision — place-b-3 + +**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. +