Editorial methodology

How the knowledge base reaches a judgment.

The method separates canonical facts from operational evidence and editorial analysis. Every profile carries its formal status, evidence tier, confidence, reviewer role, verification date, and next review trigger.

Inclusion gate

Five conditions

01
Material role in identification, semantics, exchange, provenance, quality, policy, access, or ML use.
02
Stable canonical source and knowable current, draft, superseded, or deprecated status.
03
Distinct architectural role or a decision-changing alternative.
04
At least one canonical source for scope and formal status.
05
No proprietary product presented as equivalent to an open standard.

Evidence tiers

Claims inherit their weakest input.

E1: Canonical
Normative specification, steward registry, or official version history.
E2: Independent operational
Named adopter documentation, regulator evidence, or an independent implementation report.
E3: Steward-reported
Case study, integration list, or community implementation page.
E4: Knowledge-base analysis
Crosswalk, inferred limitation, or illustrative implementation.

An E1 + E4 assessment combines source-checked formal status with knowledge-base analysis; it does not turn that analysis into a publisher claim.

Maturity roll-up

Four scored dimensions

Stability

draft → released → stable recommendation

Adoption

unverified → named evidence → independent multi-site evidence

Implementability

documentation → schemas and guides → validators and conformance

Governance

unclear → named steward → active change and maintenance process

Established7–8 with stable status and independent adoption evidence.

Scaling4–6 or a mixed-status family.

Emerging0–3 or an explicitly incomplete draft.

Maintenance ledger

Source-checked, with currency disclosed.

Last verified: 13 July 2026
Intended cadence: 180 days Established · 90 Scaling · 60 Emerging
Immediate triggers: Release, status, deprecation, conformance, access, or source-link change
Stale rule: Maturity is muted after the due window; deprecated artifacts remain as tombstones
Workflow: Source-check → domain review → cross-review → dated revision note

Open the current review ledger