Human Feedback Types
partialPairwise Preference
Directly usable for protocol triage.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
HFEPX · Eval paper review
Angel Daruna, Michael Cogswell, Tixiao Shan, Yi Yao +2 more
Published
Nov 5, 2026
Citations
0
Trust level
Low
Usefulness score
40/100 (Low)
Extraction confidence
45% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 5, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
Use this page for context, then validate protocol choices against stronger HFEPX references before implementation decisions.
Best use
Background context only
Use if you need
Background context only.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
The available metadata is too thin to trust this as a primary source.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs. Two structures complicate this: the attacker's behavioral regime persists and can switch within an episode, and each action combines an operation with state-dependent arguments whose feasible values change over time. We capture both with a hidden Markov model whose latent state is the active regime and whose regime-conditioned action law is defined on a feasibility-masked tree of executable actions. The same likelihood forms the next-action distribution and updates the regime belief once the action is seen, and a partially observed prefix contributes its resolved local factors. Estimation separates into convex logistic fits that Baum-Welch reuses when regimes are unlabeled. We derive a reach-weighted nodewise KL expression for regime information, a sequence-wise log-loss bound for switching regime paths, and a uniform fallback guarantee. On the CAGE 2 cyber defense benchmark the filtered latent state is worth 0.8 nats per step, and after a controller switch the loss begins to fall in three steps against ten for a recurrent baseline.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
Pairwise Preference
Directly usable for protocol triage.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
None explicit
Validate eval design from full paper text.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
Not reported
No explicit QC controls found.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
Not extracted
No benchmark anchors detected.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
Not extracted
No metric anchors detected.
"A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
A defender anticipating an attacker needs a probability distribution over the attacker's next action from information available before that action occurs.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
Detected: Pairwise Preference
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.