Skip to content

New release — June 3: jurisdiction support, plaintiff-side litigation, and suite-wide refinements from launch feedback - #85

Open
tobinsouth wants to merge 1 commit into
mainfrom
release-2026-06-03
Open

New release — June 3: jurisdiction support, plaintiff-side litigation, and suite-wide refinements from launch feedback#85
tobinsouth wants to merge 1 commit into
mainfrom
release-2026-06-03

Conversation

@tobinsouth

@tobinsouth tobinsouth commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

A coordinated release addressing the major themes from launch feedback. 251 files; the twelve first-party plugins are versioned 1.2.0. If you are upgrading from 1.0.x, read UPGRADING.md first — one pre-update step protects files you may have authored inside the plugin directory.

Jurisdiction support

  • Every cold-start interview now asks where you practice and records a structured ## Jurisdiction block (primary jurisdiction, procedural frame, citation style) in your practice profile
  • Skills check for per-jurisdiction reference files keyed to the procedural frame before falling back to verify-tagged US frames — and warn instead of silently applying US doctrine
  • First reference set: England & Wales litigation for eight skills (CPR pleading and summary-judgment standards, PD 57AC witness statements, PD 57AD disclosure and preservation, witness summonses, pre-action protocols and Part 36, legal advice vs litigation privilege). Each file is banner-marked as staged pending practitioner review — treat contents as unverified and carry the verify tags into your output
  • Citation style is a profile field with non-US options (OSCOLA, AGLC, McGill) alongside Bluebook/ALWD

Seven new litigation skills

cite-check (standalone citation verification with per-cite verdicts and retrieval-backed checking), complaint-drafter, discovery-requests, settlement-demand, pre-suit-investigation, damages-model, judgment-enforcement — full house guardrail pattern; nothing files or sends; the Rule 11 check informs the signing attorney.

Configuration & trust

  • Cowork users: cold-start now probes the config path and automatically falls back to a claude-for-legal-config/ folder in your working directory when the home path isn't writable (mitigates the privacy-legal cold-start can't write its own config in Cowork #55) — setup persists instead of re-running every session
  • Practice profiles record a configuration attestation (configured by / authorized by / last material change)
  • The skill-installer's shipped allowlist default is fail-closed with per-registry first-use confirmation; updates are never auto-applied
  • The managed-agent audit log is hash-chained and verifiable (orchestrate.py --verify-audit); identifiers are logged as digests
  • New validator: scripts/check-guardrail-sync.py keeps the shared guardrail blocks identical across all twelve plugin templates
  • Privacy ↔ AI-governance skills can share a pointer-only index of completed assessments — opt-out at setup, status-only entries, inert in multi-client practices without matter-workspace isolation

Corrections & accuracy

Contributor experience

Full upgrade guidance: UPGRADING.md.

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

…lls, and suite-wide corrections

Highlights, built from launch feedback:

- Jurisdiction is a first-class input: every cold-start interview asks
  where you practice, profiles carry a structured Jurisdiction block,
  and skills load per-jurisdiction reference files keyed to the
  procedural frame instead of silently applying US doctrine
- England & Wales litigation reference set for eight skills (CPR
  pleading standards, PD 57AC, PD 57AD, Part 36, privilege limbs) —
  banner-marked as staged pending practitioner review
- Seven new litigation skills: cite-check, complaint-drafter,
  discovery-requests, settlement-demand, pre-suit-investigation,
  damages-model, judgment-enforcement
- Cross-plugin assessment index between privacy and AI-governance
  skills (pointer rows only, opt-out at setup, inert without matter
  isolation in multi-client practices)
- Configuration survives sandboxed environments: cold-start probes the
  config path and falls back to a working-folder directory when the
  home path is not writable
- Practice profiles record configuration attestation; the managed-agent
  audit log is hash-chained and verifiable; a guardrail sync checker
  keeps the shared template blocks identical across plugins
- Substantive corrections throughout — citation fixes, privilege and
  work-product doctrine, statutory references including the post-AIA
  section 102 bar-date screen (incorporating the correction proposed
  in #75), deadline computations — plus documentation that matches
  what actually ships (connector scope, research coverage, agent
  scheduling)
- CLA document added and the CLA workflow made tolerant of real-world
  signing comments
- Twelve first-party plugins versioned 1.2.0; see UPGRADING.md before
  updating from 1.0.x
@tobinsouth
tobinsouth force-pushed the release-2026-06-03 branch from 62df5f4 to f189f6b Compare June 3, 2026 05:05
@tobinsouth

Copy link
Copy Markdown
Collaborator Author

Public feedback welcome on this!

@atlasrealm

Copy link
Copy Markdown

If I understand correctly, for the Cowork fix to work, I need to instruct my legal team to open a new session in the same folder each time (where the config is written).

I think it this could be explained better in the main README, otherwise you risk this fix not being adopted much, even though I (at least for our company) it is a game changer!

@soulsync-cpu

Copy link
Copy Markdown

Yes

@soulsync-cpu

Copy link
Copy Markdown
image_5b91ca09

@atlasrealm

Copy link
Copy Markdown

Is this project on hold? We'd really like this PR to be merged so we can continue using the plugin in Cowork!

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.

Missing CLA.md file

3 participants