Factory Studio — later capabilities¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
No later-stage services.
| Capability | Owner when built | Taken up when |
|---|---|---|
| Per-screen field selection for the VS Code extension and CLI | BC-29 | payload size measurably affects the interactive objective on thin clients |
| Offline-tolerant command queue in the CLI with server idempotency | BC-29 | CI and air-gapped use cases appear |
| Tenant-branded Studio themes | BC-29 with the design system | an edition includes it (D34) |
| User-authored notification rules (watch a run, a product) | BC-29 | the notification kinds stabilise |
| Mobile push through a connector | BC-29 with Integration | on-call responders ask for it (P12) |
| Azure SignalR Service profile; per-tenant connection quotas | BC-29 | connection counts exceed a cohosted hub |
| Embedded Studio widgets (approval card, run status) in generated products | BC-29 with Generated SaaS | a product owner wants operator views inside their product |
| Agent-assisted Studio (ask the Factory in natural language, with actions rendered as commands) | BC-29 with Agent Mesh | the Studio BFF contract is stable and the chat profile is published |