> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Domain Workflows: Creation, Review, Publication, and More

> Deep dive into Content domain workflows: triggers, steps, handoffs, approvals, and receipts for creation, review, publication, and knowledge updates.

Content workflows define how work moves through the domain from trigger to completion. Each workflow is governed, meaning every step requires authorization and produces a receipt.

### Content Creation Workflow

* **Trigger** — a new brief is added to the Editorial Calendar or a campaign is created.
* **Steps** — Twin assembles context from related articles and campaign goals. The author drafts, iterates, and saves versions.
* **Handoff** — the author submits for review via `content.review.request`.
* **Approval** — an editor approves via `content.approval.grant`.
* **Receipt** — a workflow receipt is attached to the article and campaign.

### Editorial Review Workflow

* **Trigger** — a review request enters the pipeline.
* **Steps** — the Editorial Agent prepares diffs, style excerpts, and prior comments. The editor reviews inline.
* **Handoff** — approval sends the item to the Publication Queue. Rejection returns it to the author with structured feedback.
* **Approval** — one or more editors must grant approval depending on topic sensitivity.
* **Receipt** — the review outcome and comments are preserved as evidence.

### Publication Workflow

* **Trigger** — an approved item reaches the Publication Queue.
* **Steps** — the Publish Agent checks links, images, and schedule conflicts. The practitioner confirms.
* **Handoff** — Spine routes the publish command to the target system via its connector.
* **Approval** — some channels require a final human confirmation before go-live.
* **Receipt** — the publish confirmation and URL are stored in the continuity layer.

### Knowledge Update Workflow

* **Trigger** — an article is flagged as outdated or a correction is submitted.
* **Steps** — the author edits, Twin diffs against the prior version, and review is reinitiated.
* **Handoff** — the updated article replaces the prior version in the knowledge base.
* **Approval** — updates to critical knowledge may require manager approval.
* **Receipt** — the version change and review record are logged.

### Related

* [Content Capabilities](/internal-docs/domains/content/capabilities)
* [Content Execution Flow](/internal-docs/domains/content/execution-flow)
* [Content Human Workbench](/internal-docs/domains/content/human-workbench)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.