wall-guard

Validate Athena research commits for evidence and judgment layer separation.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/harrymcdonagh/athena --skill wall-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wall-guard
Source: https://github.com/harrymcdonagh/athena/tree/main/.claude/skills/wall-guard
Command: npx skills add https://github.com/harrymcdonagh/athena --skill wall-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that research commits in Athena adhere to strict evidence and judgment separation rules, maintaining the integrity of research outputs.

Core Features & Use Cases

  • Pre-commit Check: Validates that no ranking, scoring, or evaluative language is added to research endpoints, answer schemas, prompts, or retrieval code.
  • Evidence Layer Protection: Ensures that no verdict fields are present in evidence-layer schemas and that FIND results are ordered by match strength.
  • Judgment Layer Separation: Enforces the separation of judgment layers, which require their own ADR and use only read-only market data.

Quick Start

Run the wall-guard skill before any commit touching research endpoints to enforce the evidence/judgment wall.

Frequently Asked Questions about wall-guard

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

FAQPage Schema
How do I enforce evidence and judgment separation in research commits?

To enforce evidence and judgment separation in research commits, validate commits affecting research endpoints, answer schemas, prompts, or retrieval code to block any ranking, scoring, or evaluative language. This maintains strict research output integrity.

What is an evidence layer in research codebase validation?

An evidence layer in research codebase validation is a structured data schema that must remain free of verdict fields and subjective judgment. It requires presenting findings, such as FIND results, strictly ordered by match strength.

How do I check commits for evaluative language before submission?

To check commits for evaluative language before submission, run a pre-commit validation against research endpoints, answer schemas, prompts, and retrieval code to ensure no ranking or scoring terms are present in the evidence layer.

Does the judgment layer require its own ADR when separating research logic?

Yes, separating the judgment layer requires its own ADR and must use only read-only market data. This ensures subjective evaluation logic remains structurally isolated from the evidence layer in the research codebase.

What types of code changes trigger research commit validation rules?

Commit validation rules are triggered by changes affecting research endpoints, answer schemas, prompts, or retrieval code. These specific areas must be checked to maintain the strict evidence and judgment separation wall.

Why are verdict fields blocked in evidence-layer schemas?

Verdict fields are blocked in evidence-layer schemas to prevent evaluative judgment from contaminating objective research data. Enforcing this separation ensures that FIND results remain ordered by match strength without subjective scoring interference.