Share it

Collaborative Document Workspace

Co-author a document without version-hell.

A shared workspace where multiple authors concurrently draft, comment, redline, and version a single document in place. Presence, suggestion mode, and thread-level comments replace the email-and-attachment loop — the workspace is the artefact, live and singular.

Shape

author Aauthor Bauthor C3suggestion modeONE CANONICAL DOCversionspresence · comments · redlines · history

Operational dimensions

Human co-pilot

Person and system work side-by-side.

On demand

Fires when a user asks.

Low data gravity

Light state; replaceable any time.

Closed surface

No external systems on either side.

Inputs

  • author roster with permissions
  • seed document content or blank canvas
  • comments and inline suggestions
  • version checkpoints

Outputs

  • canonical shared document state (current version)
  • comment and thread state
  • redline / suggestion history
  • version history with named checkpoints

Mechanism

Provides a shared document / space where multiple authors concurrently co-author, comment, redline, and version a single artefact in place — the workspace itself IS the artefact-in-progress.

Why this is a primitive

Cannot be decomposed — the operation is one act of being-a-multi-author-document-workspace: concurrent edit, presence, comment, redline, version history, on a single shared artefact. Strip the multi-author concurrency and you have a single-author editor (no primitive). Strip the document-as-shared-artefact and you have a chat tool. The combination — many authors on one document-shaped artefact — is irreducible. Note: this primitive sits at the share-it / act-on-it-together seam. Routes to share-it because the load-bearing operation is authoring-an-artefact-together (the artefact is the transmission), not coordinating multi-party WORK on shared state (no per-instance lifecycle, no routing, no gating). When the workspace is wrapped with approvals / state machines / cross-org checklists, it composes with act-on-it-together primitives (see deal-room composition).

Where it shows up

Consulting team — multiple analysts co-author a client deliverable with tracked changes and threaded review comments, then export as a final doc
Legal team — redlines a contract in a shared workspace with counterparty suggestions resolved in-thread before sending
Product team — collaboratively edits a PRD with design, engineering, and PM contributing concurrently, all in one canonical document

Related primitives

Tags

human-collaborativedocumentreal-timestructured-data

See where it fits.

Primitives are configured into named solution shapes for each client’s domain. The fastest next step is a conversation about which shape fits your problem.

Start a conversation