⛔ #34 docs(workflows): add declarative workflow pack format +321 26d ago by
amiel-35 ↗ analysis ↗ GitHub ## Summary
amiel-35/mikelaw-oss
A fork whose main idea is a shared, declarative format so Mike's legal-review workflows can travel between forks.
This is @amiel-35's take on making Mike's workflows portable. The central proposal here is a declarative format for describing Mike's workflows and prompt packs - a way to write a legal review template once and have it be versioned, translated, and shared across different forks rather than locked inside one. It's framed deliberately as a documentation-and-schema effort: a proposed standard and the spec that explains it, not a change to how Mike actually runs.
That scope is the tell. @amiel-35 isn't rebuilding Mike; they're trying to give the wider Mike ecosystem a common shape for the templates that matter to legal work. If you care about workflows outliving any single fork, this is the conversation to read.
Worth knowing: the fork currently sits level with upstream Mike - the work so far lives as a proposal rather than shipped divergence. Click through to GitHub if you want to read the spec and schema for yourself.
What's in it
- Declarative workflow pack format A proposed standard for describing Mike workflows and prompt packs declaratively, so they can be defined once instead of hand-wired per fork.
- Portable, shareable templates The pitch is that legal review templates become versioned and shareable between forks - workflows that travel rather than staying stuck in one codebase.
- Translatable packs The format anticipates templates being translated, aiming templates at more than one language or jurisdiction of reader.
- Spec-first, runtime-safe Deliberately scoped to a schema and written spec with no runtime behavior touched - a standards proposal, not an engine change.
Direction
workflowknowledge-managementi18n
Activity
📝 amiel-35 pitches a standard shape for Mike's workflows, and it stalls 2 commits 2mo ago workflowknowledge-management draft
A proposal to stop treating Mike's workflows as loose configuration and start treating them as structured, versionable documents - floated, debated, and ultimately shelved.
A proposed standard format that would let legal review templates be written once, versioned, translated, and shared between forks.
🟢 #34 docs(workflows): add declarative workflow pack format +321 2mo ago by
amiel-35 ↗ analysis ↗ GitHub ## Summary
Threads of work (detailed view)
amiel-35 pitches a standard shape for Mike's workflows, and it stalls
A proposal to stop treating Mike's workflows as loose configuration and start treating them as structured, versionable documents - floated, debated, and ultimately shelved.
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)
🟢 Open (1)
by
amiel-35 · opened 2mo ago ⛔ Closed without merge (1)
by
amiel-35 · opened 2mo ago · closed 26d ago