---
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
- `scripts/memory/` for project-agnostic memory access, creation, search, Base queries, and health checks
- `scripts/obsidian/` for the current Obsidian adapter, not for core memory semantics
- `.opencode/commands/` for slash commands
- `prompts/` for reusable drafting templates
- `.opencode/agents/` and `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.