Treats refusal, deferral, reduced work, and structural halt as explicit resource and confidence outcomes rather than silent failure.
No-op outcomes
A no-op may mean insufficient confidence, exhausted resource budget, unsupported capability, unsafe input, missing evidence, or a request that requires human review. The outcome must carry a reason code and recovery path.
Emergent halt
A halt is a model-level research concept only when it follows from the documented dynamics. A normal resource guard, timeout, or hard limit should be named accurately rather than rebranded.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?