david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
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."
|