fidelity-ai-workspace/.agents/workflows/mattermost-sync.md at antigravity

Files

david.delagneau 1ad707373a Add daily logs and templates for project fidelity

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

2026-05-21 12:28:07 -06:00

2.4 KiB

Raw Permalink Blame History

description

description
Sync Mattermost context and automatically promote high-confidence project memory

// turbo-all Use the configured Mattermost sync command and/or local proxy mirror evidence 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

Fresh Mattermost evidence, preferring the proxy mirror:

!python3 scripts/mattermost-proxy/read-context.py --mode latest

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
prefer the local proxy mirror via scripts/mattermost-proxy/read-context.py --mode latest when it has evidence
otherwise use workspaces/fidelity/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 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 workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md
update workspaces/fidelity/project-knowledge/01-current/current-work.md only for facts that materially change the current work window
update workspaces/fidelity/project-knowledge/02-work-items/*.md for explicit Jira IDs, approved titles, points, scope, and status notes
keep workspaces/fidelity/project-knowledge/01-current/work-items.md aligned 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

2.4 KiB Raw Permalink Blame History

2.4 KiB

Raw Permalink Blame History