CABINET (LITIGATION) FUNCTION RULEBOOK

Legal Sandbox Georgia LLC

Document Type: Function Rulebook (Binding) Version: 1.0 Effective Date: 13 May 2026 Document Language: English (Georgian version prevails in case of conflict) Status: Binding contract, incorporated by reference into all applicable Role Terms and Conditions

PREAMBLE

This Cabinet (Litigation) Function Rulebook ("Rulebook") establishes the rules governing Litigation Cases, ongoing legal engagements, and case management on the legal.ge platform operated by Legal Sandbox Georgia LLC, Registration Number 405713768 (the "Platform").

The Cabinet is the Platform's case management module. It supports the lifecycle of ongoing legal engagements that extend beyond a single Consultation, including litigation, transactional matters, advisory engagements, and other long-form professional services.

This Rulebook is a binding part of the Terms and Conditions of every role permitted to create, participate in, or interact with Litigation Cases. By creating a Case, accepting a Collaborator invitation, participating as a Client, or otherwise interacting with the Cabinet, You agree to be bound by this Rulebook.

This Rulebook governs case lifecycle, multi-Specialist team mechanics, document and credential management, financial tracking, withdrawal of representation, and case file delivery. It does NOT govern:

Inquiry submission, Quote, or initial Consultation mechanics (governed by Inquiries Rulebook);
Subscription tier definitions and Active Cases per Month limits (governed by Subscriptions Rulebook);
Calendar publication and book-from-calendar consultations (governed by Calendar Rulebook);
Reviews of Specialists' Case work (governed by Reviews Rulebook);
Video consultation session mechanics (governed by Video Rulebook);
Specialist's professional ethical obligations under the Georgian Bar Association — these obligations are separate and binding on the Specialist independently of this Rulebook.

In the event of any conflict between this Rulebook and another Function Rulebook, conflict resolution is governed by Article 25.

ARTICLE 1: PURPOSE AND SCOPE

1.1 Purpose

1.1.1 This Rulebook provides a single authoritative source of truth governing the Cabinet (Litigation Case) function on the Platform.

1.1.2 This Rulebook serves to:

(a) Define the Litigation Case lifecycle and states;

(b) Establish how Cases are created (Inquiry-derived or independently);

(d) Define attorney-client privilege protection within the Cabinet;

(e) Govern the Case Document management system with custom visibility levels;

(f) Govern Case Credentials (sensitive third-party access credentials);

(g) Govern Specialist Notes with per-note privacy controls;

(h) Govern Custom Pages, Hearings, Deadlines, Activity Log, and other Case detail tabs;

(i) Define the Cabinet financial model (off-Platform default + 7% Platform-handled commission);

(j) Govern Specialist withdrawal of representation and Client termination of engagement;

(k) Govern Case file delivery to Client at engagement end;

(l) Define audit trail requirements and Platform access controls;

(m) Coordinate with the Inquiries Rulebook (Inquiry-to-Cabinet handoff per Inquiries §11.6), Subscriptions Rulebook (tier features), and other Function Rulebooks.

1.2 Scope

1.2.1 This Rulebook applies to:

(a) All Litigation Cases on the Platform, regardless of how created;

(b) All Specialists who create, lead, or collaborate on Cases;

(d) All Case-related data including documents, credentials, notes, custom pages, hearings, deadlines, financials, and activity logs;

(e) Cabinet-specific notifications and audit trails.

1.2.2 This Rulebook does NOT govern:

(a) Inquiry intake, Quote, payment, or initial Consultation Capture — governed by Inquiries Rulebook (with §11.6 governing the Inquiry-to-Cabinet handoff);

(b) Subscription tiers, Active Cases per Month limits, billing of subscription fees — governed by Subscriptions Rulebook;

(d) Reviews of Specialists — governed by Reviews Rulebook;

(e) Video session mechanics for Cabinet meetings — governed by Video Rulebook;

(f) Specialist's underlying professional and ethical obligations to the Client under the Georgian Bar Association rules and applicable law — these are separate from this Rulebook and independently binding on the Specialist;

(g) Off-Platform fee arrangements between Specialist and Client — Platform does not arbitrate retainer terms, billing rates, or engagement letter content;

(h) Specialist's professional ethical compliance with Bar rules including conflicts of interest, competence, and fiduciary duties — these are Specialist obligations independent of Platform rules.

1.3 Roles Affected

1.3.1 This Rulebook directly affects the following roles:

Role	Capability
Solo Specialist	Creates and manages Cases (subject to subscription); serves as Lead or Collaborator
Company Specialist	Creates and manages Cases (subject to Affiliated Company tier); serves as Lead or Collaborator
Company	Maintains Cabinet-level visibility for Affiliated Specialists' Cases
User (Client)	Participates in Cases as Client; uploads documents; exchanges Cabinet chat
Trainer	Not affected (Trainings are not Cases)
Author	Not affected
Trainee	Not affected
Moderator	Limited access to Cases only on dispute opening, governed by Article 24
Organisation	Not affected; Affiliated Members create Cases in their individual Specialist capacity

ARTICLE 2: DEFINITIONS

2.1 Capitalized terms used but not defined in this Rulebook have the meanings given in the applicable Role Terms and Conditions or other Function Rulebook where context makes clear.

2.2 For purposes of this Rulebook:

"Cabinet" means the Platform's Litigation Case management module, comprising the systems, interfaces, and data stores that support Cases.

"Cabinet Chat" means the Platform's secure messaging interface within a Case, governed by Article 12.

"Case" or "Litigation Case" means a record in the Platform's litigation_cases data store, representing an ongoing legal engagement between a Specialist (or Specialist team) and one or more Clients, governed by this Rulebook.

"Case Credentials" means third-party access credentials (e.g., court portal logins, opposing counsel platform access) stored in the Platform's case_credentials data store, governed by Article 11.

"Case File Delivery" means the package of Case-related materials delivered to the Client at engagement end, governed by Article 19.

"Case Participant" means any Specialist (Lead or Collaborator) or Client formally associated with a Case.

"Collaborator" means a Specialist (other than Lead) participating in a Multi-Specialist Case, governed by Article 6.

"Custom Page" means a Specialist-created HTML page within a Case for strategy notes, exhibits indexes, witness lists, or other free-form content, governed by Article 14.

"Engagement" means the professional relationship between a Specialist and Client formalized through a Case, including its formation, performance, and termination.

"Engagement Letter" means the written agreement between Specialist and Client governing the substantive terms of the engagement (scope, fees, retainer, etc.), separate from this Rulebook. Engagement Letters are between the Specialist and Client; the Platform does not arbitrate their terms.

"Inquiries Rulebook" means the Inquiries & Messaging Function Rulebook v1.2 or successor.

"Lead Specialist" or "Lead" means the Specialist designated as the lead on a Case, with elevated privileges per Article 6.

"Lifecycle State" means the system-managed Case state: Draft, Active, Paused, Closed, Archived, or Deleted, governed by Article 4.

"Originating Specialist" means the Specialist who created the Case (whether by Inquiry conversion or independent creation).

"Platform-Handled Payment" means a Case-related payment processed through the Platform (subject to 7% commission), as distinct from off-Platform payment, governed by Article 16.

"Privileged Content" means all Cabinet content presumed to be subject to attorney-client privilege per Article 5.

"Procedural Stage" means a Specialist-managed informational field describing the procedural posture of a Case (e.g., "Pleadings", "Discovery", "Trial", "Appeal"), distinct from Lifecycle State.

"Specialist Notes" means notes recorded by a Specialist in the Platform's case_specialist_notes data store, governed by Article 13.

"Subscriptions Rulebook" means the Subscriptions & Billing Function Rulebook v1.3 or successor.

"Withdrawal" means the Specialist's termination of the engagement on the Specialist side, governed by Article 17.

ARTICLE 3: CASE CREATION

3.1 Two Creation Paths

3.1.1 A Case may be created through one of two paths:

(a) Inquiry Conversion:

(i) Following completion of an Inquiry-derived Consultation per Inquiries Rulebook §11.5;

(ii) The Specialist proposes conversion per Inquiries Rulebook §11.6;

(iii) The Client provides fresh consent (separate engagement letter) per Inquiries Rulebook §11.6.2(c);

(iv) The original Consultation fee remains separate from any Case retainer per Inquiries Rulebook §11.6.2(d);

(v) The Originating Specialist becomes the Lead Specialist on the Case.

(b) Independent Creation:

(i) A Verified Solo Specialist or Company Specialist may create a Case independently of any Platform-mediated Inquiry;

(ii) Suitable for off-Platform engagements: walk-in Clients, referrals, pre-existing Clients, Clients introduced through Specialist's own networks;

(iii) The Specialist creating the Case becomes the Lead Specialist;

(iv) The Client's relationship is governed by the engagement letter executed between Specialist and Client outside the Platform.

3.2 Eligibility to Create a Case

