29-pact

Validate D/T/R addresses, constraint envelopes, clearances, and audit trails for PACT governance.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill 29-pact-aliciapls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 29-pact
Source: https://github.com/aliciapls/ML-Week-2---Healthcare/tree/main/.claude/skills/29-pact
Command: npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill 29-pact-aliciapls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PACT governance prevents AI agents from drifting outside approved boundaries by enforcing positional accountability, constraint envelopes, knowledge clearance, and auditable decisions.

Core Features & Use Cases

  • D/T/R addressing for organizational containment and accountability chains.
  • Role, task, and effective envelopes with monotonic tightening and fail-closed verification.
  • Knowledge access control, MCP tool governance, governed agents, and tamper-evident audit chains.
  • Use it to govern enterprise agent teams, protect sensitive data, and safely mediate tool execution in production workflows.

Quick Start

Use the pact skill to map a role address to its envelope, clearance, and access rules for a specific AI agent workflow.

Frequently Asked Questions about 29-pact

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

FAQPage Schema
What is PACT governance for AI agents and when do I need it?

PACT governance prevents AI agents from drifting outside approved boundaries by enforcing positional accountability, constraint envelopes, and knowledge clearance. You need it to safely mediate tool execution and protect sensitive data in production agent workflows.

How do I enforce access control and audit trails for enterprise AI agent teams?

Enforce access control and audit trails by validating D/T/R addresses, constraint envelopes, and clearances to ensure tamper-evident auditing. This governs enterprise agent teams by applying fail-closed verification and default-deny tool registration across role and task scenarios.

Can I use constraint envelopes to restrict MCP tool access in production workflows?

Yes, you can restrict MCP tool access by applying role, task, and effective envelopes with monotonic tightening. This ensures fail-closed verification for governed agent organizations, safely mediating tool execution in production environments.

What's the best way to map a role address to its clearance and access rules?

Map a role address to its clearance and access rules by validating D/T/R addressing against organizational containment and accountability chains. This applies policy-driven access decisions across role, task, and knowledge scenarios for specific AI agent workflows.

Why does my AI agent workflow require fail-closed verification and default-deny tool registration?

Fail-closed verification and default-deny tool registration are required to prevent AI agents from executing unapproved tools. This PACT governance mechanism ensures immutable contexts and tamper-evident auditing, satisfying strict policy-driven access decisions.

Does this governance approach support Kaizen integration for agent organizations?

Yes, PACT governance explicitly supports Kaizen integration alongside MCP tool mediation and governed agent organizations. It applies positional accountability and constraint envelopes to maintain policy-driven access decisions across knowledge scenarios.