Skip to content

feat(skills): add incident commander workflow#347

Open
mossony wants to merge 2 commits into
runxhq:mainfrom
mossony:codex/frantic-112-incident-commander
Open

feat(skills): add incident commander workflow#347
mossony wants to merge 2 commits into
runxhq:mainfrom
mossony:codex/frantic-112-incident-commander

Conversation

@mossony

@mossony mossony commented Jul 18, 2026

Copy link
Copy Markdown

Summary

  • add the public incident-commander graph package with typed incident inputs and one incident_turn output
  • keep durable state and contention in the shipped agency spine while this package remains a side-effect-free decision layer
  • bind stakeholder sends to a fixed roster, digest, audience, and matching approval principal without performing the send
  • add deterministic fail-closed enforcement, two fixtures, inline harness coverage, packet schemas, and harness evidence
  • extend the public-skill archetype review with the incident command workflow

This 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 separate send-as or slack-notify plan only after the approval principal matches the fixed comms_lead roster entry.

The package cannot send, mint authority, or persist state. The outer agency runner owns read_events, reduction, append_event(expected_version), and the case_id:turn:driver_id lease.

Validation

  • runx-cli 0.7.1
  • runx harness ./skills/incident-commander -R ../runx-evidence/local-harness --json — 2/2 graph cases passed, 0 assertion errors
  • hosted registry harness — green, 2/2 cases
  • four production-signed receipt trees verified valid with no missing parents or findings
  • agency spine machine assertions — read_events versions 1..2, folded expected_version=2, CAS append 2→3, exact member receipt persisted
  • pnpm contracts:schemas:check
  • pnpm catalog:check
  • pnpm typecheck
  • pnpm test:fast — 16 files, 176 tests passed
  • git diff --check

Reproducible evidence

Evidence commit: 7989eb9ba08a481a0f764c19037236e774a0e0c2

The 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.

mossony and others added 2 commits July 18, 2026 19:33
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
mossony marked this pull request as ready for review July 19, 2026 02:29
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.

1 participant