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.
This commit is contained in:
51
vault/00-start/glossary.md
Normal file
51
vault/00-start/glossary.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
type: glossary
|
||||
audience: new-member
|
||||
tags:
|
||||
- onboarding
|
||||
- glossary
|
||||
---
|
||||
|
||||
# Glossary
|
||||
|
||||
Common terms used in this workspace.
|
||||
|
||||
---
|
||||
|
||||
## Workspace Terms
|
||||
|
||||
- `core`: reusable project-independent AI workspace logic.
|
||||
- `profile`: project-specific configuration and assumptions layered on top of the core.
|
||||
- `operational memory`: curated file-based memory that helps future AI sessions reason accurately.
|
||||
- `daily log`: same-day evidence and evolving findings in `vault/06-daily/`.
|
||||
- `state`: near-term active work and priorities in `vault/01-current/`.
|
||||
- `work item`: canonical memory for a ticket, story, task, or investigation in `vault/02-work-items/`.
|
||||
- `stable context`: durable project knowledge under `vault/03-context/`.
|
||||
- `inbox`: raw or lightly processed communication evidence under `ai/inbox/`.
|
||||
- `promotion`: moving high-confidence evidence into canonical memory.
|
||||
- `tooling behavior`: reusable behavior encoded in commands, prompts, skills, agents, or knowledge rules.
|
||||
|
||||
---
|
||||
|
||||
## Fidelity Terms
|
||||
|
||||
- `Fid4`: main Fidelity consumer iOS app and key validation environment.
|
||||
- `XFlowSDK`: backend-driven UI engine that renders flows from service-provided configuration.
|
||||
- `XFlowViewMaker`: adapter layer historically involved in integration and release propagation.
|
||||
- `FTFrameworks`: feature modules such as account opening or transfer flows that can mediate XFlow adoption.
|
||||
- `AO`: account opening context; many reports require careful reproduction and scope validation.
|
||||
- `Discourse`: external issue/report source; treat reports as external until confirmed.
|
||||
- `REST migration`: migration away from GraphQL/Apollo toward REST, with REST behind a feature flag unless confirmed otherwise.
|
||||
- `authenticated flow`: behavior reproduced while signed in; often differs from non-authenticated behavior.
|
||||
- `entry point`: the path used to reach a flow, which can affect backend-driven behavior.
|
||||
- `Cogstore`: flow-configuration publishing and version-comparison platform.
|
||||
|
||||
---
|
||||
|
||||
## Communication Terms
|
||||
|
||||
- `external report`: issue reported externally before regression status is confirmed.
|
||||
- `regression`: behavior confirmed to be newly broken relative to a known baseline.
|
||||
- `scope`: the exact affected flow, platform, auth state, environment, and ownership boundary.
|
||||
- `reproducibility`: whether the behavior can be repeated with known steps and context.
|
||||
- `manager-ready`: concise, explicit, natural professional English that can be sent without rewriting.
|
||||
124
vault/00-start/obsidian-usage.md
Normal file
124
vault/00-start/obsidian-usage.md
Normal file
@@ -0,0 +1,124 @@
|
||||
---
|
||||
type: guide
|
||||
audience: workspace-user
|
||||
tags:
|
||||
- onboarding
|
||||
- obsidian
|
||||
---
|
||||
|
||||
# Obsidian Usage Guide
|
||||
|
||||
Use Obsidian to navigate and review workspace memory. Do not use it as a separate memory database.
|
||||
|
||||
---
|
||||
|
||||
## Recommended Start
|
||||
|
||||
Open the `vault/` folder as the Obsidian vault, not the repository root.
|
||||
|
||||
Open:
|
||||
|
||||
- [Obsidian Vault Map](start-here.md)
|
||||
- [New Member Onboarding](onboarding.md)
|
||||
- [Knowledge Maps](../07-maps/index.md)
|
||||
|
||||
---
|
||||
|
||||
## Best Views
|
||||
|
||||
### New Member View
|
||||
|
||||
Start with:
|
||||
|
||||
- [New Member Onboarding](onboarding.md)
|
||||
- [Glossary](glossary.md)
|
||||
- [Current Work Map](../07-maps/current-work.md)
|
||||
- [Fidelity Domain Map](../07-maps/fidelity-domain.md)
|
||||
|
||||
### Daily Work View
|
||||
|
||||
Start with:
|
||||
|
||||
- [Current Work Map](../07-maps/current-work.md)
|
||||
- [Work Items Map](../07-maps/work-items.md)
|
||||
- [Logs Index](../06-daily/index.md)
|
||||
|
||||
### System Understanding View
|
||||
|
||||
Start with:
|
||||
|
||||
- [Fidelity Domain Map](../07-maps/fidelity-domain.md)
|
||||
- [AI Workspace Core Map](../07-maps/ai-workspace-core.md)
|
||||
- [Tooling Map](../07-maps/tooling.md)
|
||||
|
||||
---
|
||||
|
||||
## Graph Guidance
|
||||
|
||||
Use the graph to find clusters, not to infer truth.
|
||||
|
||||
High-value graph hubs:
|
||||
|
||||
- `start-here`
|
||||
- `onboarding`
|
||||
- `current-work`
|
||||
- `fidelity-domain`
|
||||
- `work-items`
|
||||
- `people`
|
||||
- `tooling`
|
||||
- `ai-workspace-core`
|
||||
|
||||
If a node is isolated, it may still be valid. It may be:
|
||||
|
||||
- a daily log
|
||||
- raw evidence
|
||||
- a command/prompt file
|
||||
- a file that needs to be linked from a map
|
||||
|
||||
---
|
||||
|
||||
## Global Graph Defaults
|
||||
|
||||
The global graph is configured for onboarding and project navigation, not full filesystem inspection.
|
||||
|
||||
It intentionally hides generic technical filenames such as:
|
||||
|
||||
- `index`
|
||||
- `README`
|
||||
- `AGENTS`
|
||||
- `SKILL`
|
||||
|
||||
Those files still exist and remain valid workspace files. They are hidden from the graph because Obsidian displays only the basename, which creates many indistinguishable nodes.
|
||||
|
||||
Use the file explorer or search when you need a specific technical file. Use the graph when you want to understand relationships between project concepts.
|
||||
|
||||
---
|
||||
|
||||
## When To Show Technical Files
|
||||
|
||||
Temporarily remove these filters from the graph search when debugging workspace internals:
|
||||
|
||||
```text
|
||||
-file:index -file:README -file:AGENTS -file:SKILL
|
||||
```
|
||||
|
||||
For normal onboarding, keep them hidden and navigate through the named maps.
|
||||
|
||||
---
|
||||
|
||||
## Editing Rules
|
||||
|
||||
- Edit canonical memory files when the fact is clear.
|
||||
- Prefer updating existing notes over adding duplicate summaries.
|
||||
- Do not edit generated files as durable memory.
|
||||
- Do not treat inbox files as confirmed truth.
|
||||
- Use maps to improve navigation, not to store detailed facts.
|
||||
|
||||
---
|
||||
|
||||
## Daily Notes, Templates, And Bases
|
||||
|
||||
- Daily notes live under `06-daily/` and use `09-templates/daily.md`.
|
||||
- Templates live under `09-templates/`.
|
||||
- Bases live under `08-bases/` and use simple `type` properties.
|
||||
- Bookmarks should keep `00-start/start-here.md`, `00-start/onboarding.md`, current work, work items, people, and high-value Bases easy to open.
|
||||
92
vault/00-start/onboarding.md
Normal file
92
vault/00-start/onboarding.md
Normal file
@@ -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.
|
||||
115
vault/00-start/start-here.md
Normal file
115
vault/00-start/start-here.md
Normal file
@@ -0,0 +1,115 @@
|
||||
---
|
||||
type: map
|
||||
audience: workspace-user
|
||||
tags:
|
||||
- map
|
||||
- obsidian
|
||||
---
|
||||
|
||||
# Start Here
|
||||
|
||||
Use this note as the human navigation entry point when opening `vault/` as an Obsidian vault.
|
||||
|
||||
---
|
||||
|
||||
## Start Here
|
||||
|
||||
- Repository README: `README.md`
|
||||
- [New Member Onboarding](onboarding.md)
|
||||
- [Glossary](glossary.md)
|
||||
- [Obsidian Usage Guide](obsidian-usage.md)
|
||||
- [Workspace Architecture](workspace-architecture.md)
|
||||
- [Knowledge Maps](../07-maps/index.md)
|
||||
|
||||
---
|
||||
|
||||
## Maps
|
||||
|
||||
- [AI Workspace Core](../07-maps/ai-workspace-core.md)
|
||||
- [Current Work](../07-maps/current-work.md)
|
||||
- [Fidelity Domain](../07-maps/fidelity-domain.md)
|
||||
- [Work Items](../07-maps/work-items.md)
|
||||
- [People](../07-maps/people.md)
|
||||
- [Tooling](../07-maps/tooling.md)
|
||||
|
||||
---
|
||||
|
||||
## New Members
|
||||
|
||||
If you are new to this project, read:
|
||||
|
||||
1. [New Member Onboarding](onboarding.md)
|
||||
2. [Glossary](glossary.md)
|
||||
3. [Current Work Map](../07-maps/current-work.md)
|
||||
4. [Fidelity Domain Map](../07-maps/fidelity-domain.md)
|
||||
5. [People Map](../07-maps/people.md)
|
||||
6. [Workspace Architecture](workspace-architecture.md)
|
||||
|
||||
---
|
||||
|
||||
## Current Work
|
||||
|
||||
- [Current State](../01-current/current-work.md)
|
||||
- [Active Work Items](../01-current/work-items.md)
|
||||
- [Work Item Index](../02-work-items/index.md)
|
||||
- [Logs Index](../06-daily/index.md)
|
||||
|
||||
---
|
||||
|
||||
## Stable Context
|
||||
|
||||
- [Context Index](../03-context/index.md)
|
||||
- [Project Context](../03-context/project.md)
|
||||
- [Systems Index](../03-context/systems/index.md)
|
||||
- [Workstreams Index](../03-context/workstreams/index.md)
|
||||
- [People Index](../04-people/index.md)
|
||||
- [Manager Mapping](../04-people/manager.md)
|
||||
|
||||
---
|
||||
|
||||
## Process And Rules
|
||||
|
||||
- [Workspace Model](../03-context/process/workspace-model.md)
|
||||
- [Agent Memory Rules](../03-context/process/agent-memory-rules.md)
|
||||
- [Memory Promotion Rules](../03-context/process/memory-promotion-rules.md)
|
||||
- [Communication Rules](../03-context/process/communication-rules.md)
|
||||
- [Context Maintenance](../03-context/process/context-maintenance.md)
|
||||
- [Workspace Architecture](workspace-architecture.md)
|
||||
|
||||
---
|
||||
|
||||
## Daily Logs
|
||||
|
||||
Daily notes live in:
|
||||
|
||||
```text
|
||||
vault/06-daily/
|
||||
```
|
||||
|
||||
Use the latest dated note for recent evidence, but promote durable facts into `01-current/`, `02-work-items/`, or `03-context/` when they should survive beyond the day.
|
||||
|
||||
- [Logs Index](../06-daily/index.md)
|
||||
|
||||
---
|
||||
|
||||
## Inbox And Generated Evidence
|
||||
|
||||
Inbox and generated files are evidence, not durable memory by default.
|
||||
|
||||
- `ai/inbox/`
|
||||
- `scripts/mattermost/generated/`
|
||||
- `scripts/slack/generated/`
|
||||
|
||||
Promote only high-confidence, project-relevant facts into canonical memory.
|
||||
|
||||
---
|
||||
|
||||
## Canonical Vault Areas
|
||||
|
||||
- [Current Work](../01-current/current-work.md)
|
||||
- [Work Items](../02-work-items/index.md)
|
||||
- [Fidelity Domain Map](../07-maps/fidelity-domain.md)
|
||||
- [People Map](../07-maps/people.md)
|
||||
- [Daily Notes](../06-daily/index.md)
|
||||
- [Bases](../08-bases/work-items.base)
|
||||
- [Templates](../09-templates/daily.md)
|
||||
57
vault/00-start/workspace-architecture.md
Normal file
57
vault/00-start/workspace-architecture.md
Normal file
@@ -0,0 +1,57 @@
|
||||
---
|
||||
type: guide
|
||||
project: fidelity
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
tags: [onboarding, obsidian, workspace]
|
||||
related:
|
||||
- start-here.md
|
||||
- ../07-maps/ai-workspace-core.md
|
||||
---
|
||||
|
||||
# Workspace Architecture
|
||||
|
||||
This repository has two layers:
|
||||
|
||||
- `vault/` is the clean Obsidian second brain and canonical AI memory.
|
||||
- Everything outside `vault/` is technical runtime, reusable core, profile configuration, scripts, commands, prompts, or raw evidence.
|
||||
|
||||
---
|
||||
|
||||
## Canonical Memory
|
||||
|
||||
Use these folders as the source of truth for humans and AI agents:
|
||||
|
||||
- `00-start/` for onboarding and usage guidance
|
||||
- `01-current/` for current work state
|
||||
- `02-work-items/` for ticket/task memory
|
||||
- `03-context/` for systems, workstreams, 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 `vault/`.
|
||||
|
||||
---
|
||||
|
||||
## Migration Rule
|
||||
|
||||
Legacy `ai/context`, `ai/state`, `ai/work-items`, `ai/logs`, and `knowledge` files may still exist for compatibility.
|
||||
|
||||
When a `vault/` equivalent exists, update `vault/` first.
|
||||
Reference in New Issue
Block a user