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.
This commit is contained in:
2026-05-21 12:28:07 -06:00
parent 7cbb49134a
commit 1ad707373a
203 changed files with 449 additions and 434 deletions

View File

@@ -7,9 +7,9 @@ Shared rules and context already live in the normal workspace files. Do not dupl
Read these first:
@./AGENTS.md
@./project-knowledge/00-start/start-here.md
@./project-knowledge/01-current/current-work.md
@./project-knowledge/01-current/work-items.md
@./workspaces/fidelity/project-knowledge/00-start/start-here.md
@./workspaces/fidelity/project-knowledge/01-current/current-work.md
@./workspaces/fidelity/project-knowledge/01-current/work-items.md
## Tool Surface
@@ -17,7 +17,7 @@ Read these first:
- `.agents/` is the canonical shared cross-platform surface for workflows and reusable rule/skill content.
- `.opencode/` is the OpenCode compatibility/runtime surface.
- `.agent/` is an alias for tools that expect the singular directory naming.
- `project-knowledge/` is canonical project memory.
- `workspaces/fidelity/project-knowledge/` is canonical project memory.
- `agent-memory/` is agent operating memory.
## Gemini-Specific Operating Notes
@@ -26,4 +26,4 @@ Read these first:
- Follow `AGENTS.md` as the shared source of truth for answer-first behavior, memory promotion, and lazy loading.
- For analysis, review, translation, or drafting prompts, answer first and persist second unless saving the fact is clearly required to produce a safe answer.
- Do not create new canonical notes in the critical path of a simple answer unless the user explicitly asked to save the information or the destination is obvious and non-blocking.
- When memory should be updated, prefer the smallest correct change to `project-knowledge/` and avoid duplicating stale and corrected versions.
- When memory should be updated, prefer the smallest correct change to `workspaces/fidelity/project-knowledge/` and avoid duplicating stale and corrected versions.