Skip to main content

Skip docs navigation
manual page/ Reference

Principles

sourceSource: suspec/docs/reference/principles.mdModified: 2026-07-13
  • Skills carry the method. Tools reinforce it.
  • Use proportional rigor. Intent, review, and findings stay; scaffold must earn its keep.
  • Keep durable truth native. Code, tests, project records, and supported memory outlive working artifacts.
  • Carry explicit paths. Consumers discover no store.
  • Tasks narrow. They never invent requirements.
  • Prove before assessment. Worker claims are inputs, not evidence.
  • Separate review. Implementers cannot accept their own work.
  • Keep decisions human. Diagnostics and recommendations never become authority.
  • Preserve source limits. Claims cannot exceed evidence.
  • Keep history historical. Current docs describe the product; ADRs preserve change.

When principles conflict, protect explicit intent, evidence integrity, and human authority. Process does not get a vote.

Related: workflow · source authority

Need a starting point? Install the skills