N17Q made live capture and deterministic replay mutually exclusive runtime modes, so a missing fixture could never fall through to a real tool and repeat an external effect.
Blog, page 4
N17Q placed deterministic capability policy between an agent’s proposed action and execution, regardless of how persuasively the model explained that broader access would help.
N17Q bound human consent to normalized arguments, current policy, a precise run checkpoint, effect identity, expiry, and world preconditions that could still invalidate execution.
The March 2025 agent platform release made item streams, built-in tools, orchestration, and tracing easier to reach; N17Q still kept product policy and durable run state outside one provider.
N17Q derived stable external-effect identity from the run’s semantic intent, keeping retries, approval, receipts, and reconciliation attached to one consequence instead of one transport attempt.
N17Q extended argument schemas with effect class, idempotency, queryability, compensation, authority, sensitivity, timeout, and replay contracts the harness needed to act safely.
N17Q made plans, policy decisions, approvals, tool attempts, effects, checkpoints, artifacts, and unresolved uncertainty part of the durable product record.
N17Q’s first benchmark rewarded correct tool choices and a polished report while missing the duplicate external consequence created between them.
V0M3 removed the permanently animated assistant, made the document and review state visually primary, and let generation appear only where an author deliberately invited it.
A valid MCP tool request proved that arguments had the expected shape; V0M3 still had to establish identity, authority, resource scope, current state, approval, and recoverable effect semantics.
Porting V0M3’s source and tool boundary to the newly released MCP validated its capability adapters while exposing the identity, schema, permission, content-trust, and recovery work a protocol could not own.
React 19’s stable Actions and form primitives improved V0M3’s pending and optimistic interfaces, while document authority, idempotency, policy, and recovery remained domain work.
On MCP’s launch, V0M3 treated interoperable discovery and invocation as an adapter opportunity while keeping identity, authorization, content trust, review, and effects under product policy.
V0M3 exported ordinary Markdown and durable assets first, with optional provenance beside them, so completed writing did not depend on a provider, model session, or proprietary editor.
V0M3 treated rejection as an ordinary expression of authorship, even when a generated passage was accurate, polished, and objectively useful by common review criteria.
V0M3 separated evidence assessment from prose mutation so a reviewer could identify unsupported, contradicted, or overbroad claims without silently becoming their author.