Refactor Mattermost and Slack integration workflows to remove legacy Fidelity variables, streamline command execution, and enhance documentation for project profiles. Update scripts and README files to reflect changes in directory structure and configuration precedence, ensuring a consistent approach to project knowledge management across profiles. Improve error handling and validation in profile creation and doctor commands, and enhance test coverage for profile-related functionalities.

This commit is contained in:
2026-05-21 14:13:21 -06:00
parent 1ad707373a
commit ad230e1abe
28 changed files with 263 additions and 120 deletions

View File

@@ -48,7 +48,7 @@ project-knowledge/09-templates/
Keep project-specific facts out of `core/`.
Treat `project-knowledge/` as canonical project memory. Keep connector inboxes and generated evidence outside the project knowledge vault.
Treat `workspaces/<profile>/project-knowledge/` as canonical project memory. Keep connector inboxes and generated evidence outside the project knowledge vault.
---
@@ -102,15 +102,15 @@ Before using the workspace for real work:
## 6. Obsidian Vault
Open `project-knowledge/` as the Obsidian vault.
Open `workspaces/<profile>/project-knowledge/` as the Obsidian vault.
Use `scripts/memory/` as the project-agnostic memory interface. Obsidian is the default visual and CLI-backed adapter, but profile logic should not depend on Obsidian.
Recommended rules:
- keep `project-knowledge/` as the clean canonical project knowledge
- keep runtime evidence, scripts, profiles, and generated files outside `project-knowledge/`
- version only portable `project-knowledge/.obsidian` configuration
- keep `workspaces/<profile>/project-knowledge/` as the clean canonical project knowledge
- keep runtime evidence, scripts, profiles, and generated files outside `workspaces/<profile>/project-knowledge/`
- version only portable `workspaces/<profile>/project-knowledge/.obsidian` configuration
- ignore local Obsidian workspace state and plugin runtime files
- create or update map notes under `project-knowledge/07-maps/` for human navigation
- create Bases under `project-knowledge/08-bases/` using simple `type` properties
- create or update map notes under `workspaces/<profile>/project-knowledge/07-maps/` for human navigation
- create Bases under `workspaces/<profile>/project-knowledge/08-bases/` using simple `type` properties