Specifications¶
Overview¶
Specifications are the foundation of reliable AI systems. This section teaches you how to write clear, actionable specifications that reduce cognitive friction and help AI models understand exactly what you need.
Rather than vague requirements that force models to guess, you'll learn a complete framework: MUST constraints, SHOULD guidelines, CONTEXT for planning, INTENT for understanding why, and VERIFICATION protocols to confirm success.
What You'll Learn¶
Core Framework¶
The Specifications framework has four interconnected layers and Verification Protocols:
MUST Constraints - Hard boundaries and non-negotiable requirements
SHOULD Guidelines - Flexible preferences that adapt to context
CONTEXT - Planning information about environment, users, and constraints
INTENT - The "why" behind your requirements and trade-offs
VERIFICATION - How to confirm the model met your needs
Complete Coverage¶
- Foundations - Core principles and how specifications reduce cognitive friction
- Common Pitfalls - Mistakes to avoid and how to fix them
- Supremacy Clause and Evidence Reset Protocols
- Templates - Ready-to-use specification templates
- Integration Examples - Real-world implementation examples
- Quick Reference Guide - Fast lookup for key concepts
- Verification Protocol Templates - Pre-built verification approaches
- Folder Structures - How to organize project references, complex policies, regulations, or extensive context, to be used in Specifications.
- Reverse Engineering Belief Dynamics - Dynamics Model to create a practical Belief Dynamics Control System Framework
Why Specifications Matter¶
Vague requirements create cognitive friction. When models must guess what you mean, they:
- Waste context on wrong paths
- Make incorrect assumptions
- Produce unreliable results
- Require multiple iterations
Good specifications eliminate guessing. They give models the clarity needed to deliver what you actually want, the first time.
Getting Started¶
New to Specifications?¶
Start here:
Foundations → MUST Constraints → SHOULD Guidelines
Work through the core framework sequentially to build a solid understanding.
Need Something Specific?¶
- Quick answers? → Quick Reference Guide
- Ready to start? → Templates
- Avoiding mistakes? → Common Pitfalls
- Real examples? → Integration Examples
Key Principle¶
All five work together. MUST defines boundaries. SHOULD provides flexibility. CONTEXT enables planning. INTENT reveals why. VERIFICATION PROTOCOLS confirm success.
Missing any layer increases cognitive friction and reduces reliability.
Ready to begin? Start with Foundations →