How to use Runtime trust

What this section is for

Shows workload identity, image signature, secret scope and policy attestation.

Before you start

You need access to IAM.Hosting, the correct tenant/workspace and permission to read this data. Prepare a non-sensitive example value such as agent-demo-prod.

Buttons and forms

Control	What it does
Verify	Performs the action named in the interface. Review the resulting state or message before continuing.
View attestation	Runs a check or dry run so the result can be reviewed before production use.
Copy digest	Copies the displayed value; verify that it does not contain a secret before sharing it.
Refresh	Reloads data from the server and keeps the current page context.

Primary path in the interface

Open the application link above and sign in with the least-privileged role required for this section.
Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
In the navigation, click Runtime trust. The expected address is https://iam.market/?demo=hosting.
Click View attestation. Enter the documented safe values: agent-demo-prod. Do not paste a production secret into a free-text field.
Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
Review the validation message or changed row. The result must match this purpose: Shows workload identity, image signature, secret scope and policy attestation.
Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.

Second path: direct link and CLI/API

Open the deep link https://iam.market/?demo=hosting instead of navigating through the sidebar.
Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:

curl --fail --silent --show-error https://iam.market/api/hosting/healthz

How to verify the result

All required attestations are verified and secrets appear only as references.

If it did not work

Symptom	What to do
401 / sign-in screen	Sign in again, then return to this page. Do not put a session token in a URL.
403	Check the selected tenant and request the documented role; retrying with the same role will not help.
404	Verify the exact path and whether the feature is enabled in this environment.
409	Search for an object named `agent-demo-prod`; continue with it or choose a unique name.
422 / validation error	Correct only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise.
429	Wait for the displayed retry interval or reduce the request scope; do not start parallel retries.
5xx / timeout	Refresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support.