- 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.
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
|
type: person
|
|
project: fidelity
|
|
role: collaborator
|
|
status: inactive
|
|
updated: 2026-04-17
|
|
tags:
|
|
- person
|
|
- fidelity
|
|
---
|
|
# Derian Cordoba
|
|
|
|
## Role
|
|
|
|
Historical Fidelity collaborator in project support discussions.
|
|
|
|
- No longer works with the current All-Win Software / Mattermost / Slack collaboration group.
|
|
|
|
---
|
|
|
|
## Known Context
|
|
|
|
- Appears in historical pipeline, Jenkins, and documentation conversations
|
|
- Helped document pipeline work and supported notification/credential troubleshooting
|
|
- Collaboration signal is real but current formal role remains unclear from the archive
|
|
- Often paired with David on CI/CD and notification-related work
|
|
- Showed up when the team needed operational documentation, release-process notes, or pipeline triage support
|
|
|
|
---
|
|
|
|
## Guidance
|
|
|
|
- Treat Derian as a relevant collaborator for historical pipeline/debugging context
|
|
- Treat Derian as most relevant for historical CI/CD coordination and documentation support
|
|
- Treat Derian as historical context, not a current active collaborator
|
|
- If future context clarifies the formal role or team, update this file directly
|