reality-verification

Verify software delivery claims against actual repository artifacts.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill reality-verification-mahg-es
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reality-verification
Source: https://github.com/mahg-es/araya/tree/main/skills/reality-verification
Command: npx skills add https://github.com/mahg-es/araya --skill reality-verification-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ARAYA must verify that reported capabilities and progress align with the actual repository reality, preventing gaps between claims and artifacts.

Core Features & Use Cases

  • Five-tier delivery state model (Configured, Implemented, Running, Operational, Independently Verified) with clear evidence requirements.
  • Independent verification and governance enforcement to ensure trust and traceability.
  • Reality scoring and explicit run results to support data-driven decisions.

Quick Start

Run a reality-check to surface gaps between claims and repository artifacts.

Frequently Asked Questions about reality-verification

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

FAQPage Schema
How do I verify software delivery claims against actual repository artifacts?▼

To verify software delivery claims against repository artifacts, you can run a reality-check that surfaces gaps between reported capabilities and actual artifacts using a transparent reality-score metric.

What is the five-tier delivery state model for software governance checks?▼

The five-tier delivery state model for software governance tracks artifacts across Configured, Implemented, Running, Operational, and Independently Verified states, each requiring explicit evidence collection to ensure traceability.

How do I enforce compliance and governance in a CI-CD pipeline?▼

To enforce compliance and governance in a CI-CD pipeline, apply independent verification checks that validate explicit run results and reproducible test outputs against claimed delivery progress.

What evidence is required for an end-to-end readiness assessment?▼

An end-to-end readiness assessment requires explicit evidence collection and reproducible test results to validate that software delivery has reached the Independently Verified state.

Can I use this reality-verification approach for software-quality audits without external dependencies?▼

Yes, you can perform reality-verification for software-quality audits without external dependencies by applying the built-in five-tier delivery state model and reality scoring directly to your repository.

Why does reported software progress sometimes not match the repository reality?▼

Reported software progress can mismatch repository reality due to gaps between claims and actual artifacts, which a reality-check surfaces by validating reproducible test results and explicit evidence.