fidelity-ai-workspace/.opencode/commands/mattermost-sync.md at b82194bc555d7861d0fb8c2bd6d7afeecab82e4a

Files

david.delagneau b82194bc55 Add daily logs and templates for Fidelity project

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

2026-04-16 16:01:19 -06:00

2.2 KiB

Raw Blame History

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:

AIW_MATTERMOST_SYNC_CMD
compatibility fallback: FIDELITY_MATTERMOST_SYNC_CMD
fallback: bash scripts/mattermost/sync.sh

Run the command and use its output as fresh communication context:

!if [ -n "$AIW_MATTERMOST_SYNC_CMD" ]; then bash -lc "$AIW_MATTERMOST_SYNC_CMD"; elif [ -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

Use this command implicitly when the user asks for the latest or last Mattermost message, especially messages from Jeff or the current manager.

Then:

if the command fails, stop there and do not edit any workspace files
use ai/inbox/mattermost-latest.md if it exists and is non-empty
otherwise use scripts/mattermost/generated/mattermost_context.jsonl if it exists and is non-empty
apply the memory promotion rules from vault/03-context/process/memory-promotion-rules.md, falling back to knowledge/memory-promotion-rules.md only if needed
treat Mattermost output as live communication evidence; the agent decides what becomes promoted memory
automatically promote explicit, project-relevant, high-confidence facts
default destination is vault/06-daily/$(date +%F).md
update vault/01-current/current-work.md only for facts that materially change the current work window
update vault/02-work-items/*.md for explicit Jira IDs, approved titles, points, scope, and status notes
keep vault/01-current/work-items.md aligned as the compact summary of active ticket files
use ai/* paths only as temporary compatibility fallback
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

2.2 KiB Raw Blame History

2.2 KiB

Raw Blame History