Map the inputs to the position
Describe what the wallet holds and what the application treats as collateral. Then identify the observation used for each valuation. A receipt conversion rate, a market quote, and a reference price can serve different purposes. A hypothetical lending dashboard should label them separately rather than select whichever produces the largest total. The review is incomplete until the reader can connect each number to the condition it influences.
Keep integration responsibility visible
Chainlink documentation distinguishes market integrity risks from application code risks and places responsibility for appropriate checks and contingency logic on the application developer. The practical lesson is to inspect the consumer, not only the feed provider. Ask which component rejects stale inputs, handles unexpected units, and decides what an unavailable observation permits. A reputable source cannot explain every assumption in an unrelated application's implementation.
Review liquidity as a separate question
A reference valuation does not specify the assets available through an actual exit. In a hypothetical position, compare a sale proposal with a redemption request and describe the conditions attached to each. A wallet should leave an unavailable executable quote unknown instead of presenting an estimated portfolio value as immediately withdrawable. Review the underlying DeFi and staking risk distinctions before combining several claims into one balance.
Design failure behavior by operation
Opening a position, increasing exposure, and attempting an exit need separate review under missing data. A blanket fallback may be inappropriate for one of them. Describe the permitted action, required observations, and authority controlling any exception. Record uncertainty clearly, including which input is missing. If an automated response is contemplated, keep its spending boundaries explicit rather than embedding new permissions in a general risk alert.
