david.delagneau
dbc1894e27
- 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.
2.1 KiB
2.1 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:
AIW_MATTERMOST_SYNC_CMD- Fidelity profile alias:
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.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
agent-memory/memory/promotion-rules.md - 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
project-knowledge/06-daily/$(date +%F).md - update
project-knowledge/01-current/current-work.mdonly for facts that materially change the current work window - update
project-knowledge/02-work-items/*.mdfor explicit Jira IDs, approved titles, points, scope, and status notes - keep
project-knowledge/01-current/work-items.mdaligned as the compact summary of active ticket files - 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