Context
Miner Wave 5 (Rent-a-Loop, #4778) and the separate AMS Cloud Readiness milestone (#28) are each independently scoping the same underlying problem — making AMS hosted/multi-tenant-capable — from two different angles, with no cross-reference between them today:
Left unreconciled, the risk is duplicated effort: Wave 5 could grow its own narrower, product-bolted-on multi-tenancy layer directly against self-host code, while AMS Cloud Readiness separately designs the general version of the same primitives — two implementations of tenant isolation, auth, and storage, neither aware of the other.
Dependencies
None to start — this issue itself is the dependency several Wave 5 issues (#4783, #4792, #4793, #4794, #4796, #4797) are waiting on before their own cross-references can be written correctly.
Requirements
- For each overlapping pair listed above, decide which side is authoritative and how the other references/blocks on it.
- The intended relationship (a starting hypothesis, not a final decision — reaching the actual decision is this issue's job): AMS Cloud Readiness becomes the foundation — generic, product-agnostic hosted-capable primitives (tenant-scoped storage, auth/identity, control-plane pattern) — and Wave 5 becomes a consumer of it, contributing only the business-specific layer on top (pricing, payment, ToS, idea intake, customer UI) rather than re-deriving tenancy itself.
- Update each of the six Wave 5 issues above with the resulting cross-reference once decided.
- Out of scope: writing the actual architecture spec, standing up any infrastructure — this issue is the sequencing/ownership decision only.
Deliverables / Acceptance Criteria
Expected Outcome
Wave 5's architecture/security work builds on AMS Cloud Readiness's foundation instead of quietly reinventing it, so the self-host and hosted codebases stay one seam apart rather than two divergent implementations.
Links & Resources
Context
Miner Wave 5 (Rent-a-Loop, #4778) and the separate AMS Cloud Readiness milestone (#28) are each independently scoping the same underlying problem — making AMS hosted/multi-tenant-capable — from two different angles, with no cross-reference between them today:
Left unreconciled, the risk is duplicated effort: Wave 5 could grow its own narrower, product-bolted-on multi-tenancy layer directly against self-host code, while AMS Cloud Readiness separately designs the general version of the same primitives — two implementations of tenant isolation, auth, and storage, neither aware of the other.
Dependencies
None to start — this issue itself is the dependency several Wave 5 issues (#4783, #4792, #4793, #4794, #4796, #4797) are waiting on before their own cross-references can be written correctly.
Requirements
Deliverables / Acceptance Criteria
Expected Outcome
Wave 5's architecture/security work builds on AMS Cloud Readiness's foundation instead of quietly reinventing it, so the self-host and hosted codebases stay one seam apart rather than two divergent implementations.
Links & Resources