10'OC 10 O'Clock AI

Incident intake / evidence container

MACHINE²MACHINE

Machine → Machine → Human

  1. 01 Machine Observe
  2. 02 Machine Understand
  3. 03 Human Rescue
  4. 04 Human Verify

Your AI setup isn't working. This page captures what the machine actually did — as a structured, machine-readable record. Observation only. No guesswork.

Open the form Read the contract
10OC Incident Intake

A machine-readable incident record. This is the evidence container that feeds the future diagnostic engine — not the diagnosis itself. Record what you observed, not your guess about root cause.

Artifact
incident-record.json
Direction
machine → machine
Secrets
never accepted

Do not paste passwords, API keys, access tokens, private keys, database credentials, or SSH credentials into this form. These fields never send secrets anywhere.

1. Incident Identity
2. Client
3. Incident Classification
4. Incident Report
Record what actually happened: the sequence of events, exactly what you did, and exactly what the system did. This is observation, not your guess about the root cause.
5. Hardware
6. Operating System
OS information only. Do not paste passwords, API keys, access tokens, private keys, database credentials, or SSH credentials.
7. AI Client & Agent
8. Model
9. API & Connectivity
Do not enter actual API keys or credentials — store the authentication type only (e.g. BEARER, API_KEY).
10. Application Stack
11. Cluster / Infrastructure
12. Incident Timeline
Record the chronological sequence of events. Add one or more entries.
13. Evidence
v1 stores local file references and metadata only. No file is uploaded and nothing is transmitted automatically.

Human handoff

The export contains the schema version, incident ID, and all populated fields, timeline, and evidence metadata. Empty fields are omitted. Nothing is sent anywhere.