- 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.
3.0 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 @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 @workspaces/fidelity/project-knowledge/03-context/process/index.md
Today's 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
Current Mattermost inbox, if present:
!python3 scripts/mattermost-proxy/read-context.py --mode latest
Generated Mattermost context, if present:
!if [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No legacy 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:
workspaces/fidelity/project-knowledge/06-daily/$(date +%F).mdworkspaces/fidelity/project-knowledge/01-current/current-work.mdworkspaces/fidelity/project-knowledge/02-work-items/*.mdworkspaces/fidelity/project-knowledge/01-current/work-items.mdworkspaces/fidelity/project-knowledge/03-context/project.mdworkspaces/fidelity/project-knowledge/03-context/systems/*.mdworkspaces/fidelity/project-knowledge/03-context/workstreams/*.mdworkspaces/fidelity/project-knowledge/03-context/process/*.mdworkspaces/fidelity/project-knowledge/05-decisions/*.md.opencode/commands/*.mdwhen command behavior needs to changeprompts/*.mdwhen a reusable output template needs to change.opencode/agents/*.mdorAGENTS.mdwhen default agent behavior needs to change.agents/skills/*/SKILL.mdwhen a specialized workflow needs to changeworkspaces/fidelity/project-knowledge/00-start/*.mdwhen durable project onboarding guidance needs to changeagent-memory/**/*.mdwhen 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:
- Updated files
- Promoted project facts
- Remaining uncertainty