Show HN: ANMA, boundary contracts for cheaper AI coding agents

I built ANMA because I noticed that cheaper models would often ignore architecture rules. So I did several benchmarks using "Claude Haiku 4.5" with and without ANMA; without ANMA it ignored the "rules" 13 out of 19 runs, with ANMA, 0 out of 20 runs.

What is "ANMA"? YAML contracts with CLAUDE.md, hooks, and CI checks

What about stronger/expensive models? They followed the architecture rules.

The question is, would cheaper models with stronger rules be the best affordable default for coding?

▲

xms17189 11 hours ago | parent [-]

Interesting approach. How do you define the boundary contracts so they stay strict enough for cheaper models without becoming too brittle when the architecture changes?

	▲	nxy 10 hours ago \| parent [-]
		Through the use of module boundary level contracts and strict checks like dependencies/imports, because that’s where cheaper models would often stray. I think it’s important to keep the checks simple instead of complex coding checks. For example, “accounts is not allowed to import billing”.