# Awaken Church — Claude Governance

Turns the Awaken Claude rollout guardrails (originally the internal rollout site) into **Skills** and an **MCP server** so the constraints are available to anyone on Claude Enterprise — automatically, everywhere.

## The model
- **Skills teach behavior.** Model-invoked packages that shape how Claude drafts, edits, and produces content for Awaken. Work today, no infrastructure.
- **The MCP holds the living source of truth and enforces it.** Canonical policy resources + tools that actively scan content, correct language, block integrations, route projects, and flag content for review.
- **`shared/policy-data/` is the single source of truth.** Both skills and the MCP derive from the same JSON — edit once, no drift.

## Structure
```
awaken-claude-governance/
  shared/policy-data/     Single source of truth (5 JSON files)
  skills/                 9 skills (Phase 1 deliverable)
  mcp-server/             Governance MCP (Phase 2 deliverable)
  docs/                   Deployment, governance, taxonomy
```

## Install the skills (one command)

Copy all 9 skills into your Claude Code skills directory:

```bash
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance
```

That installs into `~/.claude/skills/` (personal — available in every project). Restart/reload Claude Code to pick them up.

### Options
```bash
# List what's available
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance --list

# Preview without writing
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance --dry-run

# Install into THIS repo's ./.claude/skills (commit with a project)
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance --project

# Only specific skills
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance --only awaken-constitution,awaken-acceptable-use

# Overwrite existing (keeps a .bak copy)
npx github:Keystone-Infrastructure-Corp/awaken-claude-governance --force
```

For **org-wide** distribution to everyone on Claude Enterprise, use the admin **Skill library** upload instead (see `docs/deployment-enterprise.md`). The npx installer is for individuals and per-project setups.

### Enterprise (all staff)
For org-wide rollout, don't use npx — provision centrally:
1. Paste `enterprise/org-preferences.txt` into Admin -> Organization Preferences (the non-toggleable baseline).
2. Run `npm run package` to build `dist-enterprise/` skill zips, then upload them via admin skill provisioning (enabled by default for all users).
3. Gate seats on AUP acknowledgment.

Full steps + enforcement caveats: `docs/enterprise-admin-checklist.md`.

## The 9 skills
| Skill | Purpose |
|-------|---------|
| `awaken-constitution` | Always-on baseline: voice, language, frameworks, brand, guardrails |
| `awaken-acceptable-use` | What must never enter Claude; what needs review before publishing |
| `awaken-launch-guardrails` | Integrations off until Sept 2026; exception process |
| `awaken-brand-voice` | Project 1 — content & visual brand, sub-brands |
| `awaken-one-awaken-os` | Project 2 — EPU, 3 Harvests, S.T.A.F.F., Tables & Altars |
| `awaken-budget-partnership` | Project 3 — budget philosophy, no live actuals |
| `awaken-campus-pastor-hub` | Project 4 — day-to-day CP support |
| `awaken-staff-onboarding` | Project 5 — teaching mode for new hires |
| `awaken-prompting-guide` | How-To + FAQ, project routing |

## The MCP tools
`check_content`, `check_language`, `is_integration_allowed`, `which_project`, `flag_for_review` — plus 5 policy resources and 2 prompt flows. See `mcp-server/README.md`.

## ⚠️ Important sequencing
Awaken's own Launch Guardrails **prohibit MCP servers until September 2026**. So:
- **Phase 1 (now):** deploy the **skills** + refresh the Org Constitution. Skills carry Phase 1 entirely.
- **Phase 2 (Sept):** deploy the **MCP** as an approved, admin-managed connector alongside the other integrations.

See `docs/deployment-enterprise.md` and `docs/governance-and-maintenance.md`.