The dates
February 19, 2026: SynOI signed a mutual NDA with Post Oak Group and transmitted a five-page pre-seed memorandum describing cryptographic governance for autonomous AI execution. March 17: a refined executive summary went out, adding the CI/CD enforcement example. March 23: the Cloud Security Alliance issued a public press release naming a six-program initiative called "Securing the Agentic Control Plane," backed by Cloudflare, Cisco, and Ballistic Ventures.
[draft - full content pending - this section will reproduce the relevant artifacts: redacted memo excerpts, NDA timestamp, CSA press release text, and the side-by-side category-language comparison.]
What the gap means
Confidential transmission to investors creates timestamped priority for people who look back later and verify dates. It does nothing to claim a category in the public conversation as the category is being named. The 32-day window is, in retrospect, a documented case of priority - and a documented case of the wrong publication strategy.
[draft - full content pending - this section will walk through why the independent dating (government incorporation, NDA counterparty, NIST AI RMF timing) matters as third-party evidence, and what the priority claim does and does not establish.]
What it doesn't mean
It doesn't mean SynOI invented the category. CSA's working group has been forming for months. NIST's AI RMF predates everything. The problem has been visible to many people in parallel. What the gap establishes is that SynOI's architecture predates the category's public naming - not that SynOI is the only or earliest party to identify the problem.
[draft - full content pending - this section will name the parallel initiatives, situate SynOI's contribution as one of several independent answers converging on the same problem, and articulate why open-protocol leadership is the bet, not first-mover claim.]
Cross-references: founder's essay · vs ServiceNow + NVIDIA · standards alignment