rigour AGENTS.md

AGENTS.md - Universal AI Agent Instructions

This file provides instructions for AI coding agents (Codex, Aider, and others).

Setup

npm install
npm run dev
npm test

Quality Gates

This project uses Rigour. Before completing any task:

npx @rigour-labs/cli check

🛡️ Rigour: Mandatory Engineering Governance Protocol

You are an AI Engineering Agent governed by Rigour.

Your access to this codebase is conditional upon your strict adherence to the Rigour Governance Protocol. This is an automated requirement for every engineering task.

🚦 The Mandatory Governance Loop

You MUST execute this loop for every task. No code changes will be accepted as "Done" until they pass all Rigour quality gates.

1. Context Loading: Call rigour_recall (MCP) to align with project-specific engineering memory.
2. Verify Patterns: Before implementing new logic, call rigour_check_pattern to prevent reinvention and ensure security compliance.
3. Audit Enforcement: Before finishing, you MUST call npx @rigour-labs/cli check.
4. Failure Remediation: If the check returns FAIL, you MUST implement all required engineering refinements.
5. PASS or REJECT: You may only declare a task complete when the check returns PASS.

Agent Transaction Firewall (security boundary)

Voluntary calls to rigour_check are quality workflow, not the security boundary. Hard guarantees require installed mediation (hooks, typed rigour_run, firewall transactions, CI rigour firewall admit). An untrusted agent must not be responsible for invoking its own guardrails.

⚖️ Transparency & Accountability

Every action, tool call, and logic shift you perform is automatically logged to the project's local audit trail. This data is visible in real-time in the human-monitored Rigour Studio.

🤖 CRITICAL INSTRUCTION FOR AI

When asked to implement a feature or fix an issue:

1. FIRST: Read ALL relevant rules files (e.g., .cursor/rules/*.mdc, .clinerules, docs/AGENT_INSTRUCTIONS.md).
2. NEVER claim "done" until you can demonstrate the feature WORKS or the fix is verified.
3. ALWAYS run npx @rigour-labs/cli check before claiming completion.
4. CONNECTivity:
   • If you create backend code, you MUST wire it to the frontend.
   • If you create a service, you MUST connect it to the UI.