Files
fidelity-ai-workspace/.opencode/commands/promote-project-context.md
david.delagneau dbc1894e27 Add project-knowledge structure and templates
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.
2026-04-17 15:52:08 -06:00

2.7 KiB

description
description
Manually promote confirmed project facts into Fidelity workspace memory

Use this only when you want an explicit manual promotion pass.

Read:

@core/README.md @core/memory/operational-memory.md @project-knowledge/01-current/current-work.md @project-knowledge/01-current/work-items.md @project-knowledge/03-context/project.md @project-knowledge/03-context/systems/index.md @project-knowledge/03-context/workstreams/index.md @project-knowledge/03-context/workstreams/flow-page-references.md @project-knowledge/03-context/process/index.md

Today's log, if present:

!if [ -f project-knowledge/06-daily/$(date +%F).md ]; then cat project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi

Current Mattermost inbox, if present:

!if [ -f ai/inbox/mattermost-latest.md ]; then cat ai/inbox/mattermost-latest.md; else echo "No Mattermost inbox file is available."; fi

Generated Mattermost context, if present:

!if [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No generated Mattermost context is available."; fi

User direction or facts to promote:

$ARGUMENTS

Instructions:

  • Promote only confirmed project-relevant facts
  • Ignore tooling noise and sync status
  • Update the smallest correct set of files among:
    • project-knowledge/06-daily/$(date +%F).md
    • project-knowledge/01-current/current-work.md
    • project-knowledge/02-work-items/*.md
    • project-knowledge/01-current/work-items.md
    • project-knowledge/03-context/project.md
    • project-knowledge/03-context/systems/*.md
    • project-knowledge/03-context/workstreams/*.md
    • project-knowledge/03-context/process/*.md
    • project-knowledge/05-decisions/*.md
    • .opencode/commands/*.md when command behavior needs to change
    • prompts/*.md when a reusable output template needs to change
    • .opencode/agents/*.md or AGENTS.md when default agent behavior needs to change
    • .opencode/skills/*/SKILL.md when a specialized workflow needs to change
    • project-knowledge/00-start/*.md when durable project onboarding guidance needs to change
    • agent-memory/**/*.md when agent learning, promotion, verification, or self-maintenance behavior needs to change
  • Prefer concrete project updates over broad summaries
  • If a fact is still ambiguous, do not promote it
  • If the promoted fact is a reusable behavior correction, do not leave it only in a daily log; update the operational file that controls future behavior
  • Use this command when you want a deliberate manual pass beyond the agent's default automatic memory maintenance

Return:

  1. Updated files
  2. Promoted project facts
  3. Remaining uncertainty