KLM · Candidate standard

A common language
for the basis of an answer.

The Knowledge Layers Model develops a shared vocabulary for recording the declared basis of AI outputs. NAGE operates the reference implementation.

Cumulative requirements

A record grows. Its obligations grow with it.

Select a level to see what it adds. Earlier requirements stay in view.

Candidate standard / cumulative requirementsPublic charter ↗
Cumulative structure

Each level retains the requirements before it.

01 / 06 groups
Requirement map1 / 6 levels visible
00
Records and explicit unknowns

Structure · status · explicit unknowns

ADDED
01
Inputs and events

Source identity · model version · trace

ADDED
02
Evidence and execution links

Claim ↔ evidence · procedure ↔ execution

ADDED
03
Declared/grounded gap and governance traces

Declared/grounded distinction · policy provenance

ADDED
04
Traceable causes

Generative basis · governed attribution

ADDED
05
Independent checking

Independent checks · declared scope

ADDED
Illustrative requirement view

Declared

Required structure and epistemic statuses remain visible, including information that is unavailable.

These are requirement groups, not a certificate for this example.Examine a record check →

Level descriptions follow the supplied conference whitepaper. The public repository is at charter stage; a signature alone does not demonstrate KLM-5 conformance. This is not an automated conformance validator.

Reading guide

Six cumulative levels.

LevelNameReading guide
KLM 0DeclaredThe output has a stated basis.
KLM 1TraceableThe record adds trace information.
KLM 2GroundedGrounding information becomes inspectable.
KLM 3ReflectiveSignals about the output and its basis are disclosed.
KLM 4AttributableAttribution information has an explicit record role.
KLM 5VerifiableSpecified record properties can be checked.

This is a navigational summary of the cumulative level names, not a substitute for the conformance requirements in the supplied specification.

Interpretation boundaries

Three distinctions worth preserving.

01

Source presence and evidential support

A named source does not prove it supports a particular statement.

02

Integrity and truth

A valid signed record may still describe an incorrect answer.

03

Declaration and execution

A record of declared participation is not cryptographic proof of the computation actually performed.