david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
2.6 KiB
2.6 KiB
type, audience, tags
| type | audience | tags | ||
|---|---|---|---|---|
| glossary | new-member |
|
Glossary
Common terms used in the Fidelity project knowledge vault.
Workspace Terms
workspaces/fidelity/project-knowledge: this Obsidian vault; transferable Fidelity project knowledge.agent-memory: agent operating rules outside this vault.operational memory: curated file-based memory that helps future sessions reason accurately.daily log: same-day evidence and evolving findings inworkspaces/fidelity/project-knowledge/06-daily/.state: near-term active work and priorities inworkspaces/fidelity/project-knowledge/01-current/.work item: canonical memory for a ticket, story, task, or investigation inworkspaces/fidelity/project-knowledge/02-work-items/.stable context: durable project knowledge underworkspaces/fidelity/project-knowledge/03-context/.inbox: raw or lightly processed communication evidence underworkspaces/fidelity/inbox/.promotion: moving high-confidence evidence into canonical memory.memory interface: project-agnostic scripts underscripts/memory/that create, search, query, and validate project knowledge without coupling the workspace to Obsidian.
Fidelity Terms
Fid4: main Fidelity consumer iOS app and key validation environment.XFlowSDK: backend-driven UI engine that renders flows from service-provided configuration.XFlowViewMaker: adapter layer historically involved in integration and release propagation.FTFrameworks: feature modules such as account opening or transfer flows that can mediate XFlow adoption.AO: account opening context; many reports require careful reproduction and scope validation.Discourse: external issue/report source; treat reports as external until confirmed.REST migration: migration away from GraphQL/Apollo toward REST, with REST behind a feature flag unless confirmed otherwise.authenticated flow: behavior reproduced while signed in; often differs from non-authenticated behavior.entry point: the path used to reach a flow, which can affect backend-driven behavior.Cogstore: flow-configuration publishing and version-comparison platform.
Communication Terms
external report: issue reported externally before regression status is confirmed.regression: behavior confirmed to be newly broken relative to a known baseline.scope: the exact affected flow, platform, auth state, environment, and ownership boundary.reproducibility: whether the behavior can be repeated with known steps and context.manager-ready: concise, explicit, natural professional English that can be sent without rewriting.