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

@@ -2,7 +2,7 @@
## Purpose
Use Obsidian as a visual navigation and manual review layer over the same Markdown files that power the AI workspace.
Use Obsidian as a visual navigation and manual review layer over the same canonical Markdown memory that powers the AI workspace.
Obsidian should not become a second memory store.
@@ -10,10 +10,10 @@ Obsidian should not become a second memory store.
## Recommended Vault
Open the repository root as the Obsidian vault:
Open the `vault/` folder as the Obsidian vault:
```text
<workspace-root>/
<workspace-root>/vault/
```
This keeps one source of truth:
@@ -21,22 +21,34 @@ This keeps one source of truth:
- OpenCode and agents maintain operational memory
- Obsidian reads and edits the same Markdown files
- Git tracks intentional memory and configuration changes
- runtime evidence and generated artifacts stay outside the vault
---
## Source Of Truth
Canonical memory remains in:
Canonical human/AI memory lives in:
- `ai/logs/`
- `ai/state/`
- `ai/work-items/`
- `ai/context/`
- `knowledge/`
- `vault/00-start/`
- `vault/01-current/`
- `vault/02-work-items/`
- `vault/03-context/`
- `vault/04-people/`
- `vault/05-decisions/`
- `vault/06-daily/`
- `vault/07-maps/`
Technical runtime remains outside the vault:
- `.opencode/`
- `scripts/`
- `core/`
- `profiles/`
- `ai/inbox/`
- `scripts/*/generated/`
- archives and local virtual environments
Obsidian-specific runtime files are not project memory.
Legacy `ai/context`, `ai/state`, `ai/work-items`, `ai/logs`, and `knowledge` paths may exist temporarily as compatibility fallback during migration.
---
@@ -44,18 +56,21 @@ Obsidian-specific runtime files are not project memory.
Version portable Obsidian configuration only when it improves the workspace for every clone:
- `.obsidian/app.json`
- `.obsidian/core-plugins.json`
- `.obsidian/graph.json`
- `.obsidian/appearance.json`
- `vault/.obsidian/app.json`
- `vault/.obsidian/core-plugins.json`
- `vault/.obsidian/graph.json`
- `vault/.obsidian/appearance.json`
- `vault/.obsidian/daily-notes.json`
- `vault/.obsidian/templates.json`
- `vault/.obsidian/bookmarks.json`
Do not version local runtime state:
- `.obsidian/workspace*.json`
- `.obsidian/workspace-mobile*.json`
- `.obsidian/plugins/`
- `.obsidian/snippets/`
- `.obsidian/cache/`
- `vault/.obsidian/workspace*.json`
- `vault/.obsidian/workspace-mobile*.json`
- `vault/.obsidian/plugins/`
- `vault/.obsidian/snippets/`
- `vault/.obsidian/cache/`
Recommended graph and search exclusions:
@@ -90,4 +105,32 @@ The agent should not treat Obsidian runtime layout changes as project context.
If Obsidian metadata or properties are added, use them selectively for high-value notes such as work items, decisions, and index pages. Do not mass-convert existing files just to add metadata.
Use map notes under `knowledge/maps/` as graph hubs. This keeps the graph navigable without forcing every file into Obsidian-specific wiki-link syntax.
Use map notes under `vault/07-maps/` as graph hubs. This keeps the graph navigable without forcing every file into Obsidian-specific wiki-link syntax.
---
## Bases
Keep Bases simple and property-driven:
- work items filter on `type: work-item`
- people filter on `type: person`
- decisions filter on `type: decision`
- daily notes filter on `type: daily`
- systems filter on `type: system`
- workstreams filter on `type: workstream`
Do not use Bases for raw inboxes, generated evidence, scripts, or runtime logs.
---
## CLI Wrappers
Use `scripts/obsidian/` for non-interactive Obsidian URI helpers:
- `uri.sh` generates encoded Obsidian URIs.
- `open.sh <vault-relative-path>` opens a note.
- `daily.sh` opens the configured daily note.
- `search.sh <query>` opens Obsidian search.
The wrappers default to `vault/` and can be overridden with `AIW_OBSIDIAN_VAULT_DIR` and `AIW_OBSIDIAN_VAULT_NAME`.

View File

@@ -17,7 +17,7 @@ Use for same-day progress, findings, evolving reproduction notes, and work that
Default path pattern:
```text
ai/logs/YYYY-MM-DD.md
vault/06-daily/YYYY-MM-DD.md
```
### `state`
@@ -27,8 +27,8 @@ Use for current priorities, active blockers, near-term constraints, and communic
Default paths:
```text
ai/state/current.md
ai/state/work-items.md
vault/01-current/current-work.md
vault/01-current/work-items.md
```
### `work-items`
@@ -38,7 +38,7 @@ Use for canonical memory about active tickets, tasks, stories, investigations, o
Default path pattern:
```text
ai/work-items/<id-or-slug>.md
vault/02-work-items/<id-or-slug>.md
```
### `stable-context`
@@ -48,7 +48,7 @@ Use for durable project knowledge that should survive beyond the current work wi
Default path pattern:
```text
ai/context/<domain>/*.md
vault/03-context/<domain>/*.md
```
### `people`
@@ -58,7 +58,7 @@ Use for repeated collaborators, role mappings, manager/stakeholder context, and
Default path pattern:
```text
ai/context/people/*.md
vault/04-people/*.md
```
### `decisions`
@@ -68,7 +68,7 @@ Use for confirmed decisions with ongoing impact.
Default path pattern:
```text
ai/context/decisions/*.md
vault/05-decisions/*.md
```
### `tooling-behavior`
@@ -82,10 +82,12 @@ Default path patterns:
.opencode/agents/*.md
.opencode/skills/*/SKILL.md
prompts/*.md
knowledge/*.md
ai/context/process/*.md
vault/00-start/*.md
vault/03-context/process/*.md
```
Legacy `ai/*` and `knowledge/*` paths may remain as compatibility fallback, but new writes should target `vault/` first when a canonical note exists.
---
## Promotion Rules
@@ -135,4 +137,3 @@ Examples:
- memory routing correction -> update memory rules and context-maintenance guidance
The daily log may preserve evidence, but reusable behavior must live in the command, prompt, skill, agent, or knowledge file that enforces it.

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