Incidents
Declared incidents, what is affected, and what has been communicated.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
An incident record: what is affected, when it started, what is known, who is on it, and what customers have been told — declared and updated by staff rather than inferred from telemetry.
What has to exist first
- Reads
- staffIncidentsList
- Actions
- staffIncidentCreate
- staffIncidentUpdate
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.