Identity Health
healthyIdentity static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
identity.authtoolkit.com
Static shared health surface for project setup, integration readiness, key scopes, Commerce entitlements, product route status, Logs handoff, and safe troubleshooting.
Shared Health Preview
Static readiness surface for project setup, integrations, key scopes, Commerce entitlements, product routes, Logs handoff, and safe troubleshooting.
Platform step: Logs → Health
Static demo only. No live API wiring, real health checks, real log ingestion, or real product execution is connected.
Shared console surfaces
Health scenarios
Static cards show product readiness states without running real health checks.
Identity static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Verification static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Notification static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Commerce static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Marketing static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Analytics static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
QR Experience static readiness preview for setup, scopes, entitlements, routes, logs, and Health handoff.
Health status
Identity setup, scope, route, and Logs handoff are healthy in this static preview.
Health summarizes readiness and points to the correct owner/surface. It does not decide access, entitlement, billing, verification truth, or product execution.
Product context
atk_...projSetup summary
Readiness checks
Project ID is present for this static preview.
Route /project-settingsRelated ID project_identity_demoProduction environment is selected in demo data.
Route /project-settingsRelated ID productionIdentity Web App is configured as a static preview integration.
Route /identityRelated ID integration_identity_web_appAPI key preview exists. No real credential is stored or checked.
Route /project-settingsRelated ID atk_...projScope readiness for access.evaluate.
Route /project-settingsRelated ID access.evaluateCommerce-owned entitlement state summarized for this action.
Route /project-settingsRelated ID identityIdentity route readiness is static/demo only.
Route /identityLogs Preview can display trace handoff for this static scenario.
Route /logsRelated ID trace_identity_demo_001Safe issue list
No critical issues in this static preview.
Route status
Identity product route readiness.
Shared Test Console route is available.
Logs Preview route is available for trace handoff.
Health Preview is static/demo only.
Logs handoff
Suggested next action
Open the relevant static surface for access.evaluate. Owner: identity_security.
Shared surfaces
Controlled Action Readiness Preview
Static handoff previews showing how controlled Test Console decisions appear in Logs and Health.
Static/demo only. No live log ingestion, live health checks, Identity calls, Commerce calls, product execution, billing, provider calls, or persistence are connected.
Health shows readiness meaning from Test Console. No live checks run.
Identity and Commerce allow the action, but product execution is not connected yet.
Identity blocks the action because the key preview is missing the required scope.
Identity requires passkey/WebAuthn step-up planning before the action can proceed.
Commerce marks the action upgrade-required because the feature is not included in the plan.
Commerce blocks the action because preview credits are insufficient.
Billing artifact preview remains demo-only until a future billing phase.
Readiness Signals
Identity allows this actor, key, and scope context.
Allowed: Identity access check
Commerce allows this plan, feature, usage, and credit context.
Allowed: Identity access check
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Allowed: Identity access check
Identity blocked the action because the presented key is missing identity:admin.write.
Blocked by Identity: missing scope
Commerce allows this plan, feature, usage, and credit context.
Blocked by Identity: missing scope
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Blocked by Identity: missing scope
Identity requires passkey/WebAuthn step-up before this higher-confidence action.
Review required by Identity: passkey step-up
Commerce allows this plan, feature, usage, and credit context.
Review required by Identity: passkey step-up
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Review required by Identity: passkey step-up
Identity allows this actor, key, and scope context.
Upgrade required by Commerce: voice agent action
Commerce says this feature is not in the current plan.
Upgrade required by Commerce: voice agent action
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Upgrade required by Commerce: voice agent action
Identity allows this actor, key, and scope context.
Blocked by Commerce: insufficient credits
Commerce blocked the action because prepaid credits are insufficient.
Blocked by Commerce: insufficient credits
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Blocked by Commerce: insufficient credits
Identity allows this actor, key, and scope context.
Demo-only billing artifact preview
Commerce returned a demo-only billing artifact preview.
Demo-only billing artifact preview
Product execution is not connected in 10D, even when Identity and Commerce allow the action.
Demo-only billing artifact preview
Suggested Fixes
Identity and Commerce allow the action, but product execution remains disconnected.
OpenAdd or select a key preview with the required Identity scope before running this action later.
OpenKeep this action in review until Identity adapter work supports the required step-up ceremony.
OpenMove the feature to an allowed plan or keep the upgrade-required state visible.
OpenUse Commerce-owned credit and usage data later before allowing this action.
OpenDo not connect billing artifact previews until a future live billing phase.
Future phase noteBoundaries
Logs display static trace previews only and do not ingest runtime events.
Health displays readiness meaning only and does not call services.
Controlled actions stop at preview mapping. Product runner work comes later.
Identity trace, audit, and readiness values are safe static placeholders.
Commerce trace, audit, entitlement, credit, and billing previews are static.
No Supabase, Stripe, QRVerse, external provider, or LLM/provider call is connected.
No trace events, readiness state, settings, help sessions, or credentials are saved.
All IDs are demo-safe references. No real credential, customer, card, bank, or provider data is present.
Suggested Actions
Review the controlled action runner that produced the preview handoff.
OpenReview controlled trace cards, timeline events, and audit previews.
OpenReview controlled readiness meaning, signals, and suggested fixes.
OpenConfirm how Identity and Commerce map to the final Console decision.
OpenUse docs/controlled-test-action-runner-10c.md as the source reference.
Docs reference onlyAdapter Client Fixture Mode
Static Identity and Commerce hosted adapter fixture responses mapped into Console decisions, Logs, and Health.
Fixture mode only. No live Identity call, Commerce call, fetch, network, provider call, billing, persistence, or product execution is connected.
This section uses static fixture responses that mirror the planned Identity and Commerce hosted adapter endpoints. It does not call the endpoints.
Fixture Readiness Preview
allowed: Identity hosted fixture maps ok to allowed.
Product execution attempted: false
blocked: Identity fixture missing scope maps to blocked.
Product execution attempted: false
review required: Identity passkey/WebAuthn review maps to review required.
Product execution attempted: false
allowed: Commerce hosted fixture maps ok to allowed.
Product execution attempted: false
upgrade required: Commerce fixture upgrade required maps to upgrade required.
Product execution attempted: false
blocked: Commerce fixture insufficient credits maps to blocked.
Product execution attempted: false
demo only: Commerce demo-only billing artifact maps to demo only.
Product execution attempted: false
allowed: Identity and Commerce fixtures both allow the action. Product execution is still disabled.
Product execution attempted: false
upgrade required: Commerce fixture upgrade requirement wins after Identity allows the action.
Product execution attempted: false
review required: Identity passkey/WebAuthn review wins before Commerce allowance can proceed.
Product execution attempted: false
unavailable: Fixture unavailable fallback keeps Console static and avoids product execution.
Product execution attempted: false
Troubleshooting
Review Project ID, Integration, API key preview, scopes, and Commerce entitlements.
Identity/Security owns whether the key can technically access the action.
Commerce-owned entitlement can block a product action even when the key scope is configured.
Preview request, response, scope, and entitlement shape before live wiring exists.
Use the trace ID to inspect the shared Logs / Trace Preview pattern.
Products own execution and product route readiness.
Page Help Widget
Health Preview
I can help with this page only. Ask me about anything here that you need help understanding.
I’m not a general chatbot. I only explain information available on this page.
I can help with this page only. Ask me about anything here that you need help understanding.
Healthy means the static readiness checks for that scenario look complete in this preview.
I can help with this page only. I don’t see that information here.
Static preview only. Live answering is not connected.
I can help with this page only. I don’t see that information here.
Page Help
Page-only help for the shared static Health Preview surface.
I’m not a general chatbot. I only explain information available on this page.
What does healthy mean?
What does warning mean?
What does blocked mean?
What should I check next?
Healthy means the static readiness checks for that scenario look complete in this preview.
Fallback: I can help with this page only. I don’t see that information here.
Open related surfaceWarning means a setup or ownership detail needs review before a future live path should be trusted.
Fallback: I can help with this page only. I don’t see that information here.
Open related surfaceBlocked means the static scenario shows a clear reason product execution should not proceed, such as an entitlement issue.
Fallback: I can help with this page only. I don’t see that information here.
Open related surfaceCheck Project Settings, key scope, Commerce entitlement, Test Console output, Logs trace ID, and product route status.
Fallback: I can help with this page only. I don’t see that information here.
Open related surfaceText visible on this route.
Static model data rendered by this page.
Page-specific phase documentation.
Route, title, and platform-step context.
Global help can answer from Knowledge Hub only.
Global help can answer from Knowledge Hub only. This static console phase does not include Knowledge Hub search.
I don’t see that in the Knowledge Hub yet.