Roadmap

Please note: These updates might rollout in phases. i.e. v0.1.7a, v0.1.7, etc. ## 0.1.7 - LLI Track & Supervision Enforcement

Objective: make Rule 9/LLI the starting experience; all high-impact actions require supervisor approval/presence until promotion.

• Systems

• Supervision slice: approvals (request -> pending -> granted/denied/expired), supervisor availability calendar, daily capacity, compliance risk flags.

• Supervisor eligibility: enforce QSL requirements (3+ active years, discipline lookbacks), max 1 LLI per QSL except clinic override, dual-supervisor declarations, and same-office co-counsel presence rules.

• Calendar co-scheduling: hearings marked `requiresSupervisor` block unless supervisor slot is reserved; update `CalendarJugglingService` and practice calendar UI.

• First appearance/arraignment pipeline: auto-schedule within 48 hours when in custody; require probable-cause check, rights advisement, counsel appointment, and default-not-guilty plea unless explicitly overridden; LLI presence/approval required for plea entry or waiver of rights.

• Action gating: GameFlowManager phases (plea, filings, hearings, negotiation) check approvals and first-appearance completion; block/queue with UX prompts; save/load includes supervision state.

• Economy: LLI stipend replaces current pay; toggle to attorney salary on promotion; stress/reputation deltas for unauthorized acts.

• Progression: track supervised hours/competencies (align to `Path to Criminal Law Attorney.txt` skills); unlock bar exam event; promotion flips `isLLI=false` and removes gates.

• Mentorship/advice: add consult touchpoints with supervising partner/firm boss or public defender director for guidance, approvals, and morale; advice outcomes influence reputation/stress and unlock tactics.

• UX

• Case detail: supervisor chip, approval badge, “request approval” CTA; countdowns for due/expiring tickets.

• First-appearance banner for in-custody clients with 24/48-hour clock and advisement checklist; bail/conditions summary at arraignment.

• Tutorial beats from `LLI_FAQ.md` and `RULE9_LLI_TRACK_DESIGN.md`; toasts for granted/denied/expired approvals and unauthorized attempts.

• Acceptance

• In-custody cases generate a first-appearance task; missing the 48-hour window surfaces dismissal/release risk and ethics hits.

• Cannot accept plea/file/appear (flagged events) without active approval and supervisor availability.

• Promotion path works in new and existing saves; saves preserve approval tickets and availability.

• Tests: slice reducers, middleware gating, unauthorized-action penalties.

## 0.1.8 - Court Staff & Calendar Logistics

Objective: ship the clerk/JA layer with tasks, rapport, and favors influencing scheduling, notices, and continuances.

• Systems

• Staff slice: profiles, relationship scores, favor tokens, workloads, task queue (`confirm_hearing`, `serve_notice`, `request_interpreter`, `swap_slot`) with SLAs and outcomes.

• Hook staff into calendar/hearings: fields `staffConfirmed`, `staffTaskId`, `noticeServed`, `allowRemote`, `benchWarrantRisk`.

• Middleware/timers: process staff tasks, apply consequences (missed notices + warrant risk; expired confirmations + resets/bench warnings).

• Favor economy: spend tokens to swap slots/allow remote/late filing acceptance; overuse drains rapport and triggers cooldown.

• AddedEvent hooksstaff errors (lost filing, wrong courtroom) weighted by rapport; mitigation tasks available.

• Arraignment logistics: ensure notices/interpreters are requested, bench-warrant risk toggles when first appearance/arraignment notices are missed, and staff confirmations cover video vs in-person appearances.

• Continuance “good cause” rules: firm trial dates by default; continuance requests need reasons, timing, and affidavits; vacation-only requests low success unless pre-noticed unavailability blocks; integrate notice-of-unavailability/vacation weeks to avoid conflicts.

• Interpreter access: interpreter scheduling requests/shortages affect hearing readiness; missed interpreter triggers resets or sanctions risk.

• Expert/interpreter funding: motion-for-funds flow with budget caps; approvals gate expert retention and interpreter upgrades.

• UX

• Calendar dashboard badges for confirmed/unconfirmed; “request confirmation/escalate” buttons.

• Case detail staff card with rapport meter, favors left today, pending tasks with due times.

• Toasts for staff actions (courtesy reminders, lost filings, favor granted/denied).

• Acceptance

• Hearings cannot proceed without confirmation when required; notice failures raise risk flags.

• Continuance success rates vary with clerk rapport (per `COURT_STAFF_INTEGRATION.md`).

• Tests: task timer logic; favor spend; rapport deltas; serialization of staff state.

## 0.1.9 - Caseload Pressure, Pleas, and Detention Reality

Objective: align day flow and outcomes with overload math and plea-driven resolution rates.

• Systems

• Shared time budget: replace duplicate clocks with a single daily minutes pool; `GameFlowManager` pulls from practice/planner hours and writes back dayNumber/currentDateISO.

• Docket pressure model: minutes-per-client bands, hallway consult share, overload ratio feeding stress/energy and plea gravity (from `casebalance.md`).

• Detention/bail pressure: custody status and bail outcomes accelerate plea likelihood, trigger speedy-trial urgency, and alter deadlines.

