Add daily logs and templates for Fidelity project

- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.

vault/00-start/onboarding.md

@@ -0,0 +1,92 @@
+---
+type: onboarding
+audience: new-member
+tags:
+  - onboarding
+  - map
+---
+
+# New Member Onboarding
+
+Use this guide when someone new needs to understand this workspace and the Fidelity project context quickly.
+
+This repository is not the product codebase. It is the AI workspace used to preserve context, navigate project memory, and draft precise communication.
+
+---
+
+## First 30 Minutes
+
+Read these in order:
+
+1. [Obsidian Vault Map](start-here.md)
+2. [Current Work Map](../07-maps/current-work.md)
+3. [Fidelity Domain Map](../07-maps/fidelity-domain.md)
+4. [Work Items Map](../07-maps/work-items.md)
+5. [People Map](../07-maps/people.md)
+
+Goal:
+
+- understand where current work lives
+- identify active tickets
+- understand the main systems and people
+- avoid treating raw logs or inbox evidence as confirmed durable truth
+
+---
+
+## First 60 Minutes
+
+Read:
+
+1. [Project Context](../03-context/project.md)
+2. [XFlowSDK](../03-context/systems/xflowsdk.md)
+3. [Fid4](../03-context/systems/fid4.md)
+4. [REST Migration](../03-context/workstreams/rest-migration.md)
+5. [AO And Discourse](../03-context/workstreams/ao-discourse.md)
+6. [Communication Rules](../03-context/process/communication.md)
+
+Goal:
+
+- understand why auth state, entry point, and backend configuration matter
+- distinguish external reports from regressions
+- understand why communication precision is part of the engineering workflow
+
+---
+
+## First 120 Minutes
+
+Read:
+
+1. [Memory Promotion Rules](../03-context/process/memory-promotion-rules.md)
+2. [Workspace Architecture](workspace-architecture.md)
+3. [Agent Memory Rules](../03-context/process/agent-memory-rules.md)
+4. [Context Maintenance](../03-context/process/context-maintenance.md)
+5. [Tooling Map](../07-maps/tooling.md)
+
+Goal:
+
+- understand how the AI workspace stays current
+- know where to add new facts
+- know when to update logs, state, work items, stable context, people, decisions, or tooling behavior
+
+---
+
+## Daily Workflow
+
+1. Start from [Current Work Map](../07-maps/current-work.md).
+2. Check [Current Work](../01-current/current-work.md).
+3. Open the active work item from [Work Items Map](../07-maps/work-items.md).
+4. Review the latest relevant log from [Logs Index](../06-daily/index.md).
+5. Use [Communication Rules](../03-context/process/communication.md) before writing standups, Jira comments, or manager updates.
+
+---
+
+## Rules Of Thumb
+
+- `vault/06-daily/` is evidence from a day.
+- `vault/01-current/` is what matters now.
+- `vault/02-work-items/` is canonical ticket memory.
+- `vault/03-context/` is durable project knowledge.
+- `vault/04-people/` is collaborator and role memory.
+- `core/` is reusable workspace logic.
+- `profiles/fidelity/` is Fidelity-specific configuration.
+- `ai/inbox/` and generated files are evidence, not promoted memory.