Skip to content

validate-manifest

Validate a system manifest file against the required schema, including the framework keys in compliance_targets.

Synopsis

Bash
opencomplai validate-manifest <manifest_file> [OPTIONS]
PowerShell
opencomplai validate-manifest <manifest_file> [OPTIONS]

Arguments

Argument Description
manifest_file Path to a system-manifest.json file (positional).

Options

Option Default Description
--output / -o human Output format: human or json.

Examples

Bash
# Human-readable validation result
opencomplai validate-manifest system-manifest.json

# JSON output (returns the validated manifest)
opencomplai validate-manifest system-manifest.json --output json
PowerShell
# Human-readable validation result
opencomplai validate-manifest system-manifest.json

# JSON output (returns the validated manifest)
opencomplai validate-manifest system-manifest.json --output json

Output

Human (--output human):

Text Only
Manifest is valid.
  system_id:             my-model
  intended_purpose:      customer support chatbot
  compliance_target:     EU_AI_ACT
  high_risk_presumption: False

A manifest with compliance_targets adds a line after compliance_target:

Text Only
  compliance_targets:    EU_AI_ACT, NIST_AI_RMF

JSON (--output json):

JSON
{
  "system_id": "my-model",
  "intended_purpose": "customer support chatbot",
  "compliance_target": "EU_AI_ACT",
  "high_risk_presumption": false,
  "commit_ref": "HEAD"
}

Exit codes

Code Meaning
0 Manifest is valid.
2 Manifest file not found or schema validation failed: for example an empty compliance_targets list, an unknown framework key in it, or a malformed framework_inputs entry.

validate-manifest checks the shape of framework_inputs. Whether each key is a known framework, and each excluded or attested id a requirement of it, is checked when the targets are assessed, by gaps or check --with-gaps. See Frameworks.