david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Refactor communication context to generalize from Jeff to current manager and enhance people management structure

Browse Source
This commit is contained in:
David Delagneau
2026-04-09 15:39:46 -06:00
parent 9255055c43
commit 332fbca1c5
23 changed files with 182 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
ai/AGENTS.md
View File

@@ -13,7 +13,7 @@ This workspace is used to maintain context, organize communication, and draft ac
- Keep project context current
- Convert Mattermost communication into structured notes
- Draft standups and manager updates
- Improve technical messages before sending them to Jeff
- Improve technical messages before sending them to the current manager or stakeholder
- Translate rough notes into concise US English without changing meaning
---
@@ -36,7 +36,7 @@ Always structure technical updates as:
2. Observation
3. Action
When drafting messages for Jeff:
When drafting messages for a manager or stakeholder:
- be concise
- be specific
@@ -72,6 +72,7 @@ When drafting messages for Jeff:
- Promote to `ai/state/current.md` only when the fact changes the active work window
- Maintain `ai/state/work-items.md` with explicit Jira IDs, approved titles, and currently relevant scope/status notes
- Promote to `ai/context/project.md` only when the fact is durable beyond the current work window
- Maintain `ai/context/people/` when repeated names, roles, or stakeholder relationships become useful for future sessions
- Update existing memory when the new information is a correction, clarification, or refinement of something already stored
- Prefer updating stable project context over appending generic operational summaries
- Do not create daily log entries for tooling activity, sync status, or generic chat noise
@@ -80,7 +81,9 @@ When drafting messages for Jeff:
- When the user corrects or changes stable context, update the canonical file directly:
- `ai/state/current.md` for current focus or active concerns
- `ai/context/project.md` for durable project knowledge
- `ai/context/people/jeff.md` for communication preferences
- `ai/context/people/manager.md` for communication preferences
- `ai/context/people/index.md` for active roster mapping
- `ai/context/people/<person>.md` for person-specific context
- `ai/context/decisions/*.md` for confirmed decisions
- Prefer updating stale context over leaving conflicting statements in different files
- If context is still uncertain, record it in the daily log rather than promoting it to a stable context file