1. Inspect event evidence
Explore six synthetic experiments. Separate visible event quality from missing context and declared planning evidence.
Enterprise architecture & operations
Test the handoff.
Keep the limits visible.
Use one reference architecture, then explore the evidence behind a proposed operating relationship. These are fictional teaching cases, not client readiness findings. The AIOps steps share one workspace and keep notes in the tab. Each exercise retains distinct evidence; no result transfers or becomes a client finding.
2. Check expected sources
Compare six receipt cases against the expected-feed inventory. Clean messages alone cannot establish collection completeness.
3. Rehearse human review
Work through eight fictional cases. Keep interpretation, uncertainty and proposed next questions separate from accepted actions. This is a bounded worksheet, not a validated operational service.
Technical advisory guides & draft process prompts
Reusable guidance draws on client-specific Foundations evidence. These guides do not establish accepted scope or authorize implementation.
Plus module turnover packs
Start with the common handoff, then use the relevant standards-referencing playbook, blank editable templates and client-operated AI prompts. Download the offline reader or source pack; no data collection or engine expansion.
Hybrid cloud operational handbook
Connect service restoration, requests, change control and evidence-dependent operational capabilities across cloud and retained infrastructure. Internal guidance; client authorities retain approval.
FinOps practice playbook
Use a reusable process, ownership records and evidence-led entry criteria grounded in FinOps Foundation guidance.
Cloud foundation operations guide
Purposeful telemetry, investigation, draft AI prompts and read-only optimization profiles. Client authorities retain decisions and execution.
Marketplace commitment research
Supporting research for commitment coverage, eligibility and reconciled financial evidence.
Rehearse cost accountability
Three synthetic ledgers illustrate allocation, historical resource attribution and AI unit economics; no client inputs or live billing.
Design the cost process
Extend the cost-accountability example with proposed tagging, allocation, ephemeral tracking and invoice-reconciliation processes. Research remains proposed; no new SOW capability is implied.
Facilitated architecture workshop · Sign-in
Explore governance, support and migration choices in the protected Studio workshop. Fictional scenarios support discussion; they do not establish accepted client decisions.
Explore directional schedule impact
Use the separate planning tool for assumptions and dependencies. Directional timing and fictional RACI are not accepted client commitments.
Historical teaching examples
The earlier architecture study and fictional FedCiv rehearsal are preserved with their supporting records in the historical Library archive. Use the mission workbench for a live mission demonstration.
Training, the facilitated workshop and the four-report example retain their different jobs. Learn the method · Inspect the report package
No live telemetry, client data, AI connection or automatic response. Owner acceptance, delegated authority and applicable handling rules remain separate.