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:
@@ -18,22 +18,22 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
|
||||
|
||||
- Update canonical context when a durable fact changes.
|
||||
- Prefer correcting stale context over appending contradictory notes.
|
||||
- Keep `project-knowledge/` human-facing and project-facing: write it as an engineer maintaining shared project notes, not as an AI maintaining its own operating instructions.
|
||||
- Do not place agent-only logic, output contracts, prompting tactics, evaluation heuristics, or command-behavior rules in `project-knowledge/` unless a human engineer on the project would reasonably want that exact guidance there.
|
||||
- Put agent behavior, prompt logic, formatting contracts, and slash-command rules in `agent-memory/`, `.opencode/commands/`, `prompts/`, `.opencode/agents/`, or `.agents/skills/` instead of `project-knowledge/`.
|
||||
- Keep `workspaces/fidelity/project-knowledge/` human-facing and project-facing: write it as an engineer maintaining shared project notes, not as an AI maintaining its own operating instructions.
|
||||
- Do not place agent-only logic, output contracts, prompting tactics, evaluation heuristics, or command-behavior rules in `workspaces/fidelity/project-knowledge/` unless a human engineer on the project would reasonably want that exact guidance there.
|
||||
- Put agent behavior, prompt logic, formatting contracts, and slash-command rules in `agent-memory/`, `.opencode/commands/`, `prompts/`, `.opencode/agents/`, or `.agents/skills/` instead of `workspaces/fidelity/project-knowledge/`.
|
||||
- If a canonical note appears in an Obsidian Base, update its frontmatter properties together with the prose content.
|
||||
- When changing frontmatter properties on existing canonical notes, prefer Obsidian CLI property operations through `scripts/obsidian/cli.sh` when available so YAML spacing and property formatting stay clean; fall back to direct Markdown edits only when the CLI is unavailable or the operation is unsupported.
|
||||
- Keep templates under `project-knowledge/09-templates/` out of real-note Bases by filtering the template folder.
|
||||
- Keep templates under `workspaces/fidelity/project-knowledge/09-templates/` out of real-note Bases by filtering the template folder.
|
||||
- Role mapping files should not use `type: person`; reserve `type: person` for actual people profiles.
|
||||
- Work-item notes should keep known `systems`, `workstreams`, `people`, and `related` properties current.
|
||||
- Daily notes should keep `focus`, `work-items`, and `blockers` properties current when the values are clear.
|
||||
- Use the smallest correct destination:
|
||||
- `project-knowledge/06-daily/YYYY-MM-DD.md` for daily progress and evolving findings
|
||||
- `project-knowledge/01-current/current-work.md` for near-term active work
|
||||
- `project-knowledge/02-work-items/*.md` for canonical Jira-linked active work
|
||||
- `project-knowledge/01-current/work-items.md` for the compact active-work summary
|
||||
- `project-knowledge/03-context/` for durable project knowledge
|
||||
- `project-knowledge/04-people/` for named person context
|
||||
- `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md` for daily progress and evolving findings
|
||||
- `workspaces/fidelity/project-knowledge/01-current/current-work.md` for near-term active work
|
||||
- `workspaces/fidelity/project-knowledge/02-work-items/*.md` for canonical Jira-linked active work
|
||||
- `workspaces/fidelity/project-knowledge/01-current/work-items.md` for the compact active-work summary
|
||||
- `workspaces/fidelity/project-knowledge/03-context/` for durable project knowledge
|
||||
- `workspaces/fidelity/project-knowledge/04-people/` for named person context
|
||||
- `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.agents/skills/`, `agent-memory/`, `core/`, or `scripts/` for reusable behavior rules that control how the workspace responds
|
||||
|
||||
---
|
||||
|
||||
@@ -17,12 +17,12 @@ The reusable model lives in `core/memory/operational-memory.md`. This file recor
|
||||
|
||||
## Memory Classes
|
||||
|
||||
- `daily`: dated progress and evidence in `project-knowledge/06-daily/`.
|
||||
- `state`: near-term active work in `project-knowledge/01-current/`.
|
||||
- `work-items`: ticket-scoped memory in `project-knowledge/02-work-items/`.
|
||||
- `stable-context`: durable systems, workstreams, process, and iOS context in `project-knowledge/03-context/`.
|
||||
- `people`: collaborators, stakeholders, and role mappings in `project-knowledge/04-people/`.
|
||||
- `decisions`: accepted durable decisions in `project-knowledge/05-decisions/`.
|
||||
- `daily`: dated progress and evidence in `workspaces/fidelity/project-knowledge/06-daily/`.
|
||||
- `state`: near-term active work in `workspaces/fidelity/project-knowledge/01-current/`.
|
||||
- `work-items`: ticket-scoped memory in `workspaces/fidelity/project-knowledge/02-work-items/`.
|
||||
- `stable-context`: durable systems, workstreams, process, and iOS context in `workspaces/fidelity/project-knowledge/03-context/`.
|
||||
- `people`: collaborators, stakeholders, and role mappings in `workspaces/fidelity/project-knowledge/04-people/`.
|
||||
- `decisions`: accepted durable decisions in `workspaces/fidelity/project-knowledge/05-decisions/`.
|
||||
- `tooling-behavior`: agent and workspace behavior in `agent-memory/`, `.opencode/`, `prompts/`, `scripts/`, and `core/`.
|
||||
|
||||
---
|
||||
@@ -31,9 +31,9 @@ The reusable model lives in `core/memory/operational-memory.md`. This file recor
|
||||
|
||||
Raw evidence stays outside project knowledge:
|
||||
|
||||
- `ai/inbox/`
|
||||
- `workspaces/fidelity/inbox/`
|
||||
- `scripts/mattermost/generated/`
|
||||
- `scripts/slack/generated/`
|
||||
|
||||
Only curated, high-confidence project facts should be promoted into `project-knowledge/`.
|
||||
Only curated, high-confidence project facts should be promoted into `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ If a fact is ambiguous, skip it or keep it only in the daily log with appropriat
|
||||
|
||||
## File Selection
|
||||
|
||||
### Promote to `project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
|
||||
Use the daily log for:
|
||||
|
||||
@@ -37,7 +37,7 @@ Use the daily log for:
|
||||
|
||||
Daily logs are the default destination for most promoted Mattermost facts.
|
||||
|
||||
### Promote to `project-knowledge/01-current/current-work.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/01-current/current-work.md`
|
||||
|
||||
Use current state only for facts that materially affect active work over the next few days, such as:
|
||||
|
||||
@@ -48,9 +48,9 @@ Use current state only for facts that materially affect active work over the nex
|
||||
|
||||
Do not copy every daily update into current state.
|
||||
|
||||
### Promote to `project-knowledge/02-work-items/*.md` and `project-knowledge/01-current/work-items.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/02-work-items/*.md` and `workspaces/fidelity/project-knowledge/01-current/work-items.md`
|
||||
|
||||
Use `project-knowledge/02-work-items/*.md` for:
|
||||
Use `workspaces/fidelity/project-knowledge/02-work-items/*.md` for:
|
||||
|
||||
- explicit Jira IDs
|
||||
- approved or explicit story titles
|
||||
@@ -60,9 +60,9 @@ Use `project-knowledge/02-work-items/*.md` for:
|
||||
|
||||
If a Jira item is likely to appear again in standups or manager updates, it belongs here.
|
||||
|
||||
Use `project-knowledge/01-current/work-items.md` as the compact summary of which ticket files are active.
|
||||
Use `workspaces/fidelity/project-knowledge/01-current/work-items.md` as the compact summary of which ticket files are active.
|
||||
|
||||
### Promote to `project-knowledge/03-context/project.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/03-context/project.md`
|
||||
|
||||
Use project context only for durable project knowledge that should survive beyond the current work window, such as:
|
||||
|
||||
@@ -73,11 +73,11 @@ Use project context only for durable project knowledge that should survive beyon
|
||||
|
||||
Do not promote story-specific daily movement into project context unless it changes durable project understanding.
|
||||
|
||||
### Promote to `project-knowledge/05-decisions/*.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/05-decisions/*.md`
|
||||
|
||||
Use decisions only for explicit confirmed decisions with medium or long-term impact.
|
||||
|
||||
### Promote to `project-knowledge/04-people/index.md` and `project-knowledge/04-people/*.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/04-people/index.md` and `workspaces/fidelity/project-knowledge/04-people/*.md`
|
||||
|
||||
Use these files when:
|
||||
|
||||
@@ -141,5 +141,5 @@ Given Mattermost updates like:
|
||||
Automatic behavior should be:
|
||||
|
||||
- add all of them to today's log if they are relevant to today's work
|
||||
- promote only the currently actionable subset to `project-knowledge/01-current/current-work.md`
|
||||
- keep story-specific details out of `project-knowledge/03-context/project.md` unless they reveal a durable project rule
|
||||
- promote only the currently actionable subset to `workspaces/fidelity/project-knowledge/01-current/current-work.md`
|
||||
- keep story-specific details out of `workspaces/fidelity/project-knowledge/03-context/project.md` unless they reveal a durable project rule
|
||||
|
||||
Reference in New Issue
Block a user