1.5 KiB
1.5 KiB
description
| description |
|---|
| Sync Mattermost context and automatically promote high-confidence project memory |
Use the configured Mattermost sync command to fetch fresh communication context and maintain workspace memory automatically.
Preferred command sources:
FIDELITY_MATTERMOST_SYNC_CMD- fallback:
bash scripts/mattermost/sync.sh
Run the command and use its output as fresh communication context:
!if [ -n "$FIDELITY_MATTERMOST_SYNC_CMD" ]; then bash -lc "$FIDELITY_MATTERMOST_SYNC_CMD"; elif [ -f scripts/mattermost/sync.sh ]; then bash scripts/mattermost/sync.sh; else echo "No Mattermost sync command is configured."; fi
Then:
- if the command fails, stop there and do not edit any workspace files
- use
ai/inbox/mattermost-latest.mdif it exists and is non-empty - otherwise use
scripts/mattermost/generated/mattermost_context.jsonlif it exists and is non-empty - apply the memory promotion rules from
knowledge/memory-promotion-rules.md - automatically promote explicit, project-relevant, high-confidence facts
- default destination is
ai/logs/$(date +%F).md - update
ai/state/current.mdonly for facts that materially change the current work window - update
ai/state/work-items.mdfor explicit Jira IDs, approved titles, points, scope, and status notes - do not write tooling noise, sync status, or generic chat chatter into project memory
- if a fact is ambiguous, skip it rather than asking the user what to do
Return:
- What was synchronized
- Which files were updated
- Which facts were promoted or intentionally skipped