Concept reference

Memory Curation

How a finished case becomes durable, citable knowledge for future runs — with typed applicability bounds and cross-case invalidation.

1 min read

What memory curation is

Step 23 of the lifecycle (ADR 0028) consolidates a finished case into a published MemoryRecord: a typed claim with applicability bounds, citations, validation lineage, and a cite-cascade invalidation invariant. The agent uses curated memory to short-circuit future research, not to repeat unsupported assertions.

What gets curated

  • Validated solver-setup choices (e.g., "k-ω SST for adverse pressure gradient flows around Re=10⁵–10⁷").
  • Mesh strategies that passed the quality gate for a geometry class.
  • BC patterns that produced converged, validated runs.
  • Failures and their root causes — anti-patterns matter as much as patterns.

Applicability bounds

Each record declares the solver family, physics regime, geometry class, mesh-quality range, and validation evidence that supports it. Recall is filtered against the new case's properties — no leaking a viscous-flow claim into a high-Re turbulent context.

Cite-cascade invalidation

If a memory record is amended or retracted, every downstream case that cites it is flagged for review. Trust travels with provenance, not with stale text.

Was this page helpful?

Edit this page on GitHub

Search docs

Find pages across the SimPilot docs.