memory

To maintain a single source of truth (SSOT), initialize the project memory and use cross-tool recall to keep decisions, patterns, and learnings aligned and traceable across environments. It coordinates SSOT initialization and merging.

The best way to reuse past learnings is to query the unified harness memory using harness_mem_* MCP interfaces. This provides built-in search capabilities to retrieve and audit previously recorded decisions and patterns.

To migrate an existing workflow into a traceable SSOT memory structure, use the workflow migration process to transition plans and historical data. You can merge existing plans.md files directly into the new SSOT framework.

Yes, you can promote temporary memory items into the permanent project SSOT using explicit promotion rules. This syncs long-term memory records to the SSOT, ensuring reusable and auditable outputs are preserved.

Yes, SSOT memory management works without external dependencies, relying instead on built-in harness memory interfaces. It uses explicit promotion rules and internal references to coordinate cross-tool recall and ensure auditable outputs.