Skip to content

Document Index

PART A — Purpose

This page describes the Document Index concept for the attorney portal.

Use this index when you need to: - Locate a specific tab or exhibit quickly,
- Confirm which volume owns a topic, or
- Build a working set for review (e.g., “all executive overviews,” “all REPL verification tabs,” “all chain memos”).

This page does not embed the full index; the index should live as a database (Notion) or a table (static export) that can be filtered and sorted.

PART B — Indexing Model

Recommended implementation: maintain a Notion database (or equivalent table) as the authoritative index with these fields:

  • Volume (01–12)
  • Color
  • Tab Code (e.g., A000, WT-004, B012)
  • DocID (binder DocID or WEB DocID)
  • Title
  • Status (Draft / Working Canon / Archive‑Ready)
  • Visibility (PUBLIC / ATTORNEY‑ONLY / INTERNAL)
  • Owner Volume (single source of truth)
  • Canonical Link (preferred link)
  • Source Type (Tab / Exhibit / Memo / Spreadsheet / PDF)
  • Last Updated (YYYY‑MM‑DD)

PART C — Suggested Saved Views for Counsel Onboarding

Create saved views that match how attorneys actually consume the system:

  1. Start Here — Executive Overviews (A000 + WT‑000 + control tabs)
  2. Facts Spine (White Vol 07 WT‑series; timelines; witness directory)
  3. Damages calculators (Blue/Red/Brown calculators + verification tabs)
  4. Strategy Packets (Purple chain memos + Part B lanes + P‑series)
  5. Enforcement (Green recovery bands; lien priority; collateral map)
  6. Admin / OATH Track (Red‑OATH volume only)
  7. Criminal Pattern Evidence (Grey volume only)

PART D — Notion Publishing Controls

This index is also the best place to enforce publishing discipline (per WEB‑001):

  • Maintain two trees: a published / counsel-facing root and a separate internal root.
  • Do not nest internal drafts, archives, or coordination documents under any published root.
  • Disable Duplicate as template unless counsel explicitly requests it.
  • Disable Search engine indexing unless intentionally public.
  • When taking pages down: unpublish and revoke “anyone with link” access.

PART E — Slug Registry

Maintain a small “slug registry” table:

  • Page Title → Canonical URL Slug → Actual Notion URL

Operational notes: - Avoid deleting published pages where possible. Deprecate by renaming/moving.
- If a slug must be freed, change the slug before deletion when feasible.
- Use canonical slugs (like /damages-overview) as the stable reference in memos even if the Notion share URL is long.

END — Document Index v1.5