RAGvidence evaluation / workspace

WORKSPACE / REVIEWED EVIDENCE

Retrieval comparison

bm25-body → bm25-heading_context

One controlled retrieval comparison · 12 questions · 10 answerable · k=2

Evidence sufficiency

60% → 90%

Evidence sufficiency improved from 60% to 90%.

3 recovered0 regressions1 unresolved failure
Generated 2026-10-19T15:26:53+00:00Artifact schema v1

Baseline versus intervention

Success means every required evidence ID appeared within the recorded retrieval depth.

Baseline · bm25-body

60%

6 / 10 answerable questions sufficient

Strategy: BM25 · Representation: body · k=2

Index time: 113.0 ms (secondary run metadata)

Intervention · bm25-heading_context

90%

9 / 10 answerable questions sufficient

Strategy: BM25 · Representation: heading context · k=2

Index time: 0.9 ms (secondary run metadata)

+30.0 percentage points in evidence sufficiency

Change analysis

Review regressions first, then unresolved failures. Stable successes are grouped later.

0Pass → Fail · Regressions 1Fail → Fail · Unresolved 3Fail → Pass · Recovered 6Pass → Pass · Stable

2 N/A cases are excluded from the answerable success-rate denominator.

Diagnostic notes

Observed pattern and next experiment

Observed facts

3 failed queries passed after the intervention with no regressions.

Diagnostic interpretation

Observed pattern: Missing structural context in the baseline representation

Recommended next experiment: Repeat on a frozen slice of your own corpus and inspect every changed rank.

Confidence: medium

Limitation: This rule identifies correlation in a small labeled comparison, not universal causation.

Regressions

No questions in this group.

Unresolved failures

DEV-04 How does the pairing reset for Orion DeskHub firmware 4.1 differ in duration from version 4.2? Fail → Fail Split: dev Fail · Insufficient evidence Coverage: 0% → 50% First relevant rank: N/A → 2

Required evidence gained: E-ORION-41-RESET

Required evidence lost: None

Still missing: E-ORION-42-RESET

Baseline

Fail · Insufficient evidence

Evidence coverage
0%
First relevant rank
N/A
Reciprocal rank
0.000
Precision@k
0.000
Retrieved hits
2

Required evidence: E-ORION-41-RESET, E-ORION-42-RESET

Found required evidence: None

Missing required evidence: E-ORION-41-RESET, E-ORION-42-RESET

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 4.861 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-LYRA-30-GUEST

    Retriever score: 1.293 · Evidence IDs: E-LYRA-30-GUEST

    On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

Intervention

Fail · Insufficient evidence

Evidence coverage
50%
First relevant rank
2
Reciprocal rank
0.500
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-41-RESET, E-ORION-42-RESET

Found required evidence: E-ORION-41-RESET

Missing required evidence: E-ORION-42-RESET

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 3.002 · Evidence IDs: None

    Controller Migration Notes > Comparing reset workflows Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the instal

  2. #2 · SEC-ORION-41-RESET

    Retriever score: 1.847 · Evidence IDs: E-ORION-41-RESET

    Orion DeskHub > Firmware 4.1 > Pairing reset Hold the side button for five seconds. Release it when the status ring flashes blue once. This procedure clears the current controller pairing.

Improvements

DEV-01 How long should I hold the button to reset pairing on Orion DeskHub firmware 4.2? Fail → Pass Split: dev Pass · Sufficient evidence Coverage: 0% → 100% First relevant rank: N/A → 1

Required evidence gained: E-ORION-42-RESET

Required evidence lost: None

Still missing: None

Baseline

Fail · Insufficient evidence

Evidence coverage
0%
First relevant rank
N/A
Reciprocal rank
0.000
Precision@k
0.000
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: None

Missing required evidence: E-ORION-42-RESET

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 3.986 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-LYRA-30-GUEST

    Retriever score: 1.818 · Evidence IDs: E-LYRA-30-GUEST

    On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: E-ORION-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-42-RESET

    Retriever score: 2.442 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

  2. #2 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.097 · Evidence IDs: None

    Controller Migration Notes > Comparing reset workflows Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the instal

DEV-03 What should I do after an interrupted update on Orion DeskHub firmware 4.2? Fail → Pass Split: dev Pass · Sufficient evidence Coverage: 0% → 100% First relevant rank: N/A → 2

Required evidence gained: E-ORION-42-RECOVERY

Required evidence lost: None

Still missing: None

Baseline

Fail · Insufficient evidence

Evidence coverage
0%
First relevant rank
N/A
Reciprocal rank
0.000
Precision@k
0.000
Retrieved hits
2