• Procedural timelines: enforce speedy-trial clock, bail review windows, plea offer expirations, discovery/motion deadlines; missed first-appearance/arraignment triggers bench-warrant risk or release.

• Arraignment mechanics: plea entry defaults to not-guilty; plea at arraignment fast-paths to sentencing with waiver warnings; schedule discovery and motions automatically after arraignment.

• Discovery and evidence handling: chain-of-custody risk, suppression checks, and deadlines aligned to local rules (e.g., Spokane evidence rules); detective/witness scheduling impacts discovery completeness.

• Witness interviews/depositions: schedule/cost interviews, record statements, and log impeachment material; deposition transcripts gated by time/budget; missed prep increases trial risk.

• Conditions of release: pretrial services check-ins, no-contact orders, and electronic monitoring compliance; violations trigger custody changes and plea pressure.

• Jurisdiction profiles: toggleable local rule sets (e.g., Spokane criminal process/evidence) affecting timelines, admissibility, and scheduling strictness.

• Collateral consequences: immigration/employment/housing/licensing impacts shown in plea/trial outcomes, affecting client goals and reputation stakes.

• Evidence volume realism: digital/video discovery requires time budget to review; failure to review raises ethics/ineffective-assistance risk flags.

• Client communication/consent: advisement and consent checkpoints for pleas and waivers; poor communication increases complaint risk and stress/reputation penalties.

• Comms surface: in-game cell phone/email for client and attorney communication (approvals, updates, emergencies); online news feed/events that can alter evidence, jury pools, and court availability (closures/weather/high-profile incidents).

• Jail logistics: in-custody client meetings consume travel/security time; limited phone/visitation windows affect prep; missed visits raise stress/complaint risk.

• E-filing/eservice friction: filing cutoffs, outages, and queue delays can blow deadlines unless escalated; backup filing options with cost/risk.

• Public records requests: FOIA/public-records tasks with long lead times; returns can unlock mitigation or impeachment but consume budget/time.

• Prosecutor discretion simulation: charging/bail offers reflect leverage and evidence strength; trial penalty and offer adjustments respond to motions and discovery suppressions.

• Plea flow: auto-plea triggers require overload + custody signals; plea resolutions dominate (95-98%) with tuned probabilities and visible context.

• Continuance triage: integrate `ContinuanceManagementService` with calendar; auto-select continuances when over capacity; reprimand risk; stress/reputation hits.

• Random events -> deterministic hooks: replace ad-hoc random rolls with state-based events (detention deadlines, missed notice, staff mishaps).

• Evidence-based workload caps: apply RAND/ABA time-per-case standards (e.g., 13.8h misdemeanors, 35h low felonies, 99-286h high felonies) to capacity; intake/gating, burnout, and ethics risk tied to exceeding caps vs legacy NAC numbers.

• UX

• Performance/pressure overlay showing minutes-per-client, overload ratio, custody mix, plea gravity slider.

• Planner suggestions aligned to pressure (e.g., “prioritize in-custody clients”, “file speedy-trial motion”).

• Acceptance

• Single source of truth for day/time across GameFlowManager, gameSlice, practice slices.

• Plea distribution matches research bands under overload/detention scenarios.

• Tests: overload math, plea probability caps, time-budget sync, continuance auto-selection.

## 0.2.0 - Trial/Narrative Polish & Launch Hardening

Objective: finish courtroom/narrative consequences, stability, and compliance.

• Systems

• Courtroom depth: judge/prosecutor personality effects on objections, patience, and rulings; formal trial flow (voir dire -> openings -> prosecution case -> defense case -> instructions -> verdict -> sentencing) with timing/energy costs; verdict consequences propagate to relationships, ethics, and staff/supervisor reactions.

• Evidence-in-court realism: apply local evidence rules (foundations, objections, chain of custody) and detective/expert witness reliability; sanctions for late disclosures or bad-faith motions (tie to `Attorney Disbarment and Sanctions_.txt`).

• Witness handling: detective credibility scores, expert witness budgets, impeachment/cross options, and use of prior statements/depositions; scheduling conflicts for key witnesses affect continuance success and trial outcomes; missed deposition deadlines trigger sanctions risk.

• Jury and sentencing realism: voir dire bias detection and strike limits; sentencing guidelines/mitigation (PSI, character letters) influencing outcomes and collateral consequences.

• Pretrial publicity: news events shift juror bias, venue risk, and continuance likelihood; option to seek change of venue or sequestration with costs/risks.

• Save/telemetry: save GameFlow session state; capture metrics on approvals, staff tasks, pleas vs trials, reprimands; crash recovery paths.

• Performance: trim bundle load, timer efficiency, and memory for long sessions; seedable randomness for repro.

• AddedComplianceenforce `GAME_NAME_POLICY.md`; audit branding; finalize localization hooks for new UI strings.

• UX

• Narrative consequences dashboard post-verdict; career summary cards for launch.

• Onboarding polish for the realistic loop (planner + calendar + approvals + staff + hearing).

• Acceptance

• End-to-end playthrough from LLI start to full attorney with no dead ends; saves reload cleanly.

• Regression suite covers approvals, staff tasks, plea flow, and calendar conflicts.

• Launch checklist: QA signoff, crash/ANR budget, performance targets, storefront assets with canonical title.