Skip to content

Add Any Rule Catcher assistant workflow - #21

Open
czocher2-boop wants to merge 1 commit into
open-legal-products:mainfrom
czocher2-boop:czocher2-boop-patch-3
Open

Add Any Rule Catcher assistant workflow#21
czocher2-boop wants to merge 1 commit into
open-legal-products:mainfrom
czocher2-boop:czocher2-boop-patch-3

Conversation

@czocher2-boop

Copy link
Copy Markdown

Adds assistant-workflows/any-rule-catcher/SKILL.md.

What it does

Builds a dated, court-sourced table of every rule that actually binds one filing on one subject, across the four layers that can carry one: national or statutory, court-wide, the individual judge, and the room next door. Not a summary — a table, with a working link on every row.

No subject lives at one layer. A word limit is a national rule modified by a circuit rule modified by a judge's practices. A deadline is a triggering rule plus a computation rule plus a service rule plus a local variation.

Design decisions worth flagging

  • It asks seven questions and stops. Subject, scope, state courts, the case, ethics and statutes, columns, destination. Nothing is researched until they are answered, and a small scope is never widened quietly.
  • Withdrawn rules are listed before live ones. The most common way to be wrong is not missing a new rule; it is filing under an old one.
  • The run date goes on the face of the table. Every such table is a snapshot and has to say so, which is what lets a reader price its staleness without asking.
  • The negative is a finding. "No provision at this layer, confirmed against the current edition on [date]" is a usable answer; a blank cell is not.
  • Source of authority is never just "rule." Statute, national rule, adopted local rule, general order, judge standing order, individual practices, clerk's procedure, ethics opinion, proposal declined, proposal pending — they carry different force and different amendment paths.
  • Four named traps are checked out loud: supersession, defaults that bind by silence, the five-part computation stack, and rules a lower layer cannot lawfully change.

Compliance

  • Folder, name, and slug of metadata.mike-display-name all agree (any-rule-catcher / "Any Rule Catcher").
  • mike-availability: "add-on", mike-type: "assistant", all metadata values are strings.
  • Harness-neutral: no CLI commands, no named models or tools, and no assumption of file access — the destination step degrades to delivering the table in the conversation.
  • Original work, submitted under the repository's MIT license.
  • python3 workflow-schema/validate-workflows.py passes: 144 workflows, 16 column files, 5 packs.

Adds assistant-workflows/any-rule-catcher/SKILL.md. Builds a dated, court-sourced table of the rules that bind one filing on one subject across four layers, with withdrawn and superseded rules listed before the live ones and the run date on the face of the table.
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