R0021/2026-03-25/Q006
Query: Has RFC 2119 requirement language (MUST, MUST NOT, SHOULD, MAY) been applied to AI prompt design or AI system behavioral specifications in any published work?
BLUF: One published example was found: a practitioner blog post (deliberate.codes, Feb 2026) applying RFC 2119 vocabulary to AI coding agent specifications. No formal standard, academic paper, or major vendor documentation applies RFC 2119 to prompt engineering. The absence of formal requirement language in prompt engineering is itself a significant finding.
Answer: H3 (Applied in adjacent area, not prompt-specific) · Confidence: Medium
Summary
| Entity |
Description |
| Query Definition |
Question as received, clarified, ambiguities, sub-questions |
| Assessment |
Full analytical product |
| ACH Matrix |
Evidence × hypotheses diagnosticity analysis |
| Self-Audit |
ROBIS-adapted 4-domain process audit |
Hypotheses
| ID |
Statement |
Status |
| H1 |
RFC 2119 formally applied to AI prompt design |
Partially supported |
| H2 |
Not applied |
Eliminated |
| H3 |
Applied in adjacent areas, not prompt-specific |
Supported |
Searches
| ID |
Target |
Type |
Outcome |
| S01 |
RFC 2119 + AI specifications |
WebSearch |
2 selected, 1 rejected |
Sources
| Source |
Description |
Reliability |
Relevance |
Evidence |
| SRC01 |
deliberate.codes blog |
Medium |
High |
1 extract |
| SRC02 |
RFC 2119 Original |
High |
Medium |
1 extract |
Revisit Triggers
- Standards body publishes AI prompt specification using RFC 2119
- Academic paper on formal AI behavioral specification using requirement language