Changelog

Twenty-issue completion batch

• Expanded the end-to-end open issue batch to 20 verified issues across trust, lifecycle taxonomy, freemium conversion, security, workspace governance, OPS safety, civil registries and world rollout.
• Added completion checks for DB-session fallback safety, Dispute-vs-Matter thresholds, workspace registry coverage, safety-restoring-only live-ops actions, rights-lane isolation and deterministic rollout queue behavior.
• Recorded the 20-issue batch in the release note while keeping saved issues #86 and #157 out of scope and excluding destructive/provider-only work.

End-to-end open issue batch

• Selected and implemented a verified 10-issue open batch (#129, #154, #187, #192, #193, #194, #197, #203, #208 and #210) while keeping saved issues #86 and #157 out of the release.
• Added an open-issue completion harness that ties each issue to concrete security, OPS, civil-registry and world-rollout proof in the repository.
• Added deterministic rollout queue checks plus US, Canada and world-pack completion tests so the batch is continuously verified by npm test.

Audit-chain substrate

• Added the database-backed audit-chain substrate for issue #129: immutable audit_chain_events and audit_chain_anchors tables with tenant sequence uniqueness, hash-format constraints, RLS and no public mutation policies.
• Extended the security audit tests so tampered records, deleted/reordered chains, forged Merkle proofs, anchor signature changes and missing database immutability guards all fail.
• Updated the security plan to distinguish the existing matter activity log from the new tamper-evident substrate, while keeping backup/restore and envelope encryption listed as remaining target-state controls.

OPS and platform governance batch

• Selected the next 10 open issues across OPS handoff, canaries, break-glass, professional workspaces, document taxonomy, freemium conversion and Conflict OS, with their implementation state recorded in a committed batch note.
• Added a testable platform governance module for safety-restoring agent actions, rights-lane rollback exclusion, break-glass quorum policy, the 12 professional workspace families and Dispute-vs-Matter conversion thresholds.
• Connected the governance checks to the existing prevention-first lifecycle and canonical document taxonomy so Conflict OS and document classification stay anchored to real product surfaces.

World-edition registry integrity checks

• Added an integrity test suite for the world-edition registry: every edition must expose a non-empty 'en' fallback key, the display order and registry must describe the same id set with no duplicates, the default locale must be the first offered language, and currency and URL fields must be well-formed.
• Registered the suite in the test script so it runs continuously and blocks silent regressions when new jurisdiction packs are added.

Google OAuth activation helper

• Added an owner-only script that enables the Supabase Google provider from the ignored Google OAuth JSON file without committing the client secret.
• The helper verifies Supabase redirects to Google after activation and keeps the downloaded client secret JSON excluded from git.

Google auth and readiness issue batch

• Added Google account sign-up/sign-in through the existing Supabase auth callback, with bilingual auth labels and a system-status readiness flag.
• Recorded the selected 10 open issues and their implementation state, distinguishing implemented code from provider, legal, deployment, backup, or rollback gates that still require external action.
• Aligned trust readiness checks with the actual upload safety, CSAM, transactional delivery, Twilio, and Stripe Express payout adapters, with regression coverage for the readiness gates.

Canadian jurisdiction coverage page

• Published a public Canadian jurisdiction coverage page showing courts, small-claims ceilings, professional-verification bodies, working languages, and per-feature support for every province and territory.
• Linked the coverage page from the resources footer and added it to the canonical public route list so it is included in localized navigation helpers and sitemaps.

Provider payout escrow

• Added a provider payout escrow state machine with strictly gated release, Stripe refund and dispute handling, clawback math, and a backward-compatible ledger migration.
• Added payout escrow, disbursement, refund, and webhook regression coverage so provider funds cannot release from an invalid state.

Verifiable audit substrate

• Added a storage-agnostic audit substrate with hash-chained records, Merkle proofs, notary anchors, and proof-bundle verification.
• Added regression coverage for edited, deleted, reordered, forged, and independently verified audit records before persistence wiring.

Canadian jurisdiction model expansion

• Expanded the Canadian jurisdiction model with explicit courts, small-claims forums, law-society verification metadata, bilingual-service flags, and no Québec fallback outside Québec.
• Added coverage for province and territory support maps so unsupported features surface explicitly instead of inheriting another jurisdiction's data.

United States federal registry pack

• Added the United States federal jurisdiction pack with federal courts, agency adjudication, records access, consumer protection, legal-aid, and provenance routing.
• Refreshed the six United States territory packs so DC, Puerto Rico, Guam, the Virgin Islands, American Samoa, and the Northern Mariana Islands align with the federal registry model.

French overseas territory registry packs

• Added gated registry packs for Guadeloupe, Martinique, French Guiana, Reunion, Mayotte, Saint Barthelemy, Saint Martin, Saint Pierre and Miquelon, French Polynesia, New Caledonia, Wallis and Futuna, and the French Southern and Antarctic Lands.
• Modeled EU outermost regions, overseas collectivities, Pacific customary and land layers, and TAAF no-permanent-population routing as complete registry records.

Founder message production release

• Published the founder-message homepage release under the verified project author so production deployments can pass Vercel attribution checks.
• Kept the localized founder message behind the homepage button while preserving the full product explanation on every edition page.

Founder sprint message

• Added a founder-led sprint message behind a homepage button so visitors can understand the current July 4 development push without replacing the product page.
• Localized the founder message across shipped interface languages and linked the mission callout to JusticeSansFrontieres.ca.

Localized edition homepage and Judge911 cleanup

• Removed the remaining hyphenated Judge911 brand fallback from country edition pages so localized copy uses Judge911 consistently.
• Renamed the public Judge911 logo assets and updated the US edition header to use the non-hyphenated asset path.
• Moved country edition pages onto the shared localized homepage so Canada and every other edition show the same full product explanation as the main site.
• Linked the active QC edition badge directly to the Québec edition page and advertised the 195-country-and-territory footprint on the homepage.

Changelog sprint and category filters

• Added interactive filters to the changelog so the global chronological history can be sliced by release sprint, category and keyword.
• Inferred categories from existing release titles and change text, avoiding duplicate changelog files or manual re-tagging of past entries.
• Added unit coverage for sprint grouping, category inference and combined filter behavior.

Audio and video taxonomy groups

• Promoted Audio and Video from evidence tags into first-class document taxonomy groups and categories.
• Updated document migration so existing media records self-heal into the new Audio or Video category when loaded.
• Adjusted classifier coverage so audio recordings classify as AUDIO instead of generic EVIDENCE.

Document classification review step

• Added a dedicated Classify workspace step where users can confirm or correct each document's inferred type.
• Sorted unconfirmed and lower-confidence documents first, with one-click confirmation and grouped taxonomy selection.
• Connected the workflow stepper's Classify stage to the new review tab instead of sending users back to Evidence.

Six-stage workspace workflow

• Added a compact Create, Upload, Classify, Timeline, Resolution and Legal workflow stepper to the selected-matter view.
• Derived the current stage from existing matter state without adding backend gates or schema changes.
• Made each stage an accessible shortcut to the corresponding workspace tab.

Evidence media filters and playback

• Surfaced Communications, Audio, Video, Investigations, Resolution Activities and Legal Procedures as first-class evidence filter chips.
• Matched media filters by tag and MIME prefix so raw audio or video uploads can be found before manual tagging.
• Added inline audio and video playback to the workspace file viewer.

Dossier card action menu

• Moved matter deletion behind an accessible overflow menu so destructive actions require a deliberate second step.
• Preserved direct matter-card opening while preventing menu interactions from triggering card navigation.
• Added keyboard and outside-click handling for the matter action menu.

Floating add-document action

• Added an optional floating Add document action to the global scroll navigation stack.
• Registered the workspace intake launcher with the floating control while hiding it during full-screen overlays.
• Kept the action accessible with labels, focus states and a mount-order handshake.

Dossier upload failure handling

• Stopped swallowing evidence-upload failures during document import.
• Surfaced the real upload error with the affected filename so RLS, expired-session and storage issues are visible.
• Prevented failed uploads from creating half-imported phantom evidence records.

French changelog polish

• Polished the French 5.23.1 expert marketplace release note so the public changelog reads cleanly.
• Kept the release scoped to public-facing copy only; the expert marketplace taxonomy and routes remain unchanged.

Expert marketplace taxonomy pages

• Expanded the expert marketplace fallback taxonomy to cover every medical, engineering, financial, real-property, forensic, regulatory, language, environmental, workplace and specialized appraisal discipline.
• Turned taxonomy cards into direct marketplace links so each discipline has a shareable expert-market page.
• Updated expert marketplace copy to support legal proceedings and technical mandates beyond a Quebec-only framing.

US rollout version rollover

• Rolled the release line forward from 5.22.100 to 5.23.0 after completing the US states, DC and territories registry rollout.
• Kept the canonical package version SemVer-valid while preserving the chronological changelog history for the 5.22.x jurisdiction releases.

Northern Mariana Islands jurisdiction pack

• Added the Northern Mariana Islands civil jurisdiction pack (us.mp) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

American Samoa jurisdiction pack

• Added the American Samoa civil jurisdiction pack (us.as) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

U.S. Virgin Islands jurisdiction pack

• Added the U.S. Virgin Islands civil jurisdiction pack (us.vi) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Guam jurisdiction pack

• Added the Guam civil jurisdiction pack (us.gu) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Puerto Rico jurisdiction pack

• Added the Puerto Rico civil jurisdiction pack (us.pr) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

District of Columbia jurisdiction pack

• Added the District of Columbia civil jurisdiction pack (us.dc) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Wyoming jurisdiction pack

• Added the Wyoming civil jurisdiction pack (us.wy) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Vermont jurisdiction pack

• Added the Vermont civil jurisdiction pack (us.vt) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Alaska jurisdiction pack

• Added the Alaska civil jurisdiction pack (us.ak) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

North Dakota jurisdiction pack

• Added the North Dakota civil jurisdiction pack (us.nd) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

South Dakota jurisdiction pack

• Added the South Dakota civil jurisdiction pack (us.sd) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Cuba jurisdiction pack

• Added the gated Cuba (cu) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Zimbabwe jurisdiction pack

• Added the gated Zimbabwe (zw) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Bolivia jurisdiction pack

• Added the gated Bolivia (bo) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Ireland jurisdiction pack

• Added the gated Ireland (ie) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

United Arab Emirates jurisdiction pack

• Added the gated United Arab Emirates (ae) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Sri Lanka jurisdiction pack

• Added the gated Sri Lanka (lk) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Delaware jurisdiction pack

• Added the Delaware civil jurisdiction pack (us.de) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Russia jurisdiction pack

• Added the gated Russia (ru) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Venezuela jurisdiction pack

• Added the gated Venezuela (ve) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Angola jurisdiction pack

• Added the gated Angola (ao) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Israel jurisdiction pack

• Added the gated Israel (il) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Cameroon jurisdiction pack

• Added the gated Cameroon (cm) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Austria jurisdiction pack

• Added the gated Austria (at) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Afghanistan jurisdiction pack

• Added the gated Afghanistan (af) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Sudan jurisdiction pack

• Added the gated Sudan (sd) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Nepal jurisdiction pack

• Added the gated Nepal (np) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Kazakhstan jurisdiction pack

• Added the gated Kazakhstan (kz) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Ghana jurisdiction pack

• Added the gated Ghana (gh) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Chile jurisdiction pack

• Added the gated Chile (cl) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Rhode Island jurisdiction pack

• Added the Rhode Island civil jurisdiction pack (us.ri) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Montana jurisdiction pack

• Added the Montana civil jurisdiction pack (us.mt) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Uganda jurisdiction pack

• Added the gated Uganda (ug) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Myanmar jurisdiction pack

• Added the gated Myanmar (mm) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Algeria jurisdiction pack

• Added the gated Algeria (dz) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Iraq jurisdiction pack

• Added the gated Iraq (iq) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Switzerland jurisdiction pack

• Added the gated Switzerland (ch) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

New Zealand jurisdiction pack

• Added the gated New Zealand (nz) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Maine jurisdiction pack

• Added the Maine civil jurisdiction pack (us.me) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Uzbekistan jurisdiction pack

• Added the gated Uzbekistan (uz) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Tanzania jurisdiction pack

• Added the gated Tanzania (tz) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Peru jurisdiction pack

• Added the gated Peru (pe) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Morocco jurisdiction pack

• Added the gated Morocco (ma) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Malaysia jurisdiction pack

• Added the gated Malaysia (my) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Australia jurisdiction pack

• Added the gated Australia (au) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

New Hampshire jurisdiction pack

• Added the New Hampshire civil jurisdiction pack (us.nh) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Poland jurisdiction pack

• Added the gated Poland (pl) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Spain jurisdiction pack

• Added the gated Spain (es) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Italy jurisdiction pack

• Added the gated Italy (it) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

England and Wales jurisdiction pack

• Added the gated England and Wales (gb.ews) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

France jurisdiction pack

• Added the gated France (fr) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Germany jurisdiction pack

• Added the gated Germany (de) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Canada (federal) jurisdiction pack

• Added the gated Canada (federal) (ca.fed) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Nunavut jurisdiction pack

• Added the gated Nunavut (ca.nu) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Yukon jurisdiction pack

• Added the gated Yukon (ca.yt) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Northwest Territories jurisdiction pack

• Added the gated Northwest Territories (ca.nt) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Prince Edward Island jurisdiction pack

• Added the gated Prince Edward Island (ca.pe) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Newfoundland and Labrador jurisdiction pack

• Added the gated Newfoundland and Labrador (ca.nl) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

New Brunswick jurisdiction pack

• Added the gated New Brunswick (ca.nb) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Nova Scotia jurisdiction pack

• Added the gated Nova Scotia (ca.ns) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Saskatchewan jurisdiction pack

• Added the gated Saskatchewan (ca.sk) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Manitoba jurisdiction pack

• Added the gated Manitoba (ca.mb) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Alberta jurisdiction pack

• Added the gated Alberta (ca.ab) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

British Columbia jurisdiction pack

• Added the gated British Columbia (ca.bc) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Ontario jurisdiction pack

• Added the gated Ontario (ca.on) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Quebec jurisdiction pack

• Added the gated Quebec (ca.qc) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Saudi Arabia jurisdiction pack

• Added the gated Saudi Arabia (sa) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Kenya jurisdiction pack

• Added the gated Kenya (ke) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Argentina jurisdiction pack

• Added the gated Argentina (ar) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Colombia jurisdiction pack

• Added the gated Colombia (co) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

South Korea jurisdiction pack

• Added the gated South Korea (kr) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

DR Congo jurisdiction pack

• Added the gated DR Congo (cd) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Thailand jurisdiction pack

• Added the gated Thailand (th) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Ethiopia jurisdiction pack

• Added the gated Ethiopia (et) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Türkiye jurisdiction pack

• Added the gated Türkiye (tr) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Iran jurisdiction pack

• Added the gated Iran (ir) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

South Africa jurisdiction pack

• Added the gated South Africa (za) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Egypt jurisdiction pack

• Added the gated Egypt (eg) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Vietnam jurisdiction pack

• Added the gated Vietnam (vn) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Philippines jurisdiction pack

• Added the gated Philippines (ph) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Mexico jurisdiction pack

• Added the gated Mexico (mx) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Brazil jurisdiction pack

• Added the gated Brazil (br) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Nigeria jurisdiction pack

• Added the gated Nigeria (ng) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Japan jurisdiction pack

• Added the gated Japan (jp) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Bangladesh jurisdiction pack

• Added the gated Bangladesh (bd) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Pakistan jurisdiction pack

• Added the gated Pakistan (pk) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Indonesia jurisdiction pack

• Added the gated Indonesia (id) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

China jurisdiction pack

• Added the gated China (cn) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

India jurisdiction pack

• Added the gated India (in) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Scotland jurisdiction pack

• Added the gated Scotland (gb.sct) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Sweden jurisdiction pack

• Added the gated Sweden (se) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Romania jurisdiction pack

• Added the gated Romania (ro) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Belgium jurisdiction pack

• Added the gated Belgium (be) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Netherlands jurisdiction pack

• Added the gated Netherlands (nl) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Ukraine jurisdiction pack

• Added the gated Ukraine (ua) jurisdiction registry pack — court structure modeled true, all 12 administrative-justice categories scored, governance/records and access-to-justice routes, with official-source provenance.

Hawaii jurisdiction pack

• Added the Hawaii civil jurisdiction pack (us.hi) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

West Virginia jurisdiction pack

• Added the West Virginia civil jurisdiction pack (us.wv) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Idaho jurisdiction pack

• Added the Idaho civil jurisdiction pack (us.id) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Nebraska jurisdiction pack

• Added the Nebraska civil jurisdiction pack (us.ne) as a separate registry file.
• Documented the jurisdiction's court structure, administrative adjudication routes, public-records regime, consumer-protection body and access-to-justice resources.
• Kept this release scoped to one jurisdiction so the version history remains incremental and reviewable.

Release automation guard

• Disabled the push-based auto-version bump so manually versioned jurisdiction PRs keep their intended release numbers and changelog entries.
• Aligned package metadata, lockfile and the UI version after the automated v5.22.0 bump advanced the version without adding a bilingual changelog entry.
• Paused the US rollout merge queue until each remaining jurisdiction can land with a clean one-version, one-jurisdiction history.

New Mexico jurisdiction pack

• Added the New Mexico civil jurisdiction pack (us.nm) as a separate registry file.
• The release covers court structure, administrative adjudication, public records, consumer protection and access-to-justice routes.
• Kept this version scoped to one jurisdiction so the release history stays incremental.

Kansas jurisdiction pack

• Added the Kansas civil jurisdiction pack (us.ks) as a separate registry file.
• The release covers court structure, administrative adjudication, public records, consumer protection and access-to-justice routes.
• Kept this version scoped to one jurisdiction so the release history stays incremental.

Mississippi jurisdiction pack

• Added the Mississippi civil jurisdiction pack as one registry file with the state's court tree, administrative adjudication routes, public-records regime and access-to-justice resources.
• Modeled Mississippi's Circuit, Chancery, County, Justice and Municipal Court layers without flattening family, probate, small-claims or agency-review paths.
• Kept this release scoped to one jurisdiction so the version history remains incremental and easy to review.

US state registry wave

• Merged the gated US civil jurisdiction packs for Texas, Florida, Pennsylvania, Illinois, Ohio, Georgia, North Carolina, Michigan, Virginia, Washington, Arizona, Tennessee, Massachusetts, Indiana, Missouri, Maryland, Wisconsin, Colorado, Minnesota, Louisiana, South Carolina, Kentucky, Oregon, Alabama, Oklahoma, Utah, Nevada, Arkansas and Iowa.
• Each state pack remains jurisdiction-as-data: one registry file per state, official-source provenance, 12-category administrative adjudication coverage, court structure, governance and records routes, and access-to-justice entries.
• Aligned the release metadata, lockfile and bilingual changelog after the automated v5.21.0 bump landed separately.

Release metadata aligned

• Manually aligned the published version after the automated bump to 5.16.2 so the site, package metadata and changelog stay consistent.
• The bilingual release note confirms that the local matter sync and imported-folder provenance fixes are present on main.

Cloud sync and local provenance

• Local matter imports can now fall back to an authenticated server route that attaches the matter to the signed-in account when direct RLS-protected writes are rejected.
• Each matter can remember imported local workspaces, including the source folder name and relative file paths, preparing the ground for future local reorganization.
• The dashboard and Evidence workspace now show the local location linked to a matter without claiming direct disk access before local permission is granted.

TAQ intake and local matter recovery

• Added Tribunal administratif du Québec recognition across document intake, generated court labels and workspace court filters.
• Made local-only matters visible in the workspace sync state and easier to import into the cloud.
• Kept document intake destinations explicit so uploads can be assigned to the correct existing matter.

Fast-path folder import

• Whole-folder import now shows a progress screen with files detected, accepted, ignored, OCR pending and errors.
• Once the import queue is created, the workspace automatically opens classification review so large uploads no longer require scrolling before continuing.
• Added the “Continue automatically after upload” setting, enabled by default, with an option to stay on the screen when adding more files.

Workspace portal and evidence upload fixes

• Added Investigations and Bailiff portals to the top workspace navigation beside the Firm portal.
• Separated adding files to an open matter from importing a matter-backup JSON file, with the document intake preselecting the open matter.
• Stopped signed-in evidence uploads from silently falling back to browser storage when the cloud save fails; users now see a clear retryable error.

Visible investigation entry point

• Added an Investigations link to the workspace home navigation so the investigation module is reachable without hunting through the matter tab strip.
• Added a Plan an investigation action card that opens the Investigation module for a single matter or jumps to My matters when the user has several files.
• Added an Investigations & asset search marketplace card so investigator services are visible beside attorneys, bailiffs and commissioners.

Safer operator credential loading

• Updated owner-run Supabase scripts to prefer .env.production.local before .env.local so production admin operations do not mix development public URLs with production service credentials.
• Clarified the recovery guidance emitted by the founder script so missing admin credentials point operators to the production local env file.
• Kept real credentials out of committed source while preserving the environment-variable wiring needed for launch operations.

Launch control docs and operator scripts

• Added a launch-control note that separates what works today, intentional limits, dashboard setup gaps and claims that must not be promised yet.
• Documented the Phase 1 public-beta scope split around the self-represented litigant spine from intake through export or next action.
• Added owner-run Supabase helper scripts for founder access, attorney approval and targeted account deletion during launch operations.

Clearer AI import confirmation

• Redesigned the document-import match step with explicit Step 1 and Step 2 headings so court-file confirmation and matter destination read as separate decisions.
• Removed radio controls when there is only one detected court file number or only one destination, replacing them with confirmation cards and an edit escape hatch.
• Added an import summary card showing the court file, target matter and detected document type before the final confirmation.

Reliable cloud import for stranded local matters

• Made the stranded-local-matter import wait for the final cloud write before showing success.
• Stranded local matters now appear in My matters immediately with a local-only sync badge, so they can be opened before cloud migration.
• After a successful cloud migration, imported matters are removed from browser storage so the database remains the signed-in source of truth.
• Failed imports now keep the local matter intact and show a clear retryable error instead of silently hiding the problem.

Secret-gated founder auth recovery

• Added a locked-down POST /api/auth/recover endpoint that can mint a one-time Supabase magic link for allowlisted founder emails without sending email.
• Protected the recovery route with AUTH_RECOVERY_SECRET, service-role-only execution and an AUTH_RECOVERY_EMAILS allowlist override for production operations.
• Returns clear operational errors when recovery is disabled, the service role is missing or Supabase cannot generate the link.

Testim cross-browser E2E workflow and token wiring

• Added a manual, dispatch-only Testim grid workflow that runs the cross-browser E2E suite by label (smoke, auth, core, locale, trust) against the production site.
• Wired the Testim CLI token through a TESTIM_TOKEN repository secret and standardized the token name across the test script, local environment and CI.
• The workflow guards against a missing token and uploads JUnit results as a build artifact for review.

Momentic persona journeys and Support Center capacity notice

• Added a Momentic persona and journey suite for public smoke, self-represented litigant, lawyer ethics, expert provider, service buyer, founding partner and trust-review flows.
• Added command-line Momentic runners for local, smoke, persona, production and upload workflows, with the API key passed through the environment.
• Added an operational notice on /support explaining the current intensive testing period, observed sign-in limits and capacity upgrade work.
• Added a public progress grid for sign-in, concurrent capacity, code audit and expanded login-option workstreams.
• The communication acknowledges user inconvenience while presenting stabilization of the 5.7 family as this week's priority work.

Investigation workspace and mandate marketplace

• Added an Investigation tab to every matter: investigator assignments, fieldwork, deliverables, live feed, risk flags and promotion into chronology or tasks.
• Added an investigation mandate marketplace flow: attorneys post mandates, approved investigators can claim them, and status remains visible to the team, admin and client.
• Added a local investigator portal (/app/investigator) and a Supabase migration for mandates, assignments, deliverables, live events and risk flags.

Matter classification architecture

• Replaced litigation-only document classification with a full lifecycle taxonomy covering communications, evidence, investigation, dispute resolution, legal analysis, settlement, enforcement, AI work product and risk material.
• Added automatic classification for emails, call logs, recordings, transcripts, municipal reports, OBSI/FCAC complaints, settlement proposals and chronologies, with confidence fields and custody metadata.
• The evidence register now uses grouped category filters and neutral recording metadata such as “Participant recording.”

Public portal — upload-first onboarding

• Launched the public-facing portal with upload-first onboarding: citizens can upload a document to start, see an instant AI-powered summary, and enter the workspace without a prior account.
• Added an onboarding modal that surfaces no-legal-advice guardrails and guides new users through the first-file flow.
• Fixed import persistence across logout/login cycles so documents and matter state survive session boundaries.
• Automated semantic-version bumping on every merge to main via CI (chore(release) commit + git tag).

Provider payout escrow

• Added a provider payout escrow state machine with strictly gated release, Stripe refund and dispute handling, clawback math, and a backward-compatible ledger migration.

Transactional notification delivery

• Added provider-agnostic email/SMS delivery, an idempotent Supabase outbox with RLS, cautious bilingual templates and a gated server route to prepare deadline reminders, verification updates and marketplace intakes.

Search-engine launch preparation

• Added webmaster verification metadata hooks, an IndexNow key endpoint and submission script, and expanded the search-engine launch checklist so global edition pages are prepared for sitemap submission beyond Google.

Compact edition menu and German launch copy

• Moved the global edition list into a compact dropdown, added German as an informational locale, and made the Germany country edition resolve to German-first product and legal-prep copy.

Country-edition shortcut URLs

• Added country-edition shortcuts such as /editions/pt, /editions/br and /br so testers can reach localized country edition pages without remembering the full /{language}/editions/{country} URL pattern.

Global country editions and localized launch surfaces

• Expanded the single-codebase edition registry globally with 190+ country and regional editions, country-specific currencies, native-language launch targets, legal-template packs, local authority fallbacks, localized country-edition pages, hreflang sitemaps and a multi-search-engine launch checklist.

Operational content for beta surfaces

• Replaced temporary marketplace and expert-discipline copy with concrete beta framing, preparation guidance and actionable empty states.

Edition-aware cookies and disclaimer pages

• Cookies and disclaimer pages now use the same edition-aware legal resolver as privacy, terms and data-rights: the US edition uses Judge911.com branding and English-prevailing legal posture, while Québec keeps Loi 96/French-prevailing framing with counsel-gated placeholders where final notices still need review.

Edition-aware legal documents

• Privacy, terms, legal notices, data-rights, retention and legal-hold copy now follow the active edition: Québec remains Law 25/Loi 96 with French prevailing, while the US edition is marked as US-law, English-prevailing and counsel-gated where final legal drafting is pending.

Edition-aware money formatting

• Money displays, marketplace prompts and checkout currency now use the active edition's currency resolver, so Québec and Canada stay in CAD while the US edition uses USD.

Edition-aligned home locale and brand

• Default language routing and primary brand labels now follow the active edition: Judge911.com opens in English by default and the US edition interface uses the Judge911.com brand.

Edition-aware canonical metadata

• Metadata, HTTP Link headers, canonical links and structured data now use the active edition domain, so Judge911.com no longer publishes SEO links pointing back to Juge.ca.

Automated referral acceptance

• The growth engine now counts an invitation automatically as soon as authentication confirms the new account, with idempotent processing that prevents duplicates and keeps the accepted counter synchronized.

Multi-edition platform and marketplace contact protection

• Introduced a single-codebase edition system (Québec, Canada, United States) with an always-visible edition notice that cross-links each regional site, so brand, jurisdiction, language and currency follow the edition automatically.
• Added marketplace contact protection: a professional's email is never exposed, inquiries are relayed through our own mail servers, and shared phone numbers, emails and messaging handles are masked until an engagement is confirmed.

Footer branch links to its live deployment

• The branch name in the footer version line is now a link to that deployment's live URL, making it easy to open and review preview/experiment builds from the page itself.

Restored Juge.ca brand across the interface

• Restored "Juge.ca" as the platform display name across titles, homepage, signup, chat, FAQ, roadmap, campaigns and the disclaimer, replacing the "Judge911.com" references that had been reintroduced. Email addresses and external links were left unchanged.

HubSpot fallback submission restored

• Switched the server-side HubSpot fallback to the legacy form upload endpoint accepted by the original waitlist form, restoring successful HubSpot forwarding without a private CRM token.

Early-access lead capture fix

• Replaced the broken HubSpot embedded early-access form with the first-party newsletter signup endpoint so leads are saved before HubSpot forwarding.
• Consolidated newsletter HubSpot forwarding onto the shared server-side contact upsert helper, including updates for existing contacts.
• Added a server-side HubSpot Forms API fallback using the validated original waitlist form GUID, and surfaced that lead-capture readiness in /api/health.

IP protection attached to the sovereign canon

• Added a Juge.ca-specific IP canon, private proprietary license, no-implied-license notice and publishing rules adapted to King Legend Inc.
• Added an IP register and protection runbook that separate platform assets from confidential user-owned matter documents.
• Added `npm run check:ip` and wired the IP posture into release checks so the superseded King Legend Group operator wording cannot return.

Automatic time-tracking core

• Added a pure sessionizer that turns activity signals into non-overlapping work sessions while excluding idle gaps.
• Added a client provider that emits content-free workspace signals with heartbeats, idle detection, tab visibility handling and sendBeacon flushing.
• Added an /api/activity endpoint that validates signals, rejects note or document text metadata and prepares append-only backend ingestion.
• Added configurable billable-hour rounding, including tenth-hour billing and the demo configuration that maps 21 minutes to 0.35 hr.
• Added template billing narratives and tests covering exhibit reading, breaks, context switches, two tabs, noise drops, signal privacy and deterministic re-derivation.
• Strengthened the disclaimer with Québec-first language on general legal information, AI limits, affiliated partners, feedback and professional responsibility.

Justice and criminal expansion roadmap

• Added a "Save lives through access to justice" roadmap section connecting the civil-first strategy, distress detection, evidence intelligence, and cautious criminal-law pilots.
• Published a founding principle: Juge.ca should detect legal, financial, and personal points of collapse before they cost people rights, dignity, liberty, or safety.
• Added trust guardrails: staged criminal-law entry, separated infrastructure for sensitive evidence, mandatory human oversight, and explainable transparency.

AI and platform disclaimer

• Added a bilingual /disclaimer page (FR/EN/ES) covering no-legal-advice, AI-generated content, third-party references and feedback, built from a shared, portable brand module.
• Added a standing AI-content notice in the footer on every page, linking to the full disclaimer, plus a Disclaimer link in the legal column.
• Added the "AI content may contain errors — verify before relying" notice to generated drafts and the support assistant.
• Changed the platform display name from "Judge911" to "Juge.ca" across the interface.

Knowledge base navigation

• Added a Learn link to the main navigation so the public guide library is reachable from every page.

Legal content engine and guide library

• Added a bilingual public learning hub at /learn, a guide index at /guides and six practical starter guides for service, evidence, banking disputes, housing, deadlines and small-business contract disputes.
• Added Article, FAQPage and BreadcrumbList structured data plus sitemap coverage for every seeded guide slug.
• Added a guarded /admin/content workspace with editorial inventory, publication checklist, production prompt and Command Center shortcut.
• Added guide integrity tests covering slug uniqueness, bilingual parity, required fields, schema generation and sitemap paths.

Global expansion scoring model

• Added a Growth Engine expansion model that scores candidate markets across access-to-justice need, population scale, launch ease, revenue potential and institutional openness.
• Added strategic lenses for balanced, leverage-and-speed, raw-scale and mission-driven ranking so expansion planning can compare markets without rewriting the data.
• Added tests covering score normalization, market integrity, distinct ranking behavior and the six Wave-1 lead markets.

Referral growth engine

• Added reusable Judge911 referral links at /r/{code}, with click tracking, signup attribution and a signed-in referral dashboard.
• Added a referral_codes table so one public link can invite multiple users while referrals remains the per-accepted-user ledger.
• Added beta-safe invite-five progress tracking with manual reward review language and no attorney-referral or fee-sharing implication.

Campaign admin guard hardening

• The campaign engine admin page now forces dynamic request-time rendering so the existing server-side administrator check always runs before the page is shown.

365-day campaign engine

• Added a guarded /admin/campaigns growth workspace with the first 10 Judge911 campaign angles, A/B copy, French and English versions, and Facebook / Instagram / LinkedIn / X / Threads export previews.
• Added a deterministic 365-day scheduler and an admin JSON export route so the campaign system can produce platform-ready posts with UTM attribution.
• Seeded the existing Growth Engine campaign registry with Campaigns 001-010 and added a Command Center shortcut to the campaign engine.

Judge911 Growth Engine v1 foundation

• Homepage conversion copy now leads with “Facing a Legal Problem?”, with Start My Matter and Learn How It Works calls to action instrumented for funnel tracking.
• Added site-wide growth tracking for page views, CTA clicks, funnel starts, sticky Start My Matter clicks and exit-intent checklist requests.
• Added /api/growth/events, /api/public/stats and the Growth Engine database tables for growth_events, campaigns and referrals, plus a live activity dashboard section on the homepage.

Founding Partners Program

• Added a homepage Founding Partners Program section near the Juge.ca future-building CTA.
• Added bilingual founding partner conversion routes, including /en/founding-partners and /fr/partenaires-fondateurs, with program tiers, contribution types and a compliant application form.
• Added a trusted server intake route and RLS-protected founding partner applications table, with best-effort HubSpot forwarding and explicit King Legend Inc. consent language.

Pre-storage upload safety scanning

• Evidence ingestion now calls a server-side upload safety scanner before writing binary files to the private evidence bucket.
• The path blocks storage when malware scanning or CSAM safety is required/live but not configured, or when a scanner returns a blocking verdict.
• Tests and the trust-layer gate now verify fail-closed behavior before storage.

Provider payout architecture

• Added a provider payout ledger and edition-aware payout accounts: Stripe Connect Express for the U.S. edition, encrypted Canadian EFT for the Québec edition.
• Added /api/payouts/onboard to start U.S. Connect onboarding or store encrypted Canadian EFT details, with human approval before any disbursement.
• /api/health now exposes active payout-rail readiness; disbursement stays blocked unless PROVIDER_PAYOUTS_LIVE and edition-specific approval/configuration are present.

Verification requests in Command Center

• Command Center now surfaces pending professional verifications in the founder attention queue.
• A quick action links directly to the legal-professional review queue while keeping approval inside the human-in-the-loop admin flow.

API-verifiable authority bank

• Added the server route /api/legal/authorities/verify: it checks one citation or a text block, requires a session in production, and clearly separates “api-verified” results from public-source links.
• U.S. citations can now be verified against the CourtListener API when COURTLISTENER_API_TOKEN is configured; Canadian citations remain source-link-ready until an approved CanLII or official feed is connected.
• The Research tab can run citation-by-citation API checks, and /api/health now exposes authorityBankApi readiness.

Tomorrow vision moved to Today

• The homepage Today column now lists the copilot capabilities already shipped: litigation AI, evidence intelligence, automated chronology, procedure generation, hearing preparation and next-step recommendations.
• The forward-looking column is now “Next” and focuses on the deeper work still ahead: API-verified authority bank, filing integrations, advanced hearing simulation and settlement/enforcement intelligence.

Copilot trust layer and authority checks

• The copilot now treats matter summaries as untrusted context: suspicious instructions are neutralized, surfaced in the interface and kept out of the model instruction channel.
• AI answers return a citation report with CanLII, CourtListener or Cornell LII links based on recognized citation format, without pretending automatic judicial verification.
• Copilot runs are recorded in the matter audit log or a new ai_audit_events table for general questions, and procedure suggestions now show missing prerequisites plus the authority to verify.

Professional name in verification

• The professional verification form now asks for the professional's full name in addition to membership number, issuing authority and firm.
• The admin review queue shows the submitted name separately from the firm, backed by an idempotent Supabase migration.

Attorney-lane ethics guardrail

• The Pricing page now frames professional plans as practice SaaS subscriptions, with monetized attorney-client matching blocked until an ethics memo approves it.
• Added a machine-readable attorney marketplace policy that blocks per-lead, unapproved per-matter, success-fee and percentage-of-legal-fee models.
• The check:trust-gaps gate now fails if the old attorney lead marketplace or per-qualified-matter pricing language returns.

Marketplace trust-layer gates

• Added a check:trust-gaps gate that turns the business, ethics and trust/safety gaps into release-verifiable controls.
• /api/health now reports attorney monetization, provider payouts, upload scanning, CSAM safety, transactional communications, AI governance and rate-limiting readiness.
• Server-side evidence ingestion can reject binary files when upload scanning is required but not configured.
• Added reference docs for attorney marketplace ethics, Stripe Connect payouts, upload trust and safety, data lifecycle/DR, and AI governance.

Strict migration CI gate fix

• The strict migration CI gate no longer uses an invalid GitHub Actions expression on secrets; it decides in the shell whether to run migrations or skip them.

GA release gates and edition-aware legal framework

• Added a static release-blocker gate that verifies disabled US deadlines, authoritative Spanish, server-side attorney verification, telemetry and US legal pages.
• Added a verify:attorney harness proving professionals cannot self-verify and approval must pass through the admin review function.
• Cookies, transparency and data-rights pages are now US-edition specific when the US environment is active, with a dedicated /data-rights route.
• Added a release runbook covering CI gates, strict migrations, Vercel deploys from the repo root and production smoke tests.

Error telemetry deployment

• The migration runner now applies and verifies the telemetry_events table, so the error tracking added in 4.55.0 persists in production.

Release readiness: languages, compliance, CI and telemetry

• Spanish now ships as a release-authoritative locale with complete interface-key coverage, guarded by a static authoritative-locale check.
• The U.S. edition now renders U.S.-specific privacy and terms pages covering CCPA/CPRA notices, unauthorized-practice-of-law limits, controlled beta status and legal-review caveats.
• CI now gates dependency audit, authoritative-locale coverage and beta smoke harnesses; client-side error telemetry records incidents to a dedicated table when Supabase is configured.
• The Dependabot esbuild alert is resolved by moving the tsx/esbuild chain onto the patched esbuild release.

Deadline guardrail: U.S. edition

• The deadline calculator no longer emits automatic deadlines in the U.S. edition until CA/NY/NJ/CT/federal rules are sourced and verified; users are directed to manual entry instead.

Replayable commissioner migrations

• The commissioner portal migration now drops older write policies before recreating them, so deployment can replay 0017 and then apply the 0018 conduct controls.

Commissioner portal: identity, jurat and RON rules

• Added an appointment-authority registry and conservative RON gating so online mode is available only in enabled jurisdictions.
• The commissioner flow now runs identity → session → jurat, with completion blocked until the deponent's identity is verified.
• Sworn-document orders now record jurat data, identity status, certification references, timestamps and a reliable projection into the affidavit registry.

Commissioner portal: verification and sworn documents

• Added a complete commissioner portal: verification application, pending state, available-order board, claim flow and sworn-document certification.
• Added an RLS migration for commissioner profiles, sworn-order assignment, claim/certify functions and self-verification blocking.
• Added a dedicated admin page to approve/reject commissioners and offer sworn-document orders to verified commissioners.

Dynamic invitation and share links

• The /invite/[token] and /share/[token] pages now render dynamically so real invitation and targeted-share links do not fall through to a 404 page.

Professional portal migration deployment

• The deployment script now also applies the professional verification and targeted-share migrations, then verifies that the new RLS tables exist.

Professional portal: verification, targeted sharing and generation

• Attorney/notary verification is now server-authoritative with an RLS table, submission API, admin review queue and edition-aware authority registry for Quebec or U.S. builds.
• Clients can create targeted attorney shares with scope, expiry and review-or-collaboration permission; professionals get a dedicated inbox and can accept /share links.
• The Proceedings tab can generate a draft procedure and draft affidavit from organized facts, exhibits and witnesses, always marked as unfiled drafts.

Cloud recovery for local matters

• Importing a matter found only on the device now copies local evidence files into cloud storage before saving the matter.
• On load, the workspace also repairs cloud matters whose evidence files still existed only in IndexedDB on this device.
• The import button now shows a waiting state and clearly reports when any files remain local after a recovery attempt.

Workspace: numbered chronology, draft-judgment-first, motion package

• The chronology now numbers every fact (¶1, ¶2, …) so motions cite “Chronology, ¶143” rather than a page.
• New “Draft judgment” editor on the Judgment tab: write the order you're asking for first, with a one-page focus test that flags when it overflows.
• New read-only motion-package assembly view (the 8-part structure) that pulls together your facts, exhibits, authorities and draft judgment — no auto-generation.

Operational expert verification

• Added an expert review migration with an audit history for checks, notes, verification, publication, suspension and archival decisions.
• The admin panel can now record identity, professional order, insurance, sample report and conflict-protocol checks before publishing an expert.

Expert filter server-render fix

• Expert directory filters are now explicitly client-side to avoid importing client-module constants during server rendering.

Production expert directory fix

• Shared taxonomy helpers are now separated from the browser Supabase client so server-rendered `/experts` pages can render without error.

Idempotent migrations through expert marketplace

• Migrations 0009 and 0011 now recreate their RLS policies safely so Vercel deployments can replay the full chain through 0013.

Robust production env loading

• Activation scripts now load `.env.production.local` directly when the shell environment does not pass variables through to Node.

Expert marketplace Supabase activation

• The migration script now applies migrations 0008 through 0013 by default, including the expert marketplace.
• Added a `verify:experts` activation test to check expert tables, taxonomy, request creation and conflict logging with production Supabase variables.

Expert intake — server-side conflict screening

• Expert requests now go through an authenticated server route that creates the request, runs conflict screening, computes a qualification score and writes the audit log.
• The intake form blocks submission unless parties are identified, keeping conflict screening mandatory before expert review.

Expert marketplace — MVP foundation

• Added Supabase migration 0013: expert taxonomy, profiles, intake requests, conflict log, RLS policies, verified-field protection trigger, and admin RPCs.
• New /experts directory with search, filters, discipline pages, public profiles, verification badges, indicative fees, and a conversational intake button.
• Added the expert workspace, application flow, AI prompts for intake/qualification/conflicts, and the FR→EN profile translation route.

Copilot outage fixed + full diagnostics

• Root cause of “Copilot unavailable” found and fixed: the question-quota database function failed on every call (ambiguous column reference) — the AI was never reached. Corrective migration 0012.
• Every Copilot request now carries a request ID through the server logs and into any error message: “Copilot unavailable · Status · Provider: Anthropic · Request ID” — a user report is traceable to the exact log line.
• Server-side logging at each stage: request received, authenticated user, matter, Anthropic model used, and typed Anthropic error statuses (401 key, 403 permission, 404 model, 429 rate limit) with sanitized messages.

Homepage repositioning — early-access framing

• New hero: “Turn your legal problem into a structured case.” with the capability checklist (automatic chronology, document management, progress tracking, dispute resolution, procedure preparation), an early-users invitation and an honest 🚧 in-active-development badge.

Unified next-step engine — one answer to “what now?”

• Toward Juge 9.11 (“a litigation copilot that always knows your next step”): deadlines, hearing preparation, the resolution pathway, file-building gaps and the lifecycle journey are now fused into ONE ranked recommendation — instead of four tabs giving four different answers.
• “Your next step” leads the matter Overview: the single top recommendation with its urgency (deadline pressure dominates), why it matters, and a one-click jump to the right tab — plus the runner-up steps.
• Every matter card on the workspace home now shows its next step at a glance.
• Deterministic and explainable: each recommendation carries its source (deadline, resolution, hearing, file gap, journey) and a transparent priority — overdue deadlines first, then expired waiting periods, hearing prep, resolution steps, then file building.

Marketplace status integrated into the page header

• The build-status notice now sits directly under the Marketplace title: “build in progress — coming soon”, the network description, and a detailed note on what is still being integrated and tested (profiles, ratings, pricing, availability, ordering, payments, messaging, provider onboarding) — so visitors understand the state of the marketplace at first glance.

Marketplace construction notice

• The marketplace page now carries a permanent “coming soon — build in progress” notice making clear that, during development, profiles, pricing, reviews, ordering features and workflows shown there are illustrative and may not yet be operational.

Local matter recovery no longer re-flags imported matters

• “Import to cloud” (for matters created on this device before sync was enabled) now also updates the device copy. Previously, matters with legacy identifiers were re-detected as missing after every import, and each click created another cloud duplicate.

Reliability: local dates, stricter validation, sturdier forms

• Same-day deadlines are no longer flagged as overdue — deadline math now compares local midnights instead of mixing UTC and local time (case analysis and workspace suggestions).
• Generated documents are dated with your local date rather than UTC, removing the evening off-by-one.
• Document-service checkout: the jurisdiction field is validated server-side, fee overrides reject invalid values, and the payment form times out cleanly after 15 seconds instead of hanging.
• Matters created without a title get a bilingual default name, and corrupted locally saved team data can no longer break the firm portal.

Post-judgment lifecycle: remedies, assets, enforcement, recovery, archive

• Five new workspace tabs complete the litigation lifecycle after judgment: Remedies (appeals and recourses), Assets (recovery worthiness, debtor network, asset register and judgment-proofing detection), Enforcement (forced-execution readiness and seizure measures), Recovery (amounts recovered, distribution and satisfaction of the judgment debt) and Archive (file-closure checklist with retention guidance).
• Lifecycle steps 34 to 47 now open directly in their dedicated module instead of a neighbouring tab.
• Like the sibling engines, every check is deterministic and explains its reason, with citations where solidly established (Paulian action, arts. 1631–1636 C.C.Q.; demand to perform, art. 83 C.p.c.; prescription of a judgment debt, art. 2924 C.C.Q.). Legal information, not legal advice.

AI engine dependency upgraded

• Upgraded the AI SDK powering marketplace suggestions to version 6, resolving a published resource-consumption advisory (GHSA-866g-f22w-33x8). All known dependency vulnerabilities are now cleared.

Security dependency update

• Updated PostCSS to 8.5.15 across the entire build pipeline, addressing a published security advisory (GHSA-qx2v-qp2m-jg93) about unescaped CSS output.

Accessibility-support button now works as intended

• Support Centre: “Request adapted support” now opens the ticket form with the “Accessibility” type preselected, moves keyboard focus to the form (announced to screen readers), and reopens the form correctly after a previous submission.
• Direct links to the Support Centre (/support?type=…) now accept every ticket type, including accessibility.

More visible development banner

• The workspace's “active development” banner is now bright yellow and larger, so the invitation to report a problem can't be missed.

Corrected media kit and repository consolidation

• The Press Centre media kit now offers Juge.ca's official logo (dark background, and light background with tagline) instead of unadopted concepts.
• Consolidation: a single canonical tree for the platform — old parallel drafts are archived outside the repository; press documents and the reference judgment are grouped under docs/press.

Judgment analyzer, portfolio view, hardened Google Drive import

• New Judgment tab: analyze the rendered judgment — findings, costs, what was granted or denied — and choose the strategic path (accept, negotiate, or appeal), wired to lifecycle steps 31–33.
• Portfolio view (cross-matter risk analysis): on demand, detects risks that cross your matters — shared adverse parties or counsel, deadline collisions, the same forum, compounding workload. Read-only, never automatic, and your matters stay sealed from each other.
• Hardened Google Drive import: native Google files (Docs, Sheets, Slides) are converted on export (PDF/XLSX), errors are surfaced instead of failing silently, with “x / y” progress and a 100 MB size guard.
• System status: new “Google Drive import” check in Settings and /api/health.
• Press centre: media kit with downloadable official logos.

Privileged communications, evidence grid, founder dashboard

• New Communications tab: log every interaction — calls, branch visits, voicemails, complaints — before it becomes evidence. Client–attorney exchanges are protected by privilege: visible to you only, never shared, never sent to AI or exports. Pattern detection (repeated verbal-only communications, unanswered written requests, unkept commitments).
• Promotion to evidence only with a pertinence justification, recorded in the register; privilege-waiver warning before promoting a privileged exchange.
• Evidence register rebuilt as a professional grid: statistics, search, type filters, sorting, compact sticky-header table, bulk operations, per-row action menu and a side detail drawer.
• Control Center: “Founder Activity & Impact” section — active matters, litigation engine, attention queue, daily justice score, color-coded matter portfolio and lifetime statistics.
• Outcome tracking: closing a matter records how it ended (settled, favorable/unfavorable judgment, withdrawn…) — aggregated anonymously in platform metrics.
• The “Resolution” tab becomes the “Resolution Centre”.

Copilot chat window + matter reliability

• “Start Copilot” now opens a chat window: ask questions in sequence; answers keep the conversation context.
• A failed cloud save of a matter is now shown clearly with a Retry button — no more matters that look created and then vanish on reload.
• Local matter recovery: matters created on this device before sync was enabled are detected and importable to the cloud in one click.
• Control Center: count of cloud matters tied to your account and a matter-store read probe (detects missing migrations).

AI Copilot: 100 free questions, then 25¢ a question

• Access to justice first: every account gets 100 free AI Copilot questions.
• After that, pay as you use — 0.25 $ USD per question (4 questions = $1), billed monthly through Stripe. No bundles, no prepaid packs: you only pay for what you actually use.
• A question is never billed if the answer fails; the counter and subscription manage themselves.

Government recourse gateway + Copilot on Claude

• Recourse directory for 18 public bodies — RAMQ, SAQ, SAAQ, Revenu Québec, Hydro-Québec, CNESST, IVAC, CRA (federal tax), CERB/pandemic benefits, federal pensions (CPP/OAS), social assistance, Retraite Québec, student financial aid, municipalities, schools, police ethics, the health network and federal services. Each body loads its own resolution pathway: review, ombudsman, administrative tribunal, with orientation deadlines and jurisdiction traps (the SAQ and Hydro-Québec fall outside the Protecteur du citoyen; 15-day municipal notice; CERB is contested in Federal Court, not Tax Court). The authoritative deadline is always the one printed on the decision you received.
• Choosing “Government / administration” opens a searchable body picker; the generic ladder (review → Québec Ombudsman → TAQ) remains for any other ministry.
• The AI Copilot now runs directly on the Claude Developer Platform (Anthropic), with spending capped at the workspace level.
• Reliability: a failed matter-list load shows a warning with a Retry button instead of an empty workspace — your matters no longer visually disappear during a network failure.
• Development-phase banner in the workspace, deep-linking to the Support Center bug-report form (/support?type=bug).
• Control Center system map completed: Stripe webhooks, marketplace AI, HubSpot CRM, support GitHub mirroring, order notifications and the encryption key.

Support desk env compatibility

• The HubSpot private-app token is now read from HUBSPOT_TOKEN or HUBSPOT_ACCESS_TOKEN — either name activates live ticket mode.

Support Center → GitHub issue mirroring for bug reports

• Bug reports submitted through the Support Center are now mirrored as GitHub issues on the platform repository, titled [Bug] …, with labels created automatically (bug, user-feedback, support-ticket, language, priority).
• Privacy-aware diagnostics: when the repository is public, reporter details (email, account id, browser) are withheld from the issue and kept only in the support ticket; private repositories receive the full diagnostic block.
• Entirely best-effort: without a GITHUB_TOKEN (Issues read/write) the support flow works unchanged — the HubSpot ticket remains the source of truth.

Brand-entity SEO — Juge.ca is a platform, not a tribunal

• New homepage identity for search engines: “Juge.ca | La justice, clarifiée” with a description stating plainly that Juge.ca is an independent, private legal-navigation platform — neither a court nor a government service.
• schema.org structured data on every page: Organization (legal name 15149957 Canada Inc., disambiguating description “not a court, judge or government service”) + WebSite, so Google's knowledge systems stop resolving “judge911.com” to the Québec courts.
• New /mission page (what we are, resolution-first approach, French-first, accessibility) and an indexable launch press release: “Juge.ca lance une plateforme québécoise de navigation juridique assistée par l'IA”, with NewsArticle structured data.
• French URL aliases: /a-propos, /presse and /notre-mission permanently redirect to the right pages in every language.
• All new pages are in the per-language sitemaps, and the sitemap was resubmitted to Google Search Console.

Resolution — resolve first, escalate intelligently

• New first-class Resolution tab in every matter, before Proceedings: pick your dispute type (bank, housing, employment, consumer, insurance, government, professional discipline, construction, contract, family) and follow its tailored pathway — direct complaint, internal escalation, ombudsman, regulator — with per-step status, contacts, suggested waiting periods and linked evidence.
• Litigation Readiness Score (0–100) with a visible checklist: complaint sent, required steps concluded, waiting periods expired, evidence preserved, chronology built, settlement attempts logged.
• Smart Court Protection: the Proceedings tab stays locked until required resolution steps conclude — or you explicitly unlock it (“Have you attempted resolution?”), and the override is recorded in the file.
• Settlement & Negotiation Ledger: every offer, counter-offer, call, email, mediation and refusal is timestamped and preserved.
• One-click pathway documents built from the matter itself (parties, chronology, exhibits): complaint letter, follow-up, ombudsman submission, regulatory complaint, settlement proposal — and the “History of Resolution Attempts”, one of the most persuasive sections of a court file.
• Every resolution action is auto-logged to the chronology, so resolution activity becomes evidence if litigation happens.

Authentication flow fixes — session detection, magic links, rate limits

• The login page now detects an existing session on load and redirects you straight to your portal (client/professional/bailiff/commissioner; administrators → /admin) — an authenticated user never sees the login form again.
• Magic-link landings are fully processed: the access/refresh tokens that arrive in the URL are consumed, scrubbed from the address bar on every page, and a sign-in that completes after the page loads leaves the login screen immediately.
• Supabase email throttling now shows a clear message — “We've already sent several emails recently. Please wait a few minutes…” — instead of the raw “email rate limit exceeded”, on signup, magic links, confirmation resends and password resets alike.
• The navigation never mixes states: signed-in shows Home, Workspace, My account and Sign out; signed-out shows the public navigation with Sign in / Create account — and “Create account” now opens the signup form directly.

Support Center — a real helpdesk on /support

• /support is now a full Support Center: searchable knowledge base across 11 categories (getting started, account, workspace, document import, Copilot, marketplace, bailiff/commissioner services, privacy, billing, accessibility, technical), an FAQ, and quick actions — submit a ticket, report a bug, request a feature, accessibility support.
• Ticket submission is wired to HubSpot CRM: the contact is created or updated by email, the ticket lands in the pipeline (stage: New) associated with the contact, and you get a confirmation number on the spot.
• Tickets carry hidden diagnostics (signed-in user id with consent, page, browser, device, language, app version, timestamp) so support can help faster; required fields are validated server-side.
• A ticket-status section tracks your submissions from this device (New → In review → Waiting on user → Resolved → Closed), and a dedicated accessibility-support section prioritizes adapted-help requests.
• The legal-information disclaimer and the official-French notice stay visible on the page.

Founder Admin Access + admin audit logging

• Role-based access control formalized: user, attorney, partner, staff, admin, founder_admin — with founder_admin granted to the founder account in the database (migration 0008), never self-selectable.
• The /admin Control Center pages are now gated server-side: non-administrators are redirected to the workspace with an “Access denied” notice. Frontend hiding is cosmetic only.
• Admin audit log (who, what, when, which record): every Control Center page view and metrics read is recorded; elevated-role self-grants (staff/admin/founder_admin) are blocked at the database.
• Control Center metrics now include appointments booked and the most recent admin activity; the founder sees an “Open Control Center” card on the workspace home.

Multilingual SEO + official-language framework

• Per-language sitemaps (sitemap-fr.xml through sitemap-he.xml) for all 9 supported languages, each URL carrying hreflang alternates for every language — and sitemap.xml is now the index that references them all.
• hreflang + canonical now cover every public page in all 9 languages: HTTP Link headers are emitted per page, with x-default pointing to French (the official version).
• Official-language notice on every translated page (English included): “French is the official language of Juge.ca. In the event of any discrepancy, ambiguity, omission, or conflict of interpretation, the French version shall prevail.” — in the reader's language.
• Preferred language in your profile: pick any of the 9 languages in Settings; it is saved to your account, drives the locale cookie and switches the interface immediately.
• Right-to-left rendering (Arabic, Hebrew) and route-based localization (/fr … /he) were already in place and are unchanged.

Justice Command Center + upload-first document intake

• The workspace home is now a Justice Command Center: “What would you like to do today?” with action cards (Consult my matter, Litigation Copilot, Submit a procedure, Upload a court document), an Ask-a-Question AI front door, the legal marketplace (attorney, bailiff, commissioner, community legal resources) and your matters — the create-matter form is gone; matters are built from documents.
• Upload-first intake: drop a PDF, photo, DOCX, EML, MSG, TIFF — or a whole disclosure ZIP from a former lawyer — and Juge.ca reads it (OCR in French + English for scans and photos), then extracts court, district, file numbers, document title, filing date, parties, counsel, hearing dates, procedural stage and chronology events.
• Every extracted field carries a confidence score and stays editable; anything under 90% is flagged for review. Nothing is saved before you confirm.
• Smart matter detection: a detected court file number that matches an existing matter offers “Add to existing” or “Create new”; several numbers ask you to pick; none lets you enter one manually — and existing matter information is never overwritten (conflicts are reported).
• After confirmation the import creates parties (duplicates resolved), counsel, chronology events with source-page traceability, deadlines, hearings, exhibits, a proceeding, follow-up tasks and an import report — then opens the Litigation Copilot with a readiness score and next steps.
• Mobile gets Take photo / Upload document / Create matter manually as first-class actions.

Account-type signup + authentication feedback

• Signup now asks for your account type — Litigant/Client, Lawyer or legal professional, Bailiff, Commissioner for oaths — and routes you to the right portal (/app/client, /app/professional, /app/bailiff, /app/commissioner). Administrator access is granted in the database, never self-selected.
• All auth feedback renders in a big, unmissable alert above the first field (a single component for login and signup): “Invalid email or password.”, existing account, magic link sent, verification required, “Account created. Check your email…”.
• Live password validation under the field — 8 characters, uppercase, lowercase, number, special character — with per-rule pass/fail; “Create account” stays disabled until everything is valid.
• The signup screen says “Create your Juge.ca workspace — Select your profile to reach the right work portal.” Accounts without a type go through /onboarding/account-type.
• Security (schema 0007): the account type is stored server-side at signup via the trigger (never “admin”), and a trigger now blocks the self-service admin-role grant that was previously possible through the API.

Founder Command Center

• New internal /admin/dashboard (administrators only): executive view of every subsystem — users, lawyers, verified bailiffs, matters, documents, procedures, orders, marketplace mandates, leads — across Today / 7 days / 30 days / All-time windows.
• Growth (14-day signup chart), collected revenue (day/month/year/all-time and by service type), marketplace operations (status mix, average time to assignment and completion), support tickets, legal intelligence (procedure types, courts) and a system health map (Stripe, Supabase, storage, ingestion, AI).
• Founder alert centre: signup drops, open tickets, orders awaiting admin, new lawyers, bailiff applications, media inquiries, today's revenue.
• Aggregates go through a dedicated server route that verifies the session and the administrator role before any service-role query — RLS keeps protecting every table for everyone else.

Chat fallback email fixed

• The chat widget fallback now writes to contact@judge911.com (a real, verified Microsoft 365 mailbox) instead of hello@judge911.com, which did not exist. Every public address on the site (contact, support, press, investors, accessibility, partnerships, marketplace) is now live on a single mailbox.

Early-access page with lead capture

• New Early access page (/early-access) with the HubSpot waitlist form (portal 43986063, form waitlist-jugeca) and a no-JavaScript fallback — no lead is ever lost.
• The press release's “Sign up for early access” button now points to this page, in both French and English.

Partner and press forms, wired to the CRM

• New “Become a Partner” page (/partners): bailiffs, commissioners of oaths, attorneys, notaries and investigators apply with partner type, permit or professional-order number, territory served, languages and services — with explicit consent and verification before activation. The footer “Partnerships” link now points there.
• The Press Centre gains a media-request form: journalist identity, outlet, medium (print, web, TV, radio, podcast, agency), circulation or monthly audience, subject and deadline — so replies can be prioritized with full context.
• Every submission is persisted in Supabase (partner_applications and press_inquiries tables, RLS with no public policies — server-only writes) then forwarded to HubSpot as a qualified contact (lead status NEW, structured profile in the message property); when the contact already exists, the record is updated rather than dropped.
• Schema 0006 applies at deployment; forms are fully bilingual with accessible labels and success/error states matching site conventions.

Deadline computation engine (art. 83 CCP)

• New deadline calculator in the Deadlines tab: pick a rule (answer to the application — art. 145, case protocol — art. 149, setting down for trial — art. 173, notice of appeal — art. 360, revocation — art. 345–347, judicial review — art. 529, notification before presentation — art. 101) or a custom delay, enter the triggering date, and get the due date computed under article 83 CCP.
• Built-in Québec juridical calendar: the holidays of s. 61(23) of the Interpretation Act (Sundays, New Year's Day, Good Friday, Easter Monday, National Patriots' Day, June 24, July 1 — or July 2 when July 1 falls on a Sunday —, Labour Day, Thanksgiving, Christmas), Easter computus included; automatic extension to the first working day when the expiry falls on a Saturday or a holiday (art. 83 para. 3).
• Every result shows its legal authority, the pre-extension date, the step-by-step computation trail, “strict limit” and “case-law benchmark” badges, and adds to the matter's deadlines in one click. Statutory texts verified against LégisQuébec (2026-06-11).
• 31 unit tests covering computation (days, months by quantième, leap years), every holiday, extension chains (Easter weekend, New Year) and clear-day countdowns — npm test.

Litigation-records backend engines

• Every cloud save now feeds the backend's normalized registries (migration 0004): procedures, clerk filings, evidence, sworn documents (plus affidavits once sworn) and service of process — queryable mirrors of the matter, protected by RLS.
• New Litigation records page: six registries browsable at a glance across all your matters, including the audit log.
• The Stripe webhook now writes payments into the order registry (service_orders): the internal requestId travels through payment metadata and the normalized row flips to paid automatically, with an idempotent per-session fallback.

Bailiff marketplace + AI vision

• Order board: clients post enforcement orders (type, territory, fee, documents) and verified bailiffs claim them in one click — atomic claiming: exactly one winner even on simultaneous clicks. Admin direct assignment with accept/decline.
• Persistent bailiff workspace, tabbed (Offered, Active, Awaiting admin, Done). Fully electronic document rejection: a structured reason is required and a realtime ticket thread opens automatically with admins — no email, no phone.
• Four AI assistants (phase 1 of the /vision roadmap): document intake checks, bailiff matching, an admin copilot for tickets, and a listing optimizer. Invariant: AI suggests, humans confirm.
• Schema 0005 with RLS on every table, state transitions through SECURITY DEFINER functions, admin-only bailiff verification, ticket threads over Supabase Realtime.

“Justice, clarified” launch press release

• The Press Centre now publishes the June 10, 2026 launch press release on a dedicated bilingual page: the access-to-justice problem (Statistics Canada, 2021), the four steps (understand, navigate, organize, act), free orientation, the distinction from legal advice, and the media contact.

Brand-native hero + signup confirmation

• The hero visual is now a true product mockup built in Juge.ca's own design language (deep navy, glass, glow, coral): a "Workspace" window with live stat cards (127 exhibits, 41 events…), ✓ status pills, and per-folder intelligence (parties, evidence, timeline, exhibits, deadlines, risks, assets). No more white-background image.
• Account creation: after signing up, a "Check your email" screen confirms the link was sent to your address, with "Resend email", "I confirmed — continue", and "Change email". Loading states, clear errors (email already used, weak password, network), and duplicate-submit prevention.

Schema migration applied on deploy

• Supabase migrations now run during the production build (using Vercel's environment), applying the 0004 schema (procedures, affidavits, service_orders, bailiff_orders, document_sworn_orders, court_filings, evidence_items, audit_logs) with RLS — no secret handling involved.

Service-order persistence + audit log

• Each service ordered from a matter now writes a normalized row to service_orders (user, matter, status, price, payment status) and an audit_logs entry (created, paid) — alongside the existing in-matter tracking.
• Best-effort implementation: no-ops until migration 0004 is applied, then activates automatically with no code change.

Migration apply tool

• Added scripts/apply-migrations.mjs: applies Supabase migrations directly over the Postgres connection (URL read from the environment), to deploy the 0004 schema (procedures, affidavits, service_orders, etc.) without a management token.

Complete authenticated header

• Logged in, the header shows: Home · Workspace · Firm portal · Settings · My account · Sign out. Logged out: Home · Services · Pricing · Resources · Sign in · Create account.
• "Firm portal" and "Settings" open the matching panels in the workspace (via /app?view=firm|settings) — no dead-end links.

Litigation-OS schema + in-matter Services tab

• New schema (migration 0004): procedures, affidavits, service_orders, bailiff_orders, document_sworn_orders, court_filings, evidence_items, and audit_logs tables — each with user_id, matter_id, created_at, updated_at, and RLS (you only see your own records).
• The matter's "Operations" tab is now "Services": order a swearing, a bailiff, or another service directly from the matter.
• Reworked empty state: "Create your first matter to organize your evidence, procedures, deadlines, and judicial services."
• Truthful cloud indicator: "active" only after a successful database connectivity test; otherwise a reconnect warning.

Authenticated, persistent workspace

• /app now requires a Supabase session: signed-out visitors are redirected to /login?next=/app, with a "Verifying your session…" screen.
• Cloud sync only reads as "active" when a valid session exists; every matter is owned by the authenticated user (no anonymous or orphan matters).
• If the session expires: "Cloud sync unavailable — please sign in again." and matter creation is blocked.
• The workspace shows "Signed in as [email]" with a Sign out button; the header shows Sign in / Create account (logged out) or Workspace / Sign out (logged in).

Hero visual — 12-folder box

• Replaced the 6-folder render with the 12-folder litigation-operating-system box (Parties → Judgment enforcement), shown inside a "Workspace" window.

"Litigation operating system" hero + design system

• New hero: headline "The litigation operating system.", primary CTA "Create my case", and a "Services available today" strip under the buttons.
• The dossier-box image is framed as software (a "Workspace" window) and paired with the 12-folder Litigation-OS taxonomy.
• New design-system foundation: brand tokens (navy, coral, folder, warm), a folder-taxonomy registry, the scales emblem and wordmark, and a /design-system page documenting it all.

Hero visual — 3D dossier box

• Replaced the CSS dossier organizer with the official 3D render (file box with the scales-of-justice emblem).

Repositioning: litigation operating system

• New customer-focused headline: "Organize your case. Cut costs. Stay in control.", with a one-line explanation of what Juge.ca is (citizens, businesses, and legal professionals).
• New "Judicial services" strip under the hero: swearing, service by bailiff, legal consultation, case review, and asset search — each with an "Order a service" action.
• Litigation timeline expanded to 15 steps (added legal analysis, deadline management, asset search, recovery).
• Reworked header: explicit "Home", order Home · Services · Pricing · Resources · Community · Press, and clearly visible "Sign in" (outline) and "Create account" (solid) buttons.

Homepage redesign

• New two-column hero: "Our promise" and "A lawyer has an obligation of means." on the left, a dossier organizer (file box) on the right.
• The three commitments (billing, control, evolving platform) move directly under the hero; the "Your matter, A to Z" timeline puts its heading on the left and the "See every step" button top-right.

Litigation lifecycle, marketplace & service CTAs

• New "Lifecycle" tab in the workspace: the full litigation journey from identifying the problem to satisfying the judgment, with steps locked until they are reached and advancement fees to move the matter forward.
• New "Asset Intelligence" module (after judgment, before enforcement): investigation, identifying debtors and third parties, asset mapping, solvency analysis, and enforcement strategy.
• Plumitif (digital court registry) integration point: live tracking that will auto-advance steps and raise alerts inside the workspace.
• New professionals marketplace (lawyers, commissioners, bailiffs, medico-legal & CPA experts, asset investigators) and a workspace for bailiff firms and their staff.
• Homepage: each service now has its own button — "Order a swearing", "Order service of process", "Retain a bailiff" — instead of one shared generic button.
• Homepage: new "Your matter, A to Z" timeline with icons and a "See every step" button linking to the public lifecycle page.
• Advancement fees wired to secure Stripe payment (step unlocks on return from payment; preview-mode fallback when payments aren't configured).

Useful Links

• New "Useful Links" page: a directory of Québec and federal courts, the judicial council, the ministries of Justice, bar associations (including every sectional bar), the chambers of notaries and bailiffs, access-to-justice organizations, statutes, and case-law databases.
• Reachable from the footer's "Resources" group; every external organization is referenced for informational purposes only.

Automated contacts on import

• Imports now extract contact details (email + phone) and attach them to detected parties and witnesses, and capture email-signature senders as contacts.
• Existing parties and witnesses missing an email or phone are enriched from the imported text; witness contacts are shown (clickable) in the Witnesses tab.

Binder assembly & print guide

• New per-forum assembly guide (in Proceedings): before you print, it lists each exhibit's cote + description and tells you how many copies to print (court + parties + you), with step-by-step binder-assembly instructions. Downloadable as Markdown.

Smarter upload analysis

• On upload, documents are read and analyzed: parties are auto-detected, the court file number is detected and populated into the matter (or flagged if it conflicts), and the chronology is built automatically.
• When a folder is dropped, its name is checked for relevance to the matter and you're warned if it doesn't appear related.

Delete all matters (Danger zone)

• Settings now has a Danger zone to permanently delete and purge every matter and its evidence — local and cloud — behind a type-to-confirm (type DELETE / SUPPRIMER) safeguard.

Litigation Copilot tab — the 'Tomorrow' features, today

• New Copilot tab brings the six capabilities together: AI-powered copilot, evidence intelligence, automated chronology creation (one click builds the timeline from your evidence), procedure generation, hearing preparation, and next-step recommendations.

Reframed the future roadmap around outcomes

• The 'Tomorrow' vision now follows the litigation workflow and speaks to outcomes: AI-Powered Litigation Copilot, Evidence Intelligence, Automated Chronology Creation, Procedure Generation, Hearing Preparation, and Next-Step Recommendations.

Clickable studio partner links

• Footer studio partners (Rubicon Nexus, Rubicon Fusion, Impact Narrative Media) are now clickable links to their sites.

Attribution: access-to-justice initiative + studios

• Removed the dissolved entity (15149957 Canada Inc.) and set the company name to King Legend Inc. across the site and legal documents.
• Footer attribution now reads: an initiative of JusticeSansFrontieres.ca dedicated to access to justice, developed and operated by King Legend Inc., in collaboration with Rubicon Nexus, Rubicon Fusion, and Impact Narrative Media studios.

Home page cleanup

• Removed the abstract 3-step section now that the concrete litigation workflow graphic covers it.

Conversion-focused home page

• Outcome-first hero with action CTAs (Organize my case · Order a service) and a 'Make the future real today' line.
• Moved court services above the fold ('Need help moving your case forward?') and added a concrete litigation workflow graphic (Evidence → Hearing).
• Added audience value propositions (litigants vs attorneys), a Today-vs-Tomorrow future section, and a social-proof line (Built in Montréal, designed for Québec, expanding across Canada).

Court Services on the home page

• Added a third marketplace pillar — Court Services (swearing · service · enforcement) — alongside Find an Attorney and Organize Your Case, with an Order-a-service CTA.
• New home section and hero line surface the execute step: prepare, swear, serve, and organize in one workspace.

Persistent user profiles (cloud)

• In cloud mode your profile (name, role, contact info, plan) now loads from and saves to your Supabase account — persisting across devices and sessions instead of a per-device stub.
• New cloud users complete the profile gate once; Settings, plan upgrades, and attorney verification all write back to the profile.

Contributor guide (AGENTS.md)

• Added AGENTS.md documenting the canonical codebase, production branch, deploy procedure, and per-commit rules so parallel agents don't diverge the repo.

Closed payment loop + system status

• After Stripe checkout you now return to a confirmation: the request is marked paid and its first milestone completes (or your upgraded plan activates).
• New System status panel in Settings shows which production integrations are live (payments, ID verification, database/cloud sync, storage, ingestion, AI) via a /api/health check.

Out of beta — full production

• Juge.ca is now in full production. Removed beta/preview labels across the workspace, pricing, and FAQ.
• Status page: all systems marked Operational — litigation engine, operations marketplace, accounts & cloud sync, and the attorney portal.
• Live billing is active: plans and services are processed securely by Stripe.

Swearing video + ID, bailiff pre-auth, printing, upgrades

• Affidavit swearing now includes a secure on-platform video room with the commissioner, Stripe Identity verification (the commissioner never sees your personal information), and electronic signing — all tracked on the request.
• Bailiff service captures a pre-authorization hold on your card; the final amount is charged after service is performed.
• New professional printing & binding service for hearing binders and colour exhibits.
• Upgrade your workspace from the Operations tab — Self-Rep Unlimited ($375/mo) or a single matter ($149) via Stripe.

Operations checkout + booking

• Paid operations services now go through Stripe Checkout (not just bailiff): affidavit swearing and service of documents take payment securely.
• Affidavit swearing opens a booking step — choose the document (with a completeness check), pick a date/time, and online vs in-person — before paying.
• Updated the workspace messaging to reflect execution, not just preparation: prepare, swear, serve, and manage your case in one place.

Litigation Operations marketplace

• New Operations tab turns the workspace into an execution platform: commission affidavit swearing (Commissioner for Oaths), service of documents (bailiff), certified translation, expert reports, lawyer consultations, and court transcription — without leaving your case.
• Each commissioned service is tracked with a status pipeline and milestones (e.g. Draft created → Assigned → Attempt #1 → Served → Affidavit of service received).

Cloud sync toggle + litigation engine live

• Added a Cloud sync on/off switch in the workspace: turn it on (and sign in) to store matters and evidence in the database so your session persists across visits and devices; off keeps everything browser-local.
• The litigation engine (Organize Your Case) is now marked Operational on the status page.

Auto-exhibits, file viewer, parties & clerk filings

• Documents named like exhibits (P-1, Pièce P-23…) now populate the Exhibit list automatically on drop, keeping their numbers.
• A View button on each exhibit and evidence item opens the file in a pop-up viewer (images and PDFs inline).
• The analysis engine now detects role-labelled parties (demandeur/défendeur, plaintiff/defendant) and populates the Parties tab.
• New Clerk filings (Greffe) tab tracks deposits with internal sequential numbers (#1, #2, #3…), filed/outstanding status, filed date, and clerk reference.

Attorney onboarding & verification

• Professional accounts (lawyer/notary/paralegal/organization) now complete a verification step — bar/order number, issuing authority, firm — and accept a new Professional Services & Data Processing Agreement before guarded features unlock.
• Verification is human-in-the-loop: submitting never auto-grants access; status stays pending until a person approves. A self-represented escape hatch prevents lock-out.
• Added the Professional Services & Data Processing Agreement (attorney-client privilege, Canadian data residency, sub-processing, breach notice, return/deletion).

Folder import + auto-organize engine

• Drop a whole folder (with subfolders) onto Evidence — every file is ingested recursively, given a permanent Evidence ID, tagged and sourced from its subfolder, and byte-identical duplicates are skipped. An organization summary shows the result.
• The moment documents land, an analysis engine fans findings across the tabs: dates → Chronology and Deadlines, hearing dates → Hearing, affiants/signatories → Witnesses, key documents → Exhibits, protective steps → Tasks, and auto-generated Chronology and Exhibit-list drafts → Documents.

Password reset + suggested procedures

• Added a secure password-reset flow: 'Forgot password?' on sign-in sends a recovery email, and a dedicated reset page sets a new password.
• New Suggested Procedures panel in the Command Center detects sensitive material (financial, medical, private life) and recommends protective steps — above all a motion to seal / confidentiality order — with one-click add-as-task.

Multi-proceeding evidence propagation

• New Proceedings tab separates Evidence Identity (permanent E-0001) from Court Usage: the same evidence is referenced by many forums under their own exhibit numbers — never copied.
• Evidence × proceeding usage matrix (exhibit no · filed · served · introduced), a dissemination audit log, and Knowledge Assets that group evidence documenting the same event.
• Procedure-dependency graph: link the Evidence IDs each procedure relies on, and see which procedures are affected when a version is superseded.
• Export the usage matrix (CSV), propagation log (CSV), and the master Case Knowledge Index (Markdown).

War Room + Command Center

• New War Room is the matter homepage: commander dashboard, battlefield map (issues with strength + linked evidence/authorities/witnesses), timeline wall, procedure command center (draft/sworn/served/filed), evidence intelligence, contradictions board, judge board, decision log, missing-pieces board, and a 'What should I do next?' button.
• New Command Center: court-readiness score, action-required list, responsibility matrix (you/attorney/bailiff/clerk), per-procedure service rules (method, deadline, authority, reason), and litigation calendar export (ICS/CSV).
• Hearing binder generator produces Judge, Counsel, Witness, and Personal binders.

Litigation-grade evidence governance

• Every document now has a permanent Evidence ID (E-0001), version (V01…), and lifecycle status — with single-ACTIVE-version enforcement.
• Add a higher-quality copy as a new version that supersedes the old one (reason, date, and operator recorded); older versions are never deleted.
• SHA-256 integrity hashes, chain-of-custody logging, and source/acquisition metadata on every version.
• Export the master evidence registry (CSV/Excel + Markdown) and a migration report that flags duplicates, missing metadata, and supersession candidates.

Legal framework + accept-at-signup

• Added a comprehensive Terms of Service, an expanded Law 25 / PIPEDA Privacy Policy, and a new binding Confidentiality & Non-Disclosure Undertaking.
• Sign-up now requires accepting the Terms, Privacy Policy, and confidentiality undertaking — kept to a single frictionless checkbox with links.

Evidence ingestion API

• Added a secure ingestion endpoint so trusted automation can push documents straight into a matter's evidence — files land in secure storage and appear in the workspace.

Evidence-first onboarding + cloud import + 100 MB uploads

• New matters open directly on the Evidence tab so you can start adding documents immediately.
• Upload from your device or import directly from Google Drive (any file type), up to 100 MB per file.

Sign-in: confirm email → straight into your workspace

• Fixed account confirmation so that after you confirm your email you land directly in your workspace (already signed in) instead of on the home page.

Newsletter / waitlist — wired & polished

• Replaced the third-party embed with a clean native signup form that actually stores your email in our secure backend, with proper success and error states (bilingual).
• Signups also flow into our CRM as leads, so interactions are captured automatically.

UI polish sweep

• Workspace tabs are now a clean, horizontally-scrollable strip with a coral underline on the active tab — tidy even with many tabs and on mobile.
• Branded, centered sign-in and account screens; court-paper styling for generated documents (centered serif heading, page shadow).
• Subtle content transitions when switching tabs — automatically disabled when reduced-motion is on.

Dashboard polish

• A warmer empty state that guides you straight into a guided intake, and richer matter cards showing party/evidence/exhibit counts and the next upcoming deadline at a glance.

Client portal landing page

• New “For clients” page explaining the secure client workspace — upload evidence, review documents, track deadlines, and communicate — with how-it-works steps, a security note, and a sign-in call to action.

Live AI Copilot

• Added a live AI Copilot to the matter overview (via the Vercel AI Gateway) that reviews your matter and suggests concrete next steps and gaps, alongside the existing deterministic analysis. Clearly marked as litigation-organization assistance, not legal advice.

Evidence files in secure cloud storage

• When signed in, uploaded evidence is stored in private, encrypted Supabase Storage (Canadian region) with per-matter access control, instead of only your browser — so files sync across devices and to invited collaborators. Downloads use short-lived signed links; the export bundle pulls the real files.

Discrete language switcher + official-language notice

• Replaced the wide language row with a compact globe dropdown listing each language in its own native name.
• Your browser's language is detected automatically on first visit (e.g. an Arabic browser opens in Arabic).
• Clearly states that French is the official language of the site and prevails over any translation.

Multi-user verified end-to-end

• Verified the full lawyer↔client flow against the live database: sign-in accounts, cloud matter sync with row-level isolation, client invitations via shareable links, cross-user collaboration, and clients posting comments and uploading evidence.
• Hardened access rules: invitation acceptance runs through a secure function, and clients can comment/upload while editing stays restricted to the legal team.

Multi-user backend live — accounts, invitations, collaboration

• The secure backend is live: real sign-in accounts, cloud matter sync, client/staff invitations with accept links, and cross-user collaboration are now active end-to-end.

Secure backend activated

• Connected the Supabase backend (Canadian region) and applied the database schema with row-level security, enabling real accounts, cloud matter sync, client invitations and multi-user collaboration.

Multi-user backend wired (activates with Supabase)

• Wrote the full multi-user layer: cloud matter sync (matters stored in Postgres), client/staff invitations with shareable accept links, and matter-access sharing — all behind the secure-backend flag so the current browser-based app is unchanged.
• Lawyers can invite a client/colleague/expert to a matter from the Collaboration tab; invitees accept via a link and gain role-based access. Activates the moment the Supabase keys are set.

Emergency mode

• A dedicated Emergency view for matters that must move in hours, not days: it surfaces overdue and ≤72-hour deadlines and high-priority tasks across all matters, and routes you to the urgent templates (provisional injunction, safeguard order) and rush service of documents.

In-app notifications

• A notifications bell in the workspace surfaces what needs attention across all your matters — overdue and approaching deadlines, high-priority open tasks, recent comments, and evidence gaps — and jumps you straight to the relevant matter.

Document assembly workflows

• One-click document sets: generate a complete, coherent bundle from your matter — originating application (application + affidavit + exhibit list + notice of presentation), defence set, urgent/emergency set, service package, and a lawyer hand-off pack — all added to your saved drafts.

Multi-language expansion — 9 languages

• Added 7 informational languages — Spanish, Arabic, Mandarin, Punjabi, Portuguese, Italian and Hebrew — alongside authoritative French and English, with right-to-left support for Arabic and Hebrew.
• Each informational language translates the high-value interface and falls back to French for the rest, with a clear automated-translation notice; French and English remain authoritative and legal documents are generated in French/English.
• The architecture now supports adding any future language by dropping in a partial dictionary.

Litigation strategy & witness preparation

• The matter analysis now includes a litigation-strategy view: strengths, weaknesses, risks (missed/imminent deadlines, facts without supporting evidence), and prioritized next moves.
• Witness preparation: one-click suggested examination questions for each witness, generated from your chronology and the witness's notes — fully editable, and clearly not legal advice.

Accounts & sign-in (activates with the backend)

• Added secure sign-up / sign-in (email + password or magic link) and an auth callback, backed by Supabase Auth with MFA support.
• Feature-flagged: the login screen shows an “accounts coming” notice until the backend keys are set, then real cloud accounts activate — no disruption to the current browser-based workspace.

Secure backend foundation (Supabase)

• Added the multi-user backend foundation: Supabase Postgres schema with row-level security on every table, isolating matters per user and sharing them only through explicit access grants — the server enforcement of the role/permission model.
• Database, auth, and storage clients wired to activate automatically once the (Canadian-region) Supabase project keys are set; until then the app keeps running client-side.
• Setup guide published (docs/BACKEND.md). Next: sign-up/login, client invitations, real collaboration, billing, and secure evidence storage.

Greffe numérique gatekeeper

• Each generated document now shows a filing verdict: whether it can be transmitted electronically to the greffe numérique, must be presented urgently to the court, is filed with a tribunal, or is not a court filing at all — so nothing is sent to the wrong channel by mistake.
• Flags when a proceeding, even if e-filed, still requires service on the opposing party.

Document-service marketplace (Phase A) — pay to serve documents

• New “Service of documents” flow: request service by a bailiff (Québec), process server (other provinces), notary, or internationally, with standard / rush / emergency urgency.
• Secure Stripe Checkout (cards) with transparent, below-market pricing; orders captured for drop-ship fulfilment to a provider.
• Contextual “get these served” link from the Bailiff Instructions and Electronic Notification templates.
• Live payments activate once the Stripe account is reactivated; the flow runs in test mode until then.

Emergency, disclosure, e-notification & bailiff templates

• Emergency procedures: provisional injunction (art. 510 C.p.c.) and safeguard order (art. 49 C.p.c.) templates for matters that must move in hours, not days.
• Request for disclosure of information/documents and an electronic-notification request (to obtain an email address and avoid bailiff fees where service can be done by technological means).
• Instructions to the Bailiff packet generator — preparing the documents and service instructions ahead of the upcoming bailiff / process-server marketplace.

New pricing model + Case Brief for your lawyer

• Pricing rebuilt around how litigation actually works: Case Builder ($350) and Litigation Pro ($750) are now ONE-TIME, per-matter fees that cover a matter to completion — even if it takes years — plus a new $375/month Self-Rep Unlimited plan for ongoing or multiple matters, pausable during quiet periods.
• Positioned clearly as a litigation copilot with a human in the loop: the AI assists, you stay in control.
• New “Case Brief for your lawyer” document: a one-click, organized summary of your matter (parties, theory, chronology, exhibits, evidence, deadlines, your questions) so your attorney sees the full picture instantly — and spends less billable time getting up to speed.

“Our promise” on the home page + privacy-friendly analytics

• New “Our promise” section on the home page: a better-organized file costs less, fewer billing surprises with market-based cost estimates, you stay in control, and an evolving platform — with clear estimate/not-legal-advice framing.
• Added cookie-less Vercel Analytics and Speed Insights to start measuring the conversion funnel and page performance (activated from the Vercel dashboard).

Québec & Canadian law resources + roadmap update

• Added a Québec & Canadian law section to Legal Resources (CanLII, LégisQuébec, Justice Laws, Supreme Court of Canada, Court of Appeal of Québec) and surfaced JusticeSansFrontières.ca as an access-to-justice initiative.
• Added the same official databases to the in-app Research tab.
• Roadmap updated: secure cloud backend + analytics/funnel in the attorney beta, and Google Drive import (Dropbox/OneDrive to follow) at general availability.

Read-aloud accessibility + chat assistant

• Read-aloud: a browser-native text-to-speech control in the accessibility widget reads the page aloud in French or English — no account or setup.
• New “Chat with us” assistant on every page: a bilingual FAQ helper with an email fallback and the required not-legal-advice notice. Built to plug into live AI and a WhatsApp hand-off once the secure backend is enabled.

Plan & usage, per-matter export, security plan

• Plan & usage panel in settings: choose your plan (Free preview, Case Builder, Litigation Pro, Professional), see matters used against your allowance, and jump to pricing. Preview only — no payment is processed.
• Per-matter JSON export for clean handoff to a colleague or client (re-importable from the dashboard).
• Published a security & Canadian data-residency plan (docs/SECURITY.md) covering auth/MFA, encryption, role-based access, audit logging, backups and Law 25 / PIPEDA alignment.

Collaboration — comments + activity log

• New Collaboration tab on every matter: post comments for your team and review a chronological activity log derived from real events (matter created, evidence uploaded, drafts saved, comments posted).
• Comments and the audit trail will sync across users once the secure backend is enabled.

Lawyer / Firm portal — portfolio, status reporting & team

• New Firm portal: practice-wide portfolio summary (matter count, deadlines in the next 30 days, average readiness) and a sortable matter status report across all your files.
• Team management with a real roles & permissions model — lawyer, paralegal, assistant, client, expert and consultant — each showing exactly what it can do.
• Live multi-user sign-in, client invitations and billing remain gated on the secure backend, which is not yet enabled.

Legal Research engine + guided Legal Intake

• New Research tab: automatic Canadian legal-citation extraction from your case theory, evidence and drafts (neutral citations, reporters, and statute/Charter references), each with a one-click CanLII search, plus curated links to CanLII, LégisQuébec, Justice Laws and SOQUIJ. No account required.
• Guided Legal Intake: a step-by-step interview (legal issue, jurisdiction, parties, key dates, objectives, urgency) that automatically creates a structured matter — including an urgent task flag when warranted.

Document Automation 2.0 + Advanced analysis

• Document Automation 2.0: five new court-ready templates — Defence, Amended Application, Application for Judicial Review, Notice of Appeal, and a Tribunal Application Form — bringing the generator to twelve bilingual document types.
• Advanced analysis (no external model required): contradiction review (e.g. multiple events on the same date, dates not corroborated by evidence), missing-evidence detection, procedural recommendations, timeline-gap detection and draft-improvement checks — all clearly marked as not legal advice.

Hearing preparation + Court Presentation Mode

• New Hearing tab: examination outlines (direct and cross), argument preparation, a hearing checklist with standard items, and live courtroom notes.
• Court Presentation Mode: a full-screen presenter for the hearing with large exhibit display (including image preview), a clean timeline view, and instant search across exhibits, facts, evidence and drafts.

Functional Litigation OS — full end-to-end MVP

• Account profile gate that personalizes your file and auto-fills generated documents.
• Evidence module: upload PDF, DOCX, images and text files with in-browser text extraction, tagging, one-click exhibit creation, and automatic date detection into the timeline.
• Exhibits now support the P / D / R series with automatic per-series numbering, reordering, and a generated exhibit index.
• Document generator expanded to seven court-ready templates — affidavit, notice of presentation, originating application/motion, formal demand, email notification slip, chronology and exhibit list — all auto-filled and editable.
• One-click litigation package export to PDF, DOCX, and a ZIP bundle that includes your uploaded evidence files.
• New Tasks tab, editable chronology with evidence linking, richer party contact details, and matter status / file number / district.
• Fully bilingual (FR/EN) across every new module.

Document generator — formal demand (mise en demeure)

• Added a Documents tab that drafts a formal demand letter (mise en demeure) pre-filled from your matter — recipient, sender, subject, demand, and a configurable compliance period.
• Live letter preview with one-click print / save-to-PDF, clearly marked as a self-help template.

Litigation Copilot next steps + data export

• Added the Litigation Copilot to each matter's overview: prioritized “next best steps” and evidence-gap analysis, including approaching-deadline alerts.
• Added export and import of your matters as a JSON file for backup and transfer.

Working platform + commercial launch

• Launched the working Workspace: create matters and manage parties, chronology, auto-numbered exhibits, witnesses, and deadlines — saved in your browser.
• Added the live Justice Score™ that scores case readiness across every dimension.
• Added Courtroom Mode: a print-ready hearing package (case theory, parties, chronology, exhibits, witnesses, deadlines).
• Published commercial plans and pricing for the public and for attorneys, with value-based positioning.
• Added Workspace and Pricing to the navigation, footer, and homepage calls to action.

Repositioned as a Litigation Operating System

• Rewrote the homepage hero to lead with the outcome: a bilingual, accessibility-first Canadian Litigation Operating System.
• Expanded the About page with the full positioning for the public and for legal professionals.
• Strengthened the SEO/social description across the platform.

Attorney value proposition + Litigation Copilot vision

• Added an attorney value-proposition section: Juge.ca as the engine of a practice — less time chasing clients and on admin, more time advocating in the courtroom.
• Published the “Litigation Copilot” product vision on the roadmap: legal strategy engine, evidence-gap analysis, risk dashboard, settlement intelligence, witness center, hearing simulator, war room, AI file review, and Justice Score™.
• Hardened the waitlist fallback form against XSS (DOM API instead of innerHTML).

Added a “How it works” three-step section

• Added a homepage section presenting Juge.ca in three steps: organize your evidence, understand the procedures, present your arguments.

Updated mission statement

• Refined the homepage mission to emphasize efficiency for citizens and automation for legal professionals.

Bolder, centered design across the platform

• Restyled the whole site with a centered, dramatic, glassmorphism aesthetic inspired by the original landing page.
• Centered page heroes with bigger gradient headlines and a coral accent bar.
• Added a subtle coral background glow for depth and wrapped page content in glass panels.
• Updated the homepage mission statement.

Refined homepage copy for legal professionals

• Clarified the homepage message: legal professionals put their expertise to work to better serve their clients' interests.

Brand logo, “Coming soon” mention, security update

• Added the Juge.ca logo to the header and homepage hero.
• Kept a “Coming soon” mention on the homepage as a live badge.
• Updated Next.js to a patched, secure release.

Live version-control in the footer

• Added a live build/version-control panel to the footer: version, git commit hash, branch, and build time — so every deploy is visible on the site.
• Added the same build details to the Platform Status page.

Institutional platform launch

• Launched the bilingual (French-first / English) institutional platform.
• Added the full trust & compliance suite: About, Contact, Support, Press, Investors, Legal Community, Attorneys, Legal Resources, Privacy, Terms, Cookies, Legal, Transparency, and Accessibility.
• Introduced semantic versioning with version and last-updated information in the footer.
• Published the public Roadmap, Changelog, and Platform Status pages.
• Implemented accessibility features targeting WCAG 2.2 AA: keyboard navigation, skip link, ARIA labels, adjustable text size, and reduced-motion support.
• Built a complete footer architecture with corporate attribution to King Legend Inc.

Coming-soon landing page

• Published the initial coming-soon landing page with email waitlist capture.
• Established Vercel hosting and continuous deployment.