Data & Event Platform — UI surfaces¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
The platform's screens live in the Studio's Governance & administration work area; the registry views are read-mostly and the governance orders are the only screens a Workspace admin acts on.
Screens¶
| Screen | Reads | Acts | Roles |
|---|---|---|---|
| Topic registry | ListTopics, GetTopic |
filter by context, producer, state; open schema versions | Platform admin, Operator, Observer |
| Envelope profiles | ListEnvelopeProfiles |
none (installation setting) | Platform admin, Observer |
| Stores | ListStoreBindings, ListStoreProfiles |
none in the Studio (bindings come from provisioning) | Platform admin, Operator, Observer |
| Retention | ListRetentionRules |
shorten a rule for the tenant | Workspace admin, Platform admin |
| Residency | GetResidency |
select the region at tenant creation; request a migration later | Workspace admin, Platform admin |
| Governance orders | GetGovernanceOrder |
issue deletion, export or legal hold; watch per-owner receipts; download an export | Workspace admin, Platform admin, Operator |
States the screens must show¶
- Topic: Draft, Active, Deprecated (with retirement date), Retired; schema versions with compatibility.
- Binding: Planned, Provisioned, Active, Draining, Decommissioned; drift findings from reconciliation.
- Order: Issued, InProgress, AwaitingAcknowledgements, Completed, Overdue, Cancelled; per owner Pending, Acknowledged with receipt, Failed.
- A tenant-deletion order shows its approval and the exact scope before anything is issued (FUX-12).
Other clients¶
- CLI:
factory data topics list,factory data stores list,factory data retention set,factory data orders issue --kind export,factory data orders show <id>.