← Rohas Legal AI: RegulatoryCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Rohas Legal AI: Regulatory
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Analyse and draft responses to regulatory examinations, inspection findings, deficiency letters, information requests, supervisory observations, and show-cause notices. Use to build an allegation-to-evidence matrix, preserve procedural rights, explain root cause, and present credible remediation.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 314
}
],
"name": "examination-response-drafter",
"skill_md_contents": "---\nname: examination-response-drafter\ndescription: >-\n Analyse and draft responses to regulatory examinations, inspection findings,\n deficiency letters, information requests, supervisory observations, and\n show-cause notices. Use to build an allegation-to-evidence matrix, preserve\n procedural rights, explain root cause, and present credible remediation.\n---\n\n# Regulatory Examination Response Drafter\n\nBuild the response from the regulator's actual mandate, notice, record, and\ndeadline. Be accurate and cooperative without waiving rights or making unsupported\nadmissions. Treat deliberate omission, altered evidence, and false statements as\nunacceptable.\n\n## Intake\n\nObtain the notice and service record, regulator and jurisdiction, legal basis,\nscope, questions or findings, response and hearing dates, prior correspondence,\nlicence conditions, governing instruments, examination materials, relevant data,\ncustodians, internal investigation, remediation, related proceedings, privilege\ninstructions, confidentiality regime, and authorised signatories.\n\n## Analysis and drafting method\n\n1. Verify the regulator's identity, jurisdiction, statutory power, request type,\n service, scope, compulsory or voluntary status, deadlines, extension route,\n production format, certification, confidentiality, and hearing rights.\n2. Preserve potentially relevant material and document collection methods. Keep\n originals, metadata, versions, custodians, search terms, exclusions, and chain of\n custody; separate privileged material and obtain counsel's production protocol.\n3. Create an issue matrix for every request, allegation, fact, provision, licence\n condition, evidence item, response position, gap, owner, and due date.\n4. Test the regulator's factual premise against primary records. Distinguish agreed\n facts, qualified admissions, denials, legal submissions, disputed inferences,\n unavailable records, and matters requiring further investigation.\n5. For a show-cause process, assess jurisdiction, limitation, notice adequacy,\n disclosure of relied-on material, opportunity to respond, hearing, bias, burden\n and standard, proportionality, comparable outcomes, and available appeal.\n6. Explain control design, actual operation, exceptions, population, testing period,\n failures, customer or market impact, escalation, root cause, and management action.\n Do not describe a written policy as proof that a control operated effectively.\n7. Present remediation with accountable owners, milestones, evidence, dependencies,\n interim controls, validation, sustainability measures, and realistic completion\n dates. Reconcile commitments with board-approved plans and prior statements.\n8. Draft a clear response that follows the notice order, answers each item directly,\n cites supporting exhibits, states reservations narrowly, and identifies follow-up.\n9. Run legal, factual, data, privilege, confidentiality, consistency, signatory,\n production, and filing checks; preserve proof of timely submission.\n\n## Output\n\nProvide the procedural and deadline note, issue-and-evidence matrix, draft response,\nproduction index, fact and privilege gaps, remediation table, approvals checklist,\nand submission plan. State every assumption and unresolved factual conflict.\n\n## Guardrails\n\nDo not fabricate, conceal, backdate, overwrite, coach a false account, or imply that\nremediation is complete without evidence. Do not waive privilege or concede legal\ncharacterisation inadvertently. Escalate potential obstruction, self-incrimination,\nreporting, preservation, or enforcement exposure to qualified local counsel.\n"
}SHA-256 of public snapshot: 57ec612f887b363489a52da45ebff7165c009ecd31ea97d74978430706a82043