david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Update behavior rules and documentation for workspace maintenance and flow references

Browse Source
This commit is contained in:
David Delagneau
2026-04-16 07:50:07 -06:00
parent a375b3c3b1
commit 1f57597ca3
21 changed files with 146 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ai/context/process/communication.md
View File

@@ -24,6 +24,8 @@ When the format fits, prefer:
- For standups, report the previous workday context, not blindly the prior calendar day.
- On Mondays, use Friday's work context unless a later prior day has Mattermost activity.
- If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.
- For standups, when a Jira item has multiple concrete updates, use one top-level `JIRA-ID - Title` bullet and indented markdown sub-bullets instead of repeating the same Jira line.
- When a flow/page shorthand could be ambiguous, prefer the real flow identifier and page name from `ai/context/workstreams/flow-page-references.md`.
- Avoid vague phrasing such as:
- "same behavior"
- "looks fixed"

3
ai/context/process/context-maintenance.md
View File

@@ -17,6 +17,7 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
- `ai/state/work-items.md` for the compact active-work summary
- `ai/context/` for durable project knowledge
- `ai/context/people/` for named person context
- `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.opencode/skills/`, or `knowledge/` for reusable behavior rules that control how the workspace responds
---
@@ -26,9 +27,11 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
- Do not promote failed syncs or tooling errors as project facts.
- Promote repeated durable patterns from historical archives into stable context when confidence is high.
- Keep old status-only details archive-only unless they still change current understanding.
- Treat user corrections about command output, prompt structure, memory handling, or agent behavior as inputs to the operational surface, not just as daily notes.
---
## Curation Rule
- If a new stable context file is added, keep `project.md` and `index.md` aligned so future sessions can discover it quickly.
- If a new rule affects a slash command or reusable prompt, update that command or prompt directly so the behavior changes on the next run.