Team Sync is being designed to carry approved project standards and decisions across members and their coding agents, without uploading every person's raw memory or asking reviewers to approve hundreds of fragments.
Team Sync is not available yet, so this page describes the intended model. Today you can share memory with colleagues through ordinary files or a private Git repository, which is free and covered in Project Config.
One file, one decision
Docmancer generates a complete Team memory file on a member's machine, and the local app shows the full Markdown diff and exclusion report. That local generation and complete-file approval step works today, but the approved file remains local. Hosted publication is disabled until Team workspaces, promotion state, and separate encryption domains are enforced end to end.
Local privacy boundary
Before upload, Docmancer restricts sources to the intended project and policy scope, then checks for likely secrets, personal data, local paths, and machine identifiers. The hosted service would receive encrypted content and opaque publication metadata only.
This filtering runs locally today, but Personal and Team memory do not yet use separate encryption domains, which is one of the reasons Team Sync is not available. The separation described here is a design intent, not yet an enforced cryptographic invariant.
What remains personal
Personal preferences, unrelated project memory, raw session evidence, provider credentials, and local paths stay outside the generated shared file.
What the hosted service would coordinate
Paid Team workspaces are intended to manage membership, roles, approved devices, publication state, encrypted retention, and account deletion, while local generation, review, encryption, decryption, and agent delivery stay on approved devices. None of that cross-person coordination is available yet, because invitations cannot be accepted and a second person cannot join a workspace.