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.

.opencode/agents/workspace.md

@@ -12,12 +12,13 @@ Behavior rules:
 
 - Load `core/` first for project-independent operating rules.
 - Load the active profile from `AIW_PROJECT_PROFILE` when available; otherwise use the configured project files in this workspace.
-- Treat `vault/` as the canonical clean knowledge base.
+- Treat `project-knowledge/` as the canonical clean project knowledge base.
+- Treat `agent-memory/` as the operating memory for agent behavior, learning, promotion, verification, and self-maintenance rules.
 - Treat `scripts/memory/` as the stable memory access layer.
 - Treat tool-specific integrations such as Obsidian as replaceable adapters.
 - Treat profile files as configuration and `ai/inbox/` plus generated connector files as raw evidence.
 - Keep Obsidian Bases clean by excluding templates and typing role maps separately from people.
-- When updating canonical vault notes, maintain relationship metadata and `updated` fields so the vault remains useful to both humans and agents.
+- When updating canonical project notes, maintain relationship metadata and `updated` fields so project knowledge remains useful to both humans and agents.
 - Before answering current-state questions, inspect current state, active work items, recent logs, and inbox evidence when available.
 - For learning-style questions, answer only from known context and verified facts, label assumptions and unknowns, and ask concise clarification questions when guessing would be misleading.
 - For learning sessions, prefer durable architecture, process, ownership, debugging strategy, release mechanics, domain concepts, and decision rules over transient status.
@@ -25,8 +26,8 @@ Behavior rules:
 - Treat user corrections during learning sessions as high-value input and update the smallest correct canonical file or behavior surface when the learning should persist.
 - For any meaningful prompt, decide whether it adds, corrects, or invalidates memory.
 - Update the smallest correct canonical file when memory should change.
-- Use the memory interface to create new typed notes and inspect vault health, then edit Markdown directly for precise curation.
-- If the user corrects recurring behavior, update the command, prompt, agent, skill, vault process note, or other control file that enforces that behavior.
+- Use the memory interface to create new typed notes and inspect project knowledge health, then edit Markdown directly for precise curation.
+- If the user corrects recurring behavior, update the command, prompt, agent, skill, `agent-memory/` note, or other control file that enforces that behavior.
 - Keep imported evidence separate from promoted memory.
 - If an integration or sync command fails, do not update project memory from that failure.
 - Do not promote tooling noise, empty syncs, dependency failures, or generic chat chatter unless the user explicitly asks to track tooling work.
@@ -37,11 +38,11 @@ Behavior rules:
 
 Memory destinations:
 
-- daily facts -> `vault/06-daily/YYYY-MM-DD.md`
-- current priorities -> `vault/01-current/current-work.md`
-- active work items -> `vault/02-work-items/*.md`
-- active-work summary -> `vault/01-current/work-items.md`
-- durable project knowledge -> `vault/03-context/`
-- people and roles -> `vault/04-people/`
-- confirmed decisions -> `vault/05-decisions/`
-- reusable behavior -> `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.opencode/skills/`, `vault/00-start/`, or `vault/03-context/process/`
+- daily facts -> `project-knowledge/06-daily/YYYY-MM-DD.md`
+- current priorities -> `project-knowledge/01-current/current-work.md`
+- active work items -> `project-knowledge/02-work-items/*.md`
+- active-work summary -> `project-knowledge/01-current/work-items.md`
+- durable project knowledge -> `project-knowledge/03-context/`
+- people and roles -> `project-knowledge/04-people/`
+- confirmed decisions -> `project-knowledge/05-decisions/`
+- reusable behavior -> `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.opencode/skills/`, `agent-memory/`, `core/`, or `scripts/`