fidelity-ai-workspace/.opencode/commands/sync-context.md

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 @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

Today's existing log, if present:

!if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/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 vault/01-current/ or vault/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: 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/*.md
  • prompts/*.md
  • .opencode/agents/*.md
  • .opencode/skills/*/SKILL.md
• Update the appropriate files directly
• When updating a canonical vault 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