should add support for cloud compute

[Sheys11]

To ensure task execution and liveness guarantees, every personal operator should be provided with compute resources.
The architecture we are adopting for this, is a hybrid one.

Provider classes

The platform supports two sandbox provider classes:

• hosted: hosted, containerized, attested execution i.e: EigenCompute
• local: local-first execution on user-owned devices
  Sandbox should always be created through the same control-plane abstraction, regardless of provider.

[catchmeifyoucaan]

Proposed Issue Clarification Update (Append-Only)

Clarified Scope (MVP for this issue)

• Build a provider wizard that supports hosted provider selection across:
  • EigenCloud
  • AWS
  • DigitalOcean
• Keep local sandbox support as a first-class provider path.
• Use one shared control-plane abstraction for sandbox creation regardless of provider.

Provider and Fallback Rules

• Hosted path is multi-provider (not EigenCloud-only).
• Local fallback behavior is configurable.
• Default fallback mode is ON:
  • If selected hosted provider fails during sandbox creation, system auto-falls back to local provider.

Required Implementation Depth

• Deliver real provisioning integration for:
  • EigenCloud
  • AWS
  • DigitalOcean
• No stub-only hosted provider adapters for this issue.

Measurable Acceptance Criteria

• Wizard allows selecting EigenCloud, AWS, DigitalOcean, or Local.
• Sandbox creation path uses the same provider interface/contract across all providers.
• For each hosted provider:
  • sandbox creation succeeds in < 60 seconds
  • provider healthcheck passes after creation
• Local provider path remains functional with the same control-plane interface.
• Config toggle exists for local fallback behavior and defaults to ON.
• When fallback is ON and hosted creation fails, system creates local sandbox and logs fallback event with provider + reason.
• Add tests covering:
  • provider selection routing
  • per-provider creation success path
  • fallback enabled behavior
  • fallback disabled behavior
  • healthcheck + timing assertion path

Out of Scope for this issue

• Advanced provider cost optimization policies.
• Multi-region scheduling policies beyond minimum integration needed for creation flow.
• Wallet/reward/PSH integration.

[catchmeifyoucaan]

Product Spec (PRD) committed — View on branch

[catchmeifyoucaan]

Product Spec (PRD) committed (correct repo link) — View on branch

[catchmeifyoucaan]

Design Spec committed — View on branch

[catchmeifyoucaan]

Technical Spec committed — View on branch