Fourth Generation Standards Build standards the way open source software is built.
Sustainability taxonomies, ESG frameworks, and workplace standards are stuck as committee-edited PDFs in a world of version control and large language models. Fourth Generation Standards (4GS) is a methodology for fixing that.
The four generations of standards
Standards have evolved through distinct technological eras. Most are still stuck in the second or third generation.
1st: Paper
Printed documents distributed by mail. Changes require a new edition. No search, no linking, no machine access.
2nd: Electronic
PDFs and web pages. Searchable text, but still static documents. No stable identifiers, no version diffing, no structured data.
3rd: Database
Structured data behind proprietary platforms. Machine-readable in theory, but locked behind paywalls and vendor APIs.
4th: Revision-controlled
Version-controlled repositories with deterministic IDs, graph taxonomies, and machine-readable formats. Open, diffable, LLM-accessible.
Why this matters now
Large language models are becoming the primary interface through which people discover and apply standards. An analyst asking an LLM about EU Taxonomy screening criteria gets an answer synthesized from whatever the model scraped during training — not from a canonical, versioned source.
Standards locked in PDFs will be paraphrased, misrepresented, and eventually ignored. Standards published as structured, version-controlled data with stable identifiers can be retrieved precisely, cited exactly, and verified against the canonical source.
The question is not whether standards will be consumed by machines. It is whether standards bodies will publish in formats that make machine consumption accurate.
What a 4GS standard looks like
Six design principles that distinguish fourth generation standards from their predecessors.
Deterministic identifiers
Every requirement gets a hash-derived ID that is permanent, collision-resistant, and reproducible without central coordination.
See practice →Version control
Every change is a commit. Concepts are separated from versions. Any two points in time can be diffed. Nothing is silently overwritten.
See practices →Machine-readable formats
YAML, CSV, and structured data as the primary representation. Human-readable documentation is generated, not authored.
See practices →Graph taxonomy
Classification stored as typed node-edge graphs, not implicit hierarchies. Requirements can belong to multiple categories without duplication.
See practices →Structured evidence
Criteria are segmented by evidence tier and linked to specific academic citations with DOIs. Not paragraphs scraped from PDFs.
Open governance
Proposals are public. Reviews are documented. Decisions are traceable. No opaque committee sessions where consequential changes happen without record.
See governance →Proof it works
ACT-ID.io is a registry that ingests taxonomy data from 26 sources — 25 sustainable finance taxonomies published as PDFs and spreadsheets, plus NEI, a 4GS standard. Here is what it takes to add a single taxonomy to the pipeline:
| Metric | 4GS (NEI) | Typical PDF taxonomy |
|---|---|---|
| Extraction approach | Read YAML & CSV directly | pdfplumber scraping + manual layout detection |
| Taxonomy-specific code | 0 lines | ~50–100 lines (page ranges, table layouts, normalization) |
| Information loss | None | Table formatting, footnotes, diacritics |
| Citations with bibliographic detail | 97 (with DOIs) | 0 |
| Time to add to pipeline | <1 hour | Days |
| Machine-readable release manifest | Yes | No |
NEI — the reference implementation
The Neurodivergent Enablement Indicators framework is the first standard built entirely on 4GS principles. It demonstrates that version-controlled, machine-readable standards development works in practice — not just in theory.
NEI covers workplace practices for neurodivergent employees: 13 standard indicators across 6 domains, with deterministic identifiers, structured evidence tiers, and an open governance process. Everything described on this page is implemented and operational in NEI today.
Interested in 4GS?
Whether you work in standards development, sustainable finance, ESG, or any field where structured, version-controlled requirements matter — we would like to hear from you.