Files
fidelity-ai-workspace/vault/03-context/process/workspace-model.md
david.delagneau b82194bc55 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.
2026-04-16 16:01:19 -06:00

58 lines
1.7 KiB
Markdown

---
type: process
project: fidelity
status: active
updated: 2026-04-16
tags: [process, workspace, memory]
---
# Workspace Model
## Purpose
This repository is a support workspace, not the implementation repository.
It now has two layers:
- `core/` contains reusable project-independent operating rules
- `profiles/<project>/` contains project-specific configuration and assumptions
---
## What belongs here
- daily logs
- communication context
- manager update drafts
- stable project knowledge
- debugging summaries
- reusable command, prompt, skill, and agent rules that make the workspace behave consistently
- project profiles that configure the reusable core for a specific project
- optional navigation notes and portable Obsidian configuration
---
## What does not belong here
- product source code
- assumptions about code changes not yet verified
- statements that imply work was executed from this machine unless explicitly true
- Obsidian local layout, plugin cache, or runtime state
---
## Operational Surface
When the user corrects a recurring behavior, the workspace should update the file that controls that behavior:
- `core/` for reusable project-independent behavior
- `profiles/<project>/` for project-specific assumptions
- `vault/.obsidian/` only for portable vault configuration, not project memory
- `.opencode/commands/` for slash commands
- `prompts/` for reusable drafting templates
- `.opencode/agents/` and `ai/AGENTS.md` for default agent behavior
- `.opencode/skills/` for specialized workflows
- `vault/00-start/` and `vault/03-context/process/` for durable process rules
Daily logs can preserve evidence, but they should not be the only place where a reusable behavior rule lives.