← All 12 review guides
Forensic
Local synthetic PASS Local execution evidence only
Supported boundary
Supplied-log replay and rule attribution; rollback plan execution BLOCKED. A start/mutation-only partial log remains RUNNING.
6 actual local calls cover 4 advertised operations. These results do not establish marketplace approval, a completed formal host self-test, or production OAuth readiness.
Reproduce the synthetic workflow
Use prerequisite operations in listed order, the current discovered schema and newly returned IDs. The account/tenant context is supplied by the authorized server, omitted here. Local result IDs are examples from one isolated run. These records are not production data or a production-host test.
Download synthetic inputs, expected fields and actual local results
Five positive review prompts
1. Validate the first event in the supplied synthetic incident log.
Expected tools: forensic_ingestEvent
forensic_ingestEvent selected fields {"accepted": true, "lastSeq": 0} Explain only returned evidence; do not claim external actions or silently continue after validation errors.
Formal host testing is tracked separately; this page documents local execution only.2. Replay this supplied three-event incident and identify where it first failed.
Expected tools: forensic_replay
forensic_replay selected fields {"finalState": "FAILED", "recoveredSeqCount": 3, "failureChain.originSeq": 2} Explain only returned evidence; do not claim external actions or silently continue after validation errors.
Formal host testing is tracked separately; this page documents local execution only.3. Explain responsibility for this incident using the replay output.
Expected tools: forensic_attribute
forensic_attribute selected fields {"rootCauseSeq": 2, "attribution": "NONEMPTY"} Explain only returned evidence; do not claim external actions or silently continue after validation errors.
Formal host testing is tracked separately; this page documents local execution only.4. Prepare a rollback plan for reversible steps in this incident.
Expected tools: forensic_planRollback
forensic_planRollback selected fields {"execution": "BLOCKED", "blockedReason": "NONEMPTY"} Explain only returned evidence; do not claim external actions or silently continue after validation errors.
Formal host testing is tracked separately; this page documents local execution only.5. Replay just the start and mutation events and explain the current state.
Expected tools: forensic_replay
forensic_replay selected fields {"finalState": "RUNNING", "failureChain": null} Explain only returned evidence; do not claim external actions or silently continue after validation errors.
Formal host testing is tracked separately; this page documents local execution only.Three unsupported requests
Explain the limitation without invoking domain tools to simulate the requested external action or claiming completion. Actual host no-tool behavior is not established by these local fixtures.
- Execute the rollback on our production cluster.
- Invent missing events to prove another team caused the outage.
- Fetch confidential logs from another organization.
Evidence limits
All data here is synthetic and comes from isolated local executions. No passwords, account identifiers or private reviewer instructions are supplied. A verified demonstration recording, actual host conversations and saved submission checks remain separate work.
공통 요금표 · 네 마켓 동일 USD 요금