semantic-required-extension-in-operand
a required name that appears only as a key under an extensions member inside an in operand is missing: that member is data
semantic invalid
- Layer
- semantic
- Expected result
- invalid
- Expected diagnostic
JPS-SEMANTIC-MISSING-REQUIRED-EXTENSIONat/metadata/requiredExtensions/0- Specification
- §9.1
The expected result is conformance-corpus metadata, not a claim
about factual grounding, authority, safety, or operational fitness.
Exact fixture
{
"specVersion": "0.6.0",
"id": "https://example.com/judgment-packs/required-extension-in-operand",
"version": "0.1.0",
"title": "A required name only inside an operand",
"decision": {
"intent": "Exercise one rule of RFC 0031.",
"question": "Is the request accepted?"
},
"outcomes": [
{
"id": "accept",
"label": "Accept"
},
{
"id": "refer",
"label": "Refer for review"
}
],
"rules": [
{
"id": "accept-request",
"description": "Accept a request in a priority tier.",
"when": {
"op": "fact",
"path": "/request/tier",
"operator": "in",
"value": [
{
"extensions": {
"com.example.effective-window": {
"days": 30
}
}
}
]
},
"outcome": "accept",
"onUnknown": "escalate"
}
],
"metadata": {
"requiredExtensions": [
"com.example.effective-window"
]
}
}