david.delagneau
b82194bc55
- 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.
26 lines
777 B
Markdown
26 lines
777 B
Markdown
# Work Items
|
|
|
|
## Goal
|
|
|
|
Keep active Jira-linked work in one canonical place so standups, manager updates, and memory syncs can reference each ticket precisely.
|
|
|
|
---
|
|
|
|
## Structure
|
|
|
|
- `index.md`
|
|
Active index and quick status view.
|
|
|
|
- `<jira-id>.md`
|
|
Canonical file for a specific ticket.
|
|
|
|
---
|
|
|
|
## Update Rules
|
|
|
|
- Use one file per active or recently relevant Jira item.
|
|
- Keep titles exact when approved or explicitly confirmed.
|
|
- If the title is not confirmed, store the Jira ID and current framing without inventing a final title.
|
|
- Update the ticket file when scope, sequencing, points, status, rollout implications, or reproducibility meaningfully change.
|
|
- Keep `vault/01-current/work-items.md` as a short bridge summary, not the primary source of detailed ticket context.
|