Update to Rohas Legal AI: Litigation

{
  "description": "Audits document productions before or after disclosure for scope, completeness, format, metadata, numbering, document families, redactions, privilege, confidentiality, technical integrity, exceptions, and delivery records. Use for production quality control, disclosure certification support, deficiency review, rolling-production reconciliation, or remediation of a defective production.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 293
    }
  ],
  "name": "production-set-checker",
  "skill_md_contents": "---\nname: production-set-checker\ndescription: >-\n  Audits document productions before or after disclosure for scope, completeness,\n  format, metadata, numbering, document families, redactions, privilege,\n  confidentiality, technical integrity, exceptions, and delivery records. Use for\n  production quality control, disclosure certification support, deficiency review,\n  rolling-production reconciliation, or remediation of a defective production.\n---\n\n# Production Set Checker\n\nRun a reproducible release gate that reconciles what was ordered or agreed, what\nwas reviewed, and what is actually being delivered.\n\n## Intake\n\nObtain the governing order, request, agreement or protocol; review and collection\nreports; source and processed counts; production specification; export, load files,\nimages, text, natives and metadata; numbering ranges; privilege and redaction logs;\nconfidentiality designations; exception reports; prior rolling productions;\ntransmittal; deadline; and authorised release decision-maker.\n\nNever open or transmit a production outside the authorised environment merely to\nperform a check.\n\n## Method\n\n1. Freeze the candidate production and record version, export time, operator,\n   tool version, settings, file hashes or comparable integrity data, and location.\n2. Reconcile requested or ordered scope against collection, processing, review,\n   promotion, withholding, exclusion, exception, and production counts. Explain\n   differences; do not force totals to match.\n3. Validate numbering for uniqueness, continuity, endorsed page ranges, document\n   boundaries, parent-child relationships, gaps, overlaps, duplicates, and prior\n   rolling ranges.\n4. Check that images, extracted text, natives, placeholders, translations, media,\n   container contents, attachments, and structured data are present and linked as\n   required. Record encrypted, corrupt, unsupported, or missing items separately.\n5. Validate required metadata field names, types, encodings, date and time zones,\n   delimiters, paths, identifiers, family links, custodians, confidentiality, and\n   redaction indicators. Compare a reasoned sample to source data.\n6. Reconcile withheld and redacted items to the privilege log, redaction record,\n   slip sheets, family treatment, and counsel decisions. Search for inconsistent\n   duplicates and near-duplicates without assuming they share privilege.\n7. Test redactions visually and technically: applied area, stated basis,\n   underlying text or layer removal, OCR, comments, revision history, metadata,\n   hidden objects, attachments, thumbnails, and native leakage.\n8. Check confidentiality markings, legends, access tiers, personal or secret data,\n   agreed protective measures, and any export-control or cross-border restrictions.\n9. Perform malware and file-safety checks using authorised tools, then validate\n   archive structure, loadability, manifests, checksums, encryption, password\n   exchange, media capacity, and delivery method.\n10. Produce blocking defects, non-blocking exceptions, remediation owners,\n    re-test evidence, final approval, transmittal, receipt, and immutable release\n    record. Do not certify legal compliance without the authorised signatory.\n\n## Output\n\nProvide the production control sheet, scope and count reconciliation, numbering\nreport, family and file-completeness report, metadata validation, privilege and\nredaction reconciliation, confidentiality check, technical exception log,\nblocking-defect list, remediation tracker, and release-sign-off checklist.\n\n## Guardrails\n\nDo not release a set with unresolved privilege leakage, reversible redactions,\nmalware, missing families, unexplained count differences, wrong recipients, or\nunapproved sensitive data. Do not modify source evidence, hide adverse material,\nbackfill logs, or describe a technical QC pass as a legal certification.\n"
}