usage

Team workspaces

The problem Team Sync is being designed to solve, how the planned model works, and why it is not available yet.

Updated

The context your agents have accumulated about a feature is some of the most useful writing in the whole project, and today it is stranded on one machine where nobody else on the team can reach it. Team Sync is the tier being built for that problem, so that a decision approved once reaches the coding agents of the other engineers, PMs, and designers who need it.

Team Sync is not available yet. This page describes the product being designed rather than something you can switch on today. If you want Docmancer memory on more than one of your own machines, Personal Sync is open in early access.

The planned model

A member's local client will select project-scoped, policy-cleared files and filter risky material. A reviewer will see the complete diff and exclusion report before approval. The approved revision will be encrypted and signed locally, then published as ciphertext, so the hosted service never receives plaintext memory.

Roles are intended to separate the decisions people actually make:

  • Owners would manage billing, recovery, deletion, devices, invitations, and exports.
  • Administrators would manage devices, invitations, exports, and workspace operations.
  • Reviewers would approve or reject a complete Team memory revision.
  • Members would receive approved files and prepare new complete-file revisions locally.

Why it is not available yet

Two things have to be true before a Team workspace can be sold, and neither is finished. Invitations cannot yet be accepted, so a second person cannot join a workspace at all. Personal and Team memory also do not yet use separate encryption domains, which means the boundary between your raw local tree and an approved shared file is not yet enforced by encryption rather than only by local filtering. Publishing before both are done would risk disclosing raw harvested memory to colleagues, so it is not being shipped in that state.

Local work remains free

Local discovery, Ask, Shared Memory, Library, agent integrations, and complete-file review remain available without any subscription. Self-managed sharing through ordinary files or a private Git repository also stays free, and it will not be taken away when Team Sync arrives.