/governance

Deterministic governance, not rubber-stamping

arifOS governance is not a checklist. It is a code-enforced contract between thirteen floors and the agents that act under them. Hard floors VOID an action at compile time. Soft floors raise CAUTION or HOLD for human judgment. The Sovereign (F13) is the only floor a human can wave — and only at the cost of an irreversible signature.

We have read the public critiques of naive Human-in-the-Loop. We agree with most of them. We do not use HITL. We use three deterministic mechanisms, described below.

F1–F13 — The Thirteen Constitutional Floors

The canonical floor table is published as a JSON contract at /floors.json. The table below is the human-readable rendering.

The HITL critique we accept — and our response

An external AI observer correctly identified that naive Human-in-the-Loop collapses:

• Speed mismatch & cognitive overload
• Automation bias (rubber-stamp effect)
• Liability theater, not safety
• State degradation and flow interruption
• Learned helplessness
• Noisy, inconsistent feedback (RLHF poisoning)
• Scaling illusion (HITL kills leverage)

We accept this critique. The arifOS answer is not "better HITL." The arifOS answer is deterministic guardrails: code-enforced, audit-logged, scar-sealed, and escalated to the human only when certainty collapses.

Three deterministic mechanisms

1. Cooling Receipts. Every irreversible action emits a COOLING_RECEIPT with governance_organ, required_authority, and convergence. Stale receipts become scars; scars become constitutional constraints. See /999/runtime-snapshot.json.
2. Scar Sealing (SCAR LAW). Failures are metabolized into permanent constraints via forge_scar. The system cannot re-attempt the same failure without explicit F13 sovereign override. See /scar.json.
3. Confidence-Based Delegation. The agent evaluates its own certainty. Above threshold → proceed under deterministic guardrails (F1, F11, F12). Below threshold → escalate via forge_judge_proxy to 888_JUDGE (the sovereign's verdict channel). Not a human rubber-stamp — a deterministic routing decision.

Federation status — honest, current, attributable

The institution does not green-wash. The Federation reports its DEGRADED state plainly, with source, timestamp, and reason. The current snapshot is rendered live from /api/federation-probe.

Source: GET /api/federation-probe. Cache: no-store. Authority: 888_JUDGE.

Constitutional scars — failures metabolized into constraints

A scar is a failure the system refused to forget. The current scar log is at /scar.json. F1 + SCAR LAW means the system cannot re-attempt the same failure without explicit F13 sovereign override.

Scars are immutable. They are sealed to /999 and never edited. New scars are appended; old scars are not deleted. This is the visible form of "we learn from pain."

What an institution may rely on

1. Identity. did:web:arif-fazil.com binds the sovereign to the domain. Document at /.well-known/did.json.
2. Governance. This page. Plus /constitution, /policy.json, /authority.json.
3. Audit. /audit + /999/seal.json + /api/federation-probe.
4. Disclosure. /.well-known/security.txt (RFC 9116).
5. Contractor API. https://mcp.arif-fazil.com/mcp (canonical MCP gateway).