Required evidence: E-ORION-42-RECOVERY

Found required evidence: None

Missing required evidence: E-ORION-42-RECOVERY

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 3.495 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-ORION-42-RESET

    Retriever score: 1.303 · Evidence IDs: E-ORION-42-RESET

    If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
2
Reciprocal rank
0.500
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RECOVERY

Found required evidence: E-ORION-42-RECOVERY

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-42-RESET

    Retriever score: 1.988 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

  2. #2 · SEC-ORION-42-RECOVERY

    Retriever score: 1.795 · Evidence IDs: E-ORION-42-RECOVERY

    Orion DeskHub > Firmware 4.2 > Interrupted update recovery Disconnect power for twenty seconds, reconnect the adapter, and wait until the status ring becomes steady white before reopening the control application.

HOLD-04 What indicates that the Atlas Dock 4.2 pairing reset can be released? Fail → Pass Split: heldout Pass · Sufficient evidence Coverage: 0% → 100% First relevant rank: N/A → 2

Required evidence gained: E-ATLAS-42-RESET

Required evidence lost: None

Still missing: None

Baseline

Fail · Insufficient evidence

Evidence coverage
0%
First relevant rank
N/A
Reciprocal rank
0.000
Precision@k
0.000
Retrieved hits
2

Required evidence: E-ATLAS-42-RESET

Found required evidence: None

Missing required evidence: E-ATLAS-42-RESET

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.867 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-ORION-41-RESET

    Retriever score: 0.787 · Evidence IDs: E-ORION-41-RESET

    Hold the side button for five seconds. Release it when the status ring flashes blue once. This procedure clears the current controller pairing.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
2
Reciprocal rank
0.500
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ATLAS-42-RESET

Found required evidence: E-ATLAS-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.175 · Evidence IDs: None

    Controller Migration Notes > Comparing reset workflows Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the instal

  2. #2 · SEC-ATLAS-42-RESET

    Retriever score: 1.993 · Evidence IDs: E-ATLAS-42-RESET

    Atlas Dock > Firmware 4.2 > Pairing reset Press the recessed rear switch for three seconds, then release it when the two port indicators blink together. Existing display preferences are retained.

Stable results

DEV-02 What status-ring signal tells me to release the button during an Orion DeskHub 4.2 pairing reset? Pass → Pass Split: dev Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 2 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
2
Reciprocal rank
0.500
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: E-ORION-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.687 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-ORION-42-RESET

    Retriever score: 1.967 · Evidence IDs: E-ORION-42-RESET

    If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: E-ORION-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-42-RESET

    Retriever score: 3.184 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

  2. #2 · SEC-ORION-41-RESET

    Retriever score: 2.142 · Evidence IDs: E-ORION-41-RESET

    Orion DeskHub > Firmware 4.1 > Pairing reset Hold the side button for five seconds. Release it when the status ring flashes blue once. This procedure clears the current controller pairing.

DEV-05 How do I reset the guest access code on Lyra Travel Router firmware 3.0? Pass → Pass Split: dev Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 1 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-LYRA-30-GUEST

Found required evidence: E-LYRA-30-GUEST

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-LYRA-30-GUEST

    Retriever score: 7.268 · Evidence IDs: E-LYRA-30-GUEST

    On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

  2. #2 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 0.707 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-LYRA-30-GUEST

Found required evidence: E-LYRA-30-GUEST

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-LYRA-30-GUEST

    Retriever score: 7.582 · Evidence IDs: E-LYRA-30-GUEST

    Lyra Travel Router > Firmware 3.0 > Guest network reset On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

  2. #2 · SEC-NOVA-20-CALIBRATION

    Retriever score: 0.568 · Evidence IDs: E-NOVA-20-CALIBRATION

    Nova Room Sensor > Firmware 2.0 > Manual calibration Keep the sensor on a level surface and hold both arrow buttons for twelve seconds. Calibration is complete when the display shows a solid square.

HOLD-01 Will an Orion DeskHub 4.2 pairing reset erase saved network settings? Pass → Pass Split: heldout Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 1 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: E-ORION-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-42-RESET

    Retriever score: 2.421 · Evidence IDs: E-ORION-42-RESET

    If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

  2. #2 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.196 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-42-RESET

Found required evidence: E-ORION-42-RESET

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-42-RESET

    Retriever score: 3.652 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

  2. #2 · SEC-ORION-41-RESET

    Retriever score: 1.173 · Evidence IDs: E-ORION-41-RESET

    Orion DeskHub > Firmware 4.1 > Pairing reset Hold the side button for five seconds. Release it when the status ring flashes blue once. This procedure clears the current controller pairing.

