⛔ #34 docs(workflows): add declarative workflow pack format +321 4mo ago by
amiel-35 ↗ analysis ↗ GitHub ## Summary
amiel-35/mikelaw-oss
An exploratory Mike fork centred on portable, structured workflow packs for legal-review work.
amiel-35's mikelaw-oss explores a clearer way to package Mike workflows and prompts: as structured, versionable packs that can be shared and adapted.
The idea includes examples for assistant-led and tabular-review work, aimed at making repeatable legal workflows easier to carry between deployments. It remains a proposal rather than a distinct product direction: the format was debated and ultimately shelved.
What's in it
- Workflow packs A proposed standard format for packaging repeatable workflows and prompts.
- Portable review templates Aims to let legal-review templates be versioned, translated, and shared across forks.
- Assistant and tabular review examples Illustrates the format through conversational assistance and structured review workflows.
Direction
workflow
Activity
A proposed standard format that would let legal review templates be written once, versioned, translated, and shared between forks.
Threads of work (detailed view)
amiel-35 wants Mike's workflows to travel
A proposed standard format that would let legal review templates be written once, versioned, translated, and shared between forks.
Declarative workflow pack schema: YAML format and JSON Schema, no runtime code
amiel-35 proposes a file-based format for Mike workflows: YAML files validated against a JSON Schema, with metadata for jurisdiction, language, and practice area. Nothing in the runtime changes yet -- this is the data model proposal before any importer is written.
Pull requests (detailed view)
⛔ Closed without merge (1)
by
amiel-35 · opened 6mo ago · closed 4mo ago