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

Add project-knowledge structure and templates

Browse Source 
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.
This commit is contained in:
David Delagneau
2026-04-17 15:52:08 -06:00
parent 11fdb17fcb
commit dbc1894e27
175 changed files with 1163 additions and 914 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
core/profiles/create-project-profile.md
View File

@@ -32,23 +32,23 @@ The profile should declare:
Create or update:
```text
vault/00-start/start-here.md
vault/01-current/current-work.md
vault/01-current/work-items.md
vault/02-work-items/
vault/03-context/project.md
vault/03-context/process/
vault/04-people/
vault/05-decisions/
vault/06-daily/
vault/07-maps/
vault/08-bases/
vault/09-templates/
project-knowledge/00-start/start-here.md
project-knowledge/01-current/current-work.md
project-knowledge/01-current/work-items.md
project-knowledge/02-work-items/
project-knowledge/03-context/project.md
project-knowledge/03-context/process/
project-knowledge/04-people/
project-knowledge/05-decisions/
project-knowledge/06-daily/
project-knowledge/07-maps/
project-knowledge/08-bases/
project-knowledge/09-templates/
```
Keep project-specific facts out of `core/`.
Treat `vault/` as canonical memory. Keep connector inboxes and generated evidence outside the vault.
Treat `project-knowledge/` as canonical project memory. Keep connector inboxes and generated evidence outside the project knowledge vault.
---
@@ -58,7 +58,7 @@ Use generic variables first:
```text
AIW_PROJECT_PROFILE=<project>
AIW_MEMORY_VAULT_DIR=<optional custom vault path>
AIW_PROJECT_KNOWLEDGE_DIR=<optional custom project knowledge path>
AIW_MEMORY_BACKEND=auto
AIW_CHANNEL_PREFIX=<project-or-team-prefix>
AIW_MATTERMOST_SYNC_CMD=<optional custom command>
@@ -102,15 +102,15 @@ Before using the workspace for real work:
## 6. Obsidian Vault
Open `vault/` as the Obsidian vault.
Open `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 `vault/` as the clean canonical human/AI memory
- keep runtime evidence, scripts, profiles, and generated files outside `vault/`
- version only portable `vault/.obsidian` configuration
- 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
- ignore local Obsidian workspace state and plugin runtime files
- create or update map notes under `vault/07-maps/` for human navigation
- create Bases under `vault/08-bases/` using simple `type` properties
- create or update map notes under `project-knowledge/07-maps/` for human navigation
- create Bases under `project-knowledge/08-bases/` using simple `type` properties