- 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.
Debug backend-driven flows without losing track of dynamic dependencies or misclassifying integration behavior.
Stable Patterns
XFlow screens are backend-driven, so UI can change without local code changes.
Reproduction depends on:
entry point
authentication state
backend configuration
consumer integration path
Not all entry points are reachable from visible UI; some require exploratory validation.
Investigation Rules
Confirm the entry point before comparing behavior.
Separate service-driven behavior from client regressions.
Confirm whether the issue reproduces in:
sample app
XFlow-only environment
Fid4 / flagship
authenticated vs non-authenticated state
If a fix appears correct in the SDK but not in consumer validation, inspect the release chain before reopening root cause assumptions.
When validating service/configuration changes, check the active flow-definition version in Cogstore before assuming a change is live in QA or Production.
Do not assume a flow ID will exist in both Cogstore and Slate; verify which config system actually owns the flow you are inspecting.
david.delagneau
1ad707373a