Update to Rohas Legal AI: Regulatory

{
  "description": "Prepare periodic and event-driven regulatory returns, reports, notifications, disclosures, certifications, and portal submissions with controlled data lineage, calculations, validation, approvals, and submission evidence. Use for filing preparation, amendment, resubmission, reconciliation, or readiness review.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 305
    }
  ],
  "name": "regulatory-filing-preparer",
  "skill_md_contents": "---\nname: regulatory-filing-preparer\ndescription: >-\n  Prepare periodic and event-driven regulatory returns, reports, notifications,\n  disclosures, certifications, and portal submissions with controlled data lineage,\n  calculations, validation, approvals, and submission evidence. Use for filing\n  preparation, amendment, resubmission, reconciliation, or readiness review.\n---\n\n# Regulatory Filing Preparer\n\nUse the regulator's current official taxonomy, form, instructions, validation rules,\nportal requirements, and deadline. Keep source data, transformations, judgements,\napprovals, filed output, and receipt linked in one audit trail.\n\n## Intake\n\nObtain the reporting entity and permissions, jurisdiction and regulator, filing type,\nperiod or trigger event, legal basis, due date and timezone, current form or schema,\ninstructions, portal access constraints, prior filings, source systems, calculations,\nmateriality and correction rules, owners, reviewers, and authorised signatory.\n\n## Preparation method\n\n1. Verify the filing obligation, reporting perimeter, frequency or event trigger,\n   reference period, thresholds, exemptions, due date, extension route, and whether\n   parallel or consolidated filings are required.\n2. Freeze the authoritative requirement set: instrument, form and version, data\n   dictionary, taxonomy, instructions, FAQs, validation rules, technical schema,\n   certifications, payment, language, and submission channel.\n3. Build a field-level matrix with definition, unit, sign, currency, basis, period,\n   entity scope, source, transformation, judgement, control, preparer, reviewer,\n   evidence, validation, and form location.\n4. Extract from controlled sources and preserve query or report parameters, cutoff,\n   timestamps, versions, adjustments, manual overrides, and lineage. Minimise access\n   to personal, confidential, market-sensitive, or supervisory information.\n5. Reconcile totals to ledgers, source reports, statutory accounts, prior periods,\n   related returns, event records, and internal management information as applicable.\n   Investigate rather than force unexplained differences.\n6. Validate arithmetic, units, currencies, signs, formats, identifiers, dates,\n   cross-field rules, schema, rounding, thresholds, completeness, and reasonableness.\n7. Draft narrative explanations that match the data, distinguish estimates and\n   judgements, explain movements and exceptions, and remain consistent with other\n   regulatory, public, and financial statements.\n8. Record issues, interpretations, errors, late data, overrides, assumptions,\n   approvals, legal advice, and regulator correspondence. Escalate potential breach,\n   late filing, misstatement, or restatement promptly.\n9. Conduct independent review, management and signatory certification, portal dry\n   run, final lock, submission, receipt capture, regulator-query tracking, retention,\n   and correction or resubmission control.\n\n## Output\n\nProvide the obligations and deadline note, field-level data map, populated draft,\nreconciliations, validation report, exception and judgement log, approvals package,\nsubmission checklist, and post-filing evidence and query tracker.\n\n## Guardrails\n\nDo not guess missing values, suppress validation errors, reuse a stale taxonomy,\nalter source records, certify without authority, or submit on the user's behalf\nunless explicitly authorised. Preserve the exact filed version and receipt.\n"
}