amiel-35/mikelaw-oss

A documentation-first sketch from amiel-35 for portable legal workflow packs that could travel between Mike deployments.

Very early days - a single documentation thread, no code yet, and no pushes in the last couple of weeks.

View on GitHub →

This fork is the very early stage of an idea from amiel-35: what if legal workflows in Mike could be described in a shared, portable format - packs you could hand off, version, or share - rather than living only inside one running instance?

So far the work is a proposal on paper. There's no engine yet, no runner, no UI. amiel-35 is sketching the shape of the format first and inviting the conversation before anything gets built around it.

If you're curious about how legal workflows might be packaged and moved between Mike deployments, this is a fork to watch rather than try. Click through to GitHub to read the proposal directly.

What's in it

Direction

workflow

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

1 thread have been distilled into posts.

Pull requests (detailed view)

1 PR touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

🟢 Open (1)