Decision in 20 seconds
Including is a syntactic and semantic signal used in AI system design to indicate scope, dependency, or composability—especially in protocol definitions and model introspection tools.
Key points
- 'Including' often appears in technical specs to denote explicit dependencies or bundled capabilities.
- It signals intentional scope boundaries—not implied or emergent behavior.
- Builders use 'including' to audit surface area, assess integration effort, and manage version drift.
What changed recently
- OpenAI open-sourced the MRC protocol on May 7, 2026, explicitly listing AMD, NVIDIA, and others as collaborators—including in its specification and reference implementation.
- Anthropic’s May 8, 2026 NLA release documentation uses 'including' to enumerate supported motive-detection modalities, though full coverage details remain limited in public briefs.
Explanation
The term 'including' functions operationally in builder contexts: it anchors what is guaranteed versus what is optional or experimental.
Evidence shows recent usage aligning with formal interface definitions (e.g., MRC) and capability disclosures (e.g., NLA), but no evidence suggests new grammatical, parsing, or runtime semantics have been introduced.
Tools / Examples
- MRC protocol spec states: 'Supports RDMA offload, including vendor-specific extensions for AMD Infinity Fabric and NVIDIA NVLink.'
- Anthropic’s NLA documentation notes: 'Detects latent motives across 12 dimensions, including temporal inconsistency and reward-hacking proxies.'
Evidence timeline
Anthropic's valuation has surged to $1.2 trillion—surpassing OpenAI for the first time. Its newly released Natural Language Autoencoder (NLA) boosts detection of large-model hidden motives by over 4× and is already deplo
OpenAI open-sourced the MRC (Multi-Path Reliable Connection) protocol, collaborating with industry giants including AMD and NVIDIA to overcome network bottlenecks in large-scale GPU training; Anthropic, leveraging SpaceX
Sources
FAQ
Does 'including' imply mandatory support?
No. In current usage, it signals presence in tested or documented scope—not compliance requirement or default activation.
How should builders verify what's actually included?
Check the cited specification version, reference implementation, and test suite coverage—not just prose descriptions.
Search angles this page supports
including
Last updated: 2026-05-15 · Policy: Editorial standards · Methodology