HOLD-02 What light appears after completing recovery on Orion DeskHub firmware 4.1? Pass → Pass Split: heldout Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 2 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
2
Reciprocal rank
0.500
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-41-RECOVERY

Found required evidence: E-ORION-41-RECOVERY

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 1.930 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-ORION-41-RECOVERY

    Retriever score: 1.070 · Evidence IDs: E-ORION-41-RECOVERY

    Leave the adapter connected and hold the rear recovery switch for three seconds. The status ring turns white when recovery is complete.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-ORION-41-RECOVERY

Found required evidence: E-ORION-41-RECOVERY

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ORION-41-RECOVERY

    Retriever score: 1.845 · Evidence IDs: E-ORION-41-RECOVERY

    Orion DeskHub > Firmware 4.1 > Interrupted update recovery Leave the adapter connected and hold the rear recovery switch for three seconds. The status ring turns white when recovery is complete.

  2. #2 · SEC-ORION-42-RESET

    Retriever score: 1.059 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

HOLD-03 How long must both arrow buttons be held to calibrate Nova Room Sensor firmware 2.0? Pass → Pass Split: heldout Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 1 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-NOVA-20-CALIBRATION

Found required evidence: E-NOVA-20-CALIBRATION

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-NOVA-20-CALIBRATION

    Retriever score: 2.886 · Evidence IDs: E-NOVA-20-CALIBRATION

    Keep the sensor on a level surface and hold both arrow buttons for twelve seconds. Calibration is complete when the display shows a solid square.

  2. #2 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 1.119 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-NOVA-20-CALIBRATION

Found required evidence: E-NOVA-20-CALIBRATION

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-NOVA-20-CALIBRATION

    Retriever score: 5.347 · Evidence IDs: E-NOVA-20-CALIBRATION

    Nova Room Sensor > Firmware 2.0 > Manual calibration Keep the sensor on a level surface and hold both arrow buttons for twelve seconds. Calibration is complete when the display shows a solid square.

  2. #2 · SEC-ORION-42-RESET

    Retriever score: 0.500 · Evidence IDs: E-ORION-42-RESET

    Orion DeskHub > Firmware 4.2 > Pairing reset If the hub remains paired to an unavailable controller, hold the side button for eight seconds. Release it after the status ring flashes amber twice. The saved network settings remain unchanged.

HOLD-05 Does the Lyra Travel Router 3.0 guest reset disconnect current guest devices? Pass → Pass Split: heldout Pass · Sufficient evidence Coverage: 100% → 100% First relevant rank: 1 → 1

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-LYRA-30-GUEST

Found required evidence: E-LYRA-30-GUEST

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-LYRA-30-GUEST

    Retriever score: 6.525 · Evidence IDs: E-LYRA-30-GUEST

    On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

  2. #2 · SEC-ORION-42-RECOVERY

    Retriever score: 0.802 · Evidence IDs: E-ORION-42-RECOVERY

    Disconnect power for twenty seconds, reconnect the adapter, and wait until the status ring becomes steady white before reopening the control application.

Intervention

Pass · Sufficient evidence

Evidence coverage
100%
First relevant rank
1
Reciprocal rank
1.000
Precision@k
0.500
Retrieved hits
2

Required evidence: E-LYRA-30-GUEST

Found required evidence: E-LYRA-30-GUEST

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-LYRA-30-GUEST

    Retriever score: 7.515 · Evidence IDs: E-LYRA-30-GUEST

    Lyra Travel Router > Firmware 3.0 > Guest network reset On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

  2. #2 · SEC-ORION-41-RESET

    Retriever score: 0.993 · Evidence IDs: E-ORION-41-RESET

    Orion DeskHub > Firmware 4.1 > Pairing reset Hold the side button for five seconds. Release it when the status ring flashes blue once. This procedure clears the current controller pairing.

Unanswerable / N/A cases

DEV-06 Does Orion DeskHub firmware 4.2 support Wi-Fi 7? Not applicable Split: dev N/A · Unanswerable Coverage: N/A → N/A First relevant rank: N/A → N/A

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

N/A · Unanswerable

Evidence coverage
N/A
First relevant rank
N/A
Reciprocal rank
N/A
Precision@k
N/A
Retrieved hits
2

Required evidence: None

Found required evidence: None

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.864 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-LYRA-30-GUEST

    Retriever score: 0.525 · Evidence IDs: E-LYRA-30-GUEST

    On the Lyra Travel Router running firmware 3.0, select Guest Network, choose Reset Access Code, and confirm the prompt. Connected guest devices are disconnected.

