Verification
Verification displays real server state with a next action, not placeholder statistics.
Served by the core studio
Software records (sources, programs, runs, releases, components, environments, media, verification and exports) live in the core engine and are edited in its studio. When a connected engine answers through this workspace, the panels above render its own records as returned; without a connection the shell states that and shows nothing rather than an invented row. The surface contract below names each action and the setup it needs.
Surface contract
Primary object: verification findings: the specific checks that passed, failed or have not run, each with its evidence.
Actions
- Open findingCore studioA finding’s evidence ids, environment and reproduction inputs are engine records; the hosted shell shows a finding only when the engine returned it.
- Run checkCore studioChecks execute inside the core engine’s sandbox against the run’s artifacts; no check is simulated in the browser and a failed check is never reported as passed.
- Inspect environmentCore studioThe environment record (image digest, language tiers, tool versions) comes from the engine’s run metadata; this build holds no environment and states no versions.
Required states and how this surface reaches them
- loading
- the session probe and each list show Loading… until the control plane answers.
- ready
- the server’s own records render as returned; the primary object is named before its details.
- empty
- no verification has run for this software yet; a check runs only against a real build in the core engine.
- error
- the control plane’s status and detail are shown; no placeholder row replaces them.
- offline
- no control plane is reachable; nothing is rendered rather than invented.
- permission_denied
- a 401 returns to sign-in with this path; a 403 states that the role cannot read this surface.
- not_configured
- a 503 names the missing provider or secret; setup is shown, never fake results.
- budget_paused
- a 402 (quota_exceeded / upgrade_required) pauses spending; the budget row shows the cap and consumption that caused it.
- requires_approval
- mutations the server reserves for an explicit human owner/admin are refused with its own detail and never auto-approved here.
Scope: workspace membership. Engine records are read and written through the core engine’s own routes (proxied by the control plane); the hosted shell binds only to named contracts, shows a record only when the server returned it, and never calculates permissions in the browser.