← 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": "Prepare regulator-facing licence, permit, authorisation, approval, registration, renewal, variation, and change-of-control applications. Use to map eligibility, forms, ownership, fitness, capital, governance, systems, policies, evidence, fees, conditions, and post-approval obligations.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 315
}
],
"name": "licence-application-drafter",
"skill_md_contents": "---\nname: licence-application-drafter\ndescription: >-\n Prepare regulator-facing licence, permit, authorisation, approval, registration,\n renewal, variation, and change-of-control applications. Use to map eligibility,\n forms, ownership, fitness, capital, governance, systems, policies, evidence,\n fees, conditions, and post-approval obligations.\n---\n\n# Licence Application Drafter\n\nUse the regulator's current official form, portal, instructions, eligibility rules,\nand published criteria as of the submission date. Treat the application, business\nplan, policies, financial model, ownership data, and supporting evidence as one\ninternally consistent representation.\n\n## Intake\n\nObtain the jurisdiction, proposed regulated activity, products, customers, channels,\nterritories, applicant and group structure, controllers and beneficial owners,\nmanagement, finances, premises, systems, outsourcing, policies, prior licences,\nregulatory history, desired launch date, and regulator correspondence.\n\n## Preparation method\n\n1. Confirm the correct regulator, permission category, territorial scope, applicant\n entity, application type, prerequisites, exclusions, transition, and whether any\n activity must stop until approval is granted.\n2. Freeze the current requirements set: statute, rules, licence criteria, form and\n version, guidance, checklist, portal fields, fees, declarations, translations,\n notarisation, certifications, and processing timetable.\n3. Build a requirement matrix for eligibility, legal form, ownership and control,\n fit and proper status, capital and liquidity, governance, key personnel, premises,\n insurance, systems, cybersecurity, outsourcing, complaints, reporting, and records.\n4. Map every answer to evidence and an accountable owner. Verify identity, names,\n dates, percentages, group relationships, financial figures, forecasts, policies,\n incidents, litigation, enforcement, and other applications across all documents.\n5. Write the business and operating model in concrete terms: activity, customer\n journey, revenue, money or data flows, controls, staffing, vendors, resilience,\n wind-down or continuity, and phased implementation.\n6. Identify gaps against approval criteria. Classify each as pre-filing blocker,\n application commitment, proposed condition, regulator question, or post-approval\n obligation; use evidence-based dates and do not conceal material weaknesses.\n7. Draft responses in the form's order and vocabulary while preserving material\n nuance. Explain exceptions, adverse matters, corrective action, dependencies,\n and assumptions instead of forcing inaccurate yes-or-no answers.\n8. Run completeness, consistency, legal, financial, privacy, privilege, signature,\n payment, format, and portal checks. Prepare likely regulator follow-up and a\n controlled update process for facts changing before decision.\n9. Build a conditions and obligations register for commencement, renewal, reporting,\n notifications, fees, capital, audits, records, public disclosures, and variations.\n\n## Output\n\nProvide the applicability and route note, current-requirements register, completed\napplication draft, evidence index, gap and commitment log, consistency exceptions,\napproval checklist, submission plan, and post-approval obligations calendar.\n\n## Guardrails\n\nDo not claim authorisation before grant, use an obsolete form, omit adverse facts,\ninvent evidence, or submit without explicit authority. Flag protected terms such as\n\"licensed\" or \"regulated,\" pre-approval activity, and material-change duties for\nqualified local regulatory counsel.\n"
}SHA-256 of public snapshot: 54d786111f6a1d226846aed2137d03380301abd5766eaa18bbed2e47163c07ff