Skip to content

Add goal and success definition sections to AGENTS.md #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
axis-marbell merged 1 commit into from
Aug 18, 2026
Merged

Add goal and success definition sections to AGENTS.md #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ the operational collaboration, memory, GitNexus, skill-selection, PR, and
review workflow. This file remains the normative scientific and governance
contract when the two documents differ.

## Goal
The sole purpose of this repository and every agent working in it is the advancement and full promotion of validated claims.
An effort is complete only when its positive claims have passed every success gate, undergone individual review, entered the accepted registry, and been pinned in a release. That is the entire goal. Nothing else counts as success.
Partial harvest of reusable atoms is a tactical concession that keeps the larger objective open. It is never a substitute for claim promotion, never a terminal disposition, and never the outcome the repository exists to produce. Agents must not treat merge activity, documentation polish, validation theater, or incremental code extraction as progress toward the goal. Those activities are scaffolding; the goal is closed only by fully promoted, dependency-closed, oracle-validated claims whose downstream consumers remain consistent.
Honesty about failure is required. Presenting incomplete work, harvested fragments, or well-documented residuals as if they fulfill the requested objective is forbidden. Only the user may reduce scope. Until the claims themselves are promoted under the contract, the objective remains open and every subsequent loop or /goal iteration is obligated to advance it.

## Definition of success

Honesty is mandatory, but honesty about failure is not completion. A failed candidate, no-go, contradiction, residual, bound, inconclusive simulation, or well-documented obstruction is attempt evidence. Preserve it and continue; never present it as the victory requested by the user.
Expand Down