Guides
Enable channels, then verify
Enable the AI Channels a Project needs, validate source Topics, preview changes, then check for drift or write generated files.
AI Channel config
Enable outputs in sumr.yaml.
The source folder stays stable. The channel flags decide which generated files are written for the current Project.
playbook:
sources:
- docs
channels:
codex: true
claude: true
cursor: true
copilot: falseOne Resource can serve several AI Channels without maintaining parallel vendor-specific copies.
Before sync
Validate, preview, then check or write.
Validation checks renderable Topics before generated files change. Invalid configuration stops sync: JSON output reports INVALID_CONFIG for sync andCONFIG_SCHEMA_INVALID for validate. A dry run previews each AI Channel's changes. The --check flag compares generated output without writing and returns a nonzero status when it finds drift.
Need the command details? Open validate source docs or sync generated files.
sumr playbook validate --source docs# check source docssumr playbook sync --source docs --dry-run# preview generated AI Channel filessumr playbook sync --source docs --check# check drift in CIsumr playbook sync --source docs# write generated filesGuide map
Choose the decision you are making.
Source model
Place guidance in the Project, group reusable knowledge in Catalogs, and keep Resources reviewable before they become AI Channel output.
2Resource types
Keep source-only Markdown as a Document. Add a supported category when Playbook should render it as a typed Resource.
3Portable intent
Declare model tier, effort, access, and tools once so each AI Channel can map the Resource into its native format.
4Agent instructions
Extract durable rules with agents-md markers instead of hand-editing generated Codex, Claude, or Cursor files.