Document explicit memory destinations and membership privacy
docs: refresh wiki for current Dense-Mem behavior
Refactor documentation for clarity and accuracy across multiple files - Updated "Portals And API Keys" to reflect changes in correction workflows and removed outdated placement review sections. - Revised "Quick Start" to clarify upgrade processes and migration boundaries, emphasizing the importance of batch submissions. - Enhanced "Recall Feedback" to include new snapshot retention requirements and feedback submission constraints. - Adjusted "Recall Ranking" references for consistency in technical documentation. - Modified "Relationship Model And Lifecycle" to clarify submission processes and error handling, including updates to flowcharts. - Updated "Request Lifecycle And Security" to reflect changes in normalizer responses and submission handling. - Revised "Technical Reference" to clarify submission requirements and error handling, removing references to outdated processes. - Adjusted "Telemetry" metrics to align with recent changes in submission dispositions. - Updated "Using Dense Mem" to clarify the normalizer's role and submission processes, removing references to outdated states. - Revised "Write Pipeline" to reflect changes in submission handling, including the removal of the awaiting review state and updates to error handling.
Refactor documentation for Dense-Mem API and workflows - Updated the Request-Lifecycle-And-Security.md to clarify untrusted prompt data and added Memory Space Authorization section. - Revised Technical-Reference.md to enhance clarity on contract principles, relationship requirements, and evidence handling. - Enhanced User-Portal-SSO.md with new endpoints for credential management and clarified SSO member session behavior. - Improved Using-Dense-Mem.md to reflect changes in evidence submission and relationship proposals, emphasizing logical relationships. - Updated Write-Pipeline.md to align with new evidence and relationship handling, including changes to submission states and assessment processes.
docs: update multiple documentation files for clarity and accuracy
Refine data model and security event descriptions, enhance development documentation, and clarify community assembly processes - Updated `evidence_security_events` to specify the nature of append-only scans and audit events. - Improved clarity in the Development and Testing documentation regarding injection boundaries and quarantine processes. - Enhanced the Evaluation document to specify the conditions under which unsafe corpus input is rejected. - Revised the Home documentation to better outline the intake rejection and submission processes. - Expanded the Recall Ranking document to clarify community assembly and relationship fallback mechanisms. - Updated the Relationship Model and Lifecycle documentation to reflect changes in evidence security event handling. - Clarified request lifecycle and security processes, emphasizing the role of deterministic scans and quarantine protocols. - Improved the Write Pipeline documentation to specify conditions for intake rejections and the handling of hidden controls.
Document tier-free Relationship architecture
Document nightly conflict reviewer model
Document durable cross-profile conflict review
Document V2 search contract generations
Update semantic memory v2 architecture docs
Document recall ranking