fidelity-ai-workspace/ai/context/process/context-maintenance.md

Context Maintenance

Goal

Keep this workspace useful as living memory instead of a pile of disconnected notes.

---

Stable Rules

• Update canonical context when a durable fact changes.
• Prefer correcting stale context over appending contradictory notes.
• Use the smallest correct destination:
  • ai/logs/YYYY-MM-DD.md for daily progress and evolving findings
  • ai/state/current.md for near-term active work
  • ai/work-items/*.md for canonical Jira-linked active work
  • ai/state/work-items.md for the compact active-work summary
  • ai/context/ for durable project knowledge
  • ai/context/people/ for named person context
  • .opencode/commands/, prompts/, .opencode/agents/, .opencode/skills/, or knowledge/ for reusable behavior rules that control how the workspace responds

---

Ingestion Rules

• Treat Mattermost, Slack history, and direct prompts as potential memory sources.
• Do not promote failed syncs or tooling errors as project facts.
• Promote repeated durable patterns from historical archives into stable context when confidence is high.
• Keep old status-only details archive-only unless they still change current understanding.
• Treat user corrections about command output, prompt structure, memory handling, or agent behavior as inputs to the operational surface, not just as daily notes.

---

Curation Rule

• If a new stable context file is added, keep project.md and index.md aligned so future sessions can discover it quickly.
• If a new rule affects a slash command or reusable prompt, update that command or prompt directly so the behavior changes on the next run.