About & Governance

About & Governance

A framework should govern its own development.

Culture Key is an independent public framework for human governance of AI systems. Its purpose is not to promise perfect control. It is to make the conditions for legitimate human oversight visible, testable and open to challenge.

The work is public because claims about governance deserve examination. The framework, its status and its development process should not become a black box of their own.

Why Culture Key exists

AI governance should be understandable before it becomes urgent.

As systems gain the ability to recommend, decide, communicate, coordinate or act, the important questions are not only technical. They concern power, accountability, consent, intervention and the people who must live with outcomes.

Culture Key translates those questions into a shared language: one that can be useful to a citizen trying to understand a system, a team building one or an organisation responsible for its use.

The aim is not to replace judgment with a framework. The aim is to make responsible judgment more possible, more visible and harder to avoid.

How to read the work

Status matters.

Not every idea has the same standing. Culture Key makes this explicit so readers can distinguish what is active, what is developing and what remains exploratory.

ACTIVE

Framework

Current public principles, functions and process components that form the operative framework.

PROPOSED / UNDER REVIEW

Developing material

Material being assessed, refined or challenged before it becomes part of the active framework.

RESEARCH / EXPLORATION

Open inquiry

Questions, observations and experiments that may inform the framework without yet defining it.

ARCHIVED

Historical record

Earlier versions or superseded material retained so that change remains traceable rather than invisible.

How change happens

Development is a governed process.

A framework that asks others to document decisions should be able to show how it changes itself.

01Propose

Identify a question, gap, risk, experience or new evidence.

02Examine

Test assumptions, limits, consequences and relationship to existing principles.

03Decide

Accept, revise, defer or reject the change with a clear status.

04Publish & review

Make the current version, reasoning and future review possible to trace.

Public, but bounded

Openness needs boundaries too.

What is public

The active framework, core concepts, status information, version history, applications, sources and the public documentation that supports scrutiny.

What is not automatically public

Unreviewed internal working material, sensitive implementation details, security-relevant operational information and personal or confidential data.

Why the distinction matters

Transparency is not indiscriminate exposure. Responsible openness makes meaningful accountability possible without creating avoidable harm or false certainty.

How to challenge the work

Read the canonical documentation, distinguish fact from inference, check the stated status and bring specific evidence or questions to the point of disagreement.

Limitations are part of governance.

Culture Key is not a legal opinion, an automated assurance system, a certification mark or a guarantee that an AI system will be safe.

It is a framework for examining whether human governance capacity is real: whether authority is legitimate, accountability is assigned, intervention works and repair remains possible.

Identity is a claim. Practice is evidence. Contradiction is the test.

The framework itself should be held to this standard. Its public record exists so that its claims can be examined against its development and use.

Keep the source visible.

The public repository is the canonical documentation and version record for Culture Key. The website is the human entry point: a place to understand the work, learn the questions and see them applied.