Methodology · v1.1

SCEISEBI Enforcement Record (IN)

SEBI (Securities and Exchange Board of India) + CCI (Competition Commission of India) enforcement actions against {legal_name} in last 5y. NEGATIVE-SIGNAL (higher = cleaner record). CRITICAL OUTPUT RULE: "no enforcement found" is a GOOD outcome (clean record), NOT missing data. If after searching sebi.gov.in + cci.gov.in you find NO action in 5y, you MUST return enumerated_events with events=[] (empty array) → server scores 95 (clean). NEVER return type="absent" — absent wrongly maps to insufficient and discards a clean-record signal. EXTRACTION RULES: Cite sebi.gov.in (orders / adjudication / settlement orders) + cci.gov.in (orders under section 27). EXCLUDE merger (combination) approvals without penalties. Each event needs an official URL + date + severity. CLEAN-RECORD REASONING (MANDATORY to publish the clean 95): when you return events=[], your reasoning text MUST explicitly state ALL THREE of: (a) the official regulator source(s) you searched, named by hostname (the regulator hostnames cited above); (b) the explicit time window searched, written as "last 5 years / 60 months"; (c) an explicit negation: "no enforcement action against this specific company was found in that window". A bare events=[] WITHOUT this three-part affirmation is treated as an INCOMPLETE search (not a verified clean record): the server bails it for retry and it will NOT score 95. Server event_count_inverse.