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

Refactor workspace structure and documentation

Browse Source 
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
This commit is contained in:
David Delagneau
2026-04-16 16:28:30 -06:00
parent b82194bc55
commit 374991a568
148 changed files with 214 additions and 3576 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.opencode/agents/workspace.md
View File

@@ -13,7 +13,9 @@ Behavior rules:
- Load `core/` first for project-independent operating rules.
- Load the active profile from `AIW_PROJECT_PROFILE` when available; otherwise use the configured project files in this workspace.
- Treat `vault/` as the canonical clean knowledge base.
- Treat `ai/context/`, `ai/state/`, `ai/work-items/`, `ai/logs/`, `knowledge/`, and profile files as compatibility memory unless no vault equivalent exists.
- Treat profile files as configuration and `ai/inbox/` plus generated connector files as raw evidence.
- Keep Obsidian Bases clean by excluding templates and typing role maps separately from people.
- When updating canonical vault notes, maintain relationship metadata and `updated` fields so the vault remains useful to both humans and agents.
- Before answering current-state questions, inspect current state, active work items, recent logs, and inbox evidence when available.
- For any meaningful prompt, decide whether it adds, corrects, or invalidates memory.
- Update the smallest correct canonical file when memory should change.
@@ -21,7 +23,7 @@ Behavior rules:
- Keep imported evidence separate from promoted memory.
- If an integration or sync command fails, do not update project memory from that failure.
- Do not promote tooling noise, empty syncs, dependency failures, or generic chat chatter unless the user explicitly asks to track tooling work.
- Prefer generic `AIW_*` integration variables and support project-specific aliases only as compatibility.
- Prefer generic `AIW_*` integration variables and support project-specific aliases only when declared by the active profile.
- When drafting communication, preserve technical meaning, state scope clearly, and write in natural professional English.
Memory destinations: