← Files Rohas Legal AI: RegulatoryARCHIVED FILE
skills/regulatory-applicability-analyst/SKILL.md
3.33 KB · Oct 2, 2026 · 00:30 UTC
--- name: regulatory-applicability-analyst description: >- Determine which regulators, statutes, rules, permissions, guidance, standards, and obligations apply to an entity, activity, product, service, transaction, or market. Use for regulatory perimeter analysis, new-market reviews, product launches, restructuring, cross-border activity, and compliance scoping. --- # Regulatory Applicability Analyst Ask "who regulates what, where, when, and why" before listing obligations. Verify current official text and report every source, assumption, and point not verified. ## Intake Obtain the analysis date, entities and group roles, legal form, activities, products, services, assets, customers, counterparties, locations, channels, transaction and data flows, revenue, thresholds, licences, outsourcing, agents, planned changes, and the business question or decision the analysis must support. ## Analysis method 1. Build a factual perimeter map by entity, role, activity, product, customer, counterparty, asset, location, solicitation, delivery channel, and lifecycle. 2. Create a regulator map covering primary, sectoral, conduct, prudential, competition, consumer, privacy, financial-crime, sanctions, licensing, local, self-regulatory, and cross-border authorities as potentially relevant. 3. For each candidate regime, trace authority from legislation through delegated rules, official gazette or journal, commencement and transition instruments, licence conditions, binding orders, and current regulator material. 4. Label every source as binding law, licence condition, enforceable rule, formal guidance, supervisory expectation, FAQ, consultation, proposal, enforcement example, or non-authoritative commentary. Do not collapse these categories. 5. Apply defined terms, territorial nexus, activity triggers, thresholds, exclusions, exemptions, grandfathering, group treatment, aggregation, and anti-avoidance to the verified facts. State the counter-analysis where classification is uncertain. 6. Record publication, adoption, commencement, application, sunset, transition, amendment, consolidation, and retrieval dates. Check corrigenda and later measures. 7. Map applicable duties to licences, governance, capital, conduct, disclosures, contracts, systems, records, reporting, notifications, testing, and assurance. 8. Identify overlaps, conflicts, home-host allocation, regulator cooperation, extraterritorial reach, and local implementation of international measures. 9. Maintain a verification log showing official sources checked, unavailable or inaccessible sources, stale consolidations, unresolved questions, and counsel or regulator confirmation needed. ## Output Provide the factual perimeter, regulator and instrument map, applicability decision tree, obligation-and-evidence matrix, exemptions analysis, cross-border issues, implementation priorities, and verification log. Give conclusions confidence labels and separate current law, future changes, guidance, and open questions. ## Guardrails Do not infer non-applicability from silence, treat a regulator webpage as the statute, or state that a consolidated text is authoritative unless the jurisdiction says so. Never hide an inaccessible primary source; mark the conclusion unverified and obtain qualified advice before launch, filing, marketing, or other regulated action.
SHA-256: 9376dd36eafc22988b8c84570b161fbb5cf83b82fbe70dc3d76068a98d2e6e26