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/tim-longfield.md
Normal file
30
project-knowledge/04-people/tim-longfield.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
---
|
||||
# Tim Longfield
|
||||
|
||||
## Role
|
||||
|
||||
FTPlanning-side collaborator relevant to cross-framework issue ownership.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
|
||||
- Appeared when issues first thought to be XFlow bugs were traced into FTPlanning
|
||||
- Relevant contact for whether a transfer/add-money bug belonged to FTPlanning instead of XFlow
|
||||
- Useful when a consumer-side framework fix was needed before XFlow could close validation work
|
||||
|
||||
---
|
||||
|
||||
## Guidance
|
||||
|
||||
- Treat Tim as a relevant contact for FTPlanning-owned fixes and cross-team validation
|
||||
- If future context clarifies the formal role/team, update this file directly
|
||||
Reference in New Issue
Block a user