context-keeper

To preserve project context across sessions, maintain persistent governance registers like DECISIONS.md and RISKS.md at your project root. This ensures critical decisions and assumptions survive session resets and enable fast resumption.

Tracking project decisions and risks in markdown files requires appending entries with dates, rationale, and status fields to dedicated registers. This approach preserves governance traceability and maintains a clear history of project assumptions.

Maintaining governance history with debt registers involves enforcing append-only entries and cross-register linking. This preserves traceability by connecting related items across DEBT.md, DECISIONS.md, ASSUMPTIONS.md, and RISKS.md.

Yes, you can restore project context from markdown registers after losing a session. By reading the persistent DECISIONS.md, ASSUMPTIONS.md, RISKS.md, and DEBT.md files, you can quickly resume work with full governance traceability.

Tracking project assumptions does not require special frameworks or dependencies. It applies to any project using standard markdown files at the root directory to capture governance artifacts without external tools.

Append-only entry matters for project risk registers because it prevents the loss of historical context. Preserving the original entry alongside status updates ensures complete traceability and an accurate governance history.