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:
80
README.md
80
README.md
@@ -4,7 +4,7 @@ Reusable AI-native companion workspace with Fidelity configured as the first rea
|
||||
|
||||
This repository is not the product codebase. It is an operational context layer used to keep project state current, capture communication evidence, prepare standups, draft clear stakeholder updates, and generate self-contained prompts for another AI that has access to the implementation codebase.
|
||||
|
||||
The reusable logic lives in `core/`. Fidelity-specific context lives in the active profile and existing `ai/context/` memory.
|
||||
The reusable logic lives in `core/`. The clean human/AI memory lives in `vault/`. Fidelity-specific setup lives in the active profile under `profiles/fidelity/`.
|
||||
|
||||
---
|
||||
|
||||
@@ -44,6 +44,22 @@ Integrations extract evidence. The agent promotes memory.
|
||||
|
||||
## Reusable Architecture
|
||||
|
||||
### /vault
|
||||
|
||||
Canonical Obsidian second brain and AI memory.
|
||||
|
||||
- `00-start/` -> onboarding, glossary, start-here, and vault usage
|
||||
- `01-current/` -> current work and active work-item summary
|
||||
- `02-work-items/` -> ticket/task notes with metadata properties
|
||||
- `03-context/` -> systems, workstreams, process, and iOS context
|
||||
- `04-people/` -> people, roles, and collaboration context
|
||||
- `05-decisions/` -> durable decisions
|
||||
- `06-daily/` -> daily notes
|
||||
- `07-maps/` -> graph hubs and semantic maps
|
||||
- `08-bases/` -> Obsidian Bases
|
||||
- `09-templates/` -> Obsidian templates
|
||||
- `attachments/` -> vault assets
|
||||
|
||||
### /core
|
||||
|
||||
Project-independent workspace logic.
|
||||
@@ -76,18 +92,15 @@ Fidelity iOS ecosystem:
|
||||
|
||||
---
|
||||
|
||||
## Structure
|
||||
## Runtime Structure
|
||||
|
||||
### /ai
|
||||
|
||||
Runtime context for AI support.
|
||||
|
||||
- `AGENTS.md` -> behavior rules for AI agents
|
||||
- `context/` -> stable knowledge organized by systems, workstreams, process, people, and decisions
|
||||
- `context/ios/` -> Swift and iOS answer policy for current best practices and Fidelity-specific constraints
|
||||
- `work-items/` -> one file per active Jira-linked unit of work
|
||||
- `state/` -> current focus, active issues, and communication needs
|
||||
- `logs/` -> daily work record
|
||||
- `context/`, `work-items/`, `state/`, and `logs/` -> legacy compatibility memory during the vault migration
|
||||
- `inbox/` -> communication evidence and transient inbox files
|
||||
|
||||
### /prompts
|
||||
|
||||
@@ -115,17 +128,17 @@ Reference material for:
|
||||
- XFlow behavior
|
||||
- communication rules
|
||||
- Fidelity-specific debugging heuristics
|
||||
- Obsidian vault navigation
|
||||
- legacy navigation references during the vault migration
|
||||
|
||||
### /scripts
|
||||
|
||||
Helpers for future automation around context generation and communication drafting.
|
||||
|
||||
### /.obsidian
|
||||
### /vault/.obsidian
|
||||
|
||||
Optional Obsidian vault configuration.
|
||||
|
||||
Open the repository root as the vault. Obsidian should navigate and edit the same Markdown files used by OpenCode; it should not duplicate memory into a separate store.
|
||||
Open `vault/` as the Obsidian vault. Do not open the repository root as the vault.
|
||||
|
||||
Portable vault configuration can be versioned, while local layout and plugin runtime files are ignored.
|
||||
|
||||
@@ -137,13 +150,13 @@ Portable vault configuration can be versioned, while local layout and plugin run
|
||||
|
||||
Read:
|
||||
|
||||
- `ai/context/index.md`
|
||||
- `ai/work-items/index.md`
|
||||
- `ai/state/current.md`
|
||||
- `ai/context/project.md`
|
||||
- `ai/context/people/manager.md`
|
||||
- `ai/context/people/index.md`
|
||||
- latest file under `ai/logs/`
|
||||
- `vault/00-start/start-here.md`
|
||||
- `vault/01-current/current-work.md`
|
||||
- `vault/01-current/work-items.md`
|
||||
- `vault/03-context/project.md`
|
||||
- `vault/04-people/manager.md`
|
||||
- `vault/04-people/index.md`
|
||||
- latest file under `vault/06-daily/`
|
||||
|
||||
### During the day
|
||||
|
||||
@@ -156,7 +169,7 @@ Capture:
|
||||
|
||||
Write updates in:
|
||||
|
||||
- `ai/logs/YYYY-MM-DD.md`
|
||||
- `vault/06-daily/YYYY-MM-DD.md`
|
||||
|
||||
### Before sending a message
|
||||
|
||||
@@ -245,7 +258,7 @@ Recommended setup:
|
||||
1. Use the workspace-local script at `scripts/mattermost/sync.sh`, or override it with `AIW_MATTERMOST_SYNC_CMD`.
|
||||
2. Let OpenCode run with the project plugins enabled.
|
||||
3. The Mattermost inbox plugin will periodically refresh `ai/inbox/mattermost-latest.md`.
|
||||
4. Promote durable facts from the inbox into `ai/logs/`, `ai/state/`, and `ai/context/`.
|
||||
4. Promote durable facts from the inbox into `vault/06-daily/`, `vault/01-current/`, `vault/02-work-items/`, and `vault/03-context/`.
|
||||
|
||||
Use `/communication-sync` or `/mattermost-sync` when you want to force a refresh manually.
|
||||
|
||||
@@ -263,14 +276,15 @@ The older `FIDELITY_*` variables remain supported for compatibility with this pr
|
||||
|
||||
## Obsidian Vault
|
||||
|
||||
This repository can be opened directly as an Obsidian vault.
|
||||
Open `vault/` as the Obsidian vault. The repository root remains the technical workspace for OpenCode, scripts, profiles, runtime inboxes, and generated evidence.
|
||||
|
||||
Recommended entry point:
|
||||
|
||||
- `knowledge/obsidian-vault.md`
|
||||
- `knowledge/onboarding.md` for new members
|
||||
- `knowledge/glossary.md` for terminology
|
||||
- `knowledge/obsidian-usage.md` for navigation rules
|
||||
- `vault/00-start/start-here.md`
|
||||
- `vault/00-start/onboarding.md` for new members
|
||||
- `vault/00-start/glossary.md` for terminology
|
||||
- `vault/00-start/obsidian-usage.md` for navigation rules
|
||||
- `vault/07-maps/` for graph hubs
|
||||
|
||||
Use Obsidian for:
|
||||
|
||||
@@ -281,8 +295,24 @@ Use Obsidian for:
|
||||
|
||||
Do not use Obsidian as a second memory database. The source of truth remains the versioned Markdown files in this repository.
|
||||
|
||||
Runtime/evidence stays outside the vault:
|
||||
|
||||
- `.opencode/`
|
||||
- `scripts/`
|
||||
- `core/`
|
||||
- `profiles/`
|
||||
- `ai/inbox/`
|
||||
- `scripts/*/generated/`
|
||||
|
||||
Ignored Obsidian runtime files include workspace layout, plugin cache, snippets, and local plugin installs.
|
||||
|
||||
Obsidian URI helpers live under `scripts/obsidian/`:
|
||||
|
||||
- `scripts/obsidian/open.sh <vault-relative-path>`
|
||||
- `scripts/obsidian/daily.sh`
|
||||
- `scripts/obsidian/search.sh <query>`
|
||||
- `scripts/obsidian/uri.sh <action> key=value`
|
||||
|
||||
---
|
||||
|
||||
## Creating Another Project
|
||||
@@ -291,7 +321,7 @@ Ignored Obsidian runtime files include workspace layout, plugin cache, snippets,
|
||||
2. Fill in `profiles/<project>/profile.md`.
|
||||
3. Set `AIW_PROJECT_PROFILE=<project>`.
|
||||
4. Configure any communication connector with `AIW_*` variables.
|
||||
5. Keep project-specific context under `ai/context/`, not under `core/`.
|
||||
5. Create or adapt `vault/` for the project-specific canonical memory.
|
||||
6. Use `/workspace-context` to load the core plus active profile.
|
||||
|
||||
See `core/profiles/create-project-profile.md` for the full checklist.
|
||||
|
||||
Reference in New Issue
Block a user