Add reply-router skill: classify inbound replies, suppress unsubscribe, route governed send-as#210
Open
armstrongsam25 wants to merge 3 commits into
Open
Add reply-router skill: classify inbound replies, suppress unsubscribe, route governed send-as#210armstrongsam25 wants to merge 3 commits into
armstrongsam25 wants to merge 3 commits into
Conversation
…e, route governed send-as Skill structure: - SKILL.md contract with compliance category - X.yaml graph runner with classify → append_suppression / emit_routing / human_lane steps - classify.mjs: validates sealed receipt, matches unsubscribe signals, routes affirmative replies - append_event.mjs: CAS append_event to registry:runx/data-store@0.1.2 with idempotency key - emit_route.mjs: emits runx.reply.routing.v1 naming a separate governed send-as run - dogfood.mjs: self-contained runner exercising all branches Harness cases: - sealed_unsubscribe_suppression: sealed receipt + unsubscribe text → suppress - stop_ambiguous_or_unsealed: unsealed receipt + ambiguous text → needs_agent Fixtures: unsubscribe, ambiguous/unsealed, routed reply
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.
reply-router skill
A native runx skill that classifies inbound replies against a sealed send receipt and either appends a recipient-keyed suppression event or emits a bounded governed routing decision without sending.
Behavior
append_eventagainstregistry:runx/data-store@0.1.2. The resulting record is the compliance block the next send-as preflight reads as a fail-closed block.runx.reply.routing.v1decision naming a separate governed send-as run that performs the send later. The skill never sends.needs_agent) with no suppression write and no routing decision.Files
skills/reply-router/SKILL.md— skill contractskills/reply-router/X.yaml— graph runner profile with inline harness casesskills/reply-router/classify.mjs— classify step (validates sealed receipt, matches signals)skills/reply-router/append_event.mjs— suppression step (CAS append_event)skills/reply-router/emit_route.mjs— routing step (runx.reply.routing.v1)skills/reply-router/dogfood.mjs— self-contained dogfood runnerskills/reply-router/fixtures/— test fixturesskills/reply-router/evidence/— harness, dogfood, verification, registry-read evidenceHarness
Both inline harness cases pass:
sealed_unsubscribe_suppression→ sealed (suppress path)stop_ambiguous_or_unsealed→ needs_agent (stop path)Safety