Claim ladder

One application request creates several different questions

Intent-space deliberately avoids using a single word such as 'works' for every layer of success. A behavior can exist in the model yet fail later at validation, support, generation or product quality.

1. REPRESENTABLE  — can the required behavior exist in the model?
2. VALID          — does the proposed structure satisfy the contract?
3. SUPPORTED      — does the current runtime implement that admitted form?
4. GENERATED      — can a model create the required supported structure?
5. PRODUCT-READY  — is the resulting experience durable, ergonomic and ready for real users?

Passing a lower rung does not imply the next one

• Representability does not guarantee a producer will find the representation.
• Contract validity does not guarantee current runtime support.
• Runtime support does not guarantee generation success.
• A technical existence proof does not establish production readiness.

Why this vocabulary matters

The ladder makes failures actionable. A representability failure points at the application vocabulary; a validity failure points at the contract; a support failure points at the executor; a generation failure points at the producer or task framing; a product failure points at usability, durability or operational quality.