Files
fidelity-ai-workspace/vault/03-context/process/context-maintenance.md
david.delagneau b82194bc55 Add daily logs and templates for Fidelity project
- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.
2026-04-16 16:01:19 -06:00

1.8 KiB

type, project, status, updated, tags
type project status updated tags
process fidelity active 2026-04-16
process
fidelity

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:
    • vault/06-daily/YYYY-MM-DD.md for daily progress and evolving findings
    • vault/01-current/current-work.md for near-term active work
    • vault/02-work-items/*.md for canonical Jira-linked active work
    • vault/01-current/work-items.md for the compact active-work summary
    • vault/03-context/ for durable project knowledge
    • vault/04-people/ for named person context
    • .opencode/commands/, prompts/, .opencode/agents/, .opencode/skills/, vault/00-start/, or vault/03-context/process/ 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.