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:
@@ -26,8 +26,8 @@ AI clients and agent workflows
|
||||
|---|---|---|
|
||||
| `core/` | Reusable architecture and operating model | yes, for workspace design |
|
||||
| `profiles/<profile>/` | Project-specific configuration and assumptions | yes, for profile config |
|
||||
| `project-knowledge/` | Human-readable project memory for the active profile | yes, for project facts |
|
||||
| `ai/inbox/` | Raw evidence captured from connectors | no |
|
||||
| `workspaces/<profile>/project-knowledge/` | Human-readable project memory for the active profile | yes, for project facts |
|
||||
| `workspaces/<profile>/inbox/` | Raw evidence captured from connectors | no |
|
||||
| `.aiw/indexes/` | Rebuildable search indexes | no |
|
||||
| `.aiw/runtime/` | PID files, logs, local service state | no |
|
||||
| `scripts/aiw/` | Profile-aware service/index utilities | code source |
|
||||
@@ -36,9 +36,9 @@ AI clients and agent workflows
|
||||
|
||||
## Current Repository Shape
|
||||
|
||||
The current repo still keeps the first real profile's vault at root-level `project-knowledge/`. That is acceptable during migration, but reusable code should resolve paths from `profiles/<profile>/workspace.json` rather than hardcoding Fidelity-specific locations.
|
||||
Profile-owned data lives under `workspaces/<profile>/`. Reusable code must resolve paths from `profiles/<profile>/workspace.json` rather than hardcoding profile-specific locations.
|
||||
|
||||
Target direction:
|
||||
Current data layout:
|
||||
|
||||
```text
|
||||
profiles/<profile>/workspace.json # where profile data lives
|
||||
|
||||
Reference in New Issue
Block a user