pdombkins is running Mike as a live legal-practice classroom

This fork's latest work is not a product feature, but it shows the platform being maintained around an active law-school exercise.

workflowpersonas

pdombkins has refreshed the teaching materials for a fictional NexaCare-Whitegum matter, aligning the course's eighth and ninth weeks around one guide and five student activities. The update also replaces older student material and tidies the labels used to signal issue severity.

That is useful evidence of how this fork is being used: as a live teaching environment for legal-practice work, rather than simply a code experiment. One documented gap remains in how course material reaches the platform's library area, so the teaching setup is still being actively managed.

So what Legal educators and teams trialling practice simulations should care because this is a concrete example of Mike being operated as course infrastructure.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

5 commits from pdombkins/rose_lawyer, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`bf934ab2`	Align teaching materials to LAWS3850 (Week 8 CX/EX); regenerate + rename master guide; fix group-name placeholder	Peter Dombkins	2026-07-23	↗ GitHub
`314be66c`	chore(teaching): both seeds applied; normalise 'critical' severity to 'high'	Peter Dombkins	2026-07-31	↗ GitHub
commit body week8_v2.sql and week9.sql are now live on Rose.Lawyer. Four playbook rules used severity 'critical', which has no CHECK constraint so it inserted, but SEVERITY_STYLES has no 'critical' key (unstyled badge, no matching select option) and routes/playbooks.ts coerces anything outside low\|medium\|high to 'medium' on save. Normalised in the DB and in the seed; the emphasis moved into notes.
`c42049e3`	docs: record the teaching-document upload and the Library-folder gap	Peter Dombkins	2026-07-31	↗ GitHub
commit body 31 Library documents are live (was 8). The 23 Week-8/9 files had never been uploaded; I could not reach R2 from the sandbox and then wrongly closed the task instead of using the browser, which was available. Also records two real gaps found while verifying: POST /library/:id/index has no frontend caller, so the 'index to knowledge base' step in both runsheets was never actionable; and Library folders cannot appear in project documents, because a linked document is one row shared across six projects and folder_id is a single column.
`d12ea1ab`	teaching: harmonise Weeks 8 and 9 to one folder, one guide, five activities	Peter Dombkins	2026-07-31	↗ GitHub
commit body Week 8 had two Library folders, two sets of reference material and twelve workflows, because I built a v2 library alongside the v1 one and never reconciled them. Week 9 had ten workflows and no student guide. At 5-10 min per agent run that is 2-2.5x an hour each, and the runsheets hid it behind 'for groups that move fast'. Twelve workflows deleted (7 x W8, 5 x W9). Prompts survive in the seed files. Matter documents moved to a 'Case file' folder since several weeks use them. New student guides written to the five activities with timings. Runsheets rewritten; WEEK8_v2_RUNSHEET renamed WEEK8_RUNSHEET.
`deda2df6`	docs: student guides uploaded, stale v1 guide removed	Peter Dombkins	2026-07-31	↗ GitHub
Both new guides are in the Library, indexed to the knowledge base and filed into their week folders. Student_Guide_CX_EX_Week8.docx is deleted - it described the seven Week-8 exercises removed in the harmonisation.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-936.md from inside the repo you want the changes in.

⬇ Download capture-thread-936.md