N17Q used protocol interoperability for discovery and transport while keeping consequence, identity, idempotency, approval, recovery, and evidence in a local product contract.
#tools
N17Q separated transport calls, semantic intents, world effects, reads, cost, and recovery reserves so a cheap batch, retry loop, or alias could not hide the actual consequence budget.
N17Q inserted parsing, normalization, policy, approval, effect identity, and receipts between model output and consequence, making tool use a state machine instead of a direct function call.
N17Q extended argument schemas with effect class, idempotency, queryability, compensation, authority, sensitivity, timeout, and replay contracts the harness needed to act safely.
V0M3 treated tool names and descriptions as metadata while server policy determined the capability, resource scope, arguments, and effect actually allowed.