- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
39 lines
2.0 KiB
Markdown
39 lines
2.0 KiB
Markdown
---
|
|
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.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`
|
|
- 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
|
|
- 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:
|
|
|
|
1. What was synchronized
|
|
2. Which files were updated
|
|
3. Which facts were promoted or intentionally skipped
|