Drafts begin private
Visitor work belongs to an isolated workspace until an explicit publishing decision moves it into the shared showcase.
Lab · Architecture case study
TileOS
TileOS explores a portfolio workspace where visitors can create private app drafts, evaluate them inside isolated previews, and intentionally promote selected work into a curated showcase.
The public runtime is intentionally unavailable while the upstream contract, sandbox boundary, and production operations are being hardened. This page documents the product direction; it does not present the integration as live.
Generated work needs containment
The architecture treats generated app previews as untrusted workloads that require an explicit sandbox and service contract.
Publishing stays intentional
Generation and public promotion are separate actions so an automated draft cannot silently become public portfolio content.
System shape
Proposed architecture
- Public portfolio shell and authenticated workspace boundary
- Draft generation service with explicit request and response contracts
- Sandboxed preview runtime isolated from the main portfolio origin
- Curated publish, unpublish, and ordering controls
Current limitation
Why the live button is gone
The prior page embedded an upstream that was not configured in production. A deliberate unavailable state is more accurate than a launch control that resolves to a server error.
A future public release should return only after its health check, sandbox, cache behavior, and rollback path pass verification.