Placement decision and platform artifacts for review (#1)

This commit was merged in pull request #1.
This commit is contained in:
2026-10-12 18:54:52 +00:00
parent 7805eb8b79
commit 96c92d8078
7 changed files with 250 additions and 0 deletions

21
.platform/placement.md Normal file
View 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.

36
.platform/placement.yaml Normal file
View File

@@ -0,0 +1,36 @@
# Placement decision record. Written by the golden path from the workload profile and
# approved by merging the Gate 1 pull request. deploy.yml reads decision, runner and
# reason on every deploy: keep them top-level, one line each.
decision: refused
landing_zone: none
landing_zone_name: "none"
runner: none
reason: "No offered landing zone provides EU residency. Offered: Public cloud · US East."
workload: "place-b-2"
criteria:
- criterion: "Latency"
answer: "Batch — minutes or hours are fine"
rule: "No constraint"
outcome: "✓ no constraint"
- criterion: "Data sensitivity"
answer: "Personal vehicle data — VINs, location, driver data"
rule: "Policy: personal vehicle data stays EU-resident"
outcome: "✗ not met: needs EU residency"
- criterion: "Run cost"
answer: "Variable — follows demand"
rule: "No constraint"
outcome: "✓ no constraint"
- criterion: "Lifecycle"
answer: "Life of a vehicle — 15–20 years"
rule: "15–20-year lifecycle: the approver confirms long-term support"
outcome: "⚑ for the approver"
- criterion: "Integration"
answer: "Customers and partners over the internet"
rule: "Internet-facing needs public ingress"
outcome: "✓ met by an offered landing zone"
- criterion: "Skills & control"
answer: "The platform team"
rule: "No constraint"
outcome: "✓ no constraint"
flags: ["15–20-year lifecycle: the approver confirms long-term support"]