Update, Publish & Lifecycle
Update the draft, publish it to project into the registry and classifier, unpublish to retract, or delete the ontology — each reversing the projection as needed.
Updating an ontology edits its draft; if the ontology is already published, the update auto-forks a fresh draft so the live overlay is untouched until you publish again. Publishing projects the latest version into your workspace: authored fields become pinned registry rows (protected from cleanup), and custom doctypes become classifier types on the customer axis. Unpublishing flips the published version back to a draft and reverses the projection; deleting removes the ontology and reverses the projection too.
Publish, unpublish, and delete change extraction and classification behavior for your workspace. They are write-scope operations; treat publishing an ontology like a configuration change, not a read.
PATCH
/v1/customer-ontologies/{id}POST
/v1/customer-ontologies/{id}/publishPOST
/v1/customer-ontologies/{id}/unpublishDELETE
/v1/customer-ontologies/{id}