Add daily logs and templates for Fidelity project

- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.
This commit is contained in:
2026-04-16 16:01:19 -06:00
parent 90043ab6bf
commit b82194bc55
129 changed files with 4777 additions and 251 deletions

View File

@@ -32,17 +32,24 @@ The profile should declare:
Create or update:
```text
ai/context/project.md
ai/context/index.md
ai/context/process/
ai/context/people/
ai/state/current.md
ai/state/work-items.md
ai/work-items/index.md
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/
```
Keep project-specific facts out of `core/`.
Legacy `ai/context`, `ai/state`, `ai/work-items`, and `ai/logs` paths may be kept temporarily for compatibility, but new project profiles should treat `vault/` as canonical memory.
---
## 3. Configure Integrations
@@ -88,14 +95,15 @@ Before using the workspace for real work:
---
## 6. Optional Obsidian Vault
## 6. Obsidian Vault
Open the workspace root as an Obsidian vault when you want a visual/manual navigation layer.
Open `vault/` as the Obsidian vault.
Recommended rules:
- keep the workspace filesystem as the single source of truth
- do not copy memory into a separate Obsidian-only folder
- version only portable `.obsidian` configuration
- 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
- ignore local Obsidian workspace state and plugin runtime files
- create or update a vault map under `knowledge/` for human navigation
- create or update map notes under `vault/07-maps/` for human navigation
- create Bases under `vault/08-bases/` using simple `type` properties