david.delagneau
b82194bc55
- 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.
2.8 KiB
description
| 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 @ai/AGENTS.md @vault/00-start/start-here.md @vault/01-current/current-work.md @vault/01-current/work-items.md @vault/03-context/project.md @vault/03-context/systems/index.md @vault/03-context/workstreams/index.md @vault/03-context/workstreams/flow-page-references.md @vault/03-context/process/context-maintenance.md @vault/04-people/manager.md @vault/04-people/index.md @ai/context/index.md @ai/context/project.md @ai/context/systems/index.md @ai/context/workstreams/index.md @ai/context/workstreams/flow-page-references.md @ai/context/process/context-maintenance.md @ai/context/people/manager.md @ai/context/people/index.md @ai/work-items/index.md @ai/state/current.md @ai/state/work-items.md @knowledge/workspace-model.md @knowledge/communication-rules.md @knowledge/agent-memory-rules.md @knowledge/memory-promotion-rules.md
Today's existing log, if present:
!if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/06-daily/$(date +%F).md; elif [ -f ai/logs/$(date +%F).md ]; then cat ai/logs/$(date +%F).md; else echo "No daily note exists for today yet."; fi
New information to incorporate:
$ARGUMENTS
Instructions:
- use
workspace-memory-curationwhen available - Decide whether the new information belongs in:
- today's daily note:
vault/06-daily/$(date +%F).md - current work:
vault/01-current/current-work.md - work items:
vault/02-work-items/*.md - active work summary:
vault/01-current/work-items.md - project overview:
vault/03-context/project.md - systems:
vault/03-context/systems/ - workstreams:
vault/03-context/workstreams/ - process:
vault/03-context/process/ - manager mapping:
vault/04-people/manager.md - people roster:
vault/04-people/index.md - people notes:
vault/04-people/*.md - decisions:
vault/05-decisions/ .opencode/commands/*.mdprompts/*.md.opencode/agents/*.md.opencode/skills/*/SKILL.md
- today's daily note:
- Write to
vault/first when a canonical note exists; useai/*andknowledge/*only as temporary compatibility fallback - Update the appropriate files directly
- 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:
- Updated files
- What changed in the persistent context
- Any uncertainty that remains