feat(skills): add incident commander workflow#347
Open
mossony wants to merge 2 commits into
Open
Conversation
Add a thin incident decision layer over the agency spine with roster-bound approvals, fail-closed communication handoffs, fixtures, packet schemas, and passing harness evidence. Co-authored-by: liomilet4-png <290201513+liomilet4-png@users.noreply.github.com>
mossony
marked this pull request as ready for review
July 19, 2026 02:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
incident-commandergraph package with typed incident inputs and oneincident_turnoutputagencyspine while this package remains a side-effect-free decision layerThis implementation builds on the public incident-commander draft in #330; the original author is retained as a co-author. The material completion for Frantic #112 is the raw agency-runner evidence added on this branch: a real event-stream fold and CAS append that binds the published member receipt into the incident case.
Operator impact
An operator can advance a declared incident one governed turn at a time. Communication decisions wait in
human:incident-reviewer, preserve the reviewed content digest and audience, and name a separatesend-asorslack-notifyplan only after the approval principal matches the fixedcomms_leadroster entry.The package cannot send, mint authority, or persist state. The outer
agencyrunner ownsread_events, reduction,append_event(expected_version), and thecase_id:turn:driver_idlease.Validation
runx-cli 0.7.1runx harness ./skills/incident-commander -R ../runx-evidence/local-harness --json— 2/2 graph cases passed, 0 assertion errorsread_eventsversions 1..2, foldedexpected_version=2, CAS append 2→3, exact member receipt persistedpnpm contracts:schemas:checkpnpm catalog:checkpnpm typecheckpnpm test:fast— 16 files, 176 tests passedgit diff --checkReproducible evidence
Evidence commit:
7989eb9ba08a481a0f764c19037236e774a0e0c2The summary files are indexes only. The PR commits all 19 production-signed receipt documents, four raw runtime graph-state checkpoints, and three ledgers so reviewers can inspect the actual runner envelope.