Usage context checkpoint
Active workspace: default
Confirm workspace identity before recording usage pressure, quota evidence, or plan-limit remediation cues that will later be relayed into verification, settings, and admin notes.
Workspace context was loaded from environment fallback values. Use metadata-backed session context before production rollout.
Live metadata is unavailable. Treat this as preview data until you reconfirm metadata-backed identity and tenant on /session.
Plan limit governance lane
The usage ledger below keeps each plan limit visible. Before hitting a quota, confirm the current limit, usage pressure, and upgrade posture so you don’t accidentally throttle a critical run or block the admin readiness flow.
Plan limit enforcement is manual in this slice: you review the usage ledger, decide whether the current plan still fits, and navigate to billing or admin readiness surfaces to apply the change. There is no automation or impersonation involved.
Trusted session reminder: if the current usage window or plan posture looks attached to the wrong workspace, return to /session before you record verification evidence or trigger billing follow-up.
Admin follow-up contextUsage
You navigated here via the admin Week 8 readiness summary. Continue the targeted onboarding, billing, verification, or go-live review for this workspace, capture the outcome on that surface, then return to the filtered admin readiness view. This is navigation-only context and does not change identity, impersonate a member, or automate remediation.
Audit export continuity
Reuse the same Latest export receipt from /settings so the filename, filters, and SHA-256 stay chained from settings through verification, go-live, and back into this admin handoff. This manual evidence relay is navigation-only; open the receipt, carry the proof in the workspace surfaces, and then return here to complete the queue or readiness loop.
Current workspace: default · Requested from admin: default · Week 8 focus: Credentials
Treat this as the manual admin → workspace surface → admin loop: follow the requested surface, capture evidence or outcome notes there, then use the return link below to restore the admin context and keep the focus state aligned.
Returning keeps the same admin filter state in place so the operator can continue the governance review without rerunning the drill-down manually.
Workspace usage and plan posture
Track billing posture, current plan usage pressure, and the next upgrade action before limits block critical operator flows.
First demo evidence lane
Keep this handoff explicit: run or rerun the demo in Playground, confirm the resulting signal in usage, then capture the same run context in verification evidence.
Evidence loop follow-through
Treat Usage as one stop in the Week 8 evidence loop: confirm the meter signal here, inspect the attached artifacts for the same run, attach or refresh verification notes, then continue to the mock go-live drill before returning to admin readiness if that was your entry point.
These links are navigation-only. They preserve workspace context across the evidence surfaces, but they do not automate attachment, review, or remediation for you.
Governed first demo signal
A successful first run should leave a usage trace we can point to in the Week 8 checklist. Confirm `billing_summary` shows the assigned plan, run a workspace demo through the Playground, and capture the `run_id`/`trace_id` before moving to verification or API key follow-up.
Step 2 happens on this page: confirm the run appears in usage metrics before documenting evidence.
Evidence relay
Once usage confirms the first-run signal, carry the same workspace context into verification, artifacts, and then back into settings or admin review as needed. This relay stays manual so the evidence trail is explicit and reusable during Week 8 readiness review.
Navigation only: this handoff preserves workspace context, but it does not auto-attach evidence or resolve billing or rollout issues for you.
Audit export continuity
Usage verifies the run, but the same Latest export receipt (filename, filters, SHA-256) from /settings needs to show up again in verification and the admin handoff so every lane keeps one shared evidence thread.
Navigation-only manual relay: these links preserve workspace context but do not auto-attach the receipt or resolve rollout issues for you.
Admin readiness follow-up
You arrived here from the Week 8 readiness summary. This dashboard stays read-only for usage pressure—record evidence and keep navigation cues aligned with the originating focus before returning to the admin view.
Plan limits
Current usage window
-
Carry this billing window into verification evidence when documenting usage pressure, upgrade follow-up, or onboarding readiness.
Plan limits are not available in this workspace.
Usage ledger stays within these limits for now; keep monitoring before the next billing cycle.
Usage metrics
No usage metrics available yet.
Billing posture and window
Billing summary is unavailable for this workspace.