Add project-knowledge structure and templates

- 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:
2026-04-17 15:52:08 -06:00
parent 11fdb17fcb
commit dbc1894e27
175 changed files with 1163 additions and 914 deletions

View File

@@ -0,0 +1,39 @@
---
type: agent-memory
status: active
updated: 2026-04-17
tags:
- memory
- operations
---
# Operational Memory
Operational memory is the mechanism that turns daily evidence into durable, searchable project knowledge.
The reusable model lives in `core/memory/operational-memory.md`. This file records the active agent-specific interpretation for this workspace.
---
## 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/`.
- `tooling-behavior`: agent and workspace behavior in `agent-memory/`, `.opencode/`, `prompts/`, `scripts/`, and `core/`.
---
## Evidence Boundary
Raw evidence stays outside project knowledge:
- `ai/inbox/`
- `scripts/mattermost/generated/`
- `scripts/slack/generated/`
Only curated, high-confidence project facts should be promoted into `project-knowledge/`.