david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
62 lines
2.3 KiB
Markdown
62 lines
2.3 KiB
Markdown
---
|
|
type: agent-workflow
|
|
status: active
|
|
updated: 2026-04-17
|
|
tags: [process, workspace, memory]
|
|
---
|
|
|
|
# Workspace Model
|
|
|
|
## Purpose
|
|
|
|
This repository is a support workspace, not the implementation repository.
|
|
|
|
It separates reusable tooling, project knowledge, and agent operating memory:
|
|
|
|
- `core/` contains reusable project-independent operating rules
|
|
- `profiles/<project>/` contains project-specific configuration and assumptions
|
|
- `project-knowledge/` contains transferable project documentation and current work memory
|
|
- `agent-memory/` contains agent behavior, learning, promotion, integration, and verification rules
|
|
|
|
---
|
|
|
|
## 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
|
|
- `project-knowledge/.obsidian/` only for portable Obsidian configuration, not project memory content
|
|
- `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
|
|
- `project-knowledge/00-start/` and `project-knowledge/03-context/process/` for project-facing onboarding and process rules
|
|
- `agent-memory/` for agent-specific behavior, learning, promotion, verification, and self-maintenance rules
|
|
|
|
Daily logs can preserve evidence, but they should not be the only place where a reusable behavior rule lives.
|