You want to examine the evidence.

Research, architecture, governance, critical assessment: sources and their scopes are directly accessible here.

Sources and reading context

Reading guide to TENIR pages and demonstrations. Detailed sources are identified on each linked resource.

Simplified public rendering, read on 19 October 2026. KB3: enacted, active doctrinal rendering line. It renders meaning; it is not the code, and not a constitution. KB2: prior rendering line. This site certifies no implementation. Read the detailed status →

You may already have the questions you need. Go straight to the texts, examine gaps and locate the cited identifiers.

Framework, standard, software and demonstration are distinct objects. Their status matters when reading the evidence.

Start with the sources’ status

Published maturity and limits.

Questions you might have

Where are the requirements and code?

The Standard page presents REG. The repository map distinguishes implementations, schemas and laboratory harnesses. The architecture provides a reading guide.

Go to the REG requirements →Reference text

What do the published tests demonstrate?

The Conformance page explains scopes and limits. A laboratory or prototype result does not alone constitute certification or a general production guarantee.

Examine a sourced example too →From text to case

How do I cite or discuss a definition?

Publications and Contact provide references and their discrepancies. For software, identifying the repository, commit and file locates the exact claim being examined.

Discuss a source with Abdelaziz →Conversation

Go straight to the sources

REG standardRequirements and document status.Conformance and evidenceWhat was tested and within which scope.Repository mapCode, schemas and harnesses.PublicationsTexts and identifiers.Origin and conceptsVocabulary and reading context.

Your situation does not fit these examples?

Describe it in your own words →