tool_use Is Not invoke(). A Draft Spec for Binding the Gap Between Them.
draft-das-agentic-tool-binding-03, an individual IETF Internet Draft revised around 5 September 2026, states that a model generated tool_use block, tool_calls array or MCP tools/call request is a non effective Candidate Act until it is bound to currently scoped authority computed over its own exact arguments and verified, and consumed exactly once, at a Finality Sink positioned immediately before the underlying call actually runs. It carries no working group, and its reference implementation ships under a source available evaluation license that reserves patent rights outside that narrow use.
Not according to a new IETF individual submission, and this desk found nothing in the draft's own reference implementation that contradicts that reading. draft-das-agentic-tool-binding-03, from independent inventor Sangram Das, treats a model generated tool call representation as a Candidate Act, a deterministic but non effective intermediate structure, across the three interface families contemporary agent runtimes actually ship: Anthropic style tool_use, OpenAI style tool_calls, and Model Context Protocol tools/call. A Candidate Act becomes effective only once an Act Bound Authority object, scoped to the workload, the destination, the current policy epoch and the exact argument content of that one call, is verified and consumed exactly once at a Finality Sink positioned immediately before the underlying invoke() call. The draft's own publicly readable reference implementation, read directly by this session since every ietf.org path was blocked, names two further properties this desk did not find named this precisely elsewhere in its own corpus: parallel tool calls must each receive an independently computed authorization decision rather than sharing one, and a retried or replayed call must be denied once the authority it would consume has already been spent. It remains an individual submission with no working group behind it, one entry in a large family of execution finality drafts the same author has filed across unrelated domains, and its reference code ships under a source available license that explicitly reserves production use, commercial use and patent rights outside evaluation.
Every agent runtime this desk has read about eventually produces the same shaped object: a block of JSON naming a tool and its arguments, sitting in a model's own output, waiting for something else to decide what happens next. draft-das-agentic-tool-binding-03 is the first IETF-track document this desk has found that tries to name that waiting object formally, across all three shapes it actually takes in production interfaces, and to specify exactly what must be true before it stops waiting.
A Candidate Act, not yet an effect
The draft's own reference implementation, fetched directly from its canonical GitHub repository since every ietf.org and datatracker.ietf.org path was blocked to this session on every attempt, states its governing principle in one sentence its own README repeats: generation of a tool call envelope is not effectuation authority. The implementation maps a raw tool_use block, a tool_calls array entry, or an MCP tools/call request into a Candidate Act, a deterministic, non effective representation distinct from the interface family that produced it. Nothing about the Candidate Act's own existence authorizes anything; it is a normalized description of what a model proposed, not a decision about whether it may happen.
Act Bound Authority and the Finality Sink
Effect is gated behind two further concepts the reference code implements directly, rather than only describing. Act Bound Authority is scoped specifically to one Candidate Act: it names the workload the authority was issued to, the destination the call would reach, the policy epoch current when it was issued, and, distinctively, a deterministic digest computed over the act's own exact arguments, so an authority object issued for one call cannot be presented for a different call with different arguments even by the same caller under the same session. The Finality Sink is the verification boundary that checks all of this atomically immediately before the underlying invoke() actually runs, rather than at connection time, at session start, or anywhere earlier in the pipeline. This session's own reading of the source confirms both concepts exist as real code, not only as README prose: workload proof of possession is checked so an authority object alone, without matching workload credentials, is insufficient, and the design is explicitly fail closed, meaning consequential execution is blocked whenever Finality Sink verification does not succeed, rather than proceeding on a default allow.
Two properties this desk had not found named this precisely before
Moona's own Risk Registry already carries AEW-005, approval not bound to the executed action, and its own response patterns already call for binding an approval to the exact action object by hash or an equivalent identity and recomputing that binding at the enforcement point rather than trusting the request, the same shape this draft's Act Bound Authority and Finality Sink implement for tool dispatch specifically. What this draft's reference implementation adds, read directly from its own dispatcher and replay store modules, are two further properties this desk's own corpus had not yet named this precisely. First, parallel call independent authority: where a model issues multiple tool calls concurrently, for instance one read that is expected to succeed alongside one payout that is not authorized, the implementation's own test suite treats each call as requiring its own independently computed authorization decision, rather than one authority object or one session level trust judgment covering every call in the batch. Second, non replayable single use consumption: the replay store atomically marks an authority object consumed on first use through a local single use record, so a retried or replayed call presenting the same, already spent authority is denied rather than re-executed. The reference implementation's own stated limitations are direct about scope: this replay protection is local rather than distributed, so it does not by itself guarantee atomicity across remote consequences or across independent server instances.
What the reference implementation does and does not demonstrate
This session's own direct reading distinguishes what the code actually shows from what search corroborated only at the level of the draft's own abstract. The implementation's policy layer, read directly, enforces two named consequence classes concretely, COMMUNICATION and FINANCIAL, denying a high consequence message from an untrusted provenance and a payment to a beneficiary outside a configured allow list. Broader claims that the draft's own text extends a fail closed requirement to PHYSICAL, NETWORK_CONTROL, and defense or critical infrastructure actuation specifically rest on this session's own web search of the draft's abstract rather than on anything this session read in the reference implementation's own policy module, and are recorded here as documented through convergent search rather than verified against running code. The reference implementation's own README is equally direct that this is a research artifact rather than a product: it states plainly it is not a production security product, that it relies on synthetic test data and local software enforcement, and that production payment, email, browser automation, hardware backed key protection, formal verification and distributed atomicity across remote consequences are all explicitly out of scope for this version.
A restricted license, not an open one
The repository is publicly readable, but this session's own direct reading of its LICENSE.md file found a source available evaluation license, not an OSI approved open source one. It grants viewing, downloading, running in non production environments, local modification for evaluation, and publishing evaluation results with attribution; it explicitly denies production deployment, commercial use, incorporation into a paid or hosted service, sublicensing and commercial distribution without a separate written agreement. Its patent language reserves the licensor's patent rights generally and grants only a narrow, non-transferable patent license scoped to permitted evaluation activity, stated as not extending to production use, commercial use, or standards implementation in commercial products. The repository's own NOTICE.md separately references a pending patent application. None of this bears on whether the underlying technical claims are sound, and this record does not treat a restrictive license as evidence against the architecture; it is recorded because a reader evaluating whether to build against this reference code, rather than only reading about it, needs to know its actual terms.
Standing: an individual submission inside a large solo portfolio
draft-das-agentic-tool-binding is an individual Internet Draft with no IETF working group behind it, currently at revision 03. This session's own web search found the same author has filed a substantial family of separate execution finality drafts across largely unrelated domains under the das- naming prefix, spanning RATS attestation for AI accelerators, an EU Digital Markets Act interoperability architecture, hardware rooted export controls for critical infrastructure, RF transmit authority for satellite control, enterprise AI output release, and a general execution finality protocol layer proposal, none of which this session independently read beyond their titles as returned by search. That breadth is recorded as standing context, a single author applying one architecture across many domains as individual submissions, not as a judgment on the technical merit of any one of them. A real, on-topic sign of external engagement does exist for this specific draft: an OAuth working group mailing list thread, Binding OAuth authorized calls to specific tool call arguments in agentic or MCP flows, discusses a gap this desk's own search corroborates as revision 02 of this same draft, and reports the thread exploring whether per invocation binding of this kind belongs at the OAuth or WIMSE protocol layer or is better left to the host application layer, an open question the thread's own participants had not resolved as of this session's search. This session could not directly fetch mail-archive.com to read the thread's own text, so its content is recorded at the search corroboration level, the same evidentiary bar this desk applies to every other blocked mailing list source it carries.
Sourcing limits, stated directly
www.ietf.org and datatracker.ietf.org were both blocked by this session's own network egress policy on every attempt, the same policy level block this desk's other IETF draft records already document, so this record was not built from a direct load of the draft's own filed archive text. What this record instead rests on is a real, directly fetched primary-adjacent source: the draft's own publicly linked reference implementation repository on GitHub, read directly by this session's own fetch tooling across its README, its license, its notice file and its policy module, together with independently phrased web search convergence for the draft's own title, its individual submission status, and the existence and rough content of the OAuth working group mailing list thread discussing it. Properties drawn from the reference implementation are graded verified where this session read the actual file; properties attributed only to the draft's own filed text, including the exact scope of its consequence class thresholds, are graded documented rather than verified, and a future editor with unblocked access to ietf.org should fetch the filed revision directly and confirm every such property before it is promoted.
Sources
This analysis interprets third-party reporting, research and announcements. Moona is not the original reporter of the underlying events.
Protocol evidence
This record does not assess these architectures. The connection runs through the Risk Registry requirement each one bears on, and these published authority architectures are what the evidence says about that requirement.
Protocol evidence related through AEW-005 Approval not bound to the executed action
- Supports requirement
Agent Flight Recorder
Laurent Bindschaedler, Quentin Botha, Christoph Siebenbrunner (independent research, arXiv preprint)
Requirement Cryptographic binding of the approval field to the approver's identity and the specific action is described as a production deployment property, not an unconditional schema guarantee
This weakness's own known examples are, across every one of them, a case where an approval attached to nothing verifiable or a later state change went unchecked against a prior decision. Agent Flight Recorder's own schema keeps a human approval field and an execution field as two independently checkable facts rather than one narrative line, which is a direct answer to the underlying need this weakness names: an approval must bind to a specific action, not merely occur near one. It supports that requirement rather than implementing an enforced version of it, because the reported cryptographic binding of the approver's identity to the specific action applies only in production deployments of the construction, not as an unconditional schema guarantee, and the mechanism records the approval/execution relationship for later forensic inspection rather than checking it before the action dispatches the way EMILIA's action hash rejection or Codex CLI's authorization freshness recheck do.
- Supports requirement
Agent Infrastructure Control Protocol (AICP)
Tihan-Nico Paxton, Apollo Deploy (individual submission to the IETF)
Requirement An accepted approval binds cryptographically or transactionally to one exact plan revision
This weakness's own corrective response pattern calls for binding an approval to the exact action object by hash or an equivalent identity, and rejecting execution when the action presented for review differs from the action about to run. AICP's own Section 9.4 requires an accepted approval to be cryptographically or transactionally bound to the Plan identifier, exact revision, approving principal, material changes and expiry, stating directly that approval of prose alone is insufficient and that a changed revision is not authorized by the old approval. The HTTP binding in Section 14.5 enforces the same binding mechanically, through a conditional request against the Plan's strong entity tag. Recorded as design evidence for the requirement this weakness already states, not as a claim that any provider has implemented this draft's text.
- Supports requirement
An Architecture for Auditing Agent Delegation and Interactions (audit-architecture)
Mirja Kuehlewind (Ericsson) and Henk Birkholz (Fraunhofer SIT), individual submission to the IETF
Requirement Authorization is modeled as an ordered sequence of transitions, not a single current value
This weakness's own response pattern calls for recomputing an approval's binding to the exact action at the enforcement point rather than trusting an earlier decision, including the temporal window that decision was made under. The draft's Action Record carries an authorization scope and expiry alongside the action it bears on, and its Authorization Transition Record class exists specifically so the state in force at a given point in a run can be reconstructed rather than assumed from whatever is currently known. Recorded as design evidence for the general response pattern; this record's own evidence separately connects to a targeted extension of Moona's canonical Authority Resolution engine closing the equivalent gap in Moona's own runtime reasoning, not a claim that this draft's own text was implemented anywhere.
- Supports requirement
ChainIT Authority Protocol and Agent Subject Profile for pre execution authority validation
ChainIT
Requirement A canonical transaction digest is described binding payer, payee, destination, amount, currency or asset and payment rail to approval and execution
A canonical transaction digest binding payer, payee, destination, amount, currency or asset and payment rail to both approval and execution is a direct, more specific response to an approval that attaches to nothing in particular. This is the corrective this weakness describes, named at the level of concrete payment fields rather than a generic hashed parameter set.
- Supports requirement
Codex CLI 0.151.0, restored permission profiles and authorization bound Guardian classifications
OpenAI
Requirement A cached low risk score is checked against the current authorization state before it is allowed to approve, and a mismatch defers to strict review rather than proceeding
Codex CLI's own fix rechecks a cached decision against current authorization state before it is allowed to approve anything, refusing to let a decision computed under one state keep approving after that state has moved. Claude Code's own current plugin marketplace documentation, read directly, describes an installed plugin auto-updating on a version, commit or content digest signal with no described mechanism to diff, flag or gate a change to the plugin's own hooks.json specifically, so whatever authority a user's earlier trust decision represented is not shown to be rechecked once a later update changes what that plugin's bundled hooks execute. Codex CLI's own mechanism is the corrective the reviewed documentation does not describe for this specific binding.
- Supports requirement
EP Authorization Receipts (EMILIA Protocol)
Iman Schrock, EMILIA Protocol, Inc., individual submission to the IETF
Requirement Implementations MUST reject an approval request whose action hash does not match a locally recomputed hash of the presented Action Object
EMILIA's requirement that an approval be rejected unless the action hash matches a locally recomputed hash of the exact action object is the binding these cases lack, where an approved command's behaviour is decided by state the approval never inspected.
- Supports requirement
EP Authorization Receipts (EMILIA Protocol)
Iman Schrock, EMILIA Protocol, Inc., individual submission to the IETF
Requirement Offline verification does not establish current revocation status, and the draft requires a relying party to apply current policy and current status inputs before any new reliance decision
UiPath Maestro's own default on Refresh schema before call setting keeps an MCP tool's technical interface current immediately before each call, but nothing in UiPath's own documented behavior establishes that the parameter authority a workflow's configuration granted against the original schema is re evaluated once a later schema changes underneath it. That gap, a technically current interface with no stated authority re evaluation behind it, is exactly the condition EMILIA's own requirement, that a relying party apply current status rather than historical acceptance before a new reliance decision, exists to close. UiPath's mechanism supports the need for that requirement rather than implementing it, the distinction this dataset already keeps between this property's two linked entries. A preprint posted to arXiv on 3 September 2026, 2609.03340, Fresh Memory, Stale Plans, restates the same distinction for a derived plan specifically: an executor that has read a superseding revision of a shared requirement into its own memory can still execute a plan derived from the earlier revision, since refreshing the executor's memory does nothing to a plan already computed from the state that memory has since moved past, so current state and current authorization for a pending action are two different facts. Read at the manual review evidence level, corroborated through convergent search rather than a direct read of the primary text, since arxiv.org and every mirror this record attempted were blocked at this session's network egress proxy; treated as further support for the requirement, not as an implementation of it.
- Supports requirement
N-AALP, Native Agentic Application Layer Protocol (draft-bubblefish-naalp)
BubbleFish, individual submission to the IETF
Requirement A signed-action-object model with a content-bound Approval and a single-use consume ledger is reported, not independently verified
This weakness's own response pattern calls for binding an approval to the exact action object, by hash or an equivalent identity, rather than to a name or a connection. The reported mechanism, an Approval bound under signature to the content id of the exact canonical argument object and, for an MCP call, a tool_id and args_id together, so a changed tool description or changed arguments yields a different approved call identity, would be a clean instance of exactly that pattern if it accurately reflects the draft's own filed text. This session could not independently verify that text through any reachable primary or secondary source, so this link is recorded conditionally: design evidence for the weakness's own already-established requirement, not confirmation that this specific draft implements it.
- Supports requirement
N-AALP, Native Agentic Application Layer Protocol (draft-bubblefish-naalp)
BubbleFish, individual submission to the IETF
Requirement A durable single-use consume ledger, and a stated limit that offline verification proves validity at issue, not current unspentness, are reported, not independently verified
This weakness's authorityGap states that authority attaches to what was presented for review, not automatically to whatever executes afterward; an approval a durable ledger has already recorded spent is not, in any meaningful sense, still attached to a further execution. The reported single-use consume ledger, and the reported statement that offline cryptographic verification proves validity at issue rather than current unspentness, would instantiate that gap precisely for a signed approval's own consumption state rather than its identity binding. Unverified by this session for the reason stated above; this record's own independent contribution is the additive extension it separately motivated to Moona's canonical Authority Resolution engine (an evidenced approval's singleUse/consumed state, consulted only when singleUse is evidenced true), which does not depend on this specific draft's own claims being confirmed.
- Supports requirement
The Missing Execution-Finality Protocol Layer of the Internet (draft-das-execution-finality-protocol-layer)
Sangram Das, individual submission to the IETF
Requirement A validated Candidate Act may produce a narrowly scoped, non-bearer Execution Handle bound to that one act and to the Finality Sink that will consume it
This weakness's own response pattern calls for binding an approval to the exact action object and recomputing that binding at the enforcement point rather than trusting possession of a credential. The non-bearer Execution Handle, corroborated through convergent search rather than a direct read of the filed text, generalizes exactly that principle to a credential class broader than one interface family: a validated Candidate Act may produce a handle scoped narrowly to that one act, and possessing the handle is not itself proof the currently presented act still matches the one it was issued for. Recorded as documented design evidence restating this weakness's own already-established requirement at a general level, not as independent confirmation that this specific umbrella draft's own mechanism is demonstrated running anywhere.
- Supports requirement
The Missing Execution-Finality Protocol Layer of the Internet (draft-das-execution-finality-protocol-layer)
Sangram Das, individual submission to the IETF
Requirement Formalizes Candidate Act, Non-Effective State, Protected Enforcement Domain, Execution Handle and Finality Sink as shared vocabulary for a family of domain-specific drafts
This weakness's own known examples had, before this addition, connected to draft-das-agentic-tool-binding-03 as though it were a freestanding architecture. Convergent search corroborates this draft as the umbrella that sibling instantiates: a Protected Enforcement Domain validates authority scoped to an act's purpose, destination, jurisdiction, freshness, revocation state, policy epoch, runtime integrity and effectuation-boundary identity together, a broader validation surface than the tool-binding draft's own two directly verified consequence classes. Recorded as design evidence for this weakness's own binding requirement at the general architecture level; this session located no reference implementation for this specific umbrella draft and does not treat any part of it as independently verified running code.
- Supports requirement
The Missing Execution-Finality Protocol Layer of the Internet (draft-das-execution-finality-protocol-layer)
Sangram Das, individual submission to the IETF
Requirement Fails closed on missing, stale, mismatched, replayed or unverifiable context
This weakness's own response pattern calls for rejecting execution when the action presented for review differs from the action about to run, rather than proceeding on a default allow. The signal that prompted this record carries a five-item fail-closed enumeration, missing, stale, mismatched, replayed or unverifiable context, consistent with the fail-closed behavior this weakness's own draft-das-agentic-tool-binding-03 known example already verified directly in running code for one narrower mechanism. This session's own independent search did not itself return that exact enumeration from a secondary source, so this link is recorded as documented design evidence consistent with corroborated evidence, not as independently re-confirmed word for word against the filed text.
- Supports requirement
tool_use Is Not invoke(): Binding Execution Finality to Agentic Tool Call Interfaces and MCP (agentic-tool-binding)
Sangram Das, individual submission to the IETF
Requirement Authority is scoped to one Candidate Act through a deterministic digest of its own exact arguments
This weakness's own response pattern calls for binding an approval to the exact action object by hash or an equivalent identity and recomputing that binding at the enforcement point rather than trusting the request. Act Bound Authority, confirmed directly this session from the draft's own reference implementation, is exactly that binding applied to tool dispatch: a deterministic digest computed over a Candidate Act's own exact arguments, so authority issued for one call cannot be presented for a different call bearing different arguments even under the same session or workload. Recorded as design evidence independently demonstrated in running reference code, not as a claim that this specific implementation is deployed anywhere.
This record is the cited evidence for this relationship.
- Supports requirement
tool_use Is Not invoke(): Binding Execution Finality to Agentic Tool Call Interfaces and MCP (agentic-tool-binding)
Sangram Das, individual submission to the IETF
Requirement A Finality Sink verifies authority atomically immediately before invoke() runs, fail closed on any failure
This weakness's own response pattern calls for recomputing an approval's binding at the enforcement point rather than trusting an earlier decision. The Finality Sink, confirmed directly this session from the reference implementation's own sink module, is that enforcement point positioned immediately before the underlying invoke() call, verifying authority atomically and blocking execution whenever verification does not succeed rather than proceeding on a default allow. Recorded as design evidence for the same requirement EMILIA's own action-hash rejection requirement already formalizes for payment operations, applied here to tool dispatch generally.
This record is the cited evidence for this relationship.
- Supports requirement
tool_use Is Not invoke(): Binding Execution Finality to Agentic Tool Call Interfaces and MCP (agentic-tool-binding)
Sangram Das, individual submission to the IETF
Requirement Each parallel tool call requires its own independently computed authorization
None of this weakness's own known examples had, before this addition, named independent authorization for concurrent tool calls specifically. The reference implementation's own test scenarios, read directly this session, decide a parallel search plus unauthorized payout case as two independent authorization decisions rather than one session-level trust judgment covering an entire batch, closing a gap this weakness's own binding requirement implies but had not yet evidenced concretely for parallel dispatch.
This record is the cited evidence for this relationship.
- Supports requirement
tool_use Is Not invoke(): Binding Execution Finality to Agentic Tool Call Interfaces and MCP (agentic-tool-binding)
Sangram Das, individual submission to the IETF
Requirement A retried or replayed call presenting already-consumed authority is denied
This weakness's own known examples document an approval or a cached decision surviving a state change it never accounted for; none had yet named a retried or replayed call presenting already-spent authority as its own distinct axis. The reference implementation's own replay store, read directly this session, marks authority consumed atomically on first use and denies a subsequent presentation of the same authority, with the implementation's own stated limitation that this protection is local rather than distributed. Recorded as design evidence for a property this weakness's own response patterns imply but had not yet evidenced at this level of precision.
This record is the cited evidence for this relationship.
- Implementation evidence
EP Authorization Receipts (EMILIA Protocol)
Iman Schrock, EMILIA Protocol, Inc., individual submission to the IETF
Requirement Implementations MUST reject an approval request whose action hash does not match a locally recomputed hash of the presented Action Object
MoonPay's PayBox documents that any change to an operation's amount, merchant, destination, contract, function or secret name after submission forces a fresh approval request rather than letting the original one carry over. That is the same operation-bound approval EMILIA's action-hash rejection requirement formalizes cryptographically, arrived at independently in a live consumer product rather than a draft specification, which corroborates that the requirement is buildable outside a standards process.
- Implementation evidence
EP Authorization Receipts (EMILIA Protocol)
Iman Schrock, EMILIA Protocol, Inc., individual submission to the IETF
Requirement Offline verification does not establish current revocation status, and the draft requires a relying party to apply current policy and current status inputs before any new reliance decision
Codex CLI's own merged fix binds a cached Guardian v2 classification to the exact authorization state it was scored against and refuses to let it approve an action once that state has moved, arrived at independently in a shipped product rather than a draft specification. That corroborates EMILIA's own requirement that a relying party apply current status inputs before a new reliance decision rather than treat historical acceptance as still current, the same binding failure this weakness already describes. OpenMAIC's own 1.0.1 fix, read directly by this dataset, applies the identical principle to a network destination rather than a cached score: fetchWithRedirectValidation re-runs validateUrlForSSRF against every redirect hop before following it, rather than treating the single validation performed against the caller's originally supplied bring your own key base URL as still current once an ordinary HTTP redirect substitutes a different destination. A third independent, shipped instance of the same requirement, this one at a network authority boundary rather than at an approval or a classification.
- Missing requirement
ChainIT Authority Protocol and Agent Subject Profile for pre execution authority validation
ChainIT
Requirement No canonicalization algorithm, serialization format or independent test of the transaction digest against a live or reference transaction was found
Naming the fields a digest binds is not the same fact as a demonstrated binding. No canonicalization algorithm, serialization format or independent test of the digest against a live or reference transaction was found, so whether an executed transaction can be proven identical to the one approved remains a missing requirement rather than a closed one.
- Missing requirement
Codex CLI 0.151.0, restored permission profiles and authorization bound Guardian classifications
OpenAI
Codex CLI's own shipped Guardian v2 fix binds a cached tool call classification to the exact authorization state it was scored against, refusing to let a stale classification approve a call once that state has moved. GitHub issue 43549, read through this session's own automated web fetch and summarization tool, reports a materially different gap this record's own reviewed material states nothing about: whether a tool call's own reported terminal status, here the literal status aborted following the caller's own interruption, is checked against the account level effect that call already produced before reporting that status. The reviewed protocol record binds a decision to the state it was made under; it does not, on the material available to this session, bind a call's own reported outcome to the state the call actually left behind.
- Missing requirement
tool_use Is Not invoke(): Binding Execution Finality to Agentic Tool Call Interfaces and MCP (agentic-tool-binding)
Sangram Das, individual submission to the IETF
Requirement The reference implementation ships under a restricted evaluation license, not open source
Demonstrating a binding mechanism in reference code is not the same fact as that mechanism being available for production adoption. This session's own direct read of the reference implementation's LICENSE.md confirms a source-available evaluation license, not open source, explicitly denying production deployment and commercial use and reserving patent rights outside evaluation. Recorded as a missing requirement for anyone evaluating this reference implementation as a buildable corrective rather than as design evidence, not as a claim against the underlying architecture the draft itself describes.
This record is the cited evidence for this relationship.