Add daily logs and templates for project fidelity
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
This commit is contained in:
@@ -11,7 +11,7 @@ tags:
|
||||
|
||||
This folder contains the operating memory for the AI agent.
|
||||
|
||||
It is not Fidelity project documentation. Do not transfer this folder as project knowledge for a new engineer. Transfer `project-knowledge/` for the project second brain, and use this folder to explain how the agent should maintain that knowledge.
|
||||
It is not Fidelity project documentation. Do not transfer this folder as project knowledge for a new engineer. Transfer `workspaces/fidelity/project-knowledge/` for the project second brain, and use this folder to explain how the agent should maintain that knowledge.
|
||||
|
||||
---
|
||||
|
||||
@@ -28,8 +28,8 @@ It is not Fidelity project documentation. Do not transfer this folder as project
|
||||
|
||||
## Relationship To Project Knowledge
|
||||
|
||||
- `project-knowledge/` is the clean Obsidian vault and project second brain.
|
||||
- `workspaces/fidelity/project-knowledge/` is the clean Obsidian vault and project second brain.
|
||||
- `agent-memory/` is the agent operating manual.
|
||||
- `ai/inbox/` and connector `generated/` folders are evidence, not canonical memory.
|
||||
- `workspaces/fidelity/inbox/` and connector `generated/` folders are evidence, not canonical memory.
|
||||
- `scripts/memory/` is the project-agnostic interface for reading, searching, creating, querying, and validating project knowledge.
|
||||
- `scripts/obsidian/` is the current Obsidian adapter and must not become the core abstraction.
|
||||
|
||||
@@ -27,10 +27,10 @@ This applies to:
|
||||
- debugging discussions
|
||||
- corrections to previous understanding
|
||||
|
||||
The agent must not wait for a separate promotion command. The agent should proactively update `project-knowledge/` (including 01-current, 02-work-items, 03-context, 04-people, 06-daily) within the same conversational turn when new information is clear, durable, and the destination is obvious.
|
||||
The agent must not wait for a separate promotion command. The agent should proactively update `workspaces/fidelity/project-knowledge/` (including 01-current, 02-work-items, 03-context, 04-people, 06-daily) within the same conversational turn when new information is clear, durable, and the destination is obvious.
|
||||
|
||||
- When editing `project-knowledge/`, write as a human engineer maintaining shared project documentation.
|
||||
- Keep agent-operating logic out of `project-knowledge/`; store that logic in prompts, commands, skills, agents, or `agent-memory/`.
|
||||
- When editing `workspaces/fidelity/project-knowledge/`, write as a human engineer maintaining shared project documentation.
|
||||
- Keep agent-operating logic out of `workspaces/fidelity/project-knowledge/`; store that logic in prompts, commands, skills, agents, or `agent-memory/`.
|
||||
- Answer-first rule: when the user's main goal is analysis, review, translation, or drafting, answer first unless persistence is required to avoid losing a clear durable fact.
|
||||
- Do not create a brand-new canonical note during the critical path of the answer unless the user explicitly asked to save the fact or the new note is the smallest correct update.
|
||||
- Prefer updating an existing canonical note over creating a new file when both are valid.
|
||||
@@ -71,7 +71,7 @@ Avoid low-value learning-session questions such as:
|
||||
- whether a specific PR was approved today
|
||||
- whether a ticket moved columns today
|
||||
- what the next standup line should be
|
||||
- temporary sequencing questions that belong in `project-knowledge/01-current/` or `project-knowledge/06-daily/`
|
||||
- temporary sequencing questions that belong in `workspaces/fidelity/project-knowledge/01-current/` or `workspaces/fidelity/project-knowledge/06-daily/`
|
||||
|
||||
Prefer high-value questions such as:
|
||||
|
||||
@@ -130,7 +130,7 @@ Examples:
|
||||
- A standup formatting correction should update `prompts/standup.md` and the shared workflow in `.agents/workflows/standup.md`.
|
||||
- A Mattermost freshness correction should update the Mattermost command/plugin instructions.
|
||||
- A Copilot prompt-structure correction should update `prompts/copilot-prompt.md`, `.agents/workflows/copilot-prompt.md`, or the shared skill/rule source.
|
||||
- A Swift answer-quality correction should update the relevant iOS skill or `project-knowledge/03-context/ios/` guidance.
|
||||
- A Swift answer-quality correction should update the relevant iOS skill or `workspaces/fidelity/project-knowledge/03-context/ios/` guidance.
|
||||
|
||||
Keep the daily log as evidence of what happened, but make the reusable behavior live in the file that controls that behavior.
|
||||
|
||||
@@ -138,7 +138,7 @@ Keep the daily log as evidence of what happened, but make the reusable behavior
|
||||
|
||||
## File Selection
|
||||
|
||||
### `project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
### `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
|
||||
Default destination for:
|
||||
|
||||
@@ -148,7 +148,7 @@ Default destination for:
|
||||
- story and approval movement
|
||||
- context that is important now but may evolve later
|
||||
|
||||
### `project-knowledge/01-current/current-work.md`
|
||||
### `workspaces/fidelity/project-knowledge/01-current/current-work.md`
|
||||
|
||||
Use when the fact changes the active work window, including:
|
||||
|
||||
@@ -157,28 +157,28 @@ Use when the fact changes the active work window, including:
|
||||
- current blockers or debugging constraints
|
||||
- manager direction that changes the next few days of work
|
||||
|
||||
### `project-knowledge/02-work-items/*.md` and `project-knowledge/01-current/work-items.md`
|
||||
### `workspaces/fidelity/project-knowledge/02-work-items/*.md` and `workspaces/fidelity/project-knowledge/01-current/work-items.md`
|
||||
|
||||
Use `project-knowledge/02-work-items/*.md` as the canonical memory for current Jira-linked work that should remain easy to reference across sessions, especially:
|
||||
Use `workspaces/fidelity/project-knowledge/02-work-items/*.md` as the canonical memory for current Jira-linked work that should remain easy to reference across sessions, especially:
|
||||
|
||||
- Jira IDs
|
||||
- approved or explicit titles
|
||||
- currently relevant status notes
|
||||
- current points or scope notes
|
||||
|
||||
Use `project-knowledge/01-current/work-items.md` as the summary view of what is active now.
|
||||
Use `workspaces/fidelity/project-knowledge/01-current/work-items.md` as the summary view of what is active now.
|
||||
|
||||
These files should help standups and manager updates mention work items precisely.
|
||||
|
||||
### `project-knowledge/03-context/project.md`
|
||||
### `workspaces/fidelity/project-knowledge/03-context/project.md`
|
||||
|
||||
Use for durable project knowledge that should survive beyond the current work window.
|
||||
|
||||
### `project-knowledge/04-people/manager.md`
|
||||
### `workspaces/fidelity/project-knowledge/04-people/manager.md`
|
||||
|
||||
Use only when a communication preference or manager expectation becomes stable enough to reuse repeatedly.
|
||||
|
||||
### `project-knowledge/04-people/index.md` and `project-knowledge/04-people/*.md`
|
||||
### `workspaces/fidelity/project-knowledge/04-people/index.md` and `workspaces/fidelity/project-knowledge/04-people/*.md`
|
||||
|
||||
Use these files for:
|
||||
|
||||
@@ -192,7 +192,7 @@ When the role is not explicit, store:
|
||||
- what kinds of topics they influence
|
||||
- how they affect approvals, scope, debugging, or communication
|
||||
|
||||
### `project-knowledge/05-decisions/*.md`
|
||||
### `workspaces/fidelity/project-knowledge/05-decisions/*.md`
|
||||
|
||||
Use for explicit confirmed decisions with ongoing impact.
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ The agent must keep the workspace behavior aligned with recurring user correctio
|
||||
- Update `.opencode/agents/` and `AGENTS.md` for default agent behavior.
|
||||
- Update `.agents/skills/` for specialized workflows.
|
||||
- Update `agent-memory/` for reusable agent operating rules.
|
||||
- Update `project-knowledge/` only when the correction changes project knowledge or project-facing process documentation.
|
||||
- Update `workspaces/fidelity/project-knowledge/` only when the correction changes project knowledge or project-facing process documentation.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -17,18 +17,18 @@ Communication connectors extract evidence. The agent decides what to promote.
|
||||
|
||||
Mattermost is the current live communication connector.
|
||||
|
||||
- Primary local evidence is the Mattermost proxy mirror under `ai/inbox/mattermost-mirror/` when present.
|
||||
- Prefer `ai/inbox/mattermost-mirror/latest.md` / `latest.jsonl` for latest-message context, `by-date/YYYY/MM/YYYY-MM-DD.jsonl` for daily/standup context, `channels/<channel>/YYYY/MM/YYYY-MM-DD.jsonl` for channel-specific context, and `threads/<root-or-post-id>.jsonl` for thread-specific context.
|
||||
- Primary local evidence is the Mattermost proxy mirror under `workspaces/fidelity/inbox/mattermost-mirror/` when present.
|
||||
- Prefer `workspaces/fidelity/inbox/mattermost-mirror/latest.md` / `latest.jsonl` for latest-message context, `by-date/YYYY/MM/YYYY-MM-DD.jsonl` for daily/standup context, `channels/<channel>/YYYY/MM/YYYY-MM-DD.jsonl` for channel-specific context, and `threads/<root-or-post-id>.jsonl` for thread-specific context.
|
||||
- Use `scripts/mattermost-proxy/read-context.py` from commands/workflows instead of reading ad hoc files; it prefers the proxy mirror and falls back to legacy sync artifacts.
|
||||
- Legacy fresh output may still go to `ai/inbox/mattermost-latest.md`.
|
||||
- Legacy fresh output may still go to `workspaces/fidelity/inbox/mattermost-latest.md`.
|
||||
- Legacy generated extraction artifacts stay under `scripts/mattermost/generated/`.
|
||||
- Failed syncs must not update project knowledge.
|
||||
- Latest-message requests must refresh Mattermost before answering.
|
||||
- Latest-message requests are read-first. The agent may identify a memory update candidate, but should not edit `project-knowledge/` from the latest-message command unless the user explicitly asks to promote the fact.
|
||||
- Latest-message requests are read-first. The agent may identify a memory update candidate, but should not edit `workspaces/fidelity/project-knowledge/` from the latest-message command unless the user explicitly asks to promote the fact.
|
||||
- Standup generation is a separate required-refresh flow: it must fetch Mattermost before drafting, even though general prompts should not sync automatically.
|
||||
- Standup reads should use the focused reader mode, `scripts/mattermost-proxy/read-context.py --mode standup --today YYYY-MM-DD`, which reads date-bucketed previous-workday/today records and should use the active profile's configured `AIW_MATTERMOST_CONTEXT_CHANNELS` when available. Avoid loading broad mirror `latest.md` into standup prompts because it may include stale or unrelated channels and waste tokens. Keep project-specific channel names out of reusable connector code.
|
||||
- If adding MCP support for Mattermost, treat it as a read-only query wrapper over the existing proxy mirror and `read-context.py`, not as a replacement for the capture/mirror pipeline. Keep the mirror's file layout as canonical raw evidence and expose only narrow tools such as latest, standup/date, channel, and thread reads with channel filters and limits.
|
||||
- Do not build a write-capable Mattermost MCP or expose tokens, cookies, raw headers, or broad unfiltered raw dumps through MCP. MCP output should remain evidence for agent reasoning; promotion to `project-knowledge/` still follows normal memory rules.
|
||||
- Do not build a write-capable Mattermost MCP or expose tokens, cookies, raw headers, or broad unfiltered raw dumps through MCP. MCP output should remain evidence for agent reasoning; promotion to `workspaces/fidelity/project-knowledge/` still follows normal memory rules.
|
||||
- If the proxy mirror is running, treat it as fresher than legacy `mattermost-latest.md` / generated JSONL. Do not ignore mirror evidence merely because a legacy sync command also ran.
|
||||
- Do not refresh Mattermost just because a prompt mentions a manager or stakeholder.
|
||||
- Treat document review, message polishing, translation, and "does this align with Jeff's expectations?" prompts as normal drafting tasks unless the user explicitly asks for the latest message or fresh Mattermost evidence.
|
||||
@@ -42,6 +42,6 @@ Mattermost is the current live communication connector.
|
||||
|
||||
Slack export import is the current historical archive connector.
|
||||
|
||||
- Archive evidence stays outside `project-knowledge/`.
|
||||
- Archive evidence stays outside `workspaces/fidelity/project-knowledge/`.
|
||||
- Promote only durable project facts, people context, process rules, or historical architecture lessons.
|
||||
- Do not promote dated status details unless they explain current context.
|
||||
|
||||
@@ -15,7 +15,7 @@ Use mem9 as a cross-session, cross-agent recall layer without replacing the work
|
||||
|
||||
## Source Of Truth
|
||||
|
||||
`project-knowledge/` remains the canonical human-readable Fidelity project memory.
|
||||
`workspaces/fidelity/project-knowledge/` remains the canonical human-readable Fidelity project memory.
|
||||
|
||||
`agent-memory/` remains the canonical operating memory for agent behavior, workflows, promotion rules, and integration guidance.
|
||||
|
||||
@@ -46,7 +46,7 @@ Do not bulk-import raw inboxes, generated sync output, full chat transcripts, or
|
||||
|
||||
1. Recall mem9 early for user preferences and relevant workspace history.
|
||||
2. Load hot Markdown context from `AGENTS.md` / `opencode.json` instructions.
|
||||
3. For current-work questions, still inspect `project-knowledge/01-current/current-work.md` and the latest relevant daily note.
|
||||
3. For current-work questions, still inspect `workspaces/fidelity/project-knowledge/01-current/current-work.md` and the latest relevant daily note.
|
||||
4. Answer or act from verified context.
|
||||
5. When the interaction adds durable knowledge, update canonical Markdown first; store a compact mem9 memory only if it improves future recall.
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Use `scripts/memory/memory.sh` as the project-agnostic interface to project know
|
||||
|
||||
## Default Root
|
||||
|
||||
The primary project knowledge directory is `project-knowledge/`.
|
||||
The primary project knowledge directory is `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
Environment variable precedence:
|
||||
|
||||
|
||||
@@ -16,13 +16,13 @@ Obsidian is the current interface over canonical Markdown memory. The workspace-
|
||||
|
||||
## Recommended Start
|
||||
|
||||
Open the `project-knowledge/` folder as the Obsidian vault, not the repository root and not `agent-memory/`.
|
||||
Open the `workspaces/fidelity/project-knowledge/` folder as the Obsidian vault, not the repository root and not `agent-memory/`.
|
||||
|
||||
Open:
|
||||
|
||||
- [Start Here](../../project-knowledge/00-start/start-here.md)
|
||||
- [New Member Onboarding](../../project-knowledge/00-start/onboarding.md)
|
||||
- [Knowledge Maps](../../project-knowledge/07-maps/index.md)
|
||||
- [Start Here](../../workspaces/fidelity/project-knowledge/00-start/start-here.md)
|
||||
- [New Member Onboarding](../../workspaces/fidelity/project-knowledge/00-start/onboarding.md)
|
||||
- [Knowledge Maps](../../workspaces/fidelity/project-knowledge/07-maps/index.md)
|
||||
|
||||
---
|
||||
|
||||
@@ -32,26 +32,26 @@ Open:
|
||||
|
||||
Start with:
|
||||
|
||||
- [New Member Onboarding](../../project-knowledge/00-start/onboarding.md)
|
||||
- [Glossary](../../project-knowledge/00-start/glossary.md)
|
||||
- [Current Work Map](../../project-knowledge/07-maps/current-work.md)
|
||||
- [Fidelity Domain Map](../../project-knowledge/07-maps/fidelity-domain.md)
|
||||
- [New Member Onboarding](../../workspaces/fidelity/project-knowledge/00-start/onboarding.md)
|
||||
- [Glossary](../../workspaces/fidelity/project-knowledge/00-start/glossary.md)
|
||||
- [Current Work Map](../../workspaces/fidelity/project-knowledge/07-maps/current-work.md)
|
||||
- [Fidelity Domain Map](../../workspaces/fidelity/project-knowledge/07-maps/fidelity-domain.md)
|
||||
|
||||
### Daily Work View
|
||||
|
||||
Start with:
|
||||
|
||||
- [Current Work Map](../../project-knowledge/07-maps/current-work.md)
|
||||
- [Work Items Map](../../project-knowledge/07-maps/work-items.md)
|
||||
- [Daily Notes Index](../../project-knowledge/06-daily/index.md)
|
||||
- [Current Work Map](../../workspaces/fidelity/project-knowledge/07-maps/current-work.md)
|
||||
- [Work Items Map](../../workspaces/fidelity/project-knowledge/07-maps/work-items.md)
|
||||
- [Daily Notes Index](../../workspaces/fidelity/project-knowledge/06-daily/index.md)
|
||||
|
||||
### System Understanding View
|
||||
|
||||
Start with:
|
||||
|
||||
- [Fidelity Domain Map](../../project-knowledge/07-maps/fidelity-domain.md)
|
||||
- [Fidelity Apps Map](../../project-knowledge/07-maps/fidelity-apps.md)
|
||||
- [People Map](../../project-knowledge/07-maps/people.md)
|
||||
- [Fidelity Domain Map](../../workspaces/fidelity/project-knowledge/07-maps/fidelity-domain.md)
|
||||
- [Fidelity Apps Map](../../workspaces/fidelity/project-knowledge/07-maps/fidelity-apps.md)
|
||||
- [People Map](../../workspaces/fidelity/project-knowledge/07-maps/people.md)
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -50,4 +50,4 @@ Reusable workspace logic and project-independent operating rules.
|
||||
## Project Profile
|
||||
|
||||
- Active project profile: `profiles/fidelity/profile.md`
|
||||
- Project knowledge vault: `project-knowledge/`
|
||||
- Project knowledge vault: `workspaces/fidelity/project-knowledge/`
|
||||
|
||||
@@ -75,5 +75,5 @@ Commands, prompts, skills, workflows, and automation surfaces that make the work
|
||||
- Project-agnostic memory scripts: `scripts/memory/`
|
||||
- Current Obsidian adapter: `scripts/obsidian/`
|
||||
- Obsidian MCP migration plan: `agent-memory/workflows/obsidian-mcp-migration.md`
|
||||
- Project knowledge vault: `project-knowledge/`
|
||||
- Project knowledge vault: `workspaces/fidelity/project-knowledge/`
|
||||
- Agent operating memory: `agent-memory/`
|
||||
|
||||
@@ -18,22 +18,22 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
|
||||
|
||||
- Update canonical context when a durable fact changes.
|
||||
- Prefer correcting stale context over appending contradictory notes.
|
||||
- Keep `project-knowledge/` human-facing and project-facing: write it as an engineer maintaining shared project notes, not as an AI maintaining its own operating instructions.
|
||||
- Do not place agent-only logic, output contracts, prompting tactics, evaluation heuristics, or command-behavior rules in `project-knowledge/` unless a human engineer on the project would reasonably want that exact guidance there.
|
||||
- Put agent behavior, prompt logic, formatting contracts, and slash-command rules in `agent-memory/`, `.opencode/commands/`, `prompts/`, `.opencode/agents/`, or `.agents/skills/` instead of `project-knowledge/`.
|
||||
- Keep `workspaces/fidelity/project-knowledge/` human-facing and project-facing: write it as an engineer maintaining shared project notes, not as an AI maintaining its own operating instructions.
|
||||
- Do not place agent-only logic, output contracts, prompting tactics, evaluation heuristics, or command-behavior rules in `workspaces/fidelity/project-knowledge/` unless a human engineer on the project would reasonably want that exact guidance there.
|
||||
- Put agent behavior, prompt logic, formatting contracts, and slash-command rules in `agent-memory/`, `.opencode/commands/`, `prompts/`, `.opencode/agents/`, or `.agents/skills/` instead of `workspaces/fidelity/project-knowledge/`.
|
||||
- If a canonical note appears in an Obsidian Base, update its frontmatter properties together with the prose content.
|
||||
- When changing frontmatter properties on existing canonical notes, prefer Obsidian CLI property operations through `scripts/obsidian/cli.sh` when available so YAML spacing and property formatting stay clean; fall back to direct Markdown edits only when the CLI is unavailable or the operation is unsupported.
|
||||
- Keep templates under `project-knowledge/09-templates/` out of real-note Bases by filtering the template folder.
|
||||
- Keep templates under `workspaces/fidelity/project-knowledge/09-templates/` out of real-note Bases by filtering the template folder.
|
||||
- Role mapping files should not use `type: person`; reserve `type: person` for actual people profiles.
|
||||
- Work-item notes should keep known `systems`, `workstreams`, `people`, and `related` properties current.
|
||||
- Daily notes should keep `focus`, `work-items`, and `blockers` properties current when the values are clear.
|
||||
- Use the smallest correct destination:
|
||||
- `project-knowledge/06-daily/YYYY-MM-DD.md` for daily progress and evolving findings
|
||||
- `project-knowledge/01-current/current-work.md` for near-term active work
|
||||
- `project-knowledge/02-work-items/*.md` for canonical Jira-linked active work
|
||||
- `project-knowledge/01-current/work-items.md` for the compact active-work summary
|
||||
- `project-knowledge/03-context/` for durable project knowledge
|
||||
- `project-knowledge/04-people/` for named person context
|
||||
- `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md` for daily progress and evolving findings
|
||||
- `workspaces/fidelity/project-knowledge/01-current/current-work.md` for near-term active work
|
||||
- `workspaces/fidelity/project-knowledge/02-work-items/*.md` for canonical Jira-linked active work
|
||||
- `workspaces/fidelity/project-knowledge/01-current/work-items.md` for the compact active-work summary
|
||||
- `workspaces/fidelity/project-knowledge/03-context/` for durable project knowledge
|
||||
- `workspaces/fidelity/project-knowledge/04-people/` for named person context
|
||||
- `.opencode/commands/`, `prompts/`, `.opencode/agents/`, `.agents/skills/`, `agent-memory/`, `core/`, or `scripts/` for reusable behavior rules that control how the workspace responds
|
||||
|
||||
---
|
||||
|
||||
@@ -17,12 +17,12 @@ The reusable model lives in `core/memory/operational-memory.md`. This file recor
|
||||
|
||||
## 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/`.
|
||||
- `daily`: dated progress and evidence in `workspaces/fidelity/project-knowledge/06-daily/`.
|
||||
- `state`: near-term active work in `workspaces/fidelity/project-knowledge/01-current/`.
|
||||
- `work-items`: ticket-scoped memory in `workspaces/fidelity/project-knowledge/02-work-items/`.
|
||||
- `stable-context`: durable systems, workstreams, process, and iOS context in `workspaces/fidelity/project-knowledge/03-context/`.
|
||||
- `people`: collaborators, stakeholders, and role mappings in `workspaces/fidelity/project-knowledge/04-people/`.
|
||||
- `decisions`: accepted durable decisions in `workspaces/fidelity/project-knowledge/05-decisions/`.
|
||||
- `tooling-behavior`: agent and workspace behavior in `agent-memory/`, `.opencode/`, `prompts/`, `scripts/`, and `core/`.
|
||||
|
||||
---
|
||||
@@ -31,9 +31,9 @@ The reusable model lives in `core/memory/operational-memory.md`. This file recor
|
||||
|
||||
Raw evidence stays outside project knowledge:
|
||||
|
||||
- `ai/inbox/`
|
||||
- `workspaces/fidelity/inbox/`
|
||||
- `scripts/mattermost/generated/`
|
||||
- `scripts/slack/generated/`
|
||||
|
||||
Only curated, high-confidence project facts should be promoted into `project-knowledge/`.
|
||||
Only curated, high-confidence project facts should be promoted into `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ If a fact is ambiguous, skip it or keep it only in the daily log with appropriat
|
||||
|
||||
## File Selection
|
||||
|
||||
### Promote to `project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md`
|
||||
|
||||
Use the daily log for:
|
||||
|
||||
@@ -37,7 +37,7 @@ Use the daily log for:
|
||||
|
||||
Daily logs are the default destination for most promoted Mattermost facts.
|
||||
|
||||
### Promote to `project-knowledge/01-current/current-work.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/01-current/current-work.md`
|
||||
|
||||
Use current state only for facts that materially affect active work over the next few days, such as:
|
||||
|
||||
@@ -48,9 +48,9 @@ Use current state only for facts that materially affect active work over the nex
|
||||
|
||||
Do not copy every daily update into current state.
|
||||
|
||||
### Promote to `project-knowledge/02-work-items/*.md` and `project-knowledge/01-current/work-items.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/02-work-items/*.md` and `workspaces/fidelity/project-knowledge/01-current/work-items.md`
|
||||
|
||||
Use `project-knowledge/02-work-items/*.md` for:
|
||||
Use `workspaces/fidelity/project-knowledge/02-work-items/*.md` for:
|
||||
|
||||
- explicit Jira IDs
|
||||
- approved or explicit story titles
|
||||
@@ -60,9 +60,9 @@ Use `project-knowledge/02-work-items/*.md` for:
|
||||
|
||||
If a Jira item is likely to appear again in standups or manager updates, it belongs here.
|
||||
|
||||
Use `project-knowledge/01-current/work-items.md` as the compact summary of which ticket files are active.
|
||||
Use `workspaces/fidelity/project-knowledge/01-current/work-items.md` as the compact summary of which ticket files are active.
|
||||
|
||||
### Promote to `project-knowledge/03-context/project.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/03-context/project.md`
|
||||
|
||||
Use project context only for durable project knowledge that should survive beyond the current work window, such as:
|
||||
|
||||
@@ -73,11 +73,11 @@ Use project context only for durable project knowledge that should survive beyon
|
||||
|
||||
Do not promote story-specific daily movement into project context unless it changes durable project understanding.
|
||||
|
||||
### Promote to `project-knowledge/05-decisions/*.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/05-decisions/*.md`
|
||||
|
||||
Use decisions only for explicit confirmed decisions with medium or long-term impact.
|
||||
|
||||
### Promote to `project-knowledge/04-people/index.md` and `project-knowledge/04-people/*.md`
|
||||
### Promote to `workspaces/fidelity/project-knowledge/04-people/index.md` and `workspaces/fidelity/project-knowledge/04-people/*.md`
|
||||
|
||||
Use these files when:
|
||||
|
||||
@@ -141,5 +141,5 @@ Given Mattermost updates like:
|
||||
Automatic behavior should be:
|
||||
|
||||
- add all of them to today's log if they are relevant to today's work
|
||||
- promote only the currently actionable subset to `project-knowledge/01-current/current-work.md`
|
||||
- keep story-specific details out of `project-knowledge/03-context/project.md` unless they reveal a durable project rule
|
||||
- promote only the currently actionable subset to `workspaces/fidelity/project-knowledge/01-current/current-work.md`
|
||||
- keep story-specific details out of `workspaces/fidelity/project-knowledge/03-context/project.md` unless they reveal a durable project rule
|
||||
|
||||
@@ -11,7 +11,7 @@ tags: [obsidian, mcp, migration, memory]
|
||||
|
||||
Replace the current Obsidian CLI-backed adapter path with an Obsidian MCP-first integration while preserving the workspace memory model:
|
||||
|
||||
- `project-knowledge/` remains the canonical source of truth
|
||||
- `workspaces/fidelity/project-knowledge/` remains the canonical source of truth
|
||||
- `scripts/memory/` remains the stable workspace memory contract
|
||||
- direct Markdown edits remain the safe fallback for precise curation
|
||||
- Obsidian stays an adapter/navigation layer, not a second memory store
|
||||
@@ -66,7 +66,7 @@ The migration should change the adapter, not the memory model.
|
||||
|
||||
- Do not move canonical memory out of Markdown
|
||||
- Do not encode promotion rules into the MCP layer
|
||||
- Do not make `project-knowledge/` depend on Obsidian-only storage
|
||||
- Do not make `workspaces/fidelity/project-knowledge/` depend on Obsidian-only storage
|
||||
- Do not remove direct Markdown editing as a fallback
|
||||
- Do not delete the current scripts until MCP coverage is validated in real use
|
||||
|
||||
@@ -116,7 +116,7 @@ Current Phase 1 checklist:
|
||||
- [x] Add OpenCode MCP config using `OBSIDIAN_API_KEY` environment substitution.
|
||||
- [x] Export `OBSIDIAN_API_KEY` in the shell that launches OpenCode.
|
||||
- [x] Restart OpenCode and confirm `opencode mcp list` shows `obsidian` connected.
|
||||
- [x] Validate read/search tools against `project-knowledge/` notes.
|
||||
- [x] Validate read/search tools against `workspaces/fidelity/project-knowledge/` notes.
|
||||
- [x] Validate write/append/delete behavior on a disposable test note before touching canonical memory.
|
||||
- [ ] Determine whether Bases/properties/backlinks/template behavior needs to remain on the existing CLI/direct-Markdown path.
|
||||
|
||||
@@ -208,9 +208,9 @@ Delete later only if truly unused:
|
||||
|
||||
### Keep
|
||||
|
||||
- `project-knowledge/.obsidian/`
|
||||
- `project-knowledge/08-bases/*.base`
|
||||
- `project-knowledge/09-templates/`
|
||||
- `workspaces/fidelity/project-knowledge/.obsidian/`
|
||||
- `workspaces/fidelity/project-knowledge/08-bases/*.base`
|
||||
- `workspaces/fidelity/project-knowledge/09-templates/`
|
||||
- `scripts/memory/`
|
||||
|
||||
### Deprecate then remove
|
||||
|
||||
@@ -51,4 +51,4 @@ Capture reusable prompting lessons so the agent does not need to re-research the
|
||||
|
||||
- Treat prompt improvement as eval-driven iteration: identify the exact bad output pattern, add the smallest correction, and check whether it fixes the failure without bloating the prompt.
|
||||
- When a correction is about workspace behavior, update the controlling prompt or command immediately so the next run benefits.
|
||||
- Keep project memory clean while improving prompt quality; do not store agent heuristics in `project-knowledge/`.
|
||||
- Keep project memory clean while improving prompt quality; do not store agent heuristics in `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
@@ -11,7 +11,7 @@ related:
|
||||
|
||||
This repository separates project knowledge from agent operation:
|
||||
|
||||
- `project-knowledge/` is the clean Obsidian second brain and transferable project memory.
|
||||
- `workspaces/fidelity/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.
|
||||
|
||||
@@ -42,10 +42,10 @@ These folders are intentionally outside Obsidian memory:
|
||||
- `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.
|
||||
- `workspaces/fidelity/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/`.
|
||||
Runtime and generated files can be used as evidence, but durable project facts should be promoted into `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
Agent behavior rules belong in `agent-memory/`, not in the project vault.
|
||||
|
||||
@@ -55,7 +55,7 @@ Agent behavior rules belong in `agent-memory/`, not in the project vault.
|
||||
|
||||
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/`.
|
||||
Obsidian is the current visual and CLI-backed adapter, but the source of truth remains Markdown under `workspaces/fidelity/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.
|
||||
@@ -66,6 +66,6 @@ Obsidian is the current visual and CLI-backed adapter, but the source of truth r
|
||||
|
||||
## Memory Rule
|
||||
|
||||
Promoted memory lives in `project-knowledge/`.
|
||||
Promoted memory lives in `workspaces/fidelity/project-knowledge/`.
|
||||
|
||||
Raw inbox and generated connector evidence stays outside the vault until the agent promotes durable facts.
|
||||
|
||||
@@ -15,7 +15,7 @@ It separates reusable tooling, project knowledge, and agent operating memory:
|
||||
|
||||
- `core/` contains reusable project-independent operating rules
|
||||
- `profiles/<project>/` contains project-specific configuration and assumptions
|
||||
- `project-knowledge/` contains transferable project documentation and current work memory
|
||||
- `workspaces/fidelity/project-knowledge/` contains transferable project documentation and current work memory
|
||||
- `agent-memory/` contains agent behavior, learning, promotion, integration, and verification rules
|
||||
|
||||
---
|
||||
@@ -48,14 +48,14 @@ When the user corrects a recurring behavior, the workspace should update the fil
|
||||
|
||||
- `core/` for reusable project-independent behavior
|
||||
- `profiles/<project>/` for project-specific assumptions
|
||||
- `project-knowledge/.obsidian/` only for portable Obsidian configuration, not project memory content
|
||||
- `workspaces/fidelity/project-knowledge/.obsidian/` only for portable Obsidian configuration, not project memory content
|
||||
- `scripts/memory/` for project-agnostic memory access, creation, search, Base queries, and health checks
|
||||
- `scripts/obsidian/` for the current Obsidian adapter, not for core memory semantics
|
||||
- `.agents/workflows/` for slash commands (with `.opencode/commands/` for compatibility)
|
||||
- `prompts/` for reusable drafting templates
|
||||
- `.agents/rules/` and `AGENTS.md` for default agent behavior
|
||||
- `.agents/skills/` for specialized workflows. Do not mirror into `.opencode/skills/`; OpenCode discovers `.agents/skills/` directly.
|
||||
- `project-knowledge/00-start/` and `project-knowledge/03-context/process/` for project-facing onboarding and process rules
|
||||
- `workspaces/fidelity/project-knowledge/00-start/` and `workspaces/fidelity/project-knowledge/03-context/process/` for project-facing onboarding and process rules
|
||||
- `agent-memory/` for agent-specific behavior, learning, promotion, verification, and self-maintenance rules
|
||||
|
||||
Daily logs can preserve evidence, but they should not be the only place where a reusable behavior rule lives.
|
||||
|
||||
Reference in New Issue
Block a user