The Compliance Ledgercomplianceledger.in
Feature 6 // Version Discipline

Changelog & Version History

Corporate AI practices and Indian jurisprudence evolve constantly. The Compliance Ledger adheres to a strict versioning discipline: every report modification, rubric expansion, and platform upgrade is catalogued transparently.

v1.1.0

Three-Tier Regulatory Classification & DPDPA Staged Commencement Accuracy

Introduced a dedicated 'Enacted, Not Yet in Force' classification tier alongside Binding and Voluntary categories, accurately reflecting DPDPA 2023's staged commencement timeline (Stage 3 substantive enforcement on May 13, 2027).

Itemized Changes:

  • →Evolved evaluation matrix from two columns to a three-tier system: (1) Binding Indian Law (In Force), (2) Enacted, Not Yet in Force (Staged Commencement), and (3) Voluntary Framework.
  • →Reclassified DPDPA Section 5 notice and profiling findings in Report IN-01 (Composite Lending) from 'Binding' to 'Enacted, Not Yet in Force' with blue styling and commencement metadata (Stage 3: May 13, 2027).
  • →Added commencementDate and enactedDate fields to report schema and Finding component, distinguishing impending legislative obligations from present statutory penalty liabilities.
  • →Updated EngineOutput component to display five distinct score chips including 'Enacted (2027)' gaps.
  • →Synchronized Guide (Chapter 04), About, Methodology, and FAQ sections with the three-tier classification and detailed staged commencement timeline of DPDPA 2023.
v1.0.1

TEC 57090:2025 Alignment & Report Evidentiary Grounding

Harmonized domestic AI incident taxonomy standard designation to gazette-notified TEC 57090:2025 across Guide and Report pages, and resolved evidentiary misattribution on digital lending underwriting and bias audit findings.

Itemized Changes:

  • →Updated statutory and technical references across the Comprehensive Guide and Composite Report to gazette-notified standard TEC 57090:2025 ('Standard for the Schema and Taxonomy of an AI Incident Database in Telecommunications and Critical Digital Infrastructure').
  • →Clarified statutory scope of TEC 57090:2025 as post-incident taxonomy and database schema, distinguishing it from proactive compliance auditing.
  • →Remapped Report IN-01 (Composite Lending) Source [2] from the mismatched telecom incident standard to the platform's authentic Product Interface & Instant Approval Disclosures (Archive v2.1) to accurately support the sub-180-second automated approval claim.
  • →Grounded Voluntary Pillar 1 (Algorithmic Bias Audit) finding in the platform's Technical Whitepaper / Engineering Monograph [Source 3], rectifying citation pointing at incident schemas.
  • →Updated Composite Lending Report version log to v1.1 reflecting evidentiary alignment.
v1.0.0

The Compliance Ledger Launch & Initial Benchmark Case

Official launch of The Compliance Ledger publication, implementing the SutraCheck gap-analysis rubric, public selection methodology, and the inaugural Composite Lending audit.

Itemized Changes:

  • →Launched complianceledger.in with Claude/Anthropic warm editorial design system.
  • →Published Feature 1: Selection Methodology governing sector risk prioritization (lending, hiring, healthcare, ed-tech).
  • →Integrated Feature 2: SutraCheck Classifier Engine raw matrix terminal and evaluation pipeline.
  • →Implemented Feature 3: Template-enforced hedged evidentiary finding syntax ('no public evidence found...').
  • →Established Feature 4: 7-day Pre-publication Right of Reply workflow and formal response block.
  • →Launched Feature 5: Opt-In Review Track for forward-looking AI companies seeking third-party transparency validation.
  • →Released initial benchmark report: 'Composite — Automated Underwriting & Alternative Credit Scoring' (IN-01).
§

How Report Re-Audits Are Handled

When a previously evaluated entity updates its public privacy policy, institutes a designated algorithmic grievance mechanism, or publishes a model fairness report, we do not publish a detached new article.

Instead, we execute a re-audit against the current public record, record the findings as a dated version entry on the existing report page, and update the site-wide changelog. This ensures an immutable historical record of governance progress over time.