What are 'Laws' and 'Terms' in the ELD framework?

Terms are the domain vocabulary (entities and boundaries), while Laws are the verifiable rules or invariants the system must obey. Together, they form a Link Map that ensures code follows business logic.

How does Predict-Light improve development safety?

Predict-Light is a risk-gating mechanism that categorizes changes by impact (P0-P2). It allows trivial fixes to proceed quickly while flagging high-risk architectural changes for deeper analysis and isolation.

What is Evidence-Loop Development (ELD)?

ELD is a structured development methodology that prioritizes verifiable evidence over assumptions, using a cyclical process to sense, specify, and ground every code change in reality.

How does ELD handle knowledge accuracy?

Through Epistemic Status management, ELD tracks whether information is verified, inferred, or unknown. It features an 'Auto-Downgrade' rule that reduces confidence levels if the source code changes or time elapses.

Evidence-Loop Development (ELD)

Name: Evidence-Loop Development (ELD)
Author: CAPHTECH

byCAPHTECH

0•

Developer Tools

Implements a rigorous, evidence-driven development methodology to ensure code changes are grounded in observed facts and structured domain knowledge.

The Evidence-Loop Development (ELD) skill transforms Claude into a high-integrity software engineer by enforcing the ELD v3 framework. It guides the development process through a systematic 5+1 phase cycle—Sense, Spec, Predict-Light, Change, Ground, and Record—replacing guesswork with 'Epistemic Humility.' By defining domain 'Laws' and 'Terms' and utilizing an Evidence Ladder for verification, this skill ensures that every modification is justified, tested, and documented. It is particularly effective for complex refactoring, high-stakes feature development, and systematic debugging where maintaining a verifiable 'Source of Truth' is critical for long-term project health.

Key Features

01Evidence-driven 5+1 phase development cycle (Sense, Spec, Predict, Change, Ground, Record)

02Evidence Ladder (L0-L4) for multi-level verification from static analysis to telemetry

03Structured Law and Term card system for domain modeling and invariant tracking

040 GitHub stars

05Automated Epistemic Status management to track and downgrade knowledge confidence over time

06Predict-Light risk gating to assess and manage change impact (P0-P2 levels)

Use Cases

01Safely refactoring complex legacy codebases by identifying and verifying domain invariants

02Implementing new features with strict business logic requirements using Law-driven development

03Systematic debugging by treating bugs as Law violations and proving the fix through the Evidence Ladder

Key Features

01Evidence-driven 5+1 phase development cycle (Sense, Spec, Predict, Change, Ground, Record)

02Evidence Ladder (L0-L4) for multi-level verification from static analysis to telemetry

03Structured Law and Term card system for domain modeling and invariant tracking

040 GitHub stars

05Automated Epistemic Status management to track and downgrade knowledge confidence over time

06Predict-Light risk gating to assess and manage change impact (P0-P2 levels)

Use Cases

01Safely refactoring complex legacy codebases by identifying and verifying domain invariants

02Implementing new features with strict business logic requirements using Law-driven development

03Systematic debugging by treating bugs as Law violations and proving the fix through the Evidence Ladder