Files
fidelity-ai-workspace/agent-memory/workflows/workspace-model.md
david.delagneau 1ad707373a Add daily logs and templates for project fidelity
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
2026-05-21 12:28:07 -06:00

2.5 KiB

type, status, updated, tags
type status updated tags
agent-workflow active 2026-04-17
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
  • workspaces/fidelity/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
  • workspaces/fidelity/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
  • .agents/workflows/ for slash commands (with .opencode/commands/ for compatibility)
  • prompts/ for reusable drafting templates
  • .agents/rules/ and AGENTS.md for default agent behavior
  • .agents/skills/ for specialized workflows. Do not mirror into .opencode/skills/; OpenCode discovers .agents/skills/ directly.
  • workspaces/fidelity/project-knowledge/00-start/ and workspaces/fidelity/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.