- 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.
2.6 KiB
2.6 KiB
type, project, updated, tags
| type | project | updated | tags | ||
|---|---|---|---|---|---|
| context-index | fidelity | 2026-04-17 |
|
Context Index
Goal
Keep stable Fidelity context organized by domain so engineers and AI agents can load the right information quickly.
Structure
project.md
High-level overview of the workspace, current Fidelity scope, and where durable context lives.
systems/
Stable context about core product components and how they relate:
- systems/fid4.md
- systems/xflowsdk.md
- systems/xflowviewmaker.md
- systems/ftframeworks.md
- systems/index.md
- ../07-maps/fidelity-apps.md for internal Fidelity app/tool navigation
ios/
Swift and iOS best-practice context for programming questions:
- ios/index.md
- ios/current-practices.md
- ios/project-swift-guidance.md
- ios/cocoapods-dependency-management.md
workstreams/
Durable context about recurring streams of work and investigation:
- workstreams/rest-migration.md
- workstreams/ao-discourse.md
- workstreams/xflow-debugging.md
- workstreams/xflow-swiftui-migration.md
- workstreams/consumer-integration.md
- workstreams/flow-page-references.md
process/
Project-facing rules and expectations for how work should be communicated:
- process/communication.md
- process/communication-rules.md
- process/jira-story-rules.md
- process/pull-requests.md
people/
Named people, role mapping, and collaboration context:
decisions/
Confirmed technical or product decisions with ongoing impact.
Usage
- Load
project.mdand this index first. - Open
systems/when the question is about architecture, ownership, or integration. - Open
ios/when the question is about Swift, SwiftUI, iOS architecture, testing, concurrency, or debugging. - Open
workstreams/when the question is about current priorities, debugging themes, or historical project patterns. - Open
process/when drafting messages, standups, Jira notes, or PR descriptions.