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

knowledge/agent-memory-rules.md

@@ -41,6 +41,7 @@ Examples:
 - approved manager guidance that changes work direction
 - confirmed version, dependency, or rollout facts tied to current work
 - corrections to previously stored project context
+- repeated named people with stable roles or communication relevance
 
 ---
 
@@ -93,10 +94,18 @@ This file should help standups and manager updates mention work items precisely.
 
 Use for durable project knowledge that should survive beyond the current work window.
 
-### `ai/context/people/jeff.md`
+### `ai/context/people/manager.md`
 
 Use only when a communication preference or manager expectation becomes stable enough to reuse repeatedly.
 
+### `ai/context/people/index.md` and `ai/context/people/*.md`
+
+Use these files for:
+
+- mapping roles to actual people
+- keeping named stakeholders recognizable across sessions
+- storing stable communication or responsibility context per person
+
 ### `ai/context/decisions/*.md`
 
 Use for explicit confirmed decisions with ongoing impact.

knowledge/memory-promotion-rules.md

@@ -51,7 +51,7 @@ Use this file for:
 - current scope notes
 - active status notes that still matter for future updates
 
-If a Jira item is likely to appear again in standups or Jeff updates, it belongs here.
+If a Jira item is likely to appear again in standups or manager updates, it belongs here.
 
 ### Promote to `ai/context/project.md`
 
@@ -68,6 +68,20 @@ Do not promote story-specific daily movement into project context unless it chan
 
 Use decisions only for explicit confirmed decisions with medium or long-term impact.
 
+### Promote to `ai/context/people/index.md` and `ai/context/people/*.md`
+
+Use these files when:
+
+- a person's identity matters repeatedly
+- a role becomes associated with a specific person
+- a stakeholder's communication or approval patterns affect future work
+
+Prefer:
+
+- `manager.md` for role mapping
+- `index.md` for active roster
+- one file per person for person-specific context
+
 ---
 
 ## Do Not Promote
@@ -88,7 +102,7 @@ Do not record these as project memory:
 
 Auto-promote when the signal is high-confidence, for example:
 
-- Jeff explicitly approves something
+- the manager explicitly approves something
 - a Jira story number, title, points, or scope is explicitly confirmed
 - a version is stated directly and tied to the active project
 - a reproduction condition is clearly stated with scope qualifiers
@@ -106,7 +120,7 @@ If confidence is mixed:
 Given Mattermost updates like:
 
 - PDIAP-15836 created and sized at 8 points
-- Jeff approved a story title
+- the manager approved a story title
 - REST-removal scope was approved
 - XFlowViewMaker 0.5.0 is already in Fid4
 - AO DOB validation issue appears auth-only in TeenIdentityCheck