Add project-knowledge structure and templates
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
This commit is contained in:
30
project-knowledge/04-people/raj-sundararaj.md
Normal file
30
project-knowledge/04-people/raj-sundararaj.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
---
|
||||
# Raj Sundararaj
|
||||
|
||||
## Role
|
||||
|
||||
Repeated Fidelity collaborator involved in project coordination and active issue triage.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
|
||||
- Repeatedly surfaced or assigned XFlow/AO issues and asked for current status
|
||||
- Involved in release coordination, validation follow-up, and backlog movement
|
||||
- Relevant when the team needed to align issue ownership, repro state, or urgency with consumer-side expectations
|
||||
|
||||
---
|
||||
|
||||
## Guidance
|
||||
|
||||
- Treat Raj as a useful contact for issue routing, AO coordination, and release follow-up
|
||||
- If future context clarifies the formal role/team, update this file directly
|
||||
Reference in New Issue
Block a user