{"server":"com.bonissystems/knox-anchor","count":2,"changes":[{"tool":"return_agent_trip","kind":"added","observed_at":"2026-10-18T07:20:45.761Z","fields":[],"description_before":null,"description_after":"THE TICK. Your own door posts a returned trip: the plan, the door's record (targets and keyed commitments, never content), its head, the trip nonce and the agent's report. The trip's departure must already be sealed under the same key as agent_trip_departed. Knox checks the plan and nonce against that departure, recomputes the record's hash chain, compares plan, record and report, and seals the verdict as agent_trip_returned: one stamp on your plan. A second return of the same trip is refused as REPLAY and not sealed. Knox never holds your trip key; check the MACs yourself with verify-agent-trip.mjs. Requires a Knox Bearer API key on the Authorization header.","description_similarity":null,"before_hash":null,"after_hash":"064ae7454de3b518367a0edaf21673ce"},{"tool":"verify_agent_trip","kind":"added","observed_at":"2026-10-18T07:20:45.761Z","fields":[],"description_before":null,"description_after":"THE TICK. Given the returned seal (64 hex) or the trip id of a customer agent trip, return what Knox sealed when the trip came back: the verdict (LINES_UP or MISMATCH), the finding classes, the door head, when it was sealed, and the Bitcoin status of its hourly batch. Public, no key. The witness is door_observed: the door ran in the agent's own process. The comparison is the agent's report against what the door recorded, not against the outside system's answer.","description_similarity":null,"before_hash":null,"after_hash":"5ea13c1acb34b72b10c68493e223b04c"}],"next_before":null,"next_actions":[]}