29-pact

Validate agent actions against PACT constraint envelopes and clearance rules.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill 29-pact-myeohvmzrka92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 29-pact
Source: https://github.com/myeohVmzrka92/disease-risk-controller-S2/tree/main/.claude/skills/29-pact
Command: npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill 29-pact-myeohvmzrka92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces ad hoc agent behavior with structured governance, so AI systems follow clear accountability, access, and safety rules instead of drifting across sessions.

Core Features & Use Cases

  • Governance Engine: Verifies actions against constraint envelopes, clearance, and organizational policy before execution.
  • Access Enforcement: Controls knowledge access with D/T/R addressing, compartments, knowledge share policies, and bridges.
  • Agent Safety: Wraps agents with frozen governance context, default-deny tool registration, and fail-closed outcomes.
  • Use Case: Use this Skill when building a multi-agent workflow that must approve deployments, restrict sensitive data access, and maintain an audit trail.

Quick Start

Ask the AI to apply PACT governance to an agent organization and verify whether a specific action should be allowed under the current envelope and clearance rules.

Frequently Asked Questions about 29-pact

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

FAQPage Schema
How do I enforce policy and access control for multi-agent AI workflows?

To enforce access control for multi-agent AI workflows, you need a governance engine that validates actions against constraint envelopes and clearance rules before execution. This replaces ad hoc agent behavior with structured, default-deny policy enforcement.

What is fail-closed verification for AI agent safety?

Fail-closed verification for AI agent safety is a governance mechanism that blocks any agent action unless it explicitly passes validation against frozen governance contexts and constraint envelopes. It ensures systems default to denial, preventing unauthorized actions during failures.

How do I maintain an audit trail for AI agents executing sensitive operations?

Maintaining an audit trail for AI agents requires tamper-evident logging integrated with an accountability chain. This captures every validated action, clearance level, and knowledge access event within a frozen governance context to ensure full traceability.

Can I use MCP tool governance with default-deny access enforcement?

Yes, MCP tool governance can enforce default-deny access by wrapping agents with frozen governance contexts. It validates tool registration and actions against organizational policy and constraint envelopes before any execution is permitted.

How does D/T/R addressing work for knowledge sharing controls in AI systems?

D/T/R addressing controls knowledge sharing in AI systems by routing access requests through compartments and bridges. It validates clearance rules and knowledge share policies before granting agents access to restricted data.

When should I not use a governance engine for AI agent organizations?

You should not use a structured governance engine for AI agent organizations when your workflow operates in a fully trusted, single-agent environment with no sensitive data access, multi-agent coordination, or strict audit trail requirements.