mountain-nomad-bc/pacify-x/execution-placement-decision

Execution Placement Decision

Use runtime.execution_placement as the CPU-authoritative decision runtime. Read resources/placement-policy.md before proposing a candidate or promotion.

Workflow

1. Classify exactly one mode: language_runtime, deployment_platform, or

database_storage.

1. Record the current placement as the mandatory keep_current candidate and

bind the decision to a current baseline hash.

1. Compare provider-neutral classes before selecting a named vendor or product.
2. Score correctness, latency, throughput, operability, portability, cost,

maintainability, and reversibility; subtract serialization, network, consistency, operational, and migration boundary costs.

1. Fail closed on compatibility, correctness, baseline, or rollback gaps.
2. Prefer the smallest bounded unit: adapter, sidecar, projection, worker, or

index before a primary-system migration.

1. Freeze the decision and benchmark the selected candidate against the exact

current baseline.

1. Require hashed after-state, boundary, and rollback evidence before partial

promotion. Production remains separately authorized.

Runtime interface

• Decision: runtime.execution_placement.decide_placement
• Promotion gate: runtime.execution_placement.promotion_gate
• Learning/revision lifecycle: runtime.learning_promotion

Boundaries

• A recommendation never executes or authorizes migration.
• keep_current is valid and is selected when evidence is weak or improvement

does not clear the configured threshold.

• Filesystem, database mutation, serialization, cleanup safety, and destructive

decisions remain CPU-authoritative.

• No provider is selected before a placement class wins under current evidence.
• Losing revisions, baselines, and rollback paths are retained.