HUB_Optimus

HUB_Optimus — Custodianship

Purpose

Custodianship exists to protect the Kernel and the integrity of governance. It is not ownership, not authority over outcomes, and not a certification body.

Custodians protect:

What Custodianship is

Custodianship is a constrained governance role that:

What Custodianship is not

Custodianship is not:

Scope of powers (strictly limited)

Custodians MAY:

Custodians MUST NOT:

Kernel change rule (high bar)

Any Kernel change requires: 1) an explicit written proposal, 2) a rationale referencing Kernel principles, 3) documented objections and responses, 4) consensus review per CONSENSUS_PROCESS.md, 5) custodianship approval, 6) synchronization across all language mirrors.

Unreviewed Kernel edits are invalid by definition.

Conflict of interest and anti-capture

Custodians must disclose conflicts of interest. Capture indicators include:

If capture indicators appear, Custodians must block the change and document why.

Transparency and record

All custodian actions must be traceable:

Removal / rotation (minimum rule)

If a Custodian repeatedly violates the Kernel, hides conflicts, or acts deceptively, they lose custodianship status through the same consensus process.

Non-sovereign statement

Custodianship does not create authority over participants or institutions. It only protects the integrity and clarity of the HUB_Optimus system definition.