The v2.14 specification declares a single manifest file — grok-install.yaml — that describes an agent's runtime, prompts, tools, safety profile, and X integration. The canonical schema is locked: conformant parsers accept unknown top-level keys and unknown extensions: sub-keys for forward compatibility. Validation is one line: grok-install validate path/to/manifest.yaml.
Core Spec
spec / v2.14 / README.md
Overview — what v2.14 declares, how to validate, and where the field schemas live.
view doc →spec / v2.14 / schema.json
The canonical manifest schema. JSON Schema 2020-12. Locked at v2.14.
view schema →spec / v2.14 / extensions
The five documented extensions: blocks — constitution, multi-agent roles, provenance, demo metadata, X Money.
Fourteen Magic Standards
Fourteen sibling YAMLs under standards/ declare reusable agent components — one role per file, composable inside any manifest.
- grok-agent.yaml— single-agent definitionview yaml
- grok-workflow.yaml— multi-step pipelineview yaml
- grok-swarm.yaml— multi-agent orchestrationview yaml
- grok-tools.yaml— tool schemasview yaml
- grok-prompts.yaml— prompt templatesview yaml
- grok-voice.yaml— voice profileview yaml
- grok-security.yaml— safety profileview yaml
- grok-deploy.yaml— deployment targetsview yaml
- grok-config.yaml— agent configurationview yaml
- grok-test.yaml— test suite definitionview yaml
- grok-update.yaml— update channel + cadenceview yaml
- grok-docs.yaml— documentation pointersview yaml
- grok-analytics.yaml— analytics + reportingview yaml
- grok-ui.yaml— UI surface descriptionview yaml
Validate a Manifest
pip install grok-install
grok-install validate path/to/your.yamlOr gate manifests in CI with the in-tree GitHub Action.
The Extensions Block
v2.14 manifests carry an optional extensions: block for forward-compatible additions. Five blocks are documented in spec/v2.14/extensions/README.md: constitution (article references for the constitution-scanner integration), multi_agent_roles (role declarations for super-agents that coordinate sub-agents), provenance (citation and confidence configuration for the provenance-trust agent), demo_metadata (video and storyboard URLs), and x_money_specific (cost caps and tax disclaimer config for finance-app templates). Parsers without extension support ignore unknown top-level keys, so manifests stay backward-compatible with vanilla v2.14 parsers. The cross-platform runtime xlOS consumes these blocks for advanced usage.