proof-registry

Register evidence types and sufficiency thresholds for the Proof Authority harness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of managing complex authority boundaries by providing a structured framework to register new evidence types and sufficiency thresholds, preventing accidental overreach or security gaps.

Core Features & Use Cases

  • Capability Control: Define exactly what evidence is required to trust a specific domain or action.
  • Risk Mitigation: Implement bounded changes that can be tested in isolation before affecting production systems.
  • Use Case: When adding a new automated check to a system, use this Skill to define the specific evidence required for the check to pass, ensuring the system does not grant unauthorized permissions.

Quick Start

Use the proof-registry skill to define a new sufficiency threshold for the domain authority by specifying the required evidence type and the associated safety boundary.

Frequently Asked Questions about proof-registry

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

FAQPage Schema
How do I define authority boundaries and trust thresholds for automated security checks?

To define authority boundaries, you register new evidence types and sufficiency thresholds, specifying the exact evidence required for a check to pass and preventing unauthorized permissions or security gaps.

What is the best way to register new evidence types for policy enforcement without affecting production?

Registering new evidence types for policy enforcement allows you to implement bounded changes that can be tested in isolation, ensuring capability boundaries are strictly defined before impacting production systems.

How do I set sufficiency thresholds to expand system scoring capabilities?

You set sufficiency thresholds to expand scoring capabilities by applying defined control levers and verifying both positive and boundary test cases, ensuring the system grants authority only when sufficient evidence is provided.

When do I need to register new evidence types for system architecture compliance?

You need to register new evidence types for system architecture compliance when adding automated checks that require strictly defined capability boundaries, preventing accidental overreach or security gaps in policy enforcement.

Does defining trust thresholds require verifying boundary test cases?

Defining trust thresholds requires adherence to defined control levers and verification of both positive and boundary test cases, ensuring that the sufficiency thresholds correctly expand scoring capabilities without overreach.