Current byline
Complied AI research desk
We use an organization byline for guides and automated update records. It identifies who publishes and maintains the page without implying that a named professional reviewed it.
We add an individual author or reviewer only when their identity, role, credentials, contribution, profile details, and approval have been verified. If a page does not show a named reviewer with a linked profile, it has not been presented as independently reviewed by that person.
Source hierarchy
The official record is the verification endpoint.
Primary
Regulator, ministry, exchange, gazette, India Code, or another official publication.
Complied AI layer
Captured text, navigation, summaries, structured facts, and links back to the primary record.
Reader decision
Verify the current official document and obtain professional advice where facts or consequences matter.
Statutory updates
How an update becomes a readable brief
Capture the record
We retain the regulator or exchange title, publication date, captured text, and official page or document link as the source layer.
Prepare readable text
Automated cleanup may improve layout and Markdown without replacing the original record. If cleanup cannot be validated, the page keeps the captured source text or points back to the official document.
Build the brief
Automation may propose a plain-language title, summary, dates, affected parties, actions, thresholds, exceptions, and consequences from the validated text.
Validate or withhold
Structured facts require supporting text from the captured document. Unsupported metadata, dates, or evidence cause the brief to be withheld rather than displayed as completed.
Research guides
What “source checked” and “verified” mean
Each guide lists the official sources used and a last-verified date. Those labels record the source position checked for that publication; they do not promise that the law has remained unchanged after that date.
Automation, including AI, may assist research, drafting, extraction, and structure. The reason for using it is practical: compliance material is dispersed and repetitive, while readers need the operative date, scope, and official record quickly. Automation is not used to manufacture expertise or replace the cited source.
Corrections policy
Report the exact record, claim, or date that needs attention.
Use the site's “Raise issue” control or the contact page. Include the Complied AI URL, the disputed text, and the official source that supports the correction. We review the source relationship first and update or withhold the affected interpretation when the record does not support it.
Publication and modification dates remain part of article metadata. We do not treat a correction request, automated output, or third-party summary as authority over an official record.