- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items. - Established a daily logs index for easy navigation of daily entries. - Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation. - Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation. - Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management. - Added a placeholder for attachments to facilitate file organization.
1.2 KiB
1.2 KiB
type, project, status, updated, tags
| type | project | status | updated | tags | ||
|---|---|---|---|---|---|---|
| system-index | fidelity | active | 2026-04-16 |
|
Systems Index
Core Components
-
fid4.md Consumer app and the most important real-world validation environment.
-
xflowsdk.md Backend-driven flow engine and the center of most Fidelity behavior analysis.
-
xflowviewmaker.md Adapter layer historically involved in version bumps, release coupling, and removal evaluation.
-
ftframeworks.md Consumer-side feature modules that often mediate whether XFlow changes can be validated in Fid4.
-
cogstore.md Flow-configuration publishing and version-comparison platform used to verify what is live in QA/Production.
Guidance
- Start with
xflowsdk.mdfor backend-driven behavior questions. - Start with
fid4.mdorftframeworks.mdfor consumer validation and release flow questions. - Open
xflowviewmaker.mdwhen the question involves version bumps, transitional architecture, or pipeline friction. - Open
cogstore.mdwhen the question involves published flow-definition versions, config diffs, or whether a service/config change is live in QA vs Production.