Open disclosure standard · Version 1.0

Fashion Data Transparency Standard

Eight testable requirements for fashion statistics that keep their source, measurement context, calculations and caveats attached.

Read the open specification Request a review

Purpose and boundary

A badge is not the evidence

LFDTS reviews one named public page or dataset version. It does not certify a company, product, sustainability claim, product safety practice or government compliance.

The linked registry record is the source of status. It identifies the exact scope, assessor, issue and expiry dates, machine-readable artifact and its SHA-256 digest. Copying an SVG cannot create a valid record.

Mandatory criteria

All eight checks must pass

  1. S1

    Source identity

    Every material external statistic names its publisher and links to a supporting source page or stable record.

  2. M1

    Measurement context

    Unit, period, geography and reference population or denominator stay attached to each statistic.

  3. C1

    Calculation provenance

    Publisher-derived values are labeled and include a reproducible formula or transformation note.

  4. C2

    Comparability warning

    Unlike metrics, windows or populations are not merged into a ranking without an explicit warning.

  5. A1

    Machine-readable access

    The reviewed material is available as CSV, JSON or another documented structured format.

  6. V1

    Version and canonical identity

    The page states a release date and version, exposes a canonical URL and names its matching artifact.

  7. G1

    Corrections and contact

    A public correction route exists, and material corrections update the version history.

  8. I1

    Evidence integrity

    The record stores review dates, evidence URLs and a SHA-256 digest of the reviewed artifact.

Verification workflow

From evidence to public record

  1. 01

    Submit

    Name the exact domain, canonical evidence page, dataset version and structured artifact.

  2. 02

    Review

    The assessor follows sources, checks all criteria and reproduces at least one derived value.

  3. 03

    Record

    A schema-valid JSON record captures scope, status, dates, reviewer and artifact digest.

  4. 04

    Monitor

    Status expires within 12 months and can be revoked when evidence or claims no longer match.

A followed backlink, payment, customer relationship or reciprocal promotion is not a verification requirement.

Public registry

Current records

Status-aware badge

The image follows the registry state

LFDTS v1.0 self-assessed

This founding record is deliberately labeled self-assessed. Only an independently reviewed record can display “verified”.

After a registry pull request is merged, embed the assigned endpoint and link the image to the matching canonical record. The status JSON can change to expired or revoked without replacing the embed code.

<a href="https://lunarness.com/pages/fashion-data-transparency-standard#record-lfdts-2026-0001">
  <img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fgokimedia%2Flunarness-fashion-data-observatory-2026%2Fmain%2Fstandard%2Fbadges%2Flunarness.com.json"
       alt="LFDTS v1.0 self-assessed">
</a>

Inspect the badge status JSON

Governance

Open, scoped and revocable

The specification, registry schema, records and history are public on GitHub. Requirement changes create a new standard version; corrections remain visible in repository history.

Organizations may implement the criteria without a badge. False scope, broken evidence, undisclosed conflicts or misleading certification language can trigger revocation.

Open a verification request View governance files