Learn from the evidence.

Your first investigation

1. Open a core case and read its brief. The terminal output is authored simulation data.
2. Reveal diagnostic results, then cite the checks that support your diagnosis.
3. Choose a hypothesis and explain the connection in your own words. Submit to see feedback.
4. Review the debrief, save a useful note, and try the related transfer case without hints.

Completion checks your selected answer, required evidence, citations, and explanation length. The app does not judge the meaning or quality of your written reasoning. A peer or facilitator can review that separately. These cases are for self-study, not a certification score.

Keep your notebook safe

Guest notes, evidence selections, hints, and submission history are stored in this browser on this site. OpsTriage does not encrypt this local storage. A different browser, profile, or site address has a different notebook. An optional cloud copy is separate from this local copy.

Export a JSON backup before clearing browser data or moving devices. Import a file or paste the complete JSON; supported runs are merged and skipped records are reported. Markdown is a readable report; JSON is the restore format. If downloads or clipboard access are blocked, use the export preview and Select all to copy manually.

If another tab changes the device notebook, saving pauses to avoid overwriting that tab. You can export the work still held in the current tab before reloading. Damaged or incompatible saved data is preserved for recovery instead of being silently replaced.

Use synthetic information only. Do not paste credentials, employer logs, customer details, or private infrastructure information into notes or explanations.

Optional accounts and cloud copies

Some deployments enable Supabase email-and-password accounts. Email confirmation may be required. You can keep using guest practice without signing in, and signing in alone does not upload or merge your notebook.

1. Check cloud notebook fetches the account's cloud snapshot so you can inspect its availability.
2. Merge cloud into this device explicitly merges supported cloud runs into this browser's notebook.
3. Upload device notebook sends your saved local runs, including notes, written reasoning, hints, and answer history, to the account's cloud copy. An existing cloud copy must first be checked and merged.

If the cloud copy changes, check and merge it again before uploading. Review the device notebook before sending it to an account, especially on a shared browser. Signing out leaves the local notebook in place.

Removing a local run does not delete a cloud copy or an exported file. This beta has no in-app cloud-deletion control; contact the project operator about removing account or cloud data. Cloud features are unavailable on deployments where they have not been configured.

Optional usage counts

Usage counts are off by default. Where collection is configured, you can explicitly allow events for a case start, a case completion, or an approximate return visit on a later day. Case events include a case identifier, and events have a random event identifier.

These event payloads do not contain account identifiers, email addresses, notes, written reasoning, or notebook contents. They are sent without your signed-in session. A local date helps avoid counting the same day repeatedly; the app does not create a visitor profile for these counts.

Turning collection off stops future events and clears the local visit date. Past counts cannot be identified as yours for deletion. The collection control is disabled where the service is not configured. Usage counts are approximate and do not establish learning outcomes.

Other data choices

The practice workflow does not send evidence to an AI provider. Your notebook leaves this browser when you explicitly upload a cloud copy or share an export. Hosting and service providers may record ordinary network requests, including IP addresses; their retention depends on their configuration. External documentation links open those providers' sites.

Sharing an exported notebook is your choice. Review its notes and explanations before sending it to anyone. Removing a local run does not remove files you already exported.

Help evaluate the beta

If the project owner invites you to a pilot, agree on a session time and any recording separately. Participation is optional. You can stop or skip a question. Use a participant alias and share only the practice work you choose.

Useful feedback includes the case title, your browser, what you expected, what happened, and the step that was confusing. Contact the person who invited you. Please keep private data out of screenshots and exports.

The pilot will evaluate whether evidence-based explanations improve on an unfamiliar case. Learner outcomes and willingness to pay have not yet been established.

Current limits

This is a guided simulator. Commands shown in cases are not executed. There are no live clusters, AWS cases, payments, or automatic remediation. Content is referenced to Kubernetes documentation; a practitioner review and learner pilot are still needed to evaluate the material and the learning experience.

The earlier free-text runbook generator is retired. Its API returns a retirement message and does not process submitted evidence.