Files

david.delagneau b82194bc55 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.

2026-04-16 16:01:19 -06:00

2.3 KiB

Raw Blame History

Create A Project Profile

Use this checklist when adapting the workspace core for a new project.

1. Create The Profile

Create:

profiles/<project>/profile.md
profiles/<project>/README.md

The profile should declare:

project name
workspace purpose
primary audience
communication sources
ticket/work-item system
manager or stakeholder mapping
active context files
enabled commands
enabled skills

2. Configure Context

Create or update:

vault/00-start/start-here.md
vault/01-current/current-work.md
vault/01-current/work-items.md
vault/02-work-items/
vault/03-context/project.md
vault/03-context/process/
vault/04-people/
vault/05-decisions/
vault/06-daily/
vault/07-maps/
vault/08-bases/
vault/09-templates/

Keep project-specific facts out of core/.

Legacy ai/context, ai/state, ai/work-items, and ai/logs paths may be kept temporarily for compatibility, but new project profiles should treat vault/ as canonical memory.

3. Configure Integrations

Use generic variables first:

AIW_PROJECT_PROFILE=<project>
AIW_CHANNEL_PREFIX=<project-or-team-prefix>
AIW_MATTERMOST_SYNC_CMD=<optional custom command>
AIW_SLACK_EXPORT_PATH=<optional archive path>

Connector secrets belong in ignored .env files, not in profile files.

4. Configure Commands And Skills

Start with generic commands:

/workspace-context
/communication-sync
/archive-import
/standup
/manager-update
/translate
/ai-prompt

Add project-specific aliases only when they reduce friction.

5. Validate

Before using the workspace for real work:

confirm opencode.json is valid JSON
confirm the profile has no secrets
run a communication sync with test channels or a dry sample
generate one standup from sample context
verify that imported evidence and promoted memory stay separate

6. Obsidian Vault

Open vault/ as the Obsidian vault.

Recommended rules:

keep vault/ as the clean canonical human/AI memory
keep runtime evidence, scripts, profiles, and generated files outside vault/
version only portable vault/.obsidian configuration
ignore local Obsidian workspace state and plugin runtime files
create or update map notes under vault/07-maps/ for human navigation
create Bases under vault/08-bases/ using simple type properties

2.3 KiB Raw Blame History