Problem: Every miner CLI command opens its own local database file and does its work in-process today — a hosted, multi-tenant AMS service needs an entirely new API surface, not just a repointed config.
Area: AMS / Cloud architecture
Proposal: Design the client/server boundary: which operations become API calls, what the server-side process model looks like, and how the existing CLI could optionally become a thin client against it rather than a fully separate codepath.
Deliverables:
- A written design for the client/server split, informing the actual cross-tenant loop-execution and idea-intake wiring work already tracked in this milestone.
Resources:
- The existing multi-tenant hosted architecture spec and platform/sandboxing issues in this milestone.
Boundaries:
- Design only in this issue — implementation is covered by this milestone's existing cross-tenant execution work.
Problem: Every miner CLI command opens its own local database file and does its work in-process today — a hosted, multi-tenant AMS service needs an entirely new API surface, not just a repointed config.
Area: AMS / Cloud architecture
Proposal: Design the client/server boundary: which operations become API calls, what the server-side process model looks like, and how the existing CLI could optionally become a thin client against it rather than a fully separate codepath.
Deliverables:
Resources:
Boundaries: