trust-machine

Manage trust-state transitions and expiry policies for AI system routes.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill trust-machine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trust-machine
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/trust-machine
Command: npx skills add https://github.com/AesopScott/mojo --skill trust-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of managing capability boundaries and route trust in AI systems, preventing unauthorized authority expansion while ensuring safe, testable configuration changes.

Core Features & Use Cases

  • Trust-State Machine: Configures specific trust states for provider and model paths, such as direct, reviewed, or blocked.
  • Expiry Policy: Implements time-bound trust to ensure that permissions are periodically re-verified.
  • Use Case: When modifying a sensitive API route, use this Skill to define a restricted trust state that requires a positive test and a boundary test before the change is applied to production.

Quick Start

Use the trust-machine skill to inspect the current trust boundary and propose a configuration change for the specified route.

Frequently Asked Questions about trust-machine

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

FAQPage Schema
How do I implement capability control for AI system routes?

Capability control for AI system routes is implemented by defining a trust-state machine that configures specific trust states—such as direct, reviewed, or blocked—for provider and model paths to prevent unauthorized authority expansion.

What is a trust-state machine and how does it manage provider configurations?

A trust-state machine manages provider configurations by enforcing bounded authority through specific trust states like direct, reviewed, or blocked, ensuring that route and model permissions are rigorously verified before application.

How do I enforce time-bound permissions for security-sensitive harness updates?

Time-bound permissions for harness updates are enforced using an expiry policy that ensures permissions are periodically re-verified, preventing unauthorized access to security-sensitive configurations over time.

How do I apply safety gates to sensitive API route modifications?

Safety gates are applied to sensitive API route modifications by defining a restricted trust state that requires both positive and boundary tests before configuration changes are applied to production environments.

When do I need an expiry policy for AI capability boundaries?

An expiry policy for AI capability boundaries is needed when managing security-sensitive harness updates, ensuring that bounded authority and trust states are periodically re-verified to maintain rigorous safety standards.

Can I use trust-state transitions to prevent unauthorized access in provider paths?

Trust-state transitions prevent unauthorized access in provider paths by applying bounded authority and rigorous verification gates, ensuring configuration changes require explicit state shifts like reviewed or blocked.