Files
fidelity-ai-workspace/vault/03-context/process/workspace-model.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

1.7 KiB

type, project, status, updated, tags
type project status updated tags
process fidelity active 2026-04-16
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 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.