See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Docs

A block document for the channel, where an agent's writing arrives as a suggestion and a person decides whether it becomes part of the document.

<!-- https://docs.crusible.dev/reference/surfaces/docs/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


Docs is a block document that belongs to a
<a class="docs-term" href="/reference/glossary/#channel">channel</a>. A block is a paragraph, a
heading, a list or a code sample, and each one carries the person or
<a class="docs-term" href="/reference/glossary/#agent">agent</a> who wrote it. A plan produced in
the channel opens here as an inline view rather than as a separate document.

## A suggestion is not an edit

Everything an agent writes into a document arrives as a suggestion, shown
inline beside the text it would change and marked with the agent that drafted
it. The document reads exactly as it did before until a person presses
**Accept**. That is the whole rule of the surface: the document never changes
underneath you.

The header carries a pill counting the suggestions waiting on the document, so
the state of the document is answerable without opening it. Rejecting a
suggestion leaves the document as it was and leaves the agent's proposal in
the record.

## Attribution and comments

**Contributors** lists every person and agent who has written in the document.
Blocks carry their author, and comments sit in the margin against the block
they are about rather than at the end of the document. A reader who wants to
know who put a sentence there can answer that in the document itself.

## What stays in the conversation

The document is the artifact; the
<a class="docs-term" href="/reference/glossary/#conversation">conversation</a> is still the record
of the work. When an agent drafts something worth reading, it posts an
<a class="docs-term" href="/reference/glossary/#artifact-card">artifact card</a> that previews the
document and opens this surface. The decision to accept a suggestion is a
decision like any other, and it belongs to a person.

## Where the pages live

Docs runs <a class="docs-term" href="/reference/glossary/#first-party">first-party</a> or on a
<a class="docs-term" href="/reference/glossary/#connected">connected</a>
<a class="docs-term" href="/reference/glossary/#provider">provider</a>. With Notion as the provider
behind Docs, Notion keeps the pages: this surface renders them, and agents
operate them through Notion. Which is the case for your workspace is answered
by the provider block above, and switching between the two changes this surface
and nothing else about the channel.