Intervention

N/A · Unanswerable

Evidence coverage
N/A
First relevant rank
N/A
Reciprocal rank
N/A
Precision@k
N/A
Retrieved hits
2

Required evidence: None

Found required evidence: None

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 0.759 · Evidence IDs: None

    Controller Migration Notes > Comparing reset workflows Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the instal

  2. #2 · SEC-ORION-42-RECOVERY

    Retriever score: 0.725 · Evidence IDs: E-ORION-42-RECOVERY

    Orion DeskHub > Firmware 4.2 > Interrupted update recovery Disconnect power for twenty seconds, reconnect the adapter, and wait until the status ring becomes steady white before reopening the control application.

HOLD-06 What is the warranty period for Atlas Dock firmware 4.2? Not applicable Split: heldout N/A · Unanswerable Coverage: N/A → N/A First relevant rank: N/A → N/A

Required evidence gained: None

Required evidence lost: None

Still missing: None

Baseline

N/A · Unanswerable

Evidence coverage
N/A
First relevant rank
N/A
Reciprocal rank
N/A
Precision@k
N/A
Retrieved hits
2

Required evidence: None

Found required evidence: None

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 2.967 · Evidence IDs: None

    Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the installed device and version.

  2. #2 · SEC-ORION-41-RECOVERY

    Retriever score: 0.662 · Evidence IDs: E-ORION-41-RECOVERY

    Leave the adapter connected and hold the rear recovery switch for three seconds. The status ring turns white when recovery is complete.

Intervention

N/A · Unanswerable

Evidence coverage
N/A
First relevant rank
N/A
Reciprocal rank
N/A
Precision@k
N/A
Retrieved hits
2

Required evidence: None

Found required evidence: None

Missing required evidence: None

Ranked evidence

  1. #1 · SEC-ATLAS-42-RESET

    Retriever score: 1.493 · Evidence IDs: E-ATLAS-42-RESET

    Atlas Dock > Firmware 4.2 > Pairing reset Press the recessed rear switch for three seconds, then release it when the two port indicators blink together. Existing display preferences are retained.

  2. #2 · SEC-MIGRATION-RESET-COMPARISON

    Retriever score: 1.440 · Evidence IDs: None

    Controller Migration Notes > Comparing reset workflows Teams moving from Orion DeskHub firmware 4.2 to Atlas Dock firmware 4.2 should not assume that the pairing-reset workflows are identical. Use the procedure in the manual for the instal

Reproducibility

Keep the same reviewed dataset and retrieval depth when comparing runs. Run identifiers and configuration refer to the recorded artifacts.

Run identifiers, hashes and resolved configuration

Baseline · bm25-body

Run ID
6dce0073dba3
Run created
2026-10-19T15:26:53+00:00
Dataset hash
caea580e0969e1ec3447ad413e54f595584680eae8b6524aee09d28e948ca515
Product version
0.2.1
Python version
3.12.14
Platform
Linux-6.18.33.2-microsoft-standard-WSL2-x86_64-with-glibc2.43
Model
Not configured
Provider
Not configured
Full retrieval configuration
{
  "candidate_k": 2,
  "child_overlap": 50,
  "child_size": 500,
  "child_splitter": "none",
  "k": 2,
  "lexical_weight": 0.5,
  "model": null,
  "name": "bm25-body",
  "provider": null,
  "query_variants": {},
  "representation": "body",
  "reranker_model": null,
  "rrf_constant": 60,
  "strategy": "bm25"
}

Intervention · bm25-heading_context

Run ID
b830a46b179e
Run created
2026-10-19T15:26:53+00:00
Dataset hash
caea580e0969e1ec3447ad413e54f595584680eae8b6524aee09d28e948ca515
Product version
0.2.1
Python version
3.12.14
Platform
Linux-6.18.33.2-microsoft-standard-WSL2-x86_64-with-glibc2.43
Model
Not configured
Provider
Not configured
Full retrieval configuration
{
  "candidate_k": 2,
  "child_overlap": 50,
  "child_size": 500,
  "child_splitter": "none",
  "k": 2,
  "lexical_weight": 0.5,
  "model": null,
  "name": "bm25-heading_context",
  "provider": null,
  "query_variants": {},
  "representation": "heading_context",
  "reranker_model": null,
  "rrf_constant": 60,
  "strategy": "bm25"
}

Limitations

This report evaluates retrieved evidence; it does not establish causation or generated-answer correctness. Source previews can contain confidential content. Review before sharing.

Printing includes every question and ranked evidence item, including closed disclosures. Navigation is omitted. Use this complete view when exporting to PDF.