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

ai/AGENTS.md

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

ai/context/people/README.md

@@ -0,0 +1,19 @@
+# People Context
+
+Store reusable human context here.
+
+Use this directory for:
+
+- who is who
+- current role ownership
+- communication preferences
+- recurring stakeholders
+- stable relationship between people and project work
+
+Guidelines:
+
+- use one file per named person when that person matters repeatedly
+- keep `manager.md` as the role mapping for the current active manager
+- keep `index.md` as the quick roster for the active project
+- do not put secrets here
+- do not invent roles; use qualifiers when uncertain

ai/context/people/index.md

@@ -0,0 +1,23 @@
+# People Index
+
+## Active Roles
+
+- Manager: [jeff-dewitte.md](./jeff-dewitte.md)
+
+## Known People
+
+- [jeff-dewitte.md](./jeff-dewitte.md)
+  Current direct manager for the active Fidelity project.
+
+- [santosh.md](./santosh.md)
+  Project-related contact seen in issue discussions. Exact formal role should be clarified if it becomes important for repeated communication.
+
+## Usage
+
+When a person appears repeatedly in project communication, create or update their file here so the agent can reuse:
+
+- name
+- role
+- relationship to the project
+- communication expectations
+- important context about how they influence work

ai/context/people/jeff-dewitte.md

@@ -1,8 +1,8 @@
-# Jeff
+# Jeff DeWitte
 
 ## Role
 
-Direct supervisor.
+Current direct manager for the active Fidelity project.
 
 ---
 
@@ -11,7 +11,7 @@ Direct supervisor.
 - Native US English
 - Prefers clear, concise updates
 - Needs accurate scope, not vague reassurance
-- Should be informed of meaningful progress from this machine through Mattermost
+- Frequently asks for precise reproducibility, auth context, and regression scope
 
 ---
 
@@ -31,10 +31,8 @@ Good updates usually clarify:
 
 ---
 
-## AI Usage
+## Influence On Work
 
-AI should help:
-
-- translate rough Spanish notes into natural US English
-- tighten wording before sending
-- remove ambiguity without changing technical meaning
+- Story titles, points, and scope discussions with Jeff are often worth remembering
+- Jeff approvals can change what belongs in current state or work-item memory
+- Jeff feedback is often a signal to tighten wording before communicating externally

ai/context/people/manager.md

@@ -0,0 +1,30 @@
+# Manager
+
+## Current Holder
+
+- Name: Jeff DeWitte
+- Profile: [jeff-dewitte.md](./jeff-dewitte.md)
+
+---
+
+## Role
+
+Direct supervisor or primary reporting manager for the active project.
+
+---
+
+## Usage
+
+This file maps the current project role to the actual person.
+
+If the active manager changes in a future project, update this file to point to the new person while preserving their person-specific profile separately.
+
+---
+
+## Default Communication Requirements
+
+- Clear written English
+- Concise updates
+- Explicit scope
+- No vague reassurance
+- Useful next action when relevant

ai/context/people/santosh.md

@@ -0,0 +1,24 @@
+# Santosh
+
+## Role
+
+Project-related contact involved in issue discussions.
+
+The exact formal role is not yet confirmed in workspace memory.
+
+---
+
+## Known Context
+
+- Mentioned in relation to AO or externally reported issue discussion
+- Relevant when tracking whether a reported issue needs more investigation or can be closed
+
+---
+
+## Guidance
+
+If future communication makes Santosh's role explicit, update this file with:
+
+- team or function
+- relationship to Fidelity work
+- whether the person is a reporter, tester, partner, or stakeholder

ai/context/project.md

@@ -53,13 +53,21 @@ This machine is used to:
 - maintain current project context
 - record findings from work performed elsewhere
 - capture Mattermost communication that changes understanding
-- prepare polished updates for Jeff
+- prepare polished updates for the current manager or stakeholder
 - generate standups with better context coverage
 
 This means logs must capture both technical findings and communication context.
 
 ---
 
+## People Context
+
+- The current manager role is mapped in `ai/context/people/manager.md`
+- The active people roster lives in `ai/context/people/index.md`
+- Repeatedly relevant named people should have individual files under `ai/context/people/`
+
+---
+
 ## Communication Expectations
 
 All important updates should clarify:

ai/state/current.md

@@ -5,7 +5,7 @@
 - Keep Fidelity context current from daily work performed on another machine
 - Track REST migration findings
 - Debug Discourse and AO issues
-- Prepare better updates for Jeff through Mattermost
+- Prepare better updates for the current manager or stakeholder through Mattermost
 - Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
 
 ---