valid-annotations-required-vendor-beside
a required vendor name whose only key is beside annotations in one rule's extensions; the evaluation form keeps that key
semantic valid
- Layer
- semantic
- Expected result
- valid
- Specification
- §8.5
- Supported extensions
com.example.review-policy
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/annotations-required-vendor-beside",
"version": "0.1.0",
"title": "A required vendor key beside annotations",
"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 every request.",
"when": {
"op": "literal",
"value": true
},
"outcome": "accept",
"onUnknown": "ignore",
"extensions": {
"org.judgmentpack.annotations": {
"category": "intake"
},
"com.example.review-policy": {
"reviewMode": "two-person"
}
}
}
],
"metadata": {
"requiredExtensions": [
"com.example.review-policy"
]
}
}