Catalog lifecycle: draft, review, publish
How every “Publish …” screen works: draft, validation, independent technical review bound to the diff hash, then publish.
PEEK Platform Administrator · PEEK Technical Reviewer
/peek/customers/tenant-a/1-10Global catalogs carry no tenant content and never adopt themselves for a tenant — agency adoption is a separate agency command. Ten catalog types share one lifecycle:
| Catalog type | Screen | Publish capability |
|---|---|---|
capability | 1.10 | catalog.publish |
role | 2.1 | role_catalog.publish |
persona | 2.2 | persona_catalog.publish |
workflow | 3.4 | workflow_catalog.publish |
document_template | 3.6 | template_catalog.publish |
si_profile | 4.2 | si_profile.publish |
agent_template | 5.2 | agent_template.publish |
connector | 6.2 | connector_catalog.publish |
experience_template | 7.2 | experience_template.publish |
component | 7.5 | component_catalog.publish |
Lifecycle
1. Save draft
catalog.save_draft— the preparer edits content; structural validation lists blocking issues and non-blocking notices.2. Independent review
catalog.review— a PEEK Technical Reviewer who did not prepare it approves or returns the exact diff hash.3. Publish
publish_catalog— requires the type’s publish capability and a matching approval; a new version becomes available for agency adoption.
Related guides
Rules and guards
The system-wide rules every PEEK screen and command enforces, independent of the UI.
Authorization, testing and publishing
Screens 3.5 and 3.8 — route agency authorization and PEEK technical review, run validation scenarios and publish an approved configuration.
Operator roles and capabilities
The five PEEK platform roles, the capabilities each one holds, and how capabilities gate screens and actions.