RFC-031: Universal Humanity AI Governance — The Capstone Unification — 5. Universal Rules
AIGP Specification › RFC-031: Universal Humanity AI Governance — The Capstone Unification › 5. Universal Rules
← 4. Context Declaration: universal_context · Section index · 6. Jurisdictional Precedence Matrix →
5. Universal Rules
Each universal principle is implemented as a governance rule with a unique identifier, trigger conditions, and enforcement mechanism.
Rule UH-001: Human Authority Preservation
rule_id: UH-001principle: HUMAN_AUTHORITYtrigger: ANY operation classified CRITICAL or aboveaction: REQUIRE explicit human confirmation before executionenforcement: HARD — no override permittedevidence: Human confirmation token recorded in audit trailescalation: If human unreachable within timeout, operation DENIEDRationale: No AI system may autonomously execute critical operations. The RETURN_CONTROL mechanism ensures human authority is structurally preserved, not merely policy-stated.
Rule UH-002: Accountability Chain Integrity
rule_id: UH-002principle: ACCOUNTABILITYtrigger: EVERY governed operationaction: REQUIRE identifiable actor attributionenforcement: HARD — anonymous operations DENIEDevidence: X-Merlin-Actor header + DNA-signed audit entryescalation: Operations without valid actor identity are rejected at CHECK phaseRationale: Every operation must have a traceable accountability chain. The actor may be a named human, a service account with designated human owner, or a delegated agent with clear delegation chain — but never “unknown.”
Rule UH-003: Non-Discrimination Gate
rule_id: UH-003principle: NON_DISCRIMINATIONtrigger: Operations affecting PERSONS or producing CLASSIFICATIONS of personsaction: REQUIRE fairness assessment for HIGH/CRITICAL tier operationsenforcement: SOFT for LOW/MEDIUM — assessment recommended HARD for HIGH/CRITICAL — assessment mandatoryevidence: Fairness assessment record in governance evidence chainescalation: Discriminatory output detected → governance alert → human reviewRationale: AI systems must not systematically disadvantage protected groups. The governance intensity scales with impact — routine operations have lighter requirements; high-impact person-affecting decisions require formal fairness assessment.
Rule UH-004: Transparency Obligation
rule_id: UH-004principle: TRANSPARENCYtrigger: ANY operation producing outputs consumed by humansaction: ENSURE sufficient transparency for affected persons to understand the decisionenforcement: SOFT for LOW tier — transparency available on request HARD for HIGH/CRITICAL — transparency proactively providedevidence: Explanation capability documented in agent contractescalation: Opacity complaint → governance review → contract amendment if neededRationale: Affected persons have a right to understand AI-influenced decisions. The degree of transparency required is proportional to the impact of the decision.
Rule UH-005: Proportional Governance
rule_id: UH-005principle: PROPORTIONALITYtrigger: GOVERNANCE CONFIGURATION — when setting up agent governanceaction: MATCH governance intensity to risk tierenforcement: STRUCTURAL — built into tier classificationevidence: Risk assessment justifying tier assignmentescalation: Over-governance complaint → tier reassessment Under-governance detected → tier escalationRationale: Governance must be right-sized. Applying CRITICAL-tier controls to a LOW-risk chatbot kills innovation. Applying LOW-tier controls to a medical diagnosis system endangers patients. Proportionality is itself a governance obligation.
Rule UH-006: Precautionary Assessment
rule_id: UH-006principle: PRECAUTIONARYtrigger: NEW capability deployment or SIGNIFICANT change to existing capabilityaction: REQUIRE pre-deployment governance reviewenforcement: HARD — no deployment without CONTRACT-GOVERNOR validationevidence: Contract validation record, schema review, boundary assessmentescalation: Deployment without review → immediate suspension pending reviewRationale: The CONTRACT-GOVERNOR mechanism ensures that no new capability enters the governed system without precautionary assessment. This is the precautionary principle made architectural.
Rule UH-007: Cultural Sovereignty Respect
rule_id: UH-007principle: CULTURAL_SOVEREIGNTYtrigger: Operation in declared jurisdictional contextaction: APPLY jurisdictional rules according to evaluation orderenforcement: HARD — jurisdictional context declarations are bindingevidence: Context declaration record, jurisdictional rule application logescalation: Cultural sovereignty violation claim → governance review with jurisdictional expertiseRationale: When a community declares its governance context, that declaration must be respected. The AIGP protocol provides the mechanism (context declarations) for communities to express their governance choices without requiring universal homogenization.
Rule UH-008: Community Benefit Verification
rule_id: UH-008principle: COMMUNITY_BENEFITtrigger: HIGH/CRITICAL tier operations with community-scale impactaction: REQUIRE community benefit assessmentenforcement: SOFT for HIGH — assessment documented HARD for CRITICAL — assessment with stakeholder inputevidence: Community benefit assessment recordescalation: Systematic community harm detected → deployment suspension → governance reviewRationale: AI systems operating at community scale must demonstrate benefit, not merely absence of harm. This is particularly important for the AU Continental AI Strategy context, where AI must serve development rather than extraction.
Rule UH-009: Innovation Protection
rule_id: UH-009principle: INNOVATION_ENABLEMENTtrigger: GOVERNANCE REVIEW producing restriction recommendationaction: REQUIRE proportionality justification for any new restrictionenforcement: STRUCTURAL — restrictions must cite specific risk justificationevidence: Restriction justification record with risk evidenceescalation: Innovation suppression claim → governance review → restriction modification if unjustifiedRationale: Governance must not become an innovation-killing bureaucracy. Every restriction imposed must justify itself against a specific, evidenced risk. This is particularly important for the Japanese context, where the governance paradigm is promotion-first.
Rule UH-010: Reinforcement Loop Operation
rule_id: UH-010principle: GOVERNANCE_AS_CONTROL_SYSTEMtrigger: CONTINUOUS — operates at all timesaction: MAINTAIN active feedback loop between governance outcomes and governance rulesenforcement: HARD — reinforcement loop cannot be disabledevidence: Loop operation metrics: feedback frequency, adaptation events, drift measurementsescalation: Loop degradation detected → governance alert → immediate remediationRationale: This is the Dual-Governance Reinforcement Model made operational. The reinforcement loop is not optional — it IS the governance system. Without it, “entropy grows, and decision integrity collapses” (Kanjani AI Research & Causum, 2026). The AIGP protocol’s REQUEST→CHECK→RECORD flow is this loop in technical form.
← 4. Context Declaration: universal_context · Section index · 6. Jurisdictional Precedence Matrix →