david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add project-knowledge structure and templates

Browse Source 
- 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.
This commit is contained in:
David Delagneau
2026-04-17 15:52:08 -06:00
parent 11fdb17fcb
commit dbc1894e27
175 changed files with 1163 additions and 914 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.opencode/commands/archive-import.md
View File

@@ -24,12 +24,12 @@ Read:
@core/README.md
@core/memory/operational-memory.md
@core/integrations/communication-model.md
@vault/01-current/current-work.md
@vault/01-current/work-items.md
@vault/03-context/project.md
@vault/03-context/process/context-maintenance.md
@vault/04-people/index.md
@vault/04-people/manager.md
@project-knowledge/01-current/current-work.md
@project-knowledge/01-current/work-items.md
@project-knowledge/03-context/project.md
@agent-memory/memory/context-maintenance.md
@project-knowledge/04-people/index.md
@project-knowledge/04-people/manager.md
Imported summary, if present:
@@ -44,11 +44,11 @@ Instructions:
- treat the archive as historical evidence
- promote durable project-relevant context automatically when confidence is high
- prefer durable role/person associations, recurring architecture patterns, repeated work-item references, approval/scope history, and process lessons
- create or update `vault/04-people/*.md` when a human repeatedly affects project flow
- create or update `project-knowledge/04-people/*.md` when a human repeatedly affects project flow
- avoid promoting outdated daily status unless it changes current understanding
- update existing memory when the archive clarifies or corrects it
- keep ambiguous or likely outdated facts as archive-only context
- write promoted memory to `vault/`
- write promoted memory to `project-knowledge/`
Return: