Files
david.delagneau 1ad707373a Add daily logs and templates for project fidelity
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
2026-05-21 12:28:07 -06:00

66 lines
3.6 KiB
Markdown

---
description: Update workspace memory from new facts, corrections, or contextual notes
---
Use this command when new information should become part of the persistent workspace context.
Read:
@README.md
@workspaces/fidelity/project-knowledge/00-start/start-here.md
@workspaces/fidelity/project-knowledge/01-current/current-work.md
@workspaces/fidelity/project-knowledge/01-current/work-items.md
@workspaces/fidelity/project-knowledge/03-context/project.md
@workspaces/fidelity/project-knowledge/03-context/systems/index.md
@workspaces/fidelity/project-knowledge/03-context/workstreams/index.md
@workspaces/fidelity/project-knowledge/03-context/workstreams/flow-page-references.md
@agent-memory/memory/context-maintenance.md
@workspaces/fidelity/project-knowledge/04-people/manager.md
@workspaces/fidelity/project-knowledge/04-people/index.md
Today's existing log, if present:
!`if [ -f workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md ]; then cat workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi`
New information to incorporate:
$ARGUMENTS
Instructions:
- use `workspace-memory-curation` when available
- Treat direct user corrections and learning-session updates as memory sources.
- For learning-session updates, prefer durable project understanding over transient ticket status.
- Route durable learning to architecture/process/system/workstream notes; route only truly current operational state to `workspaces/fidelity/project-knowledge/01-current/` or `workspaces/fidelity/project-knowledge/06-daily/`.
- If the new information corrects the agent's uncertainty handling or recurring behavior, update the command, prompt, agent, skill, or process rule that controls that behavior.
- Decide whether the new information belongs in:
- today's daily note: `workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md`
- current work: `workspaces/fidelity/project-knowledge/01-current/current-work.md`
- work items: `workspaces/fidelity/project-knowledge/02-work-items/*.md`
- active work summary: `workspaces/fidelity/project-knowledge/01-current/work-items.md`
- project overview: `workspaces/fidelity/project-knowledge/03-context/project.md`
- systems: `workspaces/fidelity/project-knowledge/03-context/systems/`
- workstreams: `workspaces/fidelity/project-knowledge/03-context/workstreams/`
- process: `workspaces/fidelity/project-knowledge/03-context/process/`
- manager mapping: `workspaces/fidelity/project-knowledge/04-people/manager.md`
- people roster: `workspaces/fidelity/project-knowledge/04-people/index.md`
- people notes: `workspaces/fidelity/project-knowledge/04-people/*.md`
- decisions: `workspaces/fidelity/project-knowledge/05-decisions/`
- `.agents/workflows/*.md`
- `.agents/rules/*.md`
- `prompts/*.md`
- Update the appropriate files directly
- When updating a canonical project note, maintain frontmatter properties used by Obsidian Bases, including `updated`, `systems`, `workstreams`, `people`, `related`, `focus`, `work-items`, and `blockers` when applicable
- If an existing statement became stale, replace or refine it
- If the new information changes how this workspace should behave, update the linked command, prompt, agent, skill, or knowledge file that enforces that behavior
- Do not invent missing facts
- Keep uncertain information in the daily log instead of promoting it to stable context
- Do not ask for promotion confirmation when the correct destination is already clear
- Prefer correcting canonical memory over appending duplicate summaries
After editing, respond with:
1. Updated files
2. What changed in the persistent context
3. Any uncertainty that remains