skills.rest
terrene-foundation
terrene-foundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

32-trust-posture

Wire authored rules into L1–L5 trust posture with grace-period lifecycle handling.

Updated Mar 31, 2026
Search Tags:#claude code#ai governance#grace period#rule authoring#trust posture#compliance enforcement#audit depth scaling
One-click install
npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill 32-trust-posture-terrene-foundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 32-trust-posture
Source: https://github.com/terrene-foundation/kailash-coc-claude-rb/tree/main/.claude/skills/32-trust-posture
Command: npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill 32-trust-posture-terrene-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents untagged, unenforced rules by standardizing how every rule is wired into the graduated trust posture loop (L1–L5) so violations are detected, acknowledged, and acted on consistently across /codify, /redteam, and /implement.

Core Features & Use Cases

  • Trust Posture Wiring Standardization: Ensures rule authors include the required “Trust Posture Wiring” section with severity, grace period, thresholds, receipt requirements, and detection mechanism.
  • Grace-Period Enforcement Mechanics: Defines how newly authored rules enter pending_verification, how SessionStart communicates verification requirements, and how emergency downgrade works.
  • /codify Integration Contract: Mandates that /codify consults violations history, links addressed violations, updates posture.json, and emits proposal artifacts that pass Gate 1 validation.
  • Posture-Aware /implement Behavior: Documents how /implement must surface current posture constraints and include required acknowledgement tokens when pending_verification is non-empty.
  • Posture-Scaled /redteam Depth: Specifies audit depth requirements by posture and the carve-out for self-referential /codify surfaces to ensure correct multi-agent redteam dispatch.

Quick Start

Ask the AI to codify a new rule and explicitly include a complete Trust Posture Wiring section that matches the canonical checklist, then update posture.json pending_verification and emit the proposal for sync-reviewer Gate 1.

Frequently Asked Questions about 32-trust-posture

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

FAQPage Schema
How do I enforce AI governance rules consistently across different agents?▼

Graduated trust posture wiring standardizes rule enforcement by linking severity, grace periods, thresholds, and detection mechanisms so violations are consistently detected and acknowledged across multi-agent AI governance workflows.

What is graduated trust posture and when do I need it for compliance enforcement?▼

Graduated trust posture (L1–L5) is a tiered compliance enforcement framework needed when authoring rules that require posture-aware execution, ensuring audit depth scaling and consistent violation handling across agents.

How do I add a new rule to a trust posture system without breaking existing compliance checks?▼

Codify new rules by including a complete Trust Posture Wiring section, update posture.json with pending_verification status, and emit proposal artifacts that pass Gate 1 validation for sync-reviewer approval.

How does grace-period lifecycle handling work for newly authored compliance rules?▼

Grace-period lifecycle handling places newly authored rules into pending_verification status, where SessionStart communicates verification requirements and emergency downgrade mechanisms apply until the rule is fully verified.

Can I scale audit depth based on my current AI governance posture level?▼

Posture-scaled audit depth requirements vary by trust posture level (L1–L5), allowing redteam audits to dispatch with calibrated depth while carving out self-referential codify surfaces for multi-agent compliance.

Why do my untagged rules fail to enforce during posture-aware execution?▼

Untagged rules fail enforcement because they lack mandatory Trust Posture Wiring fields, which are required to surface current posture constraints and include necessary acknowledgement tokens during implementation.

Related Skills

Explore More Legal & Compliance Skills→
FFOO6866FFOO6866

32-trust-posture

Wire graduated trust posture fields into newly authored agent rules.

Community
Advanced
Chulf58Chulf58

forge:implement

Automate the FORGE implement pipeline from approved plans to tested implementations.

Community
Advanced
forbotsakeforbotsake
5

cso

Audit codebase security across infrastructure, dependencies, CI/CD, and AI tooling.

Official
Advanced
LoxtepIncLoxtepInc
1

governance-policies

Author and manage deploy-time governance policies via the REST API.

Official
Advanced