- 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.
4.4 KiB
Fidelity Profile
Purpose
This is the first real project profile for the reusable AI workspace core.
It keeps Fidelity-specific context, integrations, commands, and skills separate from the project-independent operating model in core/.
Project
- Name: Fidelity iOS ecosystem
- Workspace role: companion AI workspace, not the product codebase
- Main development happens on a different machine
- Primary use: context memory, communication drafting, standups, Jira/story support, and AI-to-AI prompt generation
Communication Sources
- Live communication: Mattermost
- Preferred local Mattermost evidence source: proxy mirror under
workspaces/fidelity/inbox/mattermost-mirror/when present; legacyworkspaces/fidelity/inbox/mattermost-latest.mdandscripts/mattermost/generated/are fallback evidence. - Historical archive: Slack export
- Preferred channel naming: readable channel names instead of raw IDs
- Current high-signal channel:
fidelity-preguntas - Focused Mattermost context for standups/latest project reads should come from configured profile/environment channels, not hardcoded connector defaults. For this profile, the useful context-channel set is currently
fidelity-preguntas,fidelity-standup,fidelity-code-review,fidelity-interface-meetings-on-calendar-outlook-team-etc, anddm-david--jeff; keep that list in local.envasAIW_MATTERMOST_CONTEXT_CHANNELSor an equivalent profile setup when using the reusable Mattermost reader.
Compatibility environment variables:
FIDELITY_MATTERMOST_SYNC_CMDFIDELITY_MATTERMOST_SYNC_INTERVAL_MINUTESFIDELITY_SLACK_EXPORT_PATH
Generic variables should be preferred for new setup:
AIW_PROJECT_KNOWLEDGE_DIRAIW_MATTERMOST_SYNC_CMDAIW_MATTERMOST_SYNC_INTERVAL_MINUTESAIW_SLACK_EXPORT_PATHAIW_CHANNEL_PREFIX=fidelityAIW_PROJECT_PROFILE=fidelityAIW_MATTERMOST_CONTEXT_CHANNELS=fidelity-preguntas,fidelity-standup,fidelity-code-review,fidelity-interface-meetings-on-calendar-outlook-team-etc,dm-david--jeff
Work System
- Work items are Jira-linked when available
- Active ticket memory lives in
workspaces/fidelity/project-knowledge/02-work-items/ - Compact active summary lives in
workspaces/fidelity/project-knowledge/01-current/work-items.md - Jira IDs and approved titles should remain visible for standups and manager updates
Stakeholders
- Current manager mapping lives in
workspaces/fidelity/project-knowledge/04-people/manager.md - Person-specific collaboration context lives in
workspaces/fidelity/project-knowledge/04-people/ - Manager-facing messages should be concise, explicit, and natural professional US English
Domain Context
Core Fidelity context remains in:
workspaces/fidelity/project-knowledge/03-context/project.mdworkspaces/fidelity/project-knowledge/03-context/systems/workspaces/fidelity/project-knowledge/03-context/workstreams/workspaces/fidelity/project-knowledge/03-context/ios/workspaces/fidelity/project-knowledge/03-context/process/workspaces/fidelity/project-knowledge/05-decisions/
Raw communication evidence remains outside the project knowledge vault under workspaces/fidelity/inbox/ and generated connector folders.
Memory access should go through the project-agnostic scripts/memory/ interface for note creation, search, Base queries, and health checks. Obsidian is the current visual and CLI adapter, not a Fidelity-specific dependency.
Important domain themes:
- Fid4 consumer validation
- XFlowSDK backend-driven UI
- XFlowViewMaker adapter/release coupling
- FTFrameworks feature modules
- REST migration from GraphQL/Apollo
- AO/Discourse external issue handling
- authenticated vs non-authenticated reproduction
Enabled Commands
Generic commands:
/workspace-context/memory-health/memory-create/communication-sync/archive-import/ai-prompt/standup/manager-update/translate/sync-context/log-note
Compatibility aliases:
/fidelity-context/mattermost-sync/slack-import/copilot-prompt/swift-help
Enabled Skills
Generic:
workspace-memory-curationprofessional-communicationstatus-reportingai-prompt-engineeringcopilot-prompt-engineering
Domain-specific:
ios-swift-answeringios-testing-strategyswiftui-expert-skillswiftui-xflow-reviewupdate-swiftui-apis