Update to Rohas Legal AI: Litigation

{
  "description": "Build source-linked litigation chronologies from pleadings, correspondence, records, evidence, filings, and testimony. Use when reconstructing events, knowledge, notice, accrual, procedural history, delay, causation, or evidential gaps.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 286
    }
  ],
  "name": "chronology-builder",
  "skill_md_contents": "---\nname: chronology-builder\ndescription: >-\n  Build source-linked litigation chronologies from pleadings, correspondence,\n  records, evidence, filings, and testimony. Use when reconstructing events,\n  knowledge, notice, accrual, procedural history, delay, causation, or evidential gaps.\n---\n\n# Chronology Builder\n\nCreate a reproducible chronology, not a persuasive narrative disguised as data.\nKeep event time, document time, filing time, receipt time, and asserted knowledge distinct.\n\n## Intake\n\nObtain the issues and date range, document set, metadata, time zones, pleadings,\nwitness accounts, procedural docket, naming conventions, disputed dates,\nlimitation questions, and requested level of detail.\n\n## Building method\n\n1. Create stable source IDs and preserve native dates, time zones, page or\n   paragraph locators, authors, recipients, and document relationships.\n2. Extract dates without silently converting an estimate, range, relative phrase,\n   metadata field, signature date, or later recollection into a certain event date.\n3. Create separate fields for event, creation, sent, received, filed, served,\n   discovered, and recorded dates where they differ.\n4. Normalise display dates and times while retaining the source value.\n5. Attribute every entry to a source and label direct evidence, reported account,\n   inference, allegation, agreed fact, judicial finding, and procedural event.\n6. Deduplicate copies without losing annotations, attachments, versions,\n   forwarding chains, or contradictory metadata.\n7. Link cause and response sequences, notice, opportunity, decision, performance,\n   breach, damage, mitigation, and procedural consequences only where supported.\n8. Record conflicting dates and accounts side by side. State the basis and\n   confidence of any proposed resolution.\n9. Identify unexplained gaps, missing attachments, absent periods, clock drift,\n   impossible sequence, late-created records, and discovery or preservation needs.\n10. Produce focused views for limitation, witness preparation, pleadings,\n    submissions, disclosure, damages, and hearing bundles without changing the master.\n\n## Output\n\nProvide a master chronology with date, event, actor, source, locator, status,\nconfidence, issue tags, and notes; plus conflict, gap, and key-date schedules.\n\n## Guardrails\n\nDo not infer that a document was sent, received, read, agreed, or acted on merely\nbecause it exists. Do not overwrite uncertainty or privilege labels. Protect\npersonal and confidential data and ensure exported chronologies remain traceable\nto preserved sources.\n"
}