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.
1.7 KiB
1.7 KiB
type, project, status, updated, tags
| type | project | status | updated | tags | ||
|---|---|---|---|---|---|---|
| process | fidelity | active | 2026-04-16 |
|
Communication Rules
Goal
Make technical communication precise enough for manager updates, Jira notes, standups, and cross-team messages.
Required Structure
When the format fits, prefer:
- Context
- Observation
- Action
Fidelity-Specific Rules
- Always clarify authenticated vs non-authenticated when behavior depends on it.
- Always separate external issues from regressions.
- Always state reproducibility and scope.
- For standups, report the previous workday context, not blindly the prior calendar day.
- On Mondays, use Friday's work context unless a later prior day has Mattermost activity.
- If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.
- For standups, when a Jira item has multiple concrete updates, use one top-level
JIRA-ID - Titlebullet and indented markdown sub-bullets instead of repeating the same Jira line. - When a flow/page shorthand could be ambiguous, prefer the real flow identifier and page name from
vault/03-context/workstreams/flow-page-references.md. - Avoid vague phrasing such as:
- "same behavior"
- "looks fixed"
- "working as expected"
Historical Signals From Slack
- Jeff repeatedly requested polished, explicit wording for PR descriptions, story descriptions, and cross-team messages.
- Historical Slack threads show that message quality changed how quickly stories were approved or understood.
- Explicit language mattered most when communicating root cause, ownership boundaries, or whether a report was a confirmed regression.