3.2.1 A Specialist may create a Case only if:

(a) Specialist is Verified per Subscriptions Rulebook §3.2.1;

(b) Specialist is in role SOLO_SPECIALIST, SPECIALIST (Company Specialist), or has equivalent authority;

(c) Specialist has not exceeded the Active Cases per Month quota for their subscription tier per Subscriptions Rulebook §5.1.1 (Solo: Freemium 0 / Pro 5 / Expert 30) or §6.1.1 (Company: Basic 0 / Established 30 / Enterprise 96);

(d) Specialist's subscription is in good standing (not Past Due / Suspended).

3.2.2 Where the Specialist's tier does not permit Case creation (e.g., Freemium Solo, Basic Company), Case creation is blocked at the API layer.

3.2.3 Where the Specialist's quota is exhausted, additional Case creation is blocked until either:

(a) Existing Active Cases are closed or archived to free quota; OR

(b) The Specialist upgrades to a higher tier.

3.3 Required Case Fields at Creation

3.3.1 The following fields must be provided at Case creation:

(a) Case Name (custom_name) — Specialist-defined display name;

(b) Case Type — categorical descriptor (e.g., "Civil", "Criminal", "Administrative", "Commercial", "Family");

(c) Court Instance — applicable court or tribunal where relevant (e.g., "Tbilisi City Court", "Court of Appeals", "N/A — Out-of-Court");

(d) Specialist Role (user_role) — the role the Specialist plays in the matter (e.g., "Plaintiff Counsel", "Defendant Counsel", "Advisor");

(e) Procedural Stage (current_stage) — Specialist's initial assessment of the procedural posture (e.g., "Pre-filing", "Pleadings", "Discovery").

3.3.2 Optional fields at creation:

(a) Public number (court docket reference);

(b) Brief case description;

3.4 Originating Specialist Becomes Lead

3.4.1 Upon successful Case creation, the Originating Specialist is automatically assigned as the Lead Specialist for that Case.

3.4.2 The Lead role may subsequently be transferred per Article 6.5.

3.5 Inquiry-Conversion Specifics

3.5.1 Where the Case is created via Inquiry Conversion per §3.1.1(a):

(a) The originating Inquiry record is linked to the Case via the Original Inquiry tab per Article 14.13;

(b) Documents from the Inquiry phase are preserved per Inquiries Rulebook §16.2 and may be referenced in the Case;

3.6 Independent Creation Specifics

3.6.1 Where the Case is created independently per §3.1.1(b):

(a) No originating Inquiry is linked;

(b) The Specialist is responsible for ensuring the engagement is properly documented (engagement letter, conflict checks per Article 21, privilege establishment) outside the Platform;

3.7 Conflict of Interest Check at Creation

3.7.1 Conflict of interest checking before Case creation is Specialist-self-managed:

(a) The Platform does NOT perform automated conflict checks;

(b) The Specialist bears sole professional responsibility for verifying that no conflict of interest exists per their Bar rules and ethical obligations;

ARTICLE 4: LIFECYCLE STATES

4.1 Lifecycle State Definitions

4.1.1 Each Case is in one of six Lifecycle States, system-managed by the Platform:

State	Description	Visible to Client?	Specialist Edit Access?
Draft	Case created but not yet active; preparation phase	❌ Not visible to Client	✅ Full edit
Active	Engagement is live; Case is being actively worked	✅ Visible	✅ Full edit
Paused	Engagement temporarily suspended (e.g., awaiting decision, Client unavailability)	✅ Visible	✅ Full edit
Closed	Engagement formally concluded; Case file ready for delivery	✅ Visible (read-only)	⚠️ Limited edit (closure-related actions only)
Archived	Case retained for record-keeping; no active work	✅ Visible (read-only)	❌ Read-only
Deleted	Case removed; data retained per retention policy until deletion completes	❌ Not visible	❌ No access

4.2 Lifecycle State Transitions

4.2.1 Permitted transitions:

Draft → Active (Specialist activates Case)
Draft → Deleted (Specialist deletes draft)
Active → Paused (Specialist or Client requests pause)
Active → Closed (Specialist closes Case after completion)
Paused → Active (resumes work)
Paused → Closed (closes from pause)
Closed → Archived (Specialist archives after wind-down)
Closed → Active (re-opens within reasonable period if engagement resumes)
Archived → Deleted (Specialist deletes after retention period)
Deleted → none (terminal)

4.2.2 Each transition is recorded in the Activity Log per Article 15 with timestamp, actor, and reason where provided.

4.3 Procedural Stage (Specialist-Managed)

4.3.1 Independent of the Lifecycle State, each Case has a Procedural Stage field (current_stage) describing the procedural posture of the matter.

4.3.2 Procedural Stage is Specialist-managed informational only:

(a) Specialist sets and updates as the matter progresses;

(b) Platform does not enforce or validate Procedural Stage values;

(c) Procedural Stage is informational and does not affect Lifecycle State transitions, Platform features, or Client access.

4.3.3 Suggested values include but are not limited to: Pre-filing, Pleadings, Discovery, Pre-trial, Trial, Appeal, Post-Judgment, Settlement Negotiations, Closed.

4.3.4 Specialists may use custom values consistent with their practice area.

4.4 Closure of a Case

4.4.1 A Specialist may close a Case (Active → Closed or Paused → Closed) at any time when:

(a) Engagement has reached a natural conclusion;

(b) Client has terminated engagement per Article 18;

(d) Other circumstances making closure appropriate.

4.4.2 Closure triggers:

(a) Case file delivery preparation per Article 19;

(b) Activity Log entry indicating closure;

(d) Outstanding items (deadlines, hearings) flagged for review;

(e) Case data preserved per Article 20.

4.5 Archival

4.5.1 A Specialist may archive a Closed Case after appropriate wind-down period.

4.5.2 Archived Cases:

(a) Are read-only;

(b) Remain in the Specialist's Cabinet list (filterable);

(d) May be unarchived back to Closed if access is needed.

4.6 Deletion

4.6.1 A Specialist may delete an Archived Case only after expiration of any applicable retention period under law, this Rulebook, or Specialist's professional rules.

4.6.2 Deletion is permanent — data is queued for removal from active storage per Privacy Policy (some metadata retention may continue for legal/audit purposes).

4.6.3 A Case in Active or Paused state cannot be deleted; it must first be Closed or Archived.

ARTICLE 5: ATTORNEY-CLIENT PRIVILEGE AND CONFIDENTIALITY

5.1 Privilege Default

5.1.1 All content within a Case is treated as Privileged Content by default.

5.1.2 Privileged Content includes but is not limited to:

(a) Cabinet Chat messages;

(b) Specialist Notes;

(d) Custom Pages;

(e) Case Credentials;

(f) Hearings, Deadlines, and Activity Log entries to the extent they reveal substantive work product;

(g) Financial entries, invoices, and engagement-letter related data;

(h) Any other Case-related data not expressly excluded.

5.1.3 Privilege presumption applies regardless of whether content is explicitly marked privileged.

5.2 Platform Access to Privileged Content

5.2.1 The Platform commits to NOT access Privileged Content except on the following specific grounds:

(a) Legal compulsion — court order, regulatory directive, or other legally binding requirement;

(b) Specialist's explicit request for technical support that requires content access;

(c) Investigation of suspected serious misuse — fraud, illegal activity, security incident — subject to Article 5.5 audit logging.

5.2.2 The Platform's access to Privileged Content is NOT permitted for:

(a) Routine support tickets (unless Specialist explicitly grants access);

(b) Product development, training data, or analytics (anonymised aggregate data may be derived but not from raw Privileged Content);

(d) Any purpose inconsistent with this Rulebook or the Privacy Policy.

5.3 Encryption

5.3.1 Privileged Content is stored with standard encryption-at-rest as the Platform's default protective measure.

5.3.2 Where applicable Georgian or other law specifically requires end-to-end encryption for legal practice content, the Platform commits to upgrading to end-to-end encryption for affected Cases.

5.3.3 The Platform's standard encryption protects against external attackers; the Platform retains the technical capability to decrypt Privileged Content for legitimate operational purposes (per §5.2) but contractually commits not to do so absent the §5.2 grounds.

5.4 Privilege Survives Termination

5.4.1 Privilege protections under this Article continue indefinitely after:

(a) Specialist account termination;

(b) Client account termination;

(d) Platform-side termination of service.

5.4.2 Privilege protections lapse only upon:

(a) Lawful waiver by the privilege holder (typically the Client);

(b) Court order specifically requiring disclosure;

5.5 Audit Trail of Platform Access

5.5.1 Every instance of Platform access to Privileged Content is recorded in an immutable audit trail:

(a) Timestamp;

(b) Identity of accessing party (Platform staff member, system process);

(d) Scope of access (which Case, which content);

(e) Court order or regulatory directive reference where applicable.

5.5.2 The audit trail is viewable by the Lead Specialist of the affected Case through the Platform interface or upon request.

5.5.3 The audit trail is preserved for the Case retention period plus an additional five (5) years.

5.6 Specialist's Independent Privilege Obligations

5.6.1 The Specialist's professional obligations to maintain attorney-client privilege under the Georgian Bar Association rules and applicable law are independent of and additional to the Platform's protections.

5.6.2 The Specialist is solely responsible for:

(a) Establishing privilege under Bar rules (e.g., proper engagement formation);

(b) Avoiding inadvertent waiver (e.g., disclosure to third parties);

(d) Compliance with secrecy obligations specific to their licensure.

5.6.3 The Platform's privilege-protective measures are technical and operational; they do not constitute legal advice on privilege and do not substitute for the Specialist's professional judgment.

5.7 Court-Compelled Disclosure

5.7.1 Where the Platform receives a court order or other legally binding directive compelling disclosure of Privileged Content:

(a) The Platform shall notify the Specialist of the demand before disclosure where legally permissible (i.e., where no gag order or similar restriction applies);

(b) The Platform shall give the Specialist a reasonable opportunity to assert privilege through their own counsel;

(d) Where notification is prohibited, the Platform shall notify the Specialist as soon as the prohibition expires.

5.7.2 Notwithstanding Platform's notification, the Specialist remains primarily responsible for asserting privilege; the Platform's role is procedural.

ARTICLE 6: MULTI-SPECIALIST CASE STRUCTURE

6.1 Lead and Collaborator Roles

6.1.1 Each Case has exactly one (1) Lead Specialist and may have zero or more Collaborators.

6.1.2 Differentiated privileges:

Privilege	Lead	Collaborator
Edit Case content (documents, notes, custom pages, etc.)	✅	✅
Upload documents	✅	✅
Add hearings, deadlines	✅	✅
Add financial entries	✅	✅
Invite additional Collaborators	✅	❌
Remove Collaborators	✅	❌
Transfer Lead role	✅	❌
Close, Archive, or Delete Case	✅	❌
View Activity Log (default)	✅	⚠️ Lead-granted only
Access Case Credentials	✅	✅
Initiate Withdrawal	✅	✅ (own withdrawal only)

6.1.3 Collaborators have full case-work access (edit Case content, upload documents, etc.) but cannot manage Case team membership or lifecycle state.

6.2 Inviting Collaborators

6.2.1 The Lead Specialist may invite additional Specialists as Collaborators by:

(a) Selecting a Verified Solo or Company Specialist on the Platform;

(b) Optionally specifying a role description (e.g., "Co-Counsel", "Senior Associate");

6.2.2 The invited Specialist receives a notification per Article 22 and may:

(a) Accept — becomes Collaborator with privileges per §6.1.2;

(b) Decline — invitation is dismissed; no further action;

6.2.3 Invited Specialists in pending status have no access to Case content until acceptance.

6.3 Collaborator Acceptance Requirements

6.3.1 A Specialist may accept a Collaborator invitation only if:

(a) Specialist is Verified;

(b) Specialist is in good standing on subscription;

(d) No conflict of interest as determined by the accepting Specialist's own assessment.

6.4 Removing Collaborators

6.4.1 The Lead Specialist may remove a Collaborator at any time.

6.4.2 Removal:

(a) Revokes the removed Specialist's access to Case content;

(b) Records an Activity Log entry;

(d) Does not affect content the removed Specialist has previously contributed (uploaded documents, notes, etc.) — these remain in the Case.

6.4.3 A Collaborator may also voluntarily leave a Case at any time, with notification to the Lead.

6.5 Lead Role Transfer

6.5.1 The Lead Specialist may transfer the Lead role to another Collaborator with that Collaborator's consent.

6.5.2 Transfer process:

(a) Lead initiates transfer to a designated Collaborator;

(b) The designated Collaborator receives a notification and must accept;

(d) The previous Lead becomes a Collaborator (or may simultaneously withdraw per Article 17);

(e) Activity Log records the transfer.

6.5.3 Transfer cannot occur to an unverified Specialist or one outside the Case Collaborator team.

6.6 Lead Departure Without Designated Successor

6.6.1 Where the Lead Specialist initiates Withdrawal per Article 17 without designating a successor:

(a) If Collaborators exist on the Case, the system prompts the Lead to designate a successor before Withdrawal completes;

(b) If no Collaborators exist, the Case enters Paused state and the Client is notified that representation has terminated;

(c) The Specialist's Bar-rule obligations regarding continuity of representation are independent of Platform mechanics; the Specialist bears responsibility for proper Client transition.

6.7 Off-Platform Team Coordination

6.7.1 Specialist team coordination (work allocation, internal billing, communication outside Cabinet) occurs off-Platform.

6.7.2 The Platform does not arbitrate internal team disputes about work distribution or compensation.

6.7.3 Multi-Specialist video sessions for Case meetings are governed by Video Rulebook §12.

6.8 Pending vs. Accepted Assignment Status

6.8.1 The Platform's case_specialist_assignments data store records both pending invitations and accepted assignments.

6.8.2 Cases with pending invitations to a Specialist do NOT appear in that Specialist's Case list until acceptance, preserving the privilege/confidentiality boundary.

ARTICLE 7: CABINET ACCESS AND SUBSCRIPTION GATING

7.1 Tier-Based Cabinet Access

7.1.1 Cabinet access tracks the Subscriptions Rulebook tier matrix:

Tier	Cabinet Access	Active Cases Quota
Solo Freemium	❌ Cannot create Cases	0
Solo Pro	✅ Full Cabinet access	5
Solo Expert	✅ Full Cabinet access	30
Company Basic	❌ Cannot create Cases	0
Company Established	✅ Full Cabinet access	30
Company Enterprise	✅ Full Cabinet access	96

7.1.2 Quotas are canonical in the Subscriptions Rulebook (§5.1.1, §6.1.1); this Rulebook references but does not modify them.

7.2 Read-Only Fallback

7.2.1 Where a Specialist's subscription status results in loss of write access to one or more Cases (e.g., quota exceeded after downgrade, subscription Past Due):

(a) The affected Cases remain visible in the Specialist's Cabinet;

(b) The Cases render in read-only mode — UI hides edit/delete actions and sensitive tabs;

(c) The Specialist may re-acquire write access by upgrading subscription, archiving other Cases to free quota, or restoring subscription status;

(d) Read-only mode preserves all Privileged Content protections per Article 5.

7.3 Read-Only Tab Restrictions

7.3.1 When a Case is in read-only mode for a Specialist, sensitive tabs are hidden from that Specialist:

(a) Specialist Notes — hidden (preserves privacy of new entries);

(b) Case Credentials — hidden (prevents sensitive credential view in degraded state);

7.4 Quota Exhaustion Behavior

7.4.1 Where a Specialist attempts to create a Case but quota is exhausted:

(a) Creation is blocked at the API layer;

(b) The Specialist is notified with explanation and options (close existing Cases, upgrade subscription);

7.5 Subscription Downgrade Effects

7.5.1 When a Specialist's subscription downgrades to a tier with lower quota:

(a) Existing Active Cases that exceed the new quota become read-only per §7.2;

(b) The Specialist is notified per Subscriptions Rulebook §9 (subscription change handling);

(d) Cabinet data is preserved through downgrade per Subscriptions Rulebook §8.4.1(f).

7.6 Company Specialist Departure

7.6.1 Where a Company Specialist departs an Affiliated Company (per Subscriptions Rulebook §10):

(a) Cases associated with that Specialist remain in the Cabinet;

(b) During the 15-day grace period, the departing Specialist retains access;

(c) After grace period, access depends on Specialist's post-departure subscription status (Solo activation or No Subscription).

ARTICLE 8: CASE LIST AND BROWSING

8.1 Cabinet Tab — Solo Specialist

8.1.1 Solo Specialists access their Cabinet through the Platform interface (typically the solo specialist dashboard).

8.1.2 The Cabinet displays the Specialist's Cases with:

(a) Active filter — currently active Cases;

(b) Archived filter — archived Cases;

(d) Filters — case type, court instance, procedural stage, outcome, archive status;

(e) Sort — by updated_at (default), creation date, or case name.

8.2 Cabinet Tab — Company

8.2.1 Company users (with COMPANY role authority) access a company-level Cabinet view.

8.2.2 The Company Cabinet displays:

(a) All Cases of Affiliated Specialists;

(b) Filter by individual Specialist;

8.2.3 Company users do NOT create Cases via the Company Cabinet interface; Case creation is a Specialist-side action per Article 3.

8.3 Pending Assignment Visibility

8.3.1 A Specialist's Cabinet list excludes Cases where the Specialist has only a pending (unaccepted) Collaborator invitation.

8.3.2 Cases appear in the Specialist's list upon acceptance of the invitation per §6.2.2.

8.4 Pagination and Limits

8.4.1 The Cabinet list supports pagination for performance.

8.4.2 The Platform may impose reasonable per-page limits in operational policy.

ARTICLE 9: CASE DETAIL TABS

9.1 Standard Tabs

9.1.1 Each Case detail interface presents the following tabs:

#	Tab	Article Reference
1	Overview	§9.2
2	Parties	Article 10
3	Documents	Article 10 (continued)
4	Hearings	Article 10 (continued)
5	Deadlines	Article 10 (continued)
6	Financials	Article 16
7	Delivery	Article 19 (re Case file delivery)
8	Activity Log	Article 15
9	Notes	Article 13
10	Collaborators	Article 6
11	Chat	Article 12
12	Custom Pages	Article 14
13	Original Inquiry	§3.5

9.2 Overview Tab

9.2.1 The Overview tab displays summary information including:

(a) Case Name, public number, type, court instance;

(b) Specialist Role, Procedural Stage, Lifecycle State;

(d) Client identification;

(e) Recent activity summary;

(f) Outstanding deadlines and upcoming hearings;

(g) Financial summary.

ARTICLE 10: PARTIES, DOCUMENTS, HEARINGS, DEADLINES

10.1 Parties Tab

10.1.1 The Parties tab records:

(a) Client(s) participating in the Case;

(b) Opposing parties (where applicable);

(d) Other relevant parties (witnesses, third parties).

10.1.2 Specialist team adds and edits Parties information.

10.1.3 Client visibility into Parties tab is per Specialist's discretion (default: visible).

10.2 Documents Tab

10.2.1 Document storage is provided through the case_documents data store.

10.2.2 Upload eligibility:

(a) Lead Specialist;

(b) Collaborators;

(d) Any Case Participant with active access.

10.2.3 Per-document visibility levels — set by uploader at upload time:

(a) Specialist-private — only the uploading Specialist sees;

(b) Specialist-team — Lead and Collaborators see; Client cannot;

(d) Client-shared — Client can additionally download/access.

10.2.4 Version history: every upload creates a new version; previous versions remain accessible to authorized parties; version history is immutable (cannot be altered or deleted).

10.2.5 Document deletion: permitted by uploading Specialist or Lead; deletion is logged but the previous version history remains for retention purposes.

10.2.6 Document retention: same retention as the Case per Article 20.

10.3 Hearings Tab

10.3.1 Hearings management is Specialist-managed:

(a) Specialist (Lead or Collaborator) creates, edits, and cancels Hearing entries;

(b) Client views Hearings in read-only mode where Hearings tab is shared;

10.3.2 Reminders: the Platform sends Hearing reminders to all Case Specialists 24 hours prior to each scheduled hearing per Article 22.

10.3.3 Where a Hearing is cancelled or rescheduled, the Specialist updates the entry; reminders are auto-adjusted.

10.4 Deadlines Tab

10.4.1 Deadlines are recorded in case_deadlines:

(a) Specialist-set deadline date and time;

(b) Description of deadline;

(d) Reminder configuration (24 hours prior by default per §22, or Specialist-customized per §22.X).

10.4.2 Missed deadline handling:

(a) Notification is sent to Specialist;

(b) Deadline is flagged in Activity Log;

10.4.3 Specialists are solely responsible for deadline compliance; the Platform's reminder is an aid, not a substitute for Specialist diligence.

ARTICLE 11: CASE CREDENTIALS

11.1 Purpose

11.1.1 Case Credentials store sensitive third-party access credentials used by Specialists in the course of Case work, such as:

(a) Court portal logins;

(b) Government registry access;

(d) Third-party service access provided by the Client.

11.2 Storage

11.2.1 Case Credentials are stored in case_credentials with Platform-managed encryption-at-rest.

11.2.2 Encryption keys are managed by the Platform consistent with industry standards.

11.2.3 The Platform retains technical capability to decrypt Case Credentials for legitimate operational purposes per Article 5.2; access is contractually restricted.

11.3 Visibility and Access

11.3.1 Case Credentials are visible to all Case Specialists (Lead + Collaborators) — both can use them in the course of Case work.

11.3.2 Case Credentials are NOT visible to the Client by default.

11.3.3 Where the Client provided the credentials to the Specialist (e.g., Client's own court portal login), the Client may request return of those credentials per §11.7.

11.4 Audit Logging on Credential Access

11.4.1 Credential access is logged on retrieval or copy operations, not on view alone:

(a) When a Specialist copies the credential to clipboard or otherwise extracts it from the Platform — logged;

(b) When a Specialist views the credential in the UI — not separately logged (treated as routine);

11.4.2 Access logs are reviewable by Lead Specialist and preserved per Article 5.5.

11.5 Credential Lifecycle

11.5.1 Credentials are retained for the Case retention period (typically 5 years post-Closure per Article 20).

11.5.2 Credentials may be deleted earlier by:

(a) Lead Specialist (e.g., at Case closure when access no longer needed);

(b) Originating uploader (the Specialist who entered the credential);

11.6 No Credential Use Beyond Case Scope

11.6.1 Specialists shall use Case Credentials only for purposes consistent with the Case engagement.

11.6.2 Use of credentials outside the Case scope (e.g., personal access, non-Case Client matters) is prohibited and may constitute breach of this Rulebook and applicable law.

11.7 Credential Return to Client

11.7.1 Upon Client request, the Specialist shall return any credentials the Client originally provided.

11.7.2 The Specialist shall:

(a) Confirm the credential was originally Client-provided;

(b) Return through secure means (e.g., the Platform interface);

(d) Continue to use the credential only with Client's continued authorization.

11.8 Credentials Are Not Privilege Waivers

11.8.1 The Platform's storage of Case Credentials does not waive any applicable privilege; the credentials are tools for Case work, not substantive content of the Engagement.

ARTICLE 12: CABINET CHAT

12.1 Cabinet Chat Defined

12.1.1 Cabinet Chat is the Platform's secure messaging interface within a Case, used for ongoing communication among Case Participants (Specialists and Client).

12.2 Distinction from Inquiry Messaging

12.2.1 Cabinet Chat is separate from Inquiry messaging governed by Inquiries Rulebook §6 (which covers pre-engagement communications).

12.2.2 Where an Inquiry converts to a Case per §3.1.1(a), Cabinet Chat begins fresh; Inquiry messaging history is preserved in the Original Inquiry tab but does not migrate into Cabinet Chat.

12.3 Privilege

12.3.1 Cabinet Chat is Privileged Content per Article 5.

12.3.2 Privilege survives termination per §5.4.

12.4 Participants

12.4.1 Cabinet Chat participants:

(a) Lead Specialist;

(b) Collaborators;

(d) (No external participants.)

12.4.2 Each participant sees the full Cabinet Chat history from the time of their addition forward; pre-addition history is not exposed.

12.5 Messages and Attachments

12.5.1 Messages support text content.

12.5.2 File attachments are uploaded via the Documents tab per §10.2 and may be referenced in Chat by link; in-Chat direct file upload is not supported in v1.0 (consistent with Video Rulebook approach).

12.6 Activity Log Treatment

12.6.1 Cabinet Chat events (messages sent, edited, deleted) are logged in the Activity Log per Article 15.

12.6.2 Activity Log records metadata only (sender, timestamp, message reference) — chat content remains in the Chat tab and is not duplicated into the Activity Log.

12.7 Moderation

12.7.1 Cabinet Chat is privileged and not subject to routine Platform moderation.

12.7.2 The Platform may access Chat content only on Article 5.2 grounds (court order, suspected serious misuse, etc.).

ARTICLE 13: SPECIALIST NOTES

13.1 Purpose

13.1.1 Specialist Notes are private working notes, candid analysis, strategy, and other Specialist-generated content stored in the case_specialist_notes data store.

13.2 Per-Note Visibility

13.2.1 Each note has a visibility flag set at creation:

(a) Specialist-private — only the noting Specialist sees;

(b) Team-shared — Lead and Collaborators see; Client does not;

13.2.2 Visibility may be changed by the noting Specialist or Lead.

13.3 Privilege

13.3.1 All Notes are Privileged Content per Article 5.

13.3.2 Privilege treatment applies regardless of visibility level — Specialist-private notes are equally privileged as team-shared or Client-shared notes.

13.4 Notes in Case File Delivery

13.4.1 Only Notes marked "Client-shared" are included in the Case File Delivery to Client per Article 19.

13.4.2 Specialist-private and Team-shared Notes are excluded from Case File Delivery — they are work product retained by the Specialist.

13.4.3 This treatment ensures the per-note visibility flag is meaningful: a Specialist's strategic thinking and candid analysis remain protected from Client view both during and after engagement, unless the Specialist affirmatively shares specific notes.

13.5 Edit and Delete

13.5.1 Notes may be edited or deleted by:

(a) The noting Specialist;

(b) Lead Specialist (with logging).

13.5.2 Edit history is preserved in case_specialist_notes versioning.

ARTICLE 14: CUSTOM PAGES

14.1 Custom Pages Defined

14.1.1 Custom Pages are Specialist-created free-form pages within a Case, supporting HTML content for maximum flexibility.

14.1.2 Use cases include:

(a) Strategy memos;

(b) Witness lists and witness preparation notes;

(d) Trial outlines;

(e) Negotiation strategy;

(f) Client briefings;

(g) Other free-form Case content.

14.2 Creation and Editing

14.2.1 Custom Pages may be created or edited by:

(a) Lead Specialist;

(b) Collaborators.

14.2.2 Clients cannot create or edit Custom Pages.

14.3 Link-Based Sharing

14.3.1 Custom Pages support link-based sharing:

(a) Each Page has a unique shareable URL;

(b) Anyone with the URL can view the Page (no Platform authentication required to view a shared link);

14.3.2 Use cases for link-sharing:

(a) Sharing strategy with co-counsel outside the Platform;

(b) Sharing exhibit index with expert witnesses;

14.3.3 Specialists are responsible for the consequences of distributing the URL; URL forwarded broadly leaks the content.

14.4 Privilege Caution

14.4.1 Despite Cabinet's general privilege protection, Custom Pages distributed by URL to external (non-Case Participant) recipients may waive privilege with respect to those recipients.

14.4.2 Specialists shall:

(a) Distribute Custom Page URLs only to recipients with whom privilege is preserved (e.g., co-counsel, experts under engagement, Client's authorized representatives);

(b) Avoid forwarding URLs to recipients where privilege would be waived;

14.4.3 The Platform's link-based sharing is a tool; the Specialist's professional judgment determines appropriate use.

14.5 Privilege Within Platform

14.5.1 Where Custom Page is viewed by Case Participants (Specialists, Client) within the Platform via authenticated access, full privilege protection applies.

14.5.2 Privilege concerns arise only where the URL is forwarded to non-Case-Participant recipients.

14.6 Page Lifecycle

14.6.1 Custom Pages are retained per the Case retention period (Article 20).

14.6.2 Custom Pages may be:

(a) Edited (revisions logged in version history);

(b) Hidden (URL deactivated; content preserved);

14.7 URL Revocation

14.7.1 A Specialist may revoke a Custom Page URL at any time:

(a) The URL becomes inactive;

(b) Subsequent access via the URL returns "Page not found";

ARTICLE 15: ACTIVITY LOG

15.1 Purpose

15.1.1 The Activity Log records events occurring within a Case for audit and procedural transparency purposes.

15.2 Logged Events

15.2.1 The Activity Log records all of the following:

(a) Lifecycle State changes (Draft → Active, Active → Closed, etc.);

(b) Document uploads;

(d) Specialist additions or removals (Lead changes, Collaborators added/removed);

(e) Hearing additions, edits, and cancellations;

(f) Deadline additions, edits, and missed-deadline events;

(g) Specialist Notes additions (existence and visibility category, not content);

(h) Financial entries;

(i) Custom Page edits;

(j) Cabinet Chat events (metadata only — sender, timestamp, message reference);

(k) Lead role transfers;

(l) Withdrawal initiation by Specialist;

(m) Client engagement termination.

15.3 Excluded From Activity Log

15.3.1 The following are NOT recorded in the Activity Log to preserve privacy:

(a) Client view events — when Client viewed which content (read receipts);

(b) Specialist view events — when Specialists viewed which content;

15.3.2 This exclusion preserves Client privacy and avoids invasive read-receipt tracking that would conflict with Bar-rule expectations regarding Client autonomy.

15.4 Default Visibility

15.4.1 The Activity Log is visible by default to the Lead Specialist only.

15.4.2 Collaborators do NOT see the Activity Log unless the Lead grants access.

15.4.3 The Client does NOT see the Activity Log.

15.5 Lead-Granted Access

15.5.1 The Lead may grant Activity Log visibility to specific Collaborators on a per-Case basis.

15.5.2 Granted access may be revoked by the Lead at any time.

15.6 Moderator Access on Dispute

15.6.1 Where a dispute is opened concerning the Case — through Inquiries Rulebook §12 (post-consultation appeal originating from the converted Inquiry), or through other Platform-recognized dispute channels — Platform Moderators may access the Activity Log for dispute resolution purposes.

15.6.2 Moderator access is:

(a) Limited in scope to the dispute matter;

(b) Logged in the Article 5.5 audit trail;

15.7 Immutability

15.7.1 Activity Log entries are immutable — they cannot be edited or deleted.

15.7.2 Where an event needs correction (e.g., recording an erroneous event), a corrective entry is added; the original entry remains.

ARTICLE 16: FINANCIAL MODEL

16.1 Hybrid Payment Model

16.1.1 Cabinet financial mechanics support a hybrid model:

(a) Off-Platform default — retainers, fees, and invoices are arranged and processed between Specialist and Client outside the Platform; the Platform takes no commission;

(b) Platform-handled per-payment — the Specialist may flag specific milestones, invoices, or payments as Platform-handled, in which case the Platform processes the payment and applies a 7% commission to that payment.

16.2 Specialist's Choice — Per Payment

16.2.1 The choice between off-Platform and Platform-handled is made per payment, not per Case:

(a) A single Case may have some payments off-Platform and others Platform-handled;

(b) Specialists may switch between models for different payments at their discretion;

16.3 7% Commission on Platform-Handled Payments

16.3.1 Where a Platform-handled payment occurs:

(a) Platform commission: 7% of gross payment;

(b) Specialist receives 93% of gross;

(c) Commission rate is lower than the Inquiry Rulebook's 12% to reflect the ongoing-engagement nature of Cabinet work versus one-shot Consultations;

(d) No minimum commission — 7% applies regardless of payment size.

16.4 Financials Tab — Tracking and Records

16.4.1 The Financials tab in case_financials records:

(a) Engagement letter terms (where Specialist enters them) — fee structure, retainer amount, hourly rate, etc.;

(b) Invoices — both off-Platform (Specialist tracks for own records) and Platform-handled;

(d) Expenses — Case expenses tracked by Specialist;

(e) Outstanding balance — calculated;

(f) Payment history.

16.4.2 Off-Platform entries are for Specialist record-keeping only; the Platform does not process or hold off-Platform funds.

16.4.3 Platform-handled entries trigger payment processing via the Platform's payment infrastructure (Bank of Georgia API consistent with Inquiries Rulebook §10).

16.5 Engagement Letter Independence

16.5.1 The substantive terms of the engagement letter (rate, scope, retainer, refund terms, withdrawal terms, etc.) are between the Specialist and Client. The Platform does not arbitrate, validate, or enforce engagement letter terms.

16.5.2 Where a Platform-handled payment occurs but the underlying engagement letter is disputed (e.g., Client disputes the invoice amount), the dispute is between the Specialist and Client; the Platform's role is procedural payment processing only.

16.6 Client Visibility of Financials

16.6.1 Financial entries default to Specialist-private; the Specialist may share specific entries with the Client (e.g., to issue an invoice the Client must pay).

16.6.2 Where Platform-handled payment is requested, the Client must necessarily see the invoice to authorize payment.

16.7 Refunds and Disputes

16.7.1 Refunds for Platform-handled payments follow the same general framework as Inquiries Rulebook §10.3 refund mechanics, adapted for the Cabinet context:

(a) Where Specialist or Client mutually agree a refund is appropriate, the Specialist initiates;

(b) Disputed refunds may proceed through Platform's payment dispute process;

(c) The Specialist remains responsible for any refund obligations under Bar rules (e.g., return of unearned retainer per §18.2.4) regardless of payment-handling mode.

16.8 Tax Treatment

16.8.1 Specialists are responsible for their own tax obligations on Cabinet income (consistent with Subscriptions Rulebook §15).

16.8.2 Platform-handled payments are reflected in the Specialist's payout reporting; off-Platform payments are not visible to the Platform for tax purposes.

ARTICLE 17: SPECIALIST WITHDRAWAL

17.1 Right to Withdraw

17.1.1 A Specialist may withdraw from a Case at-will, with reasonable notice and a cooperation obligation.

17.1.2 Specifically:

(a) Withdrawal is at the Specialist's discretion;

(b) Specialist must provide the Client with reasonable advance notice consistent with the engagement letter, Bar rules, and the circumstances;

(c) Specialist must reasonably cooperate in transitioning the matter to substitute counsel — providing case file, conferring with successor, returning Client property.

17.2 Notice Period

17.2.1 The notice period required is as required by Georgian Bar Association rules and a reasonable timeframe in light of the matter's status.

17.2.2 This Rulebook does not impose a specific number-of-days notice; the Specialist's professional judgment under Bar rules governs.

17.3 Mid-Trial Withdrawal

17.3.1 Mid-trial withdrawal is treated the same as general withdrawal under this Rulebook.

17.3.2 The Specialist's substantive professional ethical obligations (e.g., court permission requirements for withdrawal during ongoing proceedings) are independent of and additional to this Rulebook.

17.3.3 This Rulebook does not regulate the substantive conditions of mid-trial withdrawal; that is a matter for the courts and Bar rules.

17.4 Outstanding Fees on Withdrawal

17.4.1 Outstanding fees at withdrawal are governed by the engagement letter between Specialist and Client.

17.4.2 The Platform does not enforce or arbitrate fee obligations on withdrawal.

17.4.3 The Specialist may invoice for earned fees through withdrawal date; payment terms follow the engagement letter.

17.5 Withdrawal Mechanism

17.5.1 A Specialist initiates Withdrawal through the Cabinet interface:

(a) Specialist marks themselves as Withdrawing;

(b) Provides reason (where required by Bar rules) and notice text;

(d) Triggers a Withdrawal Notice to the Client per Article 22.

17.6 Effects of Withdrawal

17.6.1 Upon withdrawal:

(a) Specialist's role as Lead transfers to designated successor (if any) or Case enters Paused state per §6.6;

(b) Specialist loses edit access to the Case (becomes read-only or no access depending on team configuration);

(d) Activity Log records the withdrawal.

17.7 Specialist's Continuing Obligations

17.7.1 Withdrawal does not terminate the Specialist's professional ethical obligations to the Client, including:

(a) Confidentiality obligations (which survive withdrawal indefinitely);

(b) Conflict-of-interest obligations regarding subsequent representation of opposing parties;

(d) Return of unearned fees per Bar rules and engagement letter.

17.7.2 These obligations are between the Specialist and Client; the Platform does not enforce them but provides infrastructure for compliance (e.g., Case File Delivery per Article 19).

17.8 Withdrawal at Subscription Termination

17.8.1 Where a Specialist initiates Platform account termination with one or more Active Cases:

(a) The Platform issues a reminder to the Specialist of the Active Cases and the Specialist's professional obligation to transfer or close them properly;

(b) The reminder serves as evidence of Platform's procedural notice;

(d) Upon termination confirmation, Active Cases auto-archive per §17.8.2;

(e) The Specialist's failure to transfer Cases prior to termination is the Specialist's professional ethical liability under Bar rules — not a Platform-blocking matter.

17.8.2 Auto-archived Cases at Specialist termination:

(a) Become read-only and inaccessible to the terminated Specialist;

(b) Client retains read-only access to view historical Case contents;

(c) Where Collaborators exist, Lead role is automatically transferred to senior Collaborator (if designation exists) or Case enters Paused state;

(d) The Client receives notification of termination and is encouraged to engage substitute counsel.

ARTICLE 18: CLIENT TERMINATION OF ENGAGEMENT

18.1 Right to Terminate

18.1.1 A Client may terminate the engagement at-will, with immediate effect.

18.1.2 Termination does not require justification or advance notice from the Client to the Specialist.

18.2 Outstanding Fees on Client Termination

18.2.1 Earned fees through the termination date are due to the Specialist:

(a) Specialist may invoice for work performed up to termination;

(b) Client's payment obligation is governed by the engagement letter;

18.2.2 Outstanding hours, milestones, or expenses incurred before termination are due per the engagement letter.

18.2.3 Refund of unearned retainer:

(a) Per Bar Association rules, the Specialist is obligated to return unearned portions of any prepaid retainer;

(b) The Specialist's professional obligation is independent of the Platform;

18.3 Case File Delivery

18.3.1 Client termination triggers Case File Delivery per Article 19.

18.4 Specialist's Response to Termination

18.4.1 Upon Client termination, the Specialist shall:

(a) Cease active work on the matter unless the Client expressly authorizes specific continuation (e.g., emergency filings);

(b) Cooperate in transition to substitute counsel;

(d) Invoice for earned fees;

(e) Refund any unearned retainer per Bar rules.

18.4.2 The Specialist remains bound by ongoing confidentiality and conflict obligations per §17.7.

18.5 Client-Specialist Engagement End

18.5.1 Upon Client termination, the Case Lifecycle State transitions:

(a) Active or Paused → Closed;

(b) Activity Log records the termination event;

ARTICLE 19: CASE FILE DELIVERY

19.1 Hybrid Delivery Model

19.1.1 Upon Case Closure (whether by Specialist completion, Specialist Withdrawal, or Client termination), the Client receives a Case File Delivery package.

19.1.2 The Delivery model is hybrid:

(a) Client receives joint records and Client-uploaded documents;

(b) Specialist retains work product (Specialist-private notes, internal team-only documents and notes).

19.2 Contents of Case File Delivery

19.2.1 The Delivery includes:

(a) All Case-shared and Client-shared documents (per §10.2.3);

(b) Documents the Client originally uploaded to the Case;

(d) Hearings record (dates, courts, basic outcomes);

(e) Deadlines record (relevant client-facing deadlines);

(f) Cabinet Chat history of communications between Specialist team and Client;

(g) Custom Pages marked Client-shared (typically rare; most Custom Pages are internal);

(h) Financial records relating to invoices issued to Client and payments received;

(i) Original Inquiry record (where Case derived from Inquiry conversion).

19.3 Excluded From Case File Delivery

19.3.1 Excluded:

(a) Specialist-private Notes (per §13.4.2);

(b) Team-shared Notes that have not been marked Client-shared;

(d) Specialist-team Documents that have not been marked Client-shared;

(e) Specialist's internal financial tracking (e.g., internal hours not yet invoiced);

(f) Specialist Notes containing privileged work product (e.g., strategic analysis intended for Specialist's eyes only);

(g) Case Credentials (returned per §11.7 only if Client originally provided);

(h) Activity Log (Specialist work product);

(i) Custom Pages that are Specialist-team only.

19.4 Format of Delivery

19.4.1 Delivery is provided through the Platform interface:

(a) Client may download in standard formats (PDF, ZIP archive of documents);

(b) Delivery URL is generated on Closure;

19.5 Delivery Timing

19.5.1 Delivery is prepared upon Case Closure and made available to the Client:

(a) Where Closure is consensual: simultaneously with Closure;

(b) Where Closure follows Specialist Withdrawal: as soon as practicable after the Withdrawal becomes effective;

19.6 Specialist's Bar-Rule Obligations

19.6.1 The Case File Delivery mechanism in this Article supports Specialist's Bar-rule obligations to deliver Case files to clients.

19.6.2 The Specialist may have additional Bar-rule obligations to deliver materials beyond what Cabinet Delivery includes (e.g., attorney work product the Bar requires to be turned over). Compliance with such obligations is the Specialist's responsibility.

19.7 Subsequent Access to Delivered File

19.7.1 The Client may re-download the delivered file at any time during the Case retention period.

19.7.2 After the retention period expires, the file may be deleted per the Platform's data lifecycle policy.

ARTICLE 20: DATA RETENTION

20.1 Retention Periods

20.1.1 Cabinet data retention follows these periods:

Data Type	Retention Period
Active Case data (Lifecycle: Draft, Active, Paused)	Active engagement lifetime
Closed Case data	5 years post-Closure
Archived Case data	Same as Closed (5 years from original Closure)
Deleted Case data	Removed from active storage; metadata logged for audit; some retention per legal/audit requirements
Activity Log	Case retention period + 5 years (per §5.5.3)
Audit Trail of Platform Access (per §5.5)	Case retention period + 5 years
Case Credentials	Case retention period (5 years post-Closure) per §11.5
Documents	Same as Case retention
Cabinet Chat	Same as Case retention
Specialist Notes	Same as Case retention
Custom Pages	Same as Case retention
Financial records	Same as Case retention or longer per Georgian tax law

20.2 Five-Year Standard

20.2.1 The 5-year post-Closure retention reflects:

(a) Standard Georgian record-keeping requirements for legal practice;

(b) Limitation periods for malpractice claims;

20.2.2 Where applicable Georgian law requires longer retention for specific case types (e.g., real estate transactions, criminal matters), longer retention applies.

20.3 Specialist Account Termination

20.3.1 Specialist account termination does NOT shorten Case retention.

20.3.2 Cases continue to be retained per §20.1; access transitions per §17.8.

20.4 Client Account Termination

20.4.1 Client account termination does NOT delete Case data.

20.4.2 The Specialist retains access; Case data is retained per §20.1.

20.4.3 Subsequent Client requests for the Case file are honored even where Client account is terminated.

20.5 Data Subject Access

20.5.1 Specialists and Clients may request their own Case-related data per the Platform's Privacy Policy.

20.5.2 Where Specialist's request would expose another Case Participant's confidential information, the Platform balances data subject rights with confidentiality obligations under the Privacy Policy.

20.6 Court-Compelled Disclosure

20.6.1 Court orders or regulatory directives compelling disclosure of Case data are handled per §5.7.

ARTICLE 21: CONFLICTS OF INTEREST

21.1 Specialist-Self-Managed

21.1.1 Conflict-of-interest checking is Specialist-self-managed:

(a) The Platform does NOT perform automated conflict-of-interest checks at Case creation;

(b) The Specialist bears sole responsibility for verifying compliance with Bar rules regarding conflicts;

(c) The Specialist's professional duty includes affirmatively investigating potential conflicts before accepting representation.

21.2 Mid-Engagement Conflicts

21.2.1 Where a conflict of interest emerges during ongoing engagement:

(a) The Specialist's Bar-rule obligations govern (typically requiring disclosure to affected Clients and possible withdrawal);

(b) The Platform does NOT intervene or flag conflicts;

21.3 Mandatory Withdrawal on Conflict

21.3.1 Where a Specialist determines (or Bar rules require) that a conflict mandates withdrawal:

(a) The Specialist withdraws per Article 17;

(b) The Specialist's reasons for withdrawal need not be disclosed to the Platform if Bar rules permit confidentiality;

21.4 Platform's Limited Role

21.4.1 The Platform's role in conflict matters is limited to:

(a) Providing the withdrawal mechanism (Article 17);

(b) Maintaining Case data so Specialists may identify conflicts through their own searches;

ARTICLE 22: NOTIFICATIONS

22.1 Specialist Notifications

22.1.1 The Platform shall notify Specialists of:

(a) New Case assignment (when invited as Collaborator);

(b) Document uploaded (with uploader identifier);

(d) Hearing reminder (24 hours and 1 hour prior);

(e) Collaboration invitation received (and acceptance/decline result);

(f) Case state change (Draft → Active, Active → Closed, etc.);

(g) Lead role transferred (to or from this Specialist);

(h) Client uploaded document;

(i) Client message in Cabinet Chat;

(j) Specialist team change (Collaborator added or removed);

(k) Withdrawal initiated (own withdrawal or another Specialist's);

(l) Client terminated engagement;

(m) Case archived;

(n) Financial entry added (invoice issued, payment received).

22.2 Client Notifications

22.2.1 The Platform shall notify Clients of:

(a) Case created (Specialist invited Client to Case);

(b) Document uploaded by Specialist team;

(d) Deadline reminder (where deadline is shared with Client);

(e) Specialist invited additional Collaborator;

(f) Case state change (visible state changes);

(g) Specialist message in Cabinet Chat;

(h) Withdrawal notice from Specialist;

(i) Invoice issued (if Platform-handled payment);

(j) Financial entry visible to Client.

22.3 Notification Channels

22.3.1 Notifications are delivered via:

(a) In-app notification (mandatory);

(b) Email to address on file (mandatory).

22.3.2 SMS, push, and other channels may be added at the Platform's operational discretion.

22.4 Notification Failure

22.4.1 Notification delivery failures (bounced email, etc.) do not extend deadlines, hearing dates, or other time-sensitive obligations.

22.4.2 Specialists and Clients are responsible for maintaining accurate contact information.

ARTICLE 23: PROHIBITED CONDUCT

23.1 Specialist Prohibitions

23.1.1 Specialists shall NOT:

(a) Create Cases without genuine engagement (e.g., to manipulate metrics, profile statistics, or to pre-position for false billing);

(b) Use Cabinet to circumvent Inquiry-based pricing (e.g., creating an "independent" Case for a Platform-introduced Client to avoid Inquiries §10.4 commission);

(d) Distribute Custom Page URLs in a manner that breaches privilege without Client awareness (per §14.4);

(e) Misrepresent Case status to the Client (e.g., marking Closed before genuine closure);

(f) Use Cabinet Chat for non-Case communications;

(g) Forward privileged content outside the Case team without Client authorization;

(h) Manipulate Activity Log entries (impossible due to immutability, but attempts constitute prohibited conduct);

(i) Use the Case file delivery process to deliver materials inconsistent with Article 19.3 exclusions (e.g., delivering Specialist-private notes despite their privacy designation);

(j) Use Multi-Specialist team mechanics to circumvent quotas (e.g., creating sham team structures to inflate effective Active Case quotas).

23.2 Client Prohibitions

23.2.1 Clients shall NOT:

(a) Create false or misleading Cases (Cases are Specialist-initiated; this prohibition addresses Client-side actions within an existing Case);

(b) Misuse the Case File Delivery to obtain privileged materials they are not entitled to (e.g., social engineering to bypass exclusions);

(d) Misuse case-related information for harassment or defamation;

(e) Use the Engagement to extract free legal advice without intent to engage;

(f) Repeatedly initiate engagement and termination in patterns suggesting bad faith.

23.3 Consequences

23.3.1 Violations may result in:

Severity	Possible Consequences
Minor	Warning
Standard	Cabinet feature restrictions; specific records flagged
Serious	Cabinet feature suspension; account flagged
Severe	Account suspension or termination per Role T&C

23.3.2 Specific consequence application is at Platform discretion in coordination with Moderators per Moderator T&C.

ARTICLE 24: PLATFORM AND MODERATOR ACCESS

24.1 Default — No Routine Access

24.1.1 Platform staff and Moderators have NO routine access to Case content.

24.1.2 This default protection applies regardless of role within the Platform.

24.2 Exceptional Access Grounds

24.2.1 Platform access to Case content is permitted only on:

(a) Court order or legal compulsion (per §5.7);

(b) Specialist's explicit request for support (Specialist grants temporary scoped access);

(i) Internal Platform-Admin approval procedures;

(ii) Logging in the audit trail per §5.5;

(iii) Notification to the affected Specialist where lawful.

24.2.2 Moderator access to Case content is permitted only:

(a) Where a dispute is opened concerning the Case (per Inquiries Rulebook §12, where Cabinet was Inquiry-derived);

(b) Where the Moderator's role under Moderator T&C requires access for a specific dispute;

(d) Logged per §5.5.

24.3 Moderator Confidentiality

24.3.1 Moderators accessing Case content are bound by:

(a) Moderator T&C confidentiality obligations;

(b) The privilege protections of this Rulebook;

24.4 SUPER_ADMIN Authority

24.4.1 SUPER_ADMIN role may override Platform access controls in specific scenarios per Platform policy.

24.4.2 All SUPER_ADMIN access to Case content is logged per §5.5 and reviewable by Lead Specialist.

ARTICLE 25: CROSS-RULEBOOK INTEGRATION

25.1 Relationship to Other Rulebooks

25.1.1 This Rulebook coordinates with the following:

Topic	Where the Rules Live
Inquiry intake, Quote, payment, Capture	Inquiries Rulebook
Inquiry-to-Cabinet conversion	Inquiries Rulebook §11.6
Subscription tier features (Active Cases per Month quota)	Subscriptions Rulebook §5.1.1, §6.1.1
Subscription Past Due / downgrade with read-only Cabinet access	Subscriptions Rulebook §8.4.1(f), §9
Calendar publication, book-from-calendar	Calendar Rulebook
Reviews	Reviews Rulebook
Video sessions for Cabinet meetings	Video Rulebook
Specializations and pricing	Specializations & Pricing Rulebook
Organisation institutional context	Organisation T&C

25.2 Conflict Resolution

25.2.1 Conflicts are resolved as follows:

(a) Inquiry intake, initial Consultation mechanics — Inquiries Rulebook prevails;

(b) Subscription tier definitions and Active Cases quota — Subscriptions Rulebook prevails;

(d) Video session mechanics — Video Rulebook prevails;

(e) Reviews — Reviews Rulebook prevails;

(f) Pricing and specializations — Specializations & Pricing Rulebook prevails;

(g) Case lifecycle, multi-Specialist team mechanics, document/credential/notes/custom pages, withdrawal, Case file delivery, financial Cabinet model — this Rulebook prevails;

(h) Where matters cross categories — interpreted to give effect to all and avoid conflict; if irreducible, the more specific Rulebook prevails over the more general.

25.3 Required Cross-Reference Updates to Other Rulebooks

25.3.1 Adoption of this Rulebook requires the following updates to other Rulebooks (handled in companion amendment package):

(a) Inquiries Rulebook — remove "(forthcoming)" placeholders for Cabinet Function Rulebook (§1.2.2(a), §11.6.3, §13.1.2, §16.2.1, definition of "Cabinet"); add specific cross-references to this Rulebook;

(b) Subscriptions Rulebook — minor update to §8.4.1(f) cross-referencing this Rulebook; update §22.1.1; update any other "Cabinet" reference;

(d) Company Specialist T&C — parallel to Solo Specialist T&C;

(e) User T&C — new Article on Client rights and obligations within a Case;

(f) Organisation T&C — minor cross-reference (Affiliated Members may serve as Lead/Collaborators per their Specialist capacity).

25.3.2 No modifications required to: Posting Rulebook, Reviews Rulebook, Video Rulebook, Calendar Rulebook, Specializations & Pricing Rulebook, Author T&C, Trainer T&C, Trainee T&C.

ARTICLE 26: PLATFORM LIABILITY

26.1 Platform Disclaimers

26.1.1 The Platform provides Cabinet infrastructure on an "as-is, as-available" basis.

26.1.2 The Platform makes no representation or warranty regarding:

(a) Outcomes of legal matters managed in Cabinet;

(b) Quality of legal services provided by Specialists;

(d) Compliance with Bar rules by individual Specialists;

(e) Privilege establishment or maintenance (Specialist's responsibility).

26.2 Specialist Liability

26.2.1 The Specialist is solely responsible for:

(a) Quality of legal services and compliance with Bar rules;

(b) Privilege establishment and maintenance;

(d) Engagement letter terms and enforcement;

(e) Compliance with court rules, deadlines, and procedural requirements;

(f) Case strategy, advocacy, and outcomes;

(g) Refund of unearned retainer per Bar rules;

(h) Tax obligations on Cabinet income;

(i) All other professional and ethical obligations under applicable law.

26.3 Indemnification

26.3.1 The Specialist shall defend, indemnify, and hold harmless the Platform from claims arising from:

(a) Specialist-Client disputes regarding Case outcomes, fees, or service quality;

(b) Bar discipline or malpractice claims arising from the Specialist's conduct;

(d) Failure to comply with engagement letter or Bar rules;

(e) Inappropriate use of Case Credentials;

(f) Breach of this Rulebook or applicable law.

26.4 Platform Liability Limit

26.4.1 The Platform's aggregate liability for any and all claims arising under or relating to this Rulebook, regardless of theory of liability, is limited to:

(a) The total commission paid by the Specialist to the Platform under this Rulebook in the twelve (12) months preceding the event giving rise to the claim; OR

(b) 1,000 GEL, whichever is greater.

26.4.2 This limitation does not apply to:

(a) The Platform's own gross negligence or wilful misconduct;

(b) Liabilities that cannot be limited under applicable law.

26.5 Specialist's Professional Liability Insurance

26.5.1 Specialists are encouraged to maintain professional liability insurance (errors and omissions, malpractice insurance) covering their Cabinet work.

26.5.2 The Platform does not provide such insurance.

ARTICLE 27: AMENDMENTS AND RE-CONSENT

27.1 Right to Amend

27.1.1 The Platform reserves the right to amend this Rulebook at any time, in its sole discretion.

27.2 Notice and Effect

27.2.1 Non-material amendments take effect upon publication; continued use constitutes acceptance.

27.2.2 Material amendments (e.g., changes to commission rate, privilege treatment, Case File Delivery scope, Withdrawal mechanics, retention periods) are subject to:

(a) Affirmative re-consent for Specialists wishing to continue using Cabinet;

(b) At least thirty (30) days' advance notice.

27.3 Right to Decline

27.3.1 A Specialist who does not accept a material amendment may decline; the consequence is loss of Cabinet access. Existing Cases remain accessible read-only for retention purposes; no new Cases may be created.

ARTICLE 28: GOVERNING LAW AND DISPUTE RESOLUTION

28.1 Governing Law

28.1.1 This Rulebook is governed by the laws of Georgia.

28.2 Forum

28.2.1 Any dispute arising out of or relating to this Rulebook that cannot be resolved through Platform mechanisms shall be subject to the exclusive jurisdiction of the courts of Tbilisi, Georgia.

28.3 Specialist-Client Disputes

28.3.1 Disputes between Specialist and Client regarding Cabinet engagement (fee disputes, malpractice claims, etc.) are between those parties.

28.3.2 The Platform is not a forum for adjudicating Specialist-Client substantive disputes.

28.3.3 Limited Platform involvement is governed by Inquiries Rulebook §12 (where dispute relates to Inquiry-derived Cabinet) or by Platform's general dispute mechanisms.

28.4 Language

28.4.1 This Rulebook is published in English, Georgian, and Russian. In the event of any conflict between language versions, the Georgian version prevails.

ARTICLE 29: SEVERABILITY AND ENTIRE RULEBOOK

29.1 Severability

29.1.1 If any provision of this Rulebook is held invalid, illegal, or unenforceable, the provision shall be modified to the minimum extent necessary to make it valid; if not possible, the provision shall be severed, and the remaining provisions shall continue in force.

29.2 Entire Rulebook

29.2.1 This Rulebook, together with the master Terms and Conditions, Privacy Policy, Cookie Policy, and applicable Function Rulebooks and Role Terms and Conditions, constitutes the entire agreement regarding the Cabinet function on the Platform.

29.3 No Waiver

29.3.1 The Platform's failure to enforce any provision shall not constitute a waiver. Any waiver must be in writing to be effective.

29.4 Survival

29.4.1 Provisions concerning privilege (Article 5), audit trails (§5.5), data retention (Article 20), Case File Delivery (Article 19), liability allocation (Article 26), and dispute resolution (Article 28) survive termination of this Rulebook.

ARTICLE 30: VERSION HISTORY

Version	Date	Author	Description
1.0	13 May 2026	Legal Sandbox Georgia LLC	Initial publication

SCHEDULE B: SUMMARY OF KEY OPERATIONAL PARAMETERS

Parameter	Value	Source
Lifecycle states	Draft / Active / Paused / Closed / Archived / Deleted	Art. 4
Procedural Stage (separate field)	Specialist-managed informational	Art. 4.3
Case creation paths	Inquiry conversion + Independent	Art. 3.1
Active Cases per Month — Solo	0 / 5 / 30 (Freemium / Pro / Expert)	Subs Rulebook §5.1.1
Active Cases per Month — Company	0 / 30 / 96 (Basic / Established / Enterprise)	Subs Rulebook §6.1.1
Privilege default	All Cabinet content privileged	Art. 5.1
Platform access to Privileged Content	Court order / Specialist request / Suspected serious misuse	Art. 5.2
Encryption	Standard at-rest; E2E if law requires	Art. 5.3
Privilege survives	Termination of any kind	Art. 5.4
Audit trail of Platform access	Immutable; Lead-viewable; +5 years retention	Art. 5.5
Lead Specialist privileges	Invite, transfer Lead, close Case	Art. 6.1
Collaborator privileges	Edit content; cannot invite or close	Art. 6.1
Multi-Specialist invitation acceptance window	14 days	Art. 6.2.2(c)
Document upload eligibility	All Case Participants	Art. 10.2.2
Document visibility levels	Specialist-private / Team / Case-shared / Client-shared	Art. 10.2.3
Document version history	Preserved (immutable)	Art. 10.2.4
Hearing reminder	24 hours prior	Art. 10.3.2
Deadline reminder	24 hours prior (or Specialist-customized)	Art. 10.4.1
Missed deadline handling	Notification + Activity Log flag	Art. 10.4.2
Case Credentials storage	Platform encrypted at-rest	Art. 11.2
Credential audit logging	On retrieval/copy only (not view)	Art. 11.4
Credentials lifecycle	5-year Case retention	Art. 11.5.1
Specialist Notes visibility	Per-note flagged	Art. 13.2
Notes in Case File Delivery	Only Client-shared notes included	Art. 13.4.1
Custom Pages format	HTML free-form	Art. 14.1
Custom Page sharing	Public link (anyone with URL)	Art. 14.3
Activity Log default visibility	Lead Specialist only	Art. 15.4
Activity Log granted access	Per-Collaborator by Lead	Art. 15.5
Moderator access to Activity Log	On dispute opening only	Art. 15.6
Cabinet financial model	Off-Platform default + 7% Platform-handled	Art. 16.1
Cabinet commission rate	7%	Art. 16.3
Cabinet commission minimum	None	Art. 16.3.1(d)
Per-payment off/on choice	Yes	Art. 16.2
Specialist withdrawal	At-will + reasonable notice + cooperation obligation	Art. 17.1
Withdrawal notice period	Per Bar rules + reasonable	Art. 17.2
Mid-trial withdrawal	Same as general (Bar rules apply independently)	Art. 17.3
Outstanding fees on withdrawal	Per engagement letter	Art. 17.4
Account termination with Active Cases	Reminder; not blocked	Art. 17.8
Client termination of engagement	At-will, immediate	Art. 18.1
Outstanding fees on Client termination	Earned through date due	Art. 18.2.1
Unearned retainer refund	Per Bar rules; Platform doesn't enforce	Art. 18.2.3
Case File Delivery model	Hybrid (joint records + Client uploads + shared notes)	Art. 19
Case retention period	5 years post-Closure	Art. 20.1
Conflict checking	Specialist-self-managed	Art. 21.1
Mid-Case conflict	Bar rules govern; Platform doesn't intervene	Art. 21.2
Notification channels	In-app + Email	Art. 22.3
Material amendment notice	30 days	Art. 27.2
Liability cap	12-month commission OR 1,000 GEL (greater)	Art. 26.4

END OF RULEBOOK