feat: add reply-router skill#211
Open
armstrongsam25 wants to merge 4 commits into
Open
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
1 participant
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 reply messages and either appends a suppression event for unsubscribes or emits a bounded routing decision for all other classifications. Never sends — just routes.
What it does
runx.reply.routing.v1routing decision with a bounded send targetHarness
Both inline cases pass:
sealed_unsubscribe_suppression: unsubscribe reply → suppression event committedstop_ambiguous_or_unsealed: ambiguous reply → stops with failure (no suppression, no routing)$ runx harness ./skills/reply-router --json {"status":"passed","case_count":2,"assertion_error_count":0,...}Files
skills/reply-router/SKILL.md— skill contract with all required sectionsskills/reply-router/X.yaml— execution profile with typed inputs/outputs and inline harnessskills/reply-router/run.mjs— implementation (classification, suppression, routing)Built for Frantic bounty #70.