Skip to main content
Project Intelligence

Document editor

The document editor is the primary surface of collaborative review. It works with knowledge-base systems: Confluence, Bitrix24 (knowledge base), and Yandex Wiki. The agent proposes a new version of a document, and you decide precisely what goes in: you accept the blocks you need, reject the rest, add your own edits by hand — and only then publish.

This replaces the "push and pray" model: documents are no longer updated wholesale without your deliberate control.

Supported systems​

SystemWhat it is
ConfluencePage-based knowledge base. The editor is built on the same technology as Confluence: content is exchanged in the Atlassian Document Format (ADF), and the interface uses the same editor engine — so pages look and behave as in Confluence, with no loss of structure or formatting.
Bitrix24 (knowledge base)The knowledge base of the Bitrix24 portal: company knowledge sections and pages.
Yandex WikiA corporate wiki system: knowledge sections and pages of the organization.

The review mechanics are the same regardless of the system: a draft, marked blocks, a decision on each block, publishing, and verification. Only the section structure and the field set of the target system differ.

User flow​

  1. Proposal. The agent prepares a new version of the document (on your request or as part of a task, e.g. after /report or a requirements update).
  2. Review. A draft of the document opens in the working area. Changes are marked:
    • added text — highlighted;
    • removed text — struck through;
    • next to each change — Accept and Reject buttons.
  3. Editing. You can manually edit any part of the draft right in the editor.
  4. Publish. The Publish button publishes the final version to the chosen system as a new version of the document — in a single atomic action.
  5. Verification. The system checks that the document was actually updated in the target system and reports the result with a link.

New documents​

You can start from a blank draft not tied to an existing document:

  • the editor opens an empty document with an editable title;
  • on the first save you choose where it will be placed in the target system: a Confluence space, a Bitrix24 knowledge-base section, or a Yandex Wiki space;
  • creation goes through the same channel as regular publishes: no hidden intermediate versions.

When to use it​

  • Updating knowledge-base pages based on project decisions.
  • Preparing and approving process documents (processes, procedures, instructions).
  • Keeping documentation in sync with the actual project state that the agent extracted from issues and correspondence.

Limitations​

  • Moving an already published document to a different space from the editor is not supported — that is an administrative operation.
  • The agent never publishes a document without your confirmation: publishing is always initiated by a person.
  • Mermaid diagrams are stored as source code; rendering them in Confluence requires a Mermaid rendering app (e.g., Mermaid diagrams viewer).