cases

To record incident cases during conversations, you save a Markdown file under cases/YYYY-MM-DD-<slug>.md using a Case File Template, then update the cases/index.md file to include the new entry for post-mortem reviews.

Maintaining a searchable index of decision logs involves using a defined directory structure and an index file template, ensuring organized case templates and consistent field classification for reliable retrieval.

Yes, you can use this system for cross-session case record-keeping without conflicts, because it implements a safe write-flow using flock locks to ensure concurrent sessions do not overwrite each other.

Yes, the case template approach supports immutable audit trails for knowledge management by enforcing a safe write-flow that preserves historical records without deletion, ensuring a reliable audit trail.

A limitation of using Markdown files for case retrieval is that navigating records relies entirely on manually updating the index.md file, requiring strict adherence to naming rules and directory structures for accurate indexing.

The case file template works for knowledge management by providing standardized Markdown fields to document critical events, automatically sinking experience during conversations to enable subsequent retrieval and retrospective analysis.