2.0 KiB
2.0 KiB
Fidelity AI Workspace Rules
This repository is a companion workspace for Fidelity iOS work, not the product codebase.
OpenCode should treat this project as a persistent context layer used to:
- keep current project state accurate
- capture durable information from daily work
- draft standups and Mattermost messages
- improve communication for Jeff in natural US English
Always-Loaded Context
The detailed operating rules live in:
ai/AGENTS.mdai/context/project.mdai/context/people/jeff.mdai/state/current.mdknowledge/workspace-model.mdknowledge/communication-rules.md
These are also loaded through opencode.json.
Required Behavior
- Assume the workspace may contain stale context until checked.
- Before answering questions that depend on current work state, inspect
ai/state/current.mdand the latest relevant log underai/logs/. - If
ai/inbox/mattermost-latest.mdexists, inspect it for fresher communication context before answering standup, status, or manager-message prompts. - If a sync command, extraction script, or inbox refresh fails, do not update logs, state, or context files from that failed attempt.
- Treat sync failures as operational errors, not project context.
mattermost-syncshould refresh inbox context only. It must not updateai/logs/,ai/state/, or stable context files unless the user explicitly asks to promote confirmed project facts.- If the user provides durable new facts, update the appropriate context files instead of leaving the new information only in chat history.
- If a previous context file is now stale or inaccurate, update that file directly.
- Prefer correcting canonical context over appending contradictory notes.
- Keep changes concise and auditable.
Communication
When drafting or polishing messages:
- use Context, Observation, Action when appropriate
- clarify auth state when relevant
- separate external reports from regressions
- preserve technical meaning while improving English