- 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.
2.8 KiB
2.8 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
- Historical archive: Slack export
- Preferred channel naming: readable channel names instead of raw IDs
- Current high-signal channel:
fidelity-preguntas
Compatibility environment variables:
FIDELITY_MATTERMOST_SYNC_CMDFIDELITY_MATTERMOST_SYNC_INTERVAL_MINUTESFIDELITY_SLACK_EXPORT_PATH
Generic variables should be preferred for new setup:
AIW_MATTERMOST_SYNC_CMDAIW_MATTERMOST_SYNC_INTERVAL_MINUTESAIW_SLACK_EXPORT_PATHAIW_CHANNEL_PREFIX=fidelityAIW_PROJECT_PROFILE=fidelity
Work System
- Work items are Jira-linked when available
- Active ticket memory lives in
vault/02-work-items/ - Compact active summary lives in
vault/01-current/work-items.md - Jira IDs and approved titles should remain visible for standups and manager updates
Stakeholders
- Current manager mapping lives in
vault/04-people/manager.md - Person-specific collaboration context lives in
vault/04-people/ - Manager-facing messages should be concise, explicit, and natural professional US English
Domain Context
Core Fidelity context remains in:
vault/03-context/project.mdvault/03-context/systems/vault/03-context/workstreams/vault/03-context/ios/vault/03-context/process/vault/05-decisions/
Legacy ai/* paths remain available only as compatibility fallback during migration.
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/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-xflow-review