- 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.
Cogstore is an important Fidelity platform used to manage and publish many flow configuration definitions, each with its own independent version history.
Confirmed Context
In the Fidelity flow-config workflow, Cogstore is used to modify and publish individual flow definitions.
Cogstore tracks versions per flow definition rather than as one single platform-wide version.
Cogstore can be used to compare changes between flow-definition versions, similar to a Git-style diff.
Cogstore can be used to check which version of a specific flow definition is published in environments such as QA and Production, including who published it and when.
On April 16, 2026, David used Cogstore to confirm that the relevant flow-definition change tied to Rashmi's service-side update was present in QA as version 0.0.142, while Production was still on 0.0.133.
Related Context
Jeff indicated on April 15, 2026 that Slate had been used by newer consumer services during the SwiftUI refactor, but is now believed to be decommissioned.
Because service/configuration changes can be environment-specific and versioned per flow, Cogstore should be checked before concluding that a payload/config change is live in Production.
Flow IDs are not guaranteed to exist in both Cogstore and Slate. When tracing a specific flow definition, confirm which configuration system actually owns that flow instead of assuming the same ID will appear in both places.
david.delagneau
dbc1894e27