Resources Library / Foundational questions

WEKID™ explained

Ten Foundational Questions

A guided introduction to the WEKID framework, its intellectual roots, and the way evidence becomes a governed boundary on AI action.

Foundational concepts

Question 01

What is WEKID.org and what core problem does it solve?

WEKID.org publishes an AI governance framework that evaluates the maturity of an AI output’s supporting knowledge and governs how much decision authority the system may receive.

The problem is the gap between a convincing AI response and justified authority over a real decision. Factual accuracy or fluent language alone does not show that an output is fit for the context, safe to apply, or permitted to drive an autonomous action. Model One evaluates evidence across five epistemic layers. The Trust Bridge derives a ceiling on delegation from that assessment. Model Two applies consequence, reversibility, policy, and human accountability to resolve what may happen next. An organization enforces that result in its own workflow.

Source and further readingWhat is WEKID?The two-model framework

Question 02

What does the acronym WEKID stand for?

Wisdom · Experience · Knowledge · Information · Data.

The name reads from Wisdom down to Data. The Epistemic Maturity Model evaluates the supporting evidence from Data upward:

  • Data: faithful facts, measurements, and sources.
  • Information: data made relevant and meaningful through context.
  • Knowledge: sound interpretation and organized understanding.
  • Experience: demonstrated ability to apply that understanding in practice, including edge cases and recovery.
  • Wisdom: calibrated judgment about uncertainty, risk, limits, and consequence.

A strong upper-layer claim cannot repair a fatal failure in the evidence beneath it.

Question 03

Who created the WEKID framework and when was it first used?

James M. Judge (Jim Judge) created WEKID in 2007 while developing CompetitiveJuice™, a mobile human-based competitive intelligence service.

The initial hierarchy evaluated the maturity and value of human intelligence across five layers. Judge later extended it to AI-generated knowledge and added the distinct Decision Authority Model and Trust Bridge. His 2025 Foundational Whitepaper describes the modern framework. The 2007 date marks its origin, rather than the release date of the present normative standards.

Question 04

What other thought leaders and schools of thought influenced the development of WEKID?

Judge identifies these ideas as intellectual foundations of WEKID as it stands today. They inform different parts of the framework; none should be collapsed into a single theory of authority.

  • Epistemology: Plato and Aristotle help frame how knowledge is distinguished through truth, belief and justification.
  • Knowledge ontology: Russell Ackoff’s data-to-wisdom hierarchy includes Understanding. WEKID develops Experience as understanding applied in a domain and tested against outcomes.
  • Power and authority: Max Weber distinguishes the exercise of power from authority grounded in legitimacy.
  • Epistemic authority: Linda Zagzebski argues that rational deference to an epistemic authority can coexist with epistemic autonomy. That concerns authority in belief, rather than permission for AI to act.
  • Decision science: Cassie Kozyrkov emphasizes an objective-first approach to defining the decision, default, and criteria before choosing data or an AI model.
  • Social engineering: Kevin Mitnick’s wrote The Art of Deception with William L. Simon, to describe how attackers exploit trust and apparent authority, and that information security is only as strong as the people trusted with it.
  • Prediction Machines: Ajay Agrawal, Joshua Gans, and Avi Goldfarb explain the falling cost of prediction and the continuing value of its complement, human judgment is an important economic dial in AI economics.

Framework mechanics

Question 05

What is the difference between the Epistemic Maturity Model One and the AI Decision Authority Model Two?

Model One asks what the evidence supports. Model Two asks what the AI may decide or do in a specific setting.

Model One evaluates Data, Information, Knowledge, Experience, and Wisdom with layer-specific evidence and gates. The Trust Bridge turns the assessment into the highest level of AI delegation that the demonstrated maturity supports, up to AL-3. Model Two applies the consequences of the proposed action, reversibility, standing human reservations, and enterprise policy. It resolves the final Authority Level and its permitted scope. A maturity score by itself does not authorize an action.

Question 06

What are the Five Authority Levels (AL-0 to AL-4) in the WEKID Stack?

Each level states what may happen to a particular output or proposed action. AL-4 reserves a decision for an accountable human; AI autonomy peaks at AL-3.

LevelDeterminationOperational meaning
AL-0No AuthorityInformational only, or rejected by a gate. No decision or downstream automation may rely on it.
AL-1Constrained AuthorityOnly approved, reversible, impact-capped actions within predefined bounds.
AL-2Supervised AuthorityAI proposes or stages; a human reviews and releases each consequential action.
AL-3Augmented AuthorityAutonomous execution within assigned scope, with monitoring, limits, audit, and rollback.
AL-4Human AuthorityThe decision is withheld from delegation; AI can support an accountable human’s decision.

Question 07

What is the function of the “Trust Bridge” in the framework?

The Trust Bridge converts demonstrated epistemic maturity into a ceiling on AI delegation. It does not grant permission.

It receives Model One’s five layer assessments, evidence provenance, and gate outcomes. It emits the maximum AI delegation supported by those facts, from AL-0 through AL-3. A missing or invalid assessment does not earn delegation. Model Two then applies the decision’s consequences and policy; the host system enforces the resolved result. AL-4 is a human reservation based on the stakes or policy, not an outcome that maturity can produce.

Practical application & implementation

Question 08

How does an organization begin implementing the WEKID system?

Start with one consequential workflow and define the decision boundary before connecting an enforcement point.

  1. List the proposed actions, owners, consequences, reversibility, and decisions reserved to humans.
  2. Choose a sector calibration profile and define measurable, traceable evidence for all five WEKID layers.
  3. Implement assessment, hard gates, the maturity ceiling, Model Two policy, and an action gateway that checks the result before a consequential write.
  4. Run in shadow mode; test missing evidence, policy conflicts, overrides, and failures before enforcing grants.
  5. Track decisions and outcomes, review drift, and renew or reduce authority as evidence changes.

This is a practical adoption sequence drawn from the framework and enterprise blueprint, rather than a required order of operations or a claim that one packaged product provides every component.

Question 09

What are the core technical artifacts involved in a WEKID deployment?

A deployment needs versioned rules, verifiable evidence, a resolved authority decision, and proof that the host enforced it.

  • Evaluation record: layer scores, source provenance, observed signals, and gates.
  • Calibration and policy: thresholds, risk rules, human reservations, version identifiers, and optional control mappings such as NIST SP 800-53.
  • Authority decision payload: maturity ceiling, final AL, permitted scope and bounds, expiry, binding determinant, and rationale.
  • Gateway and audit record: execution, staging, escalation, or denial, tied to the proposed action, outcome, and reviewer where applicable.

These are reference categories for an implementation, not prescribed filenames or a published wire schema. A compliance mapping can connect local evidence to a control catalogue; it is not an authority grant.

Question 10

How does WEKID integrate with existing agentic AI workflows?

Place governance between an agent’s proposed consequential action and the tool that can execute it.

The agent supplies its proposed action, evidence, and operational context. Model One evaluates the evidence, the Trust Bridge sets the maturity ceiling, and Model Two resolves authority for that decision under policy. The agent host or workflow gateway validates the result before it executes, stages, escalates, or denies the action. It records both the decision and the actual outcome so later assessments can learn from observed results. The host retains ownership of the tools and transactions; planning, retrieval, and conversation do not bypass the mandatory enforcement point.

Back to top ↑