david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
2.3 KiB
2.3 KiB
type, project, status, updated, tags
| type | project | status | updated | tags | ||
|---|---|---|---|---|---|---|
| process | fidelity | active | 2026-04-16 |
|
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.
- Keep templates under
vault/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:
vault/06-daily/YYYY-MM-DD.mdfor daily progress and evolving findingsvault/01-current/current-work.mdfor near-term active workvault/02-work-items/*.mdfor canonical Jira-linked active workvault/01-current/work-items.mdfor the compact active-work summaryvault/03-context/for durable project knowledgevault/04-people/for named person context.opencode/commands/,prompts/,.opencode/agents/,.opencode/skills/,vault/00-start/, orvault/03-context/process/for reusable behavior rules that control how the workspace responds
Ingestion Rules
- Treat Mattermost, Slack history, and direct prompts as potential memory sources.
- 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.