Files

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

Raw Permalink Blame History

type, status, updated, tags, related

type

status

updated

Workspace Architecture

This repository separates project knowledge from agent operation:

workspaces/fidelity/project-knowledge/ is the clean Obsidian second brain and transferable project memory.
agent-memory/ is the operating manual for the AI agent.
Everything else is technical runtime, reusable core, profile configuration, scripts, commands, prompts, or raw evidence.

Canonical Memory

Use these folders as the source of truth for project knowledge:

00-start/ for project onboarding and terminology
01-current/ for current work state
02-work-items/ for ticket/task memory
03-context/ for systems, workstreams, project-facing process, and iOS context
04-people/ for people and role memory
05-decisions/ for confirmed decisions
06-daily/ for daily notes
07-maps/ for graph hubs
08-bases/ for table-style review
09-templates/ for note templates

Runtime Outside The Vault

These folders are intentionally outside Obsidian memory:

.opencode/ stores agents and slash commands.
core/ stores reusable workspace logic.
profiles/ stores project-specific profile declarations.
scripts/ stores connectors, importers, and wrappers.
workspaces/fidelity/inbox/ stores live evidence from communication sync.
scripts/*/generated/ stores extracted evidence.

Runtime and generated files can be used as evidence, but durable project facts should be promoted into workspaces/fidelity/project-knowledge/.

Agent behavior rules belong in agent-memory/, not in the project vault.

Memory Access Layer

Use scripts/memory/ as the platform-agnostic interface to canonical memory.

Obsidian is the current visual and CLI-backed adapter, but the source of truth remains Markdown under workspaces/fidelity/project-knowledge/.

Agents use scripts/memory/memory.sh create when a new typed note is needed.
Agents use scripts/memory/memory.sh search or direct Markdown reads for context lookup.
Agents use scripts/memory/memory.sh base-query and health for structured review.
Precise memory edits should still be made directly to Markdown so changes stay auditable.

Memory Rule

Promoted memory lives in workspaces/fidelity/project-knowledge/.

Raw inbox and generated connector evidence stays outside the vault until the agent promotes durable facts.

2.5 KiB Raw Permalink Blame History