Skip to content

docs: manual test runbook for fork-style diagnostic exploration#92

Merged
atomicdragonranch merged 1 commit into
masterfrom
docs/78-fork-runbook
Jul 9, 2026
Merged

docs: manual test runbook for fork-style diagnostic exploration#92
atomicdragonranch merged 1 commit into
masterfrom
docs/78-fork-runbook

Conversation

@atomicdragonranch

Copy link
Copy Markdown
Owner

Closes #78. Companion to #67.

Documents how to run and verify fork-style parallel diagnostic exploration:

  • How to run locally: STREAMOPS_AGENT_DIAGNOSTIC_FORKS=3, via scripts/demo_scenario.py or --single-cycle.
  • What to expect in the logs and audit trail, using the real emitted strings: the Fanning out N diagnostic forks line, per-fork Spawning Diagnostic Agent (hypothesis: ...) lines, the merged confidence distribution, cross-fork xf- conflicts with f{i}: namespaced claim ids, and the escalation surfacing (UNRESOLVED diagnostic conflict(s); forcing review).
  • How to prove it forked (4 ways): shared cid= with interleaved spawn lines (concurrent, not sequential), distinct hypotheses per fork, f{i}: namespaced ids in the merged diagnosis, xf- cross-fork conflict ids. Cross-references the asyncio.Barrier unit test.
  • Single-agent baseline (forks=1) to diff against.
  • Pointers to follow-ups feat(agent): dynamic, anomaly-derived diagnostic hypotheses (not a hard-coded list) #91 (dynamic hypotheses) and feat: cross-cycle state volatility gauge (incident dedup + change awareness) #77 (cross-cycle change awareness).

Also refreshes the README topology: the Monitor->Diagnostic edge now shows the typed DetectedAnomaly handoff (was "full text", stale since #80), the report edge notes it is attributed (#88), and a note + link points to the runbook.

Docs only; no code change.

https://claude.ai/code/session_01R5VygSzbGTggW7mHd3PVwE

Closes #78.

Companion to #67. Documents how to run the coordinator in multi-fork mode
(STREAMOPS_AGENT_DIAGNOSTIC_FORKS), what to expect in the logs and the audit
trail (with the real emitted strings: fan-out line, per-fork hypothesis spawn
lines, merged confidence distribution, cross-fork xf- conflicts, the escalation
surfacing), and four concrete ways to prove it actually forked (shared cid with
interleaved spawn lines, distinct hypotheses, f{i}: namespaced ids, xf- conflict
ids). Includes the single-agent baseline to diff against and pointers to the
follow-ups (#91 dynamic hypotheses, #77 cross-cycle change awareness).

Also refreshes the README topology: the Monitor->Diagnostic edge now shows the
typed DetectedAnomaly handoff (was "full text", stale since #80), the report
edge notes it is attributed (#88), and a note + link points to the runbook.
@atomicdragonranch atomicdragonranch merged commit 9fd4204 into master Jul 9, 2026
3 checks passed
@atomicdragonranch atomicdragonranch deleted the docs/78-fork-runbook branch July 9, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: manual test runbook for fork-style diagnostic exploration

1 participant