GQ-017 · Compute Placement and Continuity

How should source, data and runtimes be placed across available hosts so useful work stays discoverable and recoverable within real resource limits?

SISO Open Source Foundation

experimental

scoped

Not declared

Define the minimum public-safe question program before scheduling research.

No selected release

Not released — the selected Release has no public answer artifact.

hybrid

Choose execution and data placement from verified host capability, ownership, connectivity and recovery evidence.

Trace one source revision to its authorized runtime and durable output without exposing private infrastructure. · Verify the required capacity, access and recovery path on the actual intended host.

The chosen host cannot demonstrate the required resource or recovery capability. · Placement makes source or outputs undiscoverable, crosses a data boundary or adds more recovery burden than it removes.

A historical readiness report does not establish current capacity or permission to move or restart a workload.

New owner-approved outcome or counterexample changes the decision evidence. · The relevant source, operating constraint or acceptance boundary materially changes.

Public runtime and project portability contracts · Redacted, owner-approved capacity, placement and restore receipts

A source-to-runtime placement receipt with resource constraints, restoration proof, remaining gaps and the owning operator.

Review when relevant owner evidence or decision conditions change; registration starts no collector, benchmark, scheduler or new execution lane.

public metadata only