I3258 — Evidence for and against one criterion is kept and named, and the criterion reads unknown until it is settled
When two current pieces of evidence for one criterion disagree (a passing test and a failing claim, two observations), the criterion keeps both with their sources and reads unknown with reason `conflicting`; nothing averages or drops one.
READY wave 0 · p2 · implementation profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I3258 will be accepted.
Objective
When two current pieces of evidence for one criterion disagree (a passing test and a failing claim, two observations), the criterion keeps both with their sources and reads unknown with reason `conflicting`; nothing averages or drops one.
Why
2026-10-08 and 2026-10-11: contradicting evidence must be preserved; the vocabulary constraint (do not extend public states unless needed) is kept by the proposed ADR on conflicting evidence. It builds on I2822 (satisfaction is explained), a local revival in flight and not on master or origin; record it as depends_on once I2822's record lands. Proposed in ADR 0193 (Conflicting evidence keeps the verdict vocabulary: the criterion reads unknown and cites both sides) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c221#2.
Current state
IntentVerdictState is satisfied, unsatisfied, unknown; a criterion carries one evidence ref; the gap schema already has `conflicting` for a worker's observation.
Desired state
Conflict is a reason on unknown, served on CLI, HTTP, MCP and /ui identically.
Scope
- apps/majordomus-cli/src/intent.rs
- apps/majordomus-cli/tests/intent.rs
- docs/CONCEPTS.md
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- A criterion with one passing and one failing current source reads unknown naming both
- The public verdict vocabulary is unchanged (schema test)
Validation
- majordomus plan validate
- majordomus intent validate
Evidence required
- test_conflicting_evidence_is_kept
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I3258.yaml. Read it back with majordomus plan show I3258.