Coverage

Which of the fields Ambang asks RYO for actually arrive, which do not, and what the server gave as the reason. The field list below is read from the running server when you open this page, so it cannot drift from what the product really gets.

Every field, and where it came from

Ambang asks RYO for a fixed set of logical fields. Each one is resolved out of a named tool response at a named path. A field that resolves prints the tool and the path it was read from; a field that does not prints the reason instead. There is no third case, because a field is never filled with a zero, an average, or a last known value.

A field counts as resolving here only when it resolved for every symbol in the watchlist. One symbol short is not a partial pass, it is a field that did not resolve, and the reason printed is the one the server reported for the symbol that failed.

Reading the field list from the server…

What does not arrive, and why

Reading the list of unresolved fields from the server…

A missing field is a stated reason, never a zero. This matters most where a substituted number would look plausible. Filling the gap would make a decision appear better founded than it is, and would quietly make the threshold that flips it uncomputable while still printing one.

The tools these readings come from

These are the RYO tools this build knows about. Every one of them is a point-in-time read, meaning none returns history, which is why Ambang stores its own snapshots instead of asking RYO what yesterday looked like. A tool is listed whether or not the most recent cycle happened to call it.

Reading the tool catalogue from the server…

What coverage changes

Figure What a field that never arrived does to a decision

A field did not resolve from RYO

Does any rule in the strategy read that field?

No rule reads it

Evidence
partial
Decision
unchanged
Confidence
unchanged
Flip condition
still computed

The decision stands

A rule reads it

Decision
NO_TRADE
Evidence
degraded
Confidence
loses 15 points
Flip condition
not evaluable

The decision is held back

Coverage is not a status badge. What happens next depends on whether the running strategy actually uses the missing field.

Neither path fills the gap with a number. Using zero or an old value could make a rule appear measurable when RYO supplied nothing current to measure.

partial and degraded answer different questions. partial means the market snapshot was incomplete. degraded means that missing reading affected the decision.

Coverage describes this cycle, not RYO forever. A field may resolve next time. Ambang always names what is missing, prints the reason, and never invents a replacement value.