Files
fidelity-ai-workspace/profiles/fidelity/profile.md

132 lines
3.5 KiB
Markdown

# 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 `ai/inbox/mattermost-mirror/` when present; legacy `ai/inbox/mattermost-latest.md` and `scripts/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`
Compatibility environment variables:
- `FIDELITY_MATTERMOST_SYNC_CMD`
- `FIDELITY_MATTERMOST_SYNC_INTERVAL_MINUTES`
- `FIDELITY_SLACK_EXPORT_PATH`
Generic variables should be preferred for new setup:
- `AIW_PROJECT_KNOWLEDGE_DIR`
- `AIW_MATTERMOST_SYNC_CMD`
- `AIW_MATTERMOST_SYNC_INTERVAL_MINUTES`
- `AIW_SLACK_EXPORT_PATH`
- `AIW_CHANNEL_PREFIX=fidelity`
- `AIW_PROJECT_PROFILE=fidelity`
---
## Work System
- Work items are Jira-linked when available
- Active ticket memory lives in `project-knowledge/02-work-items/`
- Compact active summary lives in `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 `project-knowledge/04-people/manager.md`
- Person-specific collaboration context lives in `project-knowledge/04-people/`
- Manager-facing messages should be concise, explicit, and natural professional US English
---
## Domain Context
Core Fidelity context remains in:
- `project-knowledge/03-context/project.md`
- `project-knowledge/03-context/systems/`
- `project-knowledge/03-context/workstreams/`
- `project-knowledge/03-context/ios/`
- `project-knowledge/03-context/process/`
- `project-knowledge/05-decisions/`
Raw communication evidence remains outside the project knowledge vault under `ai/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-curation`
- `professional-communication`
- `status-reporting`
- `ai-prompt-engineering`
- `copilot-prompt-engineering`
Domain-specific:
- `ios-swift-answering`
- `ios-testing-strategy`
- `swiftui-expert-skill`
- `swiftui-xflow-review`
- `update-swiftui-apis`