Validate and publish

Publishing turns the current files into an immutable version. Validation catches structural and configuration problems before that version can run.

Pre-publish checklist#

1. Include all five required root files.
2. Keep AGENTS.md and README.md non-empty.
3. Parse every TOML file and check its accepted fields.
4. Use only safe relative paths.
5. Keep schedule intervals at one hour or longer.
6. Use qualified secret and variable references.
7. Remove credentials and private data.

Publish a version#

Upload the complete bundle or edit supported files in Aleph. The platform validates paths and configuration, then creates the version. The version cannot be changed afterward; publish another version for revisions.

Review before enabling#

Publishing and enabling are separate. Inspect the new version, confirm its configuration requirements and schedules, then enable it to pin that version.

Public visibility makes the agent discoverable and its bundle inspectable. It does not bypass validation or copy secret values to consumers.

Shared-memory clones have a narrower rule: they may publish changes only to schedules.toml.