Verify configuration content

AXL can verify signed skills, agents, and RAG documents before loading or ingesting them. Use the axl CLI to create keys, sign content, and verify manifests, then store trusted public authors in the config keyring.

Enable verification policies at the platform level:

SKILL_VERIFICATION=require
EVAL_DATASET_VERIFICATION=require

Use warn while introducing signing, then move to require after all deployed content and trusted authors are ready. A valid signature proves integrity; trust still depends on the configured keyring.

See Signing reference.

Next

• Add reusable skills - the content most often signed.
• Ingest documents - provenance on ingested chunks.
• Signing reference - keys, manifests, and policies.