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.
1.2 KiB
1.2 KiB
type, status, updated, tags
| type | status | updated | tags | ||
|---|---|---|---|---|---|
| agent-memory | active | 2026-04-17 |
|
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 inproject-knowledge/06-daily/.state: near-term active work inproject-knowledge/01-current/.work-items: ticket-scoped memory inproject-knowledge/02-work-items/.stable-context: durable systems, workstreams, process, and iOS context inproject-knowledge/03-context/.people: collaborators, stakeholders, and role mappings inproject-knowledge/04-people/.decisions: accepted durable decisions inproject-knowledge/05-decisions/.tooling-behavior: agent and workspace behavior inagent-memory/,.opencode/,prompts/,scripts/, andcore/.
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/.