OPERATOR WORKSPACE
where identifiers are issued and start requests are read back
The workspace reads its identity from the server, never from this page. Opening the sign-in page — the workspace returns here once the session is verified.
DESK
Every fact here is copied from the desk's own published page linked below — never runtime claims. A planned item stays planned until the desk's real materials replace it; nothing on this desk view invents metrics, positions or records.
business further work — copied from the desk's development plan
A start request was recorded for this desk in the operator log of the access registry — against your verified operator identity. This workspace is where the programme open lands; nothing else is started from here.
Read from the registry at request time. Empty means none were recorded — the workspace never invents a row.
- reading the registry…
Start requests are recorded against your operator identifier — that is the identifier this workspace works with. Desk operator identifiers and credentials are issued by the operator's own console; this demonstration workspace records the start and reads the log back. It issues no credentials.
This page is a surface, not an operation console: it claims nothing beyond the rows the registry actually returned. If the registry is unreachable, this page says so — there is no local fallback that could say otherwise.