fidelity-ai-workspace/.agents/workflows/log-note.md at 60868b9c96147e140e746ed2519d3badb3f1fb5b

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

1.7 KiB

Raw Blame History

description

description
Update today's log from rough notes or contextual notes

Use this command for quick same-day note capture.

Read:

@README.md @core/README.md @core/memory/operational-memory.md @workspaces/fidelity/project-knowledge/01-current/current-work.md @workspaces/fidelity/project-knowledge/01-current/work-items.md @workspaces/fidelity/project-knowledge/03-context/project.md @workspaces/fidelity/project-knowledge/03-context/workstreams/index.md @agent-memory/memory/context-maintenance.md

Today's existing log, if present:

!if [ -f workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md ]; then cat workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi

Incorporate these new rough notes into today's log:

$ARGUMENTS

Instructions:

use workspace-memory-curation when available
Update or create workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md
Maintain daily-note frontmatter for Obsidian Bases: date, focus, work-items, blockers, and updated
Preserve concrete technical meaning
Capture both technical findings and communication context when relevant
Keep the log concise but reusable for later standups and manager updates
If the notes are ambiguous, normalize them without inventing facts
If a note clearly corrects or sharpens existing current memory, update the corresponding canonical file as well
If a note reveals durable system, workstream, process, or people context, update the relevant canonical file instead of only appending to the log
Prefer sync-context for broader memory updates; use this command for fast daily capture

After editing, respond with:

What was added or clarified
Whether any broader memory was also updated

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History