Placement decision and platform artifacts for review (#1)
This commit was merged in pull request #1.
This commit is contained in:
18
.platform/placement.md
Normal file
18
.platform/placement.md
Normal file
@@ -0,0 +1,18 @@
|
||||
# Placement decision — place-b-1
|
||||
|
||||
**Decision: PLACED.** Every requirement is met by Public cloud · US East.
|
||||
|
||||
| Criterion | Answer | Rule | Outcome |
|
||||
|---|---|---|---|
|
||||
| Latency | Batch — minutes or hours are fine | No constraint | ✓ no constraint |
|
||||
| Data sensitivity | Internal — no personal data | No constraint | ✓ no constraint |
|
||||
| Run cost | Variable — follows demand | No constraint | ✓ no constraint |
|
||||
| Lifecycle | 3–5 years, then replaced | No constraint | ✓ no constraint |
|
||||
| Integration | Customers and partners over the internet | Internet-facing needs public ingress | ✓ met by Public cloud · US East |
|
||||
| Skills & control | A product team on the golden path | No constraint | ✓ no constraint |
|
||||
|
||||
**Landing zone:** Public cloud · US East · runner `crucible-orchestrator-dev-apps-dev-runner`
|
||||
|
||||
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
36
.platform/placement.yaml
Normal 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: placed
|
||||
landing_zone: public-us-east
|
||||
landing_zone_name: "Public cloud · US East"
|
||||
runner: crucible-orchestrator-dev-apps-dev-runner
|
||||
reason: "Every requirement is met by Public cloud · US East."
|
||||
workload: "place-b-1"
|
||||
criteria:
|
||||
- criterion: "Latency"
|
||||
answer: "Batch — minutes or hours are fine"
|
||||
rule: "No constraint"
|
||||
outcome: "✓ no constraint"
|
||||
- criterion: "Data sensitivity"
|
||||
answer: "Internal — no personal data"
|
||||
rule: "No constraint"
|
||||
outcome: "✓ no constraint"
|
||||
- criterion: "Run cost"
|
||||
answer: "Variable — follows demand"
|
||||
rule: "No constraint"
|
||||
outcome: "✓ no constraint"
|
||||
- criterion: "Lifecycle"
|
||||
answer: "3–5 years, then replaced"
|
||||
rule: "No constraint"
|
||||
outcome: "✓ no constraint"
|
||||
- criterion: "Integration"
|
||||
answer: "Customers and partners over the internet"
|
||||
rule: "Internet-facing needs public ingress"
|
||||
outcome: "✓ met by Public cloud · US East"
|
||||
- criterion: "Skills & control"
|
||||
answer: "A product team on the golden path"
|
||||
rule: "No constraint"
|
||||
outcome: "✓ no constraint"
|
||||
flags: []
|
||||
|
||||
Reference in New Issue
Block a user