Shared memory deserves a review trail.

Members submit encrypted memory proposals. Reviewers approve, reject, or request changes, and the client applies approved state locally before agents recall it.

• Owner and administrator controls
• Reviewer and member roles
• Invitations and seat lifecycle
• Webhook-driven subscription entitlement

• Versioned policy distribution and device acknowledgement
• Retention, export, SSO, and SCIM controls
• Operational audit events and secret-risk summaries
• Managed private deployment design

Teams that do not need managed hosting can keep using Git-versioned memory under .docmancer/memory. Hosted team features add coordination and administration, not better local recall.