Normativity

The source document's normative strength and modal wording, kept separate from project activation.

$defs.normativity · object

Definition JSON

This fragment is shown exactly as published. Use the chevrons to fold objects and arrays; linked $ref values return to their targets in the complete schema.

{    "type": "object",
    "additionalProperties": false,
    "required": [        "source_level"    ],
    "properties": {        "source_level": {            "enum": [                "mandatory",
                "recommended",
                "permitted",
                "prohibited",
                "informative",
                "example"            ]        },
        "source_modal": {            "enum": [                "shall",
                "should",
                "may",
                "can",
                "must",
                "prohibited",
                "none",
                "other"            ]        },
        "contractual_elevation_allowed": {            "type": "boolean",
            "description": "True when explicit mandatory invocation in the material requisition can make an informative/example source scope contractually binding."        }    }}

Fields

FieldTypeStatusMeaning
source_levelenum — "mandatory", "recommended", "permitted", "prohibited", "informative", "example"RequiredNormative strength of the requirement in its source document.
source_modalenum — "shall", "should", "may", "can", "must", "prohibited", …OptionalModal word used by the external source. MatJSON-authored requirements use must/must not, while this field preserves source wording.
contractual_elevation_allowedbooleanOptionalTrue when explicit mandatory invocation in the material requisition can make an informative/example source scope contractually binding.