Establishing WEKID-STD-001 as the Normative WEKID Open Standard

Abstract

WEKID has reached the point where its normative framework should no longer be carried primarily by a document titled a whitepaper. This RFC proposes a publication transition: establish WEKID-STD-001 v1.0, “WEKID Open Standard for Epistemic Maturity and AI Decision Authority,” as the authoritative normative specification of the framework, while retaining the WEKID Master Whitepaper v1.3 as its foundational, explanatory, and historical source.

The proposed Standard does not intentionally redesign the framework. It extracts and formalizes the normative core already embodied in Master Whitepaper v1.3: the Epistemic Maturity Model, the Trust Bridge, the AI Decision Authority Model, the AL-0 through AL-4 authority structure, hierarchical gating, conservative authority resolution, calibration boundaries, auditability, and related invariants. If accepted, this RFC authorizes publication of WEKID-STD-001 v1.0 and establishes numbered Standards as the future destination for Standards-Track changes.

Evidence base

The primary evidence for this RFC is the WEKID framework and governance record itself. Master Whitepaper v1.3 contains the current integrated framework baseline, including the two-model architecture, Trust Bridge, Experience layer, overseer-engagement concepts, authority levels, gating logic, calibration model, audit requirements, and governance cycle. The existing RFC register provides provenance for contributions incorporated into that baseline.

The proposed WEKID-STD-001 v1.0 draft is the principal standards artifact for review under this RFC. Reviewers should evaluate it against Master Whitepaper v1.3 for fidelity: the question for v1.0 is primarily whether the draft accurately extracts and formalizes the existing normative Core, not whether it introduces a new theory of WEKID.

Companion research, including Dynamic Epistemic Authority, may be cited as informative context but is intentionally outside the proposed normative v1.0 baseline unless separately adopted through a Standards-Track RFC.

Where this proposal stands

• Proposed · 2026-09-05 18:16:34
  Submitted by Jim Judge
• Triaged · 2026-09-05 18:17:30
• Working-group review · 2026-09-05 18:17:41
• Public comment · 2026-09-05 18:23:04
• Council decision · 2026-09-05 18:23:19
• Versioned release · 2026-09-05 18:23:49