Analysis, drafts and publishing

Compilation checks XML vocabulary, the Journey contract and binding order. It never executes your GraphQL operations. Server analysis, analyzeJourneySource(sourceXML:), adds schema-aware GraphQL checks, variable checks and response capture checks against your instance. Always run server analysis before publishing API-dependent journeys.

Writes use the source input: a JSON envelope with format equal to cococo-journey-source/1 and sourceXML equal to the full XML string. Serialize the envelope with a JSON encoder; do not hand-escape multiline XML. Version source returns this author-owned envelope. Version definition is the server-owned compiled execution artifact.

CreateJourney creates a container with a draft. UpdateJourney patches an existing container; omitted fields keep their prior values. CreateJourneyVersion creates another draft. PublishJourney promotes the chosen versionId; published versions are immutable. The server rechecks stored source against the compiled artifact before publishing, preventing mismatched source and output. Inspect returned errors rather than treating an HTTP success as successful publication.

Scope is PERSONAL, TEAM or INSTANCE. PERSONAL belongs to the caller; TEAM requires tenant-local team assignments; INSTANCE is the default. TEAM/INSTANCE authoring requires journey:write. PERSONAL authoring is self-service subject to ownership rules. Required domains narrow eligibility but never grant permission to the underlying operations.

For a Journey containing agent steps, confirm that an LLM is configured in AiAdapters and that the intended runner supports AI execution. Include a manual-fallback as well: configuring an LLM alone does not add an assistant integration to the CoCoCo app.

Use the normal Journey resource index for discovery and the standard new/edit form for authoring. Source diagnostics should be resolved before saving or publishing. Save changes first so publication refers to a concrete stored version, not an unsaved editor buffer.

IaC exports author-owned source, not editable compiled JSON. Use the generated IaC schema and guides for exact operation signatures and write/publish behavior on your installed version. Container identifiers, version identifiers and the root XML handle are different values; do not substitute one for another.

There is no automatic conversion from the older JSON-based Journeys to XML. Those Journeys, with their versions and assignments, were retired when XML Journeys were introduced. Recreate needed processes in XML and update Workspace references to the new journey handles.