workflow-memory

Prevent markdown bloat in workflow documentation by separating strategic metadata WF-* nodes from heavy agent-output execution artifacts. This approach enforces Just-In-Time context protection and strict lifecycle cleanup by moving completed artifacts to closed directories.

JIT context isolation for markdown memory workflows is a mechanism that separates Baseline context from Append context. It ensures deterministic native memory by strictly managing how metadata and execution artifacts are loaded and appended during epic-driven projects.

Set up a native markdown workflow graph by creating WF-* nodes and grouping them into epic subtrees. This method uses canonical filename rules to maintain a clean historical graph without requiring external tools like Obsidian or MCP.

No, this markdown memory workflow does not require Obsidian or MCP to operate. It uses strictly native file paths to coordinate deterministic relational memory without adding external software overhead to your project.

The best way to manage agent-output baselines in epic-driven projects is to enforce strict document lifecycle cleanup. This involves preserving WF-* nodes for history while moving completed execution artifacts to a closed directory to maintain a navigable graph.

You should move workflow artifacts to a closed directory during lifecycle cleanup after execution is complete. This action prevents markdown bloat while preserving the original WF-* strategic metadata nodes to maintain a navigable historical workflow graph.