david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
49 lines
816 B
Markdown
49 lines
816 B
Markdown
---
|
|
type: decision
|
|
project: fidelity
|
|
status: accepted
|
|
title: "Discourse Issues Handling"
|
|
updated: 2026-04-16
|
|
tags:
|
|
- decision
|
|
- fidelity
|
|
---
|
|
# Discourse Issues Handling
|
|
|
|
## Context
|
|
|
|
External reports from AO testing or Discourse may:
|
|
|
|
- already exist in main
|
|
- be partially reproducible
|
|
- depend on authentication
|
|
- reflect backend behavior rather than a new regression
|
|
|
|
---
|
|
|
|
## Decision
|
|
|
|
Treat incoming reports as external issues until scope is confirmed.
|
|
|
|
---
|
|
|
|
## Validation Rules
|
|
|
|
Always confirm:
|
|
|
|
- reproducibility
|
|
- environment
|
|
- auth state
|
|
- entry point
|
|
- whether the issue exists in main
|
|
|
|
---
|
|
|
|
## Communication Rule
|
|
|
|
Do not say a report is a regression until comparison has been validated.
|
|
|
|
Preferred framing:
|
|
|
|
"Investigating external report. Scope, auth state, and reproducibility still being confirmed."
|