eightforge-truth-engine-reviewer

Reviews EightForge truth-engine changes for provenance, validation freshness, and finding lifecycle integrity.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-truth-engine-reviewer-ericanalysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eightforge-truth-engine-reviewer
Source: https://github.com/EricAnalysis/eightforge-os/tree/main/.cursor/skills/eightforge-truth-engine-reviewer
Command: npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-truth-engine-reviewer-ericanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes to EightForge's truth and validation core can silently collapse distinct provenance classes, let stale dependencies pass validation, or desynchronize findings from decisions and execution. This Skill provides a structured expert review lens that catches those violations before they ship. ## Core Features & Use Cases - Authority Classification: Classifies every reviewed path and finding as production authority, compatibility, shadow, design target, or superseded, preventing legacy projections from masquerading as truth sources. - Truth-Record Separation Checks: Verifies that source-derived, derived, human, and effective truth records stay distinct with intact provenance and supersession history. - Validation Freshness and Lifecycle Review: Traces snapshot identities, rule versions, rerun deduplication, finding resolution, suppression, overrides, and downstream decision/execution reconciliation. - Use Case: When a PR modifies lib/projectFacts.ts, validator assembly, or finding closure logic, run this review to confirm compatibility fallbacks cannot hide stale inputs and that findings drive execution through idempotent reconciliation. ## Quick Start Review this pull request touching lib/projectFacts.ts and the validation findings lifecycle using the EightForge truth-engine review checklist.

Frequently Asked Questions about eightforge-truth-engine-reviewer

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

FAQPage Schema
How do I review changes to a validation and truth engine?▼

Trace the full authority chain from persisted records through validator input assembly, effective truth selection, findings, and downstream projections. Classify each path as production authority, compatibility, shadow, or superseded, then verify freshness checks, rerun deduplication, and finding lifecycle reconciliation.

What is the difference between source-derived, derived, human, and effective truth?▼

Source-derived machine facts come from verified source dependencies, derived facts cite exact inputs plus rule version and calculation trace, and human assertions retain actor, reason, and supersession history. Effective truth selects among these for consumption without rewriting the underlying records or hiding provenance.

When should I use this reviewer versus other EightForge reviewers?▼

Use it for changes to persisted truth, validators, findings, project summaries, overrides, and decision/execution synchronization. Route extraction mechanics, cross-document relationships, execution internals, audit storage, database, UX, and performance concerns to the corresponding specialized reviewers.

Can a compatibility fallback let stale validation inputs pass?▼

No. A stale, missing, or unverifiable dependency must never silently degrade into a PASS through a compatibility fallback. Compatibility readers must be contained, visible, and covered by explicit removal or promotion gates.

What output format does the truth-engine review produce?▼

It produces a verdict of Pass, Pass with Concerns, or Fail, followed by severity-ordered key issues with evidence and authority classification, minimal fixes, regression risks, suggested tests, and one evidence-based positive note.