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

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