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:
71
agent-memory/workflows/workspace-architecture.md
Normal file
71
agent-memory/workflows/workspace-architecture.md
Normal file
@@ -0,0 +1,71 @@
|
||||
---
|
||||
type: agent-workflow
|
||||
status: active
|
||||
updated: 2026-04-17
|
||||
tags: [onboarding, obsidian, workspace]
|
||||
related:
|
||||
- ../maps/ai-workspace-core.md
|
||||
---
|
||||
|
||||
# Workspace Architecture
|
||||
|
||||
This repository separates project knowledge from agent operation:
|
||||
|
||||
- `project-knowledge/` is the clean Obsidian second brain and transferable project memory.
|
||||
- `agent-memory/` is the operating manual for the AI agent.
|
||||
- Everything else is technical runtime, reusable core, profile configuration, scripts, commands, prompts, or raw evidence.
|
||||
|
||||
---
|
||||
|
||||
## Canonical Memory
|
||||
|
||||
Use these folders as the source of truth for project knowledge:
|
||||
|
||||
- `00-start/` for project onboarding and terminology
|
||||
- `01-current/` for current work state
|
||||
- `02-work-items/` for ticket/task memory
|
||||
- `03-context/` for systems, workstreams, project-facing process, and iOS context
|
||||
- `04-people/` for people and role memory
|
||||
- `05-decisions/` for confirmed decisions
|
||||
- `06-daily/` for daily notes
|
||||
- `07-maps/` for graph hubs
|
||||
- `08-bases/` for table-style review
|
||||
- `09-templates/` for note templates
|
||||
|
||||
---
|
||||
|
||||
## Runtime Outside The Vault
|
||||
|
||||
These folders are intentionally outside Obsidian memory:
|
||||
|
||||
- `.opencode/` stores agents and slash commands.
|
||||
- `core/` stores reusable workspace logic.
|
||||
- `profiles/` stores project-specific profile declarations.
|
||||
- `scripts/` stores connectors, importers, and wrappers.
|
||||
- `ai/inbox/` stores live evidence from communication sync.
|
||||
- `scripts/*/generated/` stores extracted evidence.
|
||||
|
||||
Runtime and generated files can be used as evidence, but durable project facts should be promoted into `project-knowledge/`.
|
||||
|
||||
Agent behavior rules belong in `agent-memory/`, not in the project vault.
|
||||
|
||||
---
|
||||
|
||||
## Memory Access Layer
|
||||
|
||||
Use `scripts/memory/` as the platform-agnostic interface to canonical memory.
|
||||
|
||||
Obsidian is the current visual and CLI-backed adapter, but the source of truth remains Markdown under `project-knowledge/`.
|
||||
|
||||
- Agents use `scripts/memory/memory.sh create` when a new typed note is needed.
|
||||
- Agents use `scripts/memory/memory.sh search` or direct Markdown reads for context lookup.
|
||||
- Agents use `scripts/memory/memory.sh base-query` and `health` for structured review.
|
||||
- Precise memory edits should still be made directly to Markdown so changes stay auditable.
|
||||
|
||||
---
|
||||
|
||||
## Memory Rule
|
||||
|
||||
Promoted memory lives in `project-knowledge/`.
|
||||
|
||||
Raw inbox and generated connector evidence stays outside the vault until the agent promotes durable facts.
|
||||
Reference in New Issue
Block a user