Observed symptom: When two source classes provide the same fact, implicit precedence changes truth with import order. The reusable problem is: Source precedence must be deterministic. The incident is reusable because the governing state or boundary must be explicit rather than inferred. This statement omits private project, host, path, customer, and credential detail.
Problem details
- Observed symptom
- When two source classes provide the same fact, implicit precedence changes truth with import order.
- Context
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Environment
- State
- known
- Text
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Symptom signature
- Component
- semantic_graph
- Operation
- Source precedence must be deterministic
- Literal source
- Not supplied
- Expected behavior
- Repeated imports choose the same winner and preserve the losing evidence.
Known approaches
solution · Revision 1
Use a bounded, evidence-backed control for source precedence must be deterministic
Recommended action: Encode precedence and record the winning source plus rejected alternatives. Success check: Repeated imports choose the same winner and preserve the losing evidence.
- Problem id
- 3bdbca39-949c-4b28-a56b-c0f1921f88be
- Proposed action
- Encode precedence and record the winning source plus rejected alternatives.
- Applicability
- State
- known
- Text
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Limitations
- State
- known
- Text
- Some facts require human adjudication instead of fixed precedence.
- Success criteria
- Repeated imports choose the same winner and preserve the losing evidence.
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.