uncertainty-to-law

Convert validated hypotheses into enforceable laws with structured Law Card drafts.

1|Updated Dec 17, 2025

Search Tags:#automation #compliance #engineering #uncertainty #risk-management #law #business-rules

Ready to run

npx skills add https://github.com/CAPHTECH/claude-marketplace --skill uncertainty-to-law

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: uncertainty-to-law
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/uncertainty-to-law
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill uncertainty-to-law

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts validated uncertainties (hypotheses) into formal Laws (Law-Driven Engineering) to codify business rules, reduce ambiguity, and enable reproducible risk management across sessions and systems.

Core Features & Use Cases

Hypotheses to Laws workflow: Collect validated hypotheses from the resolving-uncertainty output and plan Law formation.
Law Card drafting & governance: Generate a structured law_card_draft with type, scope, statement, evidence, and verification details for cataloging.
Review, formalization & cataloging: Move drafts into the official Law Catalog and update the Grounding Map; ensure traceability of promotion history.
Use Case: Formalize patterns observed over multiple sessions to create enforceable business rules that prevent recurring issues.

Quick Start

Load the validated hypotheses from resolving-uncertainty results and request Law Card drafts for each hypothesis. Then review and formalize selected drafts into the Law Catalog.

Frequently Asked Questions about uncertainty-to-law

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

FAQPage Schema

How do I convert validated business hypotheses into formal laws?▼

Convert validated hypotheses into formal laws by loading results from hypothesis validation, generating structured Law Card drafts that classify each hypothesis by type (Invariant, Pre, Post, Policy), and cataloging them for cross-system governance. This codifies business rules and prevents recurring issues across sessions.

What information should a Law Card contain?▼

A Law Card draft includes id, type, scope, statement, formal_ish representation, evidence tracing back to validation, verification criteria, and observability markers. These fields ensure laws are enforceable, traceable, and compatible with automated review workflows and pce-memory logging.

When should I formalize uncertainties into laws?▼

Formalize uncertainties into laws after multi-session hypothesis validation and post-incident standardization confirm patterns. This ensures business constraints are based on validated evidence rather than single observations, creating reproducible risk management rules.

How does law formalization reduce compliance and automation risk?▼

Formalizing validated uncertainties as Laws extracts and codifies business constraints into an official Law Catalog, enabling consistent enforcement across systems and reducing ambiguity that leads to compliance gaps or engineering inconsistencies.

Can I track the promotion history of laws from draft to catalog?▼

Yes. The workflow maintains traceability by moving Law Card drafts through review stages into the official Law Catalog and updating the Grounding Map, so you can audit when and why each business rule was formalized.