Publishing reference
Developer/Operator reference. Publishing controls belong to authors and account administrators, separate from normal Agent conversations.
Create a private draft
Open Workspace → Private drafts in Console. Start from the rule editors, a checked document proposal, or an eligible result in From cases. A saved draft belongs to your account and is not executable configuration.
The document workflow is an example of local creation and checking. Its model and Worker do the work using the same capability and evidence boundaries as other tasks.
Review before publication
Check the Vocabulary, Rules, Actions, Sources and Case Contracts together. Include positive examples, negative examples, boundaries, distinct business keys and changed input versions.
Mechanical checks establish only what they actually exercised. Review unresolved questions and business meaning yourself. A set of green examples is not an exhaustive proof of the policy.
Publication makes the Release content public, including embedded examples and quotations. Remove private source material and credentials before publishing.
Publish through a Publisher
Choose or create a Publisher from Publishers. A Publisher is the durable identity that owns a namespace and Releases. Membership governs who may publish; it does not grant access to customer Agents or their data.
Publish the reviewed draft to create an immutable Release. Capability and Constitution are separate Release kinds. A later change creates another Release rather than rewriting the content already installed elsewhere.
Install and verify
Install the chosen Release on an Agent, bind its Sources to real Connections, and verify that the desired configuration became effective. Live Cases can delay the switch.
Run a small Case and inspect its evidence and terminal receipt. Keep draft validation, publication, installation, effective configuration and successful execution as separate outcomes.
Learning from Cases
The From cases workspace supports eligible private Cases and candidate review. Replay and shadow reports describe bounded checks against retained evidence. They do not grant execution permission, install a capability or publish it automatically.
When material or frozen evidence is unavailable, the resulting gap must remain visible. Do not treat a generated candidate as a ready Release.