← Rohas Legal AI: PracticeCONTENT HISTORY

Update to Rohas Legal AI: Practice

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Convert contemporaneous legal work records into accurate, specific, privilege-aware time-entry narratives. Use for billing review, matter coding, invoice preparation, outside-counsel guidelines, fee applications, or audits where task, purpose, stage, value, and time must be defensible.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 317
    }
  ],
  "name": "time-narrative-drafter",
  "skill_md_contents": "---\nname: time-narrative-drafter\ndescription: >-\n  Convert contemporaneous legal work records into accurate, specific,\n  privilege-aware time-entry narratives. Use for billing review, matter coding,\n  invoice preparation, outside-counsel guidelines, fee applications, or audits\n  where task, purpose, stage, value, and time must be defensible.\n---\n\n# Time Narrative Drafter\n\nDescribe work actually performed; never reconstruct unsupported time. Preserve\nenough specificity for review without revealing privileged advice or strategy.\n\n## Intake\n\nObtain the contemporaneous source record, date, timekeeper, role, duration,\nmatter, task and activity codes, work product, participants, purpose, phase,\nbilling guidelines, privilege and confidentiality restrictions, block-billing\nrules, travel or administrative policies, duplicate-attendance rules, and\nnon-billable or write-off instructions.\n\n## Drafting method\n\n1. Verify that the source supports the date, duration, task, participants, and\n   work product. Flag gaps rather than guessing.\n2. Use a clear action, specific subject, and legitimate purpose: reviewed,\n   analysed, drafted, revised, prepared, conferred, researched, or attended.\n3. Identify the document, issue, transaction, hearing, witness, negotiation, or\n   procedural stage without disclosing protected conclusions.\n4. Distinguish substantive legal work from clerical, training, business\n   development, duplicate, supervisory, travel, waiting, or administrative time.\n5. Split unrelated tasks where contemporaneous records and billing rules permit.\n   Do not allocate time artificially to defeat block-billing restrictions.\n6. Apply task, activity, phase, jurisdiction, and expense codes consistently.\n7. Describe internal conferences by participants' roles, subject, and purpose;\n   explain multiple attendance where required.\n8. Remove vague phrases such as “attention to matter,” unnecessary rhetoric,\n   outcome guarantees, internal commentary, and privileged legal conclusions.\n9. Test reasonableness against the work product, complexity, staffing, duplication,\n   delegation, and client guidelines without changing actual recorded time.\n10. Route questionable, late, reconstructed, excessive, duplicate, or\n    non-compliant entries for timekeeper and billing-lawyer review.\n\n## Output\n\nProvide revised narratives, code suggestions, split recommendations,\nprivilege-safe alternatives, exception flags, and a source-to-entry audit table.\n\n## Guardrails\n\nNever invent, increase, shift, round deceptively, duplicate, or disguise time.\nDo not alter another timekeeper's record without approval. Do not reveal\nprivileged advice or confidential identities merely to add detail. Follow the\nengagement, client guidelines, court rules, fee law, and firm policy.\n"
}

SHA-256 of public snapshot: 124045c7ea9871aa8907b147c3c97943d06fc18a3eb45e5f6980b7eaa6ccf8d7