david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
3.0 KiB
3.0 KiB
type, status, updated, tags
| type | status | updated | tags | ||
|---|---|---|---|---|---|
| agent-memory | active | 2026-04-17 |
|
Context Maintenance
Goal
Keep this workspace useful as living memory instead of a pile of disconnected notes.
Stable Rules
- Update canonical context when a durable fact changes.
- Prefer correcting stale context over appending contradictory notes.
- 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.shwhen 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. - Role mapping files should not use
type: person; reservetype: personfor actual people profiles. - Work-item notes should keep known
systems,workstreams,people, andrelatedproperties current. - Daily notes should keep
focus,work-items, andblockersproperties current when the values are clear. - Use the smallest correct destination:
project-knowledge/06-daily/YYYY-MM-DD.mdfor daily progress and evolving findingsproject-knowledge/01-current/current-work.mdfor near-term active workproject-knowledge/02-work-items/*.mdfor canonical Jira-linked active workproject-knowledge/01-current/work-items.mdfor the compact active-work summaryproject-knowledge/03-context/for durable project knowledgeproject-knowledge/04-people/for named person context.opencode/commands/,prompts/,.opencode/agents/,.opencode/skills/,agent-memory/,core/, orscripts/for reusable behavior rules that control how the workspace responds
Ingestion Rules
- Treat Mattermost, Slack history, and direct prompts as potential memory sources.
- Treat learning sessions as durable-understanding sessions, not status refreshes.
- In learning sessions, prioritize architecture, ownership, release mechanics, debugging strategy, domain concepts, and process rules.
- Avoid promoting transient ticket status from learning sessions unless it exposes a reusable rule.
- Do not promote failed syncs or tooling errors as project facts.
- Promote repeated durable patterns from historical archives into stable context when confidence is high.
- Keep old status-only details archive-only unless they still change current understanding.
- Treat user corrections about command output, prompt structure, memory handling, or agent behavior as inputs to the operational surface, not just as daily notes.
Curation Rule
- If a new stable context file is added, keep
project.mdandindex.mdaligned so future sessions can discover it quickly. - If a new rule affects a slash command or reusable prompt, update that command or prompt directly so the behavior changes on the next run.