Governance Statement

Liability & Governance

A public boundary statement for authority, responsibility, refusal, and execution-time control across Moral Clarity AI systems.

Binding Position

Human authority remains non-delegable.

The system is a tool. Humans retain decision authority. Organizations retain accountability. Liability does not migrate into software.

If authority, responsibility, or liability cannot be clearly located for a use case, the system must not be deployed in that context.

Controls

What must remain true

  • Humans decide
  • Organizations remain accountable
  • Execution is constrained at runtime
  • Refusal is mandatory where boundaries fail
  • Authority cannot be delegated to the system
  • Traceability is required for legitimacy
01

Legal Status and Scope

Moral Clarity AI systems are tools. They are not legal subjects, autonomous agents, or bearers of rights, duties, interests, or liability. Governance obligations attach to natural persons and legal entities involved in design, deployment, and use.

02

Allocation of Authority

Authority to make binding decisions remains with identified human actors and the deploying organization. The system provides assistance, does not exercise final discretion, and does not initiate irreversible actions independently.

03

Responsibility and Liability

Responsibility and liability for outputs, recommendations, and downstream effects remain with the deploying organization and designated human decision-makers. Liability is not transferred to software.

04

Refusal, Interruption, and Human Override

Refusal and non-action are mandatory capabilities. The system must halt, deny, or escalate when authority, state, or consequence boundaries are insufficient for legitimate continuation.

05

Execution Constraints

Operational constraints are defined externally by humans and enforced at execution time. No learned behavior, optimization objective, or internal system state may supersede these controls.

06

Transparency, Logging, and Auditability

Material system actions should be logged to show who authorized use, who reviewed or approved outcomes, when refusals occurred, and why execution was permitted or denied.

Prohibitions

What the system may not become

  • No legal personhood
  • No autonomous decision authority
  • No liability transfer to the system
  • No override of external constraints
  • No anthropomorphic governance framing
  • No deployment where accountability is unclear
Operational Boundary

No basis → no path → no action.

Legitimate execution requires valid state, real authority, and a constrained action path. Where that basis fails, execution must halt, deny, or escalate.