axiom-rejection-protocol

Reject axioms conflicting with verified ground truth and output rejection logs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/starwreckntx/IRP__METHODOLOGIES- --skill axiom-rejection-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-rejection-protocol
Source: https://github.com/starwreckntx/IRP__METHODOLOGIES-/tree/main/skills/axiom-rejection-protocol
Command: npx skills add https://github.com/starwreckntx/IRP__METHODOLOGIES- --skill axiom-rejection-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a mechanism to identify and reject axioms when they conflict with verified ground truth.

Core Features & Use Cases

  • Axiom Evaluation: Assess axioms against established facts.
  • Rejection & Flagging: Mark and report violations for correction.
  • Traceable Rationale: Document reasoning for rejection decisions.

Quick Start

Evaluate a proposed axiom against current ground truth and reject if inconsistent.

Frequently Asked Questions about axiom-rejection-protocol

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

FAQPage Schema
How do I validate axioms against ground truth?

Validation against ground truth involves comparing proposed axioms to established facts using automated checks. This Skill assesses each axiom against your verified ground-truth corpus, flags inconsistencies, and outputs rejection decisions with documented reasoning for traceability.

What does it mean to reject axioms that violate ground truth?

Rejection occurs when an axiom conflicts with verified ground truth. This Skill identifies such violations across reasoning pipelines and knowledge bases, marks them for correction, and logs rejection decisions with full justification so you can track why each axiom was flagged.

Can I use axiom rejection to catch inconsistencies in my data curation workflow?

Yes. The Skill applies automated consistency checks during data curation to identify axioms misaligned with ground truth. It flags violations early, preventing inconsistent assumptions from propagating downstream and maintaining data quality across your validation pipeline.

How do I get traceable rationale for axiom rejections?

The Skill documents reasoning for every rejection decision, producing logs that explain which ground-truth facts caused each axiom to be rejected. This traceability lets you audit decisions, understand conflicts, and refine your ground-truth corpus or axiom definitions.

What's the difference between flagging and rejecting an inconsistent axiom?

Flagging marks potential issues for review; rejection definitively removes an axiom when it violates ground truth. This Skill performs rejection—automatically removing inconsistent axioms based on your ground-truth corpus—rather than merely flagging them for manual inspection.