care-reference

Provides reference documentation for the CARE enterprise AI governance framework.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Hamza-Haadi/disease-risk-classifier-hamza --skill care-reference-hamza-haadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: care-reference
Source: https://github.com/Hamza-Haadi/disease-risk-classifier-hamza/tree/main/.claude/skills/27-care-reference
Command: npx skills add https://github.com/Hamza-Haadi/disease-risk-classifier-hamza --skill care-reference-hamza-haadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams discussing enterprise AI governance lack a shared, authoritative reference for the CARE framework's concepts, making conversations about trust boundaries, accountability, and human-AI collaboration inconsistent and ungrounded. ## Core Features & Use Cases - Framework Reference: Distills the CARE (Collaborative Autonomous Reflective Enterprise) thesis, including the Dual Plane Model, Mirror Thesis, and Human-on-the-Loop governance pattern. - Competency & Principle Catalog: Documents six human competency categories and eight CARE principles for designing AI governance architectures. - Framework Mapping: Explains how CARE relates to EATP (trust chain protocol), COC (AI code generation), and the Kailash reference implementation. - Use Case: When drafting an AI governance policy, load this reference to correctly apply Human-on-the-Loop boundaries and accountability chains instead of defaulting to human-in-the-loop bottlenecks. ## Quick Start Explain how the CARE Dual Plane Model separates trust from execution and how it applies to our AI deployment governance.

Frequently Asked Questions about care-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the CARE framework for AI governance?▼

CARE (Collaborative Autonomous Reflective Enterprise) is a governance philosophy proposing a third path between human-in-the-loop bottlenecks and human-out-of-the-loop accountability loss. It separates trust establishment, which stays human, from execution, which is shared with AI.

How does Human-on-the-Loop differ from human-in-the-loop?▼

Human-in-the-loop requires approval for each action, creating bottlenecks. Human-on-the-Loop lets humans define the operating envelope while AI executes at machine speed within it, with humans observing patterns and refining boundaries continuously.

What is the Dual Plane Model in CARE?▼

The Dual Plane Model splits governance into a Trust Plane holding accountability, authority, and values that remain permanently human, and an Execution Plane covering task completion and coordination shared with AI. It draws prior art from SDN control/data planes and aviation.

How does CARE relate to EATP and COC?▼

EATP operationalizes CARE's trust chains as a verifiable protocol, while COC applies CARE's Human-on-the-Loop philosophy to software development. Kailash serves as the reference implementation of the CARE governance architecture.

What are the limitations of the CARE framework?▼

CARE's six human competencies are a 2026 snapshot, not permanent boundaries. It does not solve displacement economics, guarantee regulatory compliance, or eliminate power asymmetries, and constraint gaming remains the central operational risk.