Where Council of AI takes part, and what each listing does not mean
Council of AI (CSOAI Ltd) takes part in standards bodies as a participant or member, publishes into open registries and archives, holds scholarly identifiers, and files comments with regulators. Each entry below links to the page that proves it, or names the dated mailbox record when that is the only evidence, and says in its own row what it does not prove. Participation is not endorsement, and a listing is not adoption. Every entry links to its evidence.
Machine-readable: /interop/memberships.json (schema csoai.memberships/0.1, as of , unsigned — it says so in the file). Re-checked by scripts/memberships-check.mjs, which fails when any public evidence URL stops answering with our name.
Where we take part
Every entry, its evidence, and what it does not mean →Standards bodies
- W3C AI KR CGparticipant
- W3C Agent Conformance CGparticipant
- W3C Agent Identity CGparticipant
- IETF Internet-Draftfiled
- IETF scitt listparticipant
- IETF agentproto listparticipant
- IETF audit listparticipant
- C2PAmember
- DIFmemberprivate evidence
- Linux Foundationmemberprivate evidence
- OSAIAmemberprivate evidence
- BSI ART/1 commentscontributorprivate evidence
Registries & indexes
Scholarly identifiers
Regulatory filings
Policy programmes
Open-source commons
Participation is not endorsement, and a listing is not adoption. Every entry links to its evidence. Manifest as of , unsigned; re-checked by scripts/memberships-check.mjs.
Every entry, with what it proves and what it does not
Standards bodies
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| W3C AI KR (Artificial Intelligence Knowledge Representation) Community Group | participant | W3C Accounts Team notice: Nicholas Templeman became a participant representing csoai ltd at 2026-09-22 04:27 UTC (INBOX 9001; welcome INBOX 9002). | https://www.w3.org/community/aikr/participants public url · checked 2026-09-22 | Nicholas Templeman is listed on the group's public participants page, representing csoai ltd, which means the organisation signed the W3C Community Contributor License Agreement for this group. | Council of AI is not a W3C Member. Community Groups are free and open to anyone; joining one confers no W3C membership, no vote, and no W3C review of our work. The group has adopted nothing of ours. | VERIFIED |
| W3C Agent Conformance and Benchmarking Community Group | participant | Joined on behalf of csoai ltd on 2026-09-22 (the W3C join page reported the organisation had already signed the group's CLA); the participants page names us on the same day. | https://www.w3.org/community/agent-conformance/participants public url · checked 2026-09-22 | Nicholas Templeman is listed on the group's public participants page, representing csoai ltd. | Not W3C Membership. The group has not adopted, reviewed or endorsed any Council of AI benchmark or conformance method; participation is the whole of the claim. | VERIFIED |
| W3C Agent Identity Registry Protocol Community Group | participant | On or before 2026-09-22: the W3C join page on that date reported Nicholas Templeman as an existing individual participant. The exact join date was not recovered, so the date given is the day it was verified, not the day it began. | https://www.w3.org/community/agent-identity/participants public url · checked 2026-09-22 | Nicholas Templeman is listed on the group's public participants page. | Individual participation, not an organisational seat and not W3C Membership. The group has adopted nothing of ours. | VERIFIED |
| IETF Datatracker — Internet-Draft draft-templeman-scitt-framing-space | filed | Posted to the Datatracker on 2026-09-05 as an individual submission by the sole author. | https://datatracker.ietf.org/doc/draft-templeman-scitt-framing-space/ public url · checked 2026-09-22 | One individual-submission Internet-Draft, authored by Nicholas Templeman, is live on the IETF Datatracker. It is the only active Internet-Draft in our name. | An Internet-Draft is not endorsed by the IETF and holds no formal standing; the draft's own boilerplate says so. It has not been adopted by the SCITT working group or any other. There is no such status as 'IETF member'. | VERIFIED |
| IETF SCITT working group mailing list | participant | Earliest archived post by Nicholas Templeman that this check retrieved (2026-08-29). Earlier posts may exist; the archive search was rate-limited during verification. | https://mailarchive.ietf.org/arch/msg/scitt/ETVUZjsZ8XgkWR2XUW5oMexkdug/ public url · checked 2026-09-22 | A message from Nicholas Templeman is in the public IETF mail archive for the scitt list. | Posting to an open mailing list is participation only. It is not working-group membership (there is none), not consensus, and not adoption of anything we proposed. | VERIFIED |
| IETF agentproto mailing list | participant | Earliest archived post by Nicholas Templeman that this check retrieved (2026-09-05). | https://mailarchive.ietf.org/arch/msg/agentproto/LeKdTLTa6e_XBUfSO7Q8tiDuMvE/ public url · checked 2026-09-22 | A message from Nicholas Templeman is in the public IETF mail archive for the agentproto list. | Open-list participation only; no adoption, no consensus, no standing. | VERIFIED |
| IETF audit mailing list | participant | Earliest archived post by Nicholas Templeman that this check retrieved (2026-09-05 04:32 +0100, 'Control-delivery evidence as an input to audit semantics'). | https://mailarchive.ietf.org/arch/msg/audit/P6BcIxUmlzk3F6zz51bM-U6KDjI/ public url · checked 2026-09-22 | A message from Nicholas Templeman is in the public IETF mail archive for the audit list. | Open-list participation only. The audit effort is a proposed charter, not a working group we belong to; no adoption, no consensus, no standing. | VERIFIED |
| C2PA — Coalition for Content Provenance and Authenticity | member | Membership contract completed 2026-08-06; welcome 2026-08-17; logo supplied for the roster 2026-09-18 (INBOX 8835, 8885). The public roster now carries the entry. | https://c2pa.org/membership/ public url · checked 2026-09-22 | CSOAI LTD appears on the public C2PA membership page under Contributor Members. | Contributor is the entry tier: no steering role, no vote on the specification. Membership does not mean C2PA has reviewed or approved any Council of AI implementation, and no Council of AI product has passed the C2PA conformance program. | VERIFIED |
| Decentralized Identity Foundation (DIF) | member | Contributor agreement completed in the name of CSOAI LTD on 2026-08-18; DIF's membership team asked on 2026-09-21 which name to display for our Contributor Member listing (INBOX 8945) and we replied the same day (Sent 487). | private evidence INBOX 8945 (DIF Membership, 2026-09-21) and Sent 487 (2026-09-21) private email · checked 2026-09-22 | DIF's operations team treats CSOAI LTD as a Contributor Member and is preparing a website listing. | DIF publishes no member roster we could find (identity.foundation/members answered 404 on 2026-09-22), so no public page confirms this yet. No DIF working group has adopted any Council of AI specification. | VERIFIED |
| The Linux Foundation | member | The Linux Foundation sent CSOAI LTD one DocuSign envelope carrying the membership agreement for its Open Secure AI Alliance and Linux Foundation memberships (INBOX 8955, 2026-09-21). DocuSign reported that envelope completed by all parties at 22:56 UTC the same day (INBOX 8987). The tier, Silver, and the 2027-09-30 expiry come from the LF member portal record M-018884, which requires a login. | private evidence INBOX 8955 (the Linux Foundation, 2026-09-21: one DocuSign envelope carrying the membership agreement for both the Open Secure AI Alliance and the Linux Foundation memberships) and INBOX 8987 (DocuSign, 2026-09-21 22:56 UTC: 'All parties have completed'); LF member portal record M-018884 (login required) private email · checked 2026-09-23 | CSOAI LTD's Linux Foundation membership agreement was executed: DocuSign reported the envelope completed by all parties on 2026-09-21. | The evidence is private. We rely on DocuSign's completion notice and have not re-read the completed document; the Silver tier is taken from the login-required portal record, not from any mail. The Foundation's public members page did not list us on 2026-09-22. Membership is a paid participation tier, not an endorsement of our method, and no Linux Foundation project has adopted our work. | VERIFIED |
| Open Secure AI Alliance (a Linux Foundation project) | member | Application received 2026-09-18 (INBOX 8859). The Participation Agreement and Funding Charter travelled in the DocuSign envelope the Linux Foundation sent on 2026-09-21 (INBOX 8955), reported completed by all parties at 22:56 UTC (INBOX 8987). At 23:17 UTC the Alliance's onboarding mail opened 'Thank you for becoming a member of the Open Secure AI Alliance!' (INBOX 8988). | private evidence INBOX 8987 (DocuSign 'All parties have completed', 2026-09-21, attaching the Open Secure AI Alliance Participation Agreement and Funding Charter), INBOX 8988 (the Alliance, 2026-09-21: 'Thank you for becoming a member') and INBOX 8859 (application received, 2026-09-18) private email · checked 2026-09-23 | CSOAI LTD is a member of the Open Secure AI Alliance: the participation agreement was completed by all parties on 2026-09-21 and the Alliance welcomed CSOAI LTD as a member the same day. | No record we checked names a membership class, so we name none. The evidence is private, and secureaialliance.org publishes no member list. The note CSOAI published to the Alliance's SAFE discussion is our own; we have no record of SAFE adopting or acknowledging it. Membership is not an endorsement of Council of AI tooling. | VERIFIED |
| BSI — comments on draft BS ISO/IEC 4213 (project 2024-01986), committee ART/1 | contributor | Fourteen comments on the draft were sent to the BSI project mailbox on 2026-09-15; BSI Standards Assist replied the same day that the comments "have now been shared with the committee manager of ART/1" (INBOX 8363). A BSI Standards Development account was created on 2026-08-22 (INBOX 7116). | private evidence INBOX 8363 (AdminStart@bsigroup.com, 2026-09-15) and INBOX 7116 (2026-08-22) private email · checked 2026-09-22 | BSI received fourteen comments from Council of AI on a draft British Standard and passed them to the manager of committee ART/1, the UK committee for artificial intelligence. | We are NOT a member of ART/1 and have not been nominated to it. Commenting on a public draft is open to anyone; it is not committee membership, it is not a vote, and no comment of ours has been accepted into any standard. ART/1 mirrors ISO/IEC JTC 1/SC 42 and CEN-CENELEC JTC 21, and this row says nothing about our standing in either. | VERIFIED |
Registries & indexes
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| mcpservers.org directory — server "Council of AI — GSPC" | listed | mcpservers.org wrote on 2026-09-05 that the submission "has been approved and is now live", naming the listing URL https://mcpservers.org/servers/csoai-org/councilof-ai (INBOX 7848). | private evidence INBOX 7848 (contact@mcpservers.org, 2026-09-05) private email · checked 2026-09-22 | A Council of AI MCP server was accepted into the mcpservers.org directory. | The listing is self-submitted and the directory reviewed the submission, not the measurements. The row is private evidence because mcpservers.org answers HTTP 403 to every automated client: the only place our name appears in that response is the URL we ourselves requested, echoed back in the challenge, which proves nothing about the page. | VERIFIED |
| MCP Registry (registry.modelcontextprotocol.io), namespace io.github.CSOAI-ORG | listed | Earliest publishedAt among the io.github.CSOAI-ORG servers returned by the registry API on 2026-09-22. | https://registry.modelcontextprotocol.io/v0/servers?search=io.github.CSOAI-ORG public url · checked 2026-09-22 | Servers published under the io.github.CSOAI-ORG namespace are in the official MCP Registry; the API answers with them. | Registry entries are self-published under a GitHub namespace. The registry reviews nothing, ranks nothing, and a listing does not mean any client ships, installs or recommends these servers. | VERIFIED |
| PayAI x402 discovery index | listed | The index carries no listing date; the date given is when this check first walked the index and found councilof.ai doors in it. | https://facilitator.payai.network/discovery/resources public url · checked 2026-09-22 | councilof.ai x402 doors appear in the PayAI facilitator's public discovery index (the check walks every page of the index until it finds them). | A discovery listing is self-registered. It is not a settlement, a buyer, revenue, or PayAI's opinion of the doors. Read live settlement counts from GET /api/revenue, never from this row. | VERIFIED |
| Hugging Face organisation csoai | registered | The organisation page shows no creation date; the date given is when this check verified it. Datasets under it carry their own dates. | https://huggingface.co/csoai public url · checked 2026-09-22 | An organisation named Council of AI exists on Hugging Face under the handle csoai and publishes datasets and models there. | Hosting is not curation: Hugging Face reviews nothing we upload. Download counters are distribution, not adoption or a grade. | VERIFIED |
| PyPI (packages csoai and csoai-gspc) | registered | First release upload of the csoai package on 2026-08-13 (PyPI JSON API); csoai-gspc first released 2026-09-04. | https://pypi.org/project/csoai/ public url · checked 2026-09-22 | Packages published by CSOAI Ltd are on the Python Package Index. | PyPI reviews nothing. Download counts are distribution, not adoption; a package on PyPI is not a standard. | VERIFIED |
| npm (package csoai-gspc-mcp) | registered | Package created on 2026-08-28 per the npm registry's time.created. | https://www.npmjs.com/package/csoai-gspc-mcp public url · checked 2026-09-22 | The csoai-gspc-mcp package is published on the npm registry. | npm reviews nothing. Download counts are distribution, not adoption. | VERIFIED |
| OpenSSF Best Practices badge programme (project 14391) | registered | Project entry created 2026-09-01. | https://www.bestpractices.dev/en/projects/14391 public url · checked 2026-09-22 | The councilof-ai project is registered in the OpenSSF Best Practices badge programme. | Badge criteria are self-attested by the project. Registration is not a badge, and a badge is not a security audit. The completion state is whatever the project page says on the day, not what this row says. | VERIFIED |
| Software Heritage archive (origin github.com/CSOAI-ORG/councilof-ai) | registered | First full archive visit recorded 2026-09-02; a second full snapshot on 2026-09-15. The save request of 2026-09-22 failed with visit status not_found because GitHub hides the organisation profile while the account is flagged. | https://archive.softwareheritage.org/browse/origin/?origin_url=https://github.com/CSOAI-ORG/councilof-ai public url · checked 2026-09-22 | The repository has been archived by Software Heritage with at least one full snapshot. | Archival is preservation, not review or endorsement. The most recent snapshot may lag the repository; the latest save request failed and is recorded as such. | VERIFIED |
| Smithery MCP directory (csoai/gspc) | listed | The directory shows no listing date; the date given is when this check verified it. | https://smithery.ai/servers/csoai/gspc public url · checked 2026-09-22 | The gspc server has a page in the Smithery directory. | A directory page is a listing. Any score the directory shows is the directory's, not a measurement of ours, and a listing is not adoption. | VERIFIED |
Scholarly identifiers
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| ORCID iD 0009-0001-3869-1068 (Nicholas Templeman) | registered | Record created 2026-08-22. | https://orcid.org/0009-0001-3869-1068 public url · checked 2026-09-22 | A public ORCID record exists for the founder, naming Council of AI (CSOAI Ltd). | An ORCID iD is an identifier. It is not a credential, an affiliation check, or a review of any work attached to it. | VERIFIED |
| Zenodo record with DataCite DOI 10.5281/zenodo.21991104 | registered | Version 1 published 2026-08-18 (author Templeman, Nicholas; CSOAI Ltd). | https://doi.org/10.5281/zenodo.21991104 public url · checked 2026-09-22 | A methodology record by Council of AI is published on Zenodo with a resolving DOI. | Zenodo hosts; it does not referee. A DOI is a persistent identifier, not peer review and not an endorsement of the method. | VERIFIED |
| OpenAIRE Explore — research product record harvested from Zenodo | listed | OpenAIRE carries no date we can cite for when the record was harvested; the date given is when this check first queried OpenAIRE for the DOI and found the record naming us. The OpenAIRE record's own status field read UNDER_CURATION on that day. | https://explore.openaire.eu/search/publication?pid=10.5281%2Fzenodo.21991105 public url · checked 2026-09-22 | The Zenodo deposit 10.5281/zenodo.21991105 has been harvested into OpenAIRE, the European open-science aggregator, and the record names Council of AI. It means the deposit is discoverable through OpenAIRE and through the services that consume it. | Harvesting is automatic. OpenAIRE aggregates from Zenodo without reviewing, refereeing or endorsing anything, and the record's own status field read UNDER_CURATION when checked. This is indexing, not peer review, not publication in a journal, and not a statement by OpenAIRE about the work. | VERIFIED |
| Wikidata item Q141128616 (Council of AI) | registered | Item created 2026-08-19 (first revision timestamp from the Wikidata API). | https://www.wikidata.org/wiki/Q141128616 public url · checked 2026-09-22 | A Wikidata item exists for Council of AI (CSOAI Ltd). | A Wikidata item is not notability, recognition or endorsement; its statements are community-editable and only as good as their sources. | VERIFIED |
| Research Organization Registry (ROR) — registration request ror-updates#39647 | applied | Request opened on the public ror-updates issue tracker on 2026-09-02 (issue created_at from the GitHub API); still open, no ROR identifier assigned. | https://github.com/ror-community/ror-updates/issues/39647 public url · checked 2026-09-22 | A request to add Council of AI to ROR is open and public. | No ROR identifier has been issued. A request is not a registration; ROR curators may decline it. | PENDING |
Regulatory filings
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| NIST AI 200-2 (TEVV-Athlon) — public comment | filed | Comment sent from nicholas@csoai.org to TEVV-Athlon@nist.gov on 2026-09-17 with Date and Message-ID headers (Sent 417). | private evidence Sent 417 (2026-09-17, to TEVV-Athlon@nist.gov) private email · checked 2026-09-22 | A public comment on NIST AI 200-2 left our mailbox to the address NIST published for it. | NIST has not published the comment where we can link to it and has not replied on it. A comment is input to a process; it is not NIST recognition, adoption or endorsement. | VERIFIED |
| NIST AI 300-1 (initial public draft) — public comment | filed | Comment sent 2026-09-16 (Sent 345); a NIST reply thread followed, to which we answered on 2026-09-19 (Sent 465). | private evidence Sent 345 (2026-09-16) and Sent 465 (2026-09-19) private email · checked 2026-09-22 | A public comment on NIST AI 300-1 ipd left our mailbox, and a reply from a NIST address was received on the same thread. | A reply acknowledging a comment is not agreement with it. Nothing has been published by NIST at a URL we can cite. | VERIFIED |
| NIST SP 800-239 (initial public draft) — public comment | filed | Comment sent to sp800-239-comments@nist.gov on 2026-09-21 (Sent 485). | private evidence Sent 485 (2026-09-21, to sp800-239-comments@nist.gov) private email · checked 2026-09-22 | A public comment on NIST SP 800-239 ipd left our mailbox to the address NIST published for it. | Not published by NIST at a URL we can cite; not recognition or adoption. | VERIFIED |
| Bank of England — consultation on the draft Code of Practice for sterling-denominated systemic stablecoin issuers | filed | Response sent to CP-systemicstablecoin@bankofengland.co.uk on 2026-09-22 05:23 -0400, Message-ID <1509486989.87654.1790069007934@privateemail.com> (Sent 499). | private evidence Sent 499 (2026-09-22, Message-ID <1509486989.87654.1790069007934@privateemail.com>) private email · checked 2026-09-22 | A consultation response left our mailbox to the address the Bank published for this consultation, with Date and Message-ID headers. | The Bank publishes no acknowledgement we can link to. A consultation response is a submission; it is not recognition, and it does not make Council of AI a Bank of England stakeholder in any formal sense. | VERIFIED |
| US Department of the Treasury — docket TREAS-DO-2026-0496 (GENIUS Act implementation) comment | filed | — Comment drafted; the owner submits it on regulations.gov by hand. Until a tracking number exists the row stays PENDING and claims nothing. | https://www.federalregister.gov/documents/2026/08/18/2026-16796/genius-act-regulations-on-payment-stablecoin-issuance-offer-and-sale public url · checked 2026-09-22 | The rule is published and open for comment: Federal Register document 2026-16796, published 2026-08-18, docket TREAS-DO-2026-0496, comments close 2026-10-19. Nothing more: no comment from Council of AI is on it yet. | Not filed. The evidence link is the Federal Register document rather than the regulations.gov docket page because regulations.gov answers HTTP 403 to every non-browser client, which would make this row fail its own check for a reason that has nothing to do with the filing. Comments are still submitted at https://www.regulations.gov/docket/TREAS-DO-2026-0496. When the comment is filed, the row will carry the regulations.gov tracking number; a filing is still not recognition. | PENDING closes 2026-10-19 |
Policy programmes
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| European Commission — AI Pact | participant | The AI Office wrote on 2026-08-20 opening "Thank you for having recently joined the AI Pact" and invited this address to the AI Pact community on Microsoft Teams (INBOX 7036); the Teams guest invitation arrived the same day (INBOX 7035). | private evidence INBOX 7036 (EU-AI-PACT@ec.europa.eu, 2026-08-20) and INBOX 7035 (2026-08-20) private email · checked 2026-09-22 | The European Commission's AI Office records this address as having joined the AI Pact and invited it to the AI Pact community. | We have not signed the AI Pact's voluntary pledges, and the Commission's public AI Pact page did not name Council of AI when checked on 2026-09-22 — so this row is private evidence, not a signatory claim. Joining the community is not a statement by anyone that we comply with the AI Act, and it is not a relationship with the AI Office: the AI Office declined in writing on 2026-08-17 to review or validate our work. | VERIFIED |
Open-source commons
| Body | Standing | Since | Evidence | What it proves | What it does not prove | State |
|---|---|---|---|---|---|---|
| Open Invention Network — OIN 2.0 licensee | member | The OIN 2.0 License Agreement was signed on 2026-08-15 and OIN wrote the same day, "Welcome to OIN 2.0 — You're Officially Part of the Community!" (INBOX 6827). OIN's public community page lists us as CSOAI LTD. | https://openinventionnetwork.com/community-of-licensees/ public url · checked 2026-09-22 | CSOAI LTD has signed the OIN 2.0 License Agreement and appears by name on Open Invention Network's public list of licensees, which means we grant and receive a royalty-free patent cross-licence covering the Linux System definition. | This is a patent non-aggression arrangement and nothing else. It is not a standards body, it is not an AI governance body, and OIN has reviewed, endorsed or adopted nothing we publish. It says nothing about our measurements. | VERIFIED |
| LOT Network — member | member | LOT Network wrote on 2026-08-23 with the subject "Welcome CSOAI LTD to LOT Network" (INBOX 7148), after the joining mail of 2026-08-14 (INBOX 6829). The public member directory lists CSOAI LTD under C. | https://lotnet.com/members/?dir=1&name_directory_startswith=C public url · checked 2026-09-22 | CSOAI LTD appears by name in LOT Network's public member directory, which means we take part in its licence-on-transfer arrangement against patent assertion entities. | Like the OIN row, this is a patent arrangement and nothing more. LOT Network is not a standards body, not an AI governance body, and has adopted, reviewed or endorsed nothing we publish. | VERIFIED |
States follow the evidence. VERIFIED means the public URL answered with our name on the day checked, or a dated mailbox record exists and the row says the evidence is private. PENDING means an application or filing that has not been granted or submitted; it claims nothing. Rows with a link marked private evidence point at this page, not at a third party, because there is no third-party page to point at.
Named, and not listed
Bodies a reader might expect to find above, and are not there. Three reasons appear: we hold something weaker than the word would suggest, we are not eligible, or the body has no membership to hold. Each says which. This list exists so that absence from the table is an answer rather than a gap.
World Economic Forum — AI Governance Alliance
not open to usA personal Strategic Intelligence account was opened on 2026-09-21. That is a reader account on My Forum, not a membership or a partnership. WEF corporate participation runs through Partnership, which is invitation-based, revenue-screened and charged in six figures a year, and the AI Governance Alliance is a community inside that structure rather than an open sign-up. weforum.org answers HTTP 403 to every automated client we tried on 2026-09-22, so even that description rests on secondary reporting and is not something we can evidence ourselves. Not listed.
European Commission — General-Purpose AI Code of Practice
not eligibleThe Commission's own text limits signing to providers of general-purpose AI models. Council of AI provides no general-purpose AI model; we measure models other people place on the market. Signing would misdescribe what we are, so we have not applied and will not. This is an eligibility answer, not a backlog item.
https://digital-strategy.ec.europa.eu/en/policies/contents-code-gpai
OECD.AI Network of Experts (ONE AI)
not open to usMembers are nominated by OECD member countries and by stakeholder delegations, which renew or replace their representatives each year. There is no application form and no expression-of-interest route, so there is nothing for us to have applied to. The OECD door that is open to a company is the Catalogue of Tools & Metrics for Trustworthy AI, and that is a submission rather than a membership.
Global Partnership on AI (GPAI)
no membership existsGPAI membership is held by countries, and its work has been integrated with the OECD. There has never been a company membership to apply for, so any claim of GPAI participation by a company is a category error.
LF AI & Data Foundation
not eligibleThe free Associate tier is limited to government bodies, nonprofits and universities. CSOAI Ltd is a private for-profit company and fails that at the first requirement. The tier we could buy starts at USD 15,000 a year at our headcount, less an existing-Linux-Foundation-member discount, and we have not bought it. We do hold Linux Foundation membership at Silver, which is the row above; it is not the same thing.
IETF
no membership existsThe IETF has no membership. What is true and checkable is listed above as three mailing-list rows and one Internet-Draft. Three further submissions uploaded on 2026-09-12 were never posted and are not documents on the Datatracker, so they are not participation and are not counted here.
C2PA conformance programme
application in flightDistinct from C2PA membership, which is listed above with public evidence. A conformance application has been in flight since 2026-08-17 and must be resubmitted on the programme's 0.2 intake form. An application is not a conformance result and nothing about it is claimed on any Council of AI surface.
MLCommons
no recordA full sweep of nicholas@csoai.org across the whole of 2026 — every folder, headers and full-text body search — returns exactly one message containing the word MLCommons, and it is outbound: a note we wrote on 2026-09-17 about a measurement WE published, in which MLCommons AILuminate is one of fifteen organisations we examined. There is no welcome, no invoice, no agreement and no confirmation of any kind. Council of AI is not a member of MLCommons and no row claims otherwise. MLCommons does publish a free Observer tier for organisations of nought to nine employees, which we would qualify for; if we ever apply, the conflict — that we have published a measurement about them — is declared in the application and recorded here.
OpenML
cannot verifyA sign-up mail arrived on 2026-08-19 (INBOX 7000) and it is a verification request: "To verify your email address, please click". No confirmation followed, no later OpenML mail exists, and openml.org serves its profiles from a client-side application that we could not query for a user. We therefore cannot show that the account was ever completed. Signing up is not registration, so there is no row — and this entry exists so the absence is recorded rather than read as an oversight.
Glama
cannot verifyGlama mail confirms an account from 2026-04-16 and several approved MCP-server listings. We cannot show it publicly: Glama's index requires an API key, and its terms require visible attribution and a link wherever its records are displayed, which is a condition on republishing rather than an evidence URL a stranger can open. Listed here rather than as a row until a stable public URL exists.
NVIDIA Inception
no recordNo application or acceptance record exists in the mailbox as of 2026-09-22. Not listed.
Agentry
no recordThe operator's follow-up mail of 2026-09-15 says the agent is listed, but no public listing URL was located and the automated listing confirmation is not in the mailbox. Not listed until a stranger can open the page.
What changed, and when
/interop/memberships-updates.jsonAn update is a record of a change, not an announcement of an achievement. Nothing here upgrades a row; the rows say what they prove.
- Recorded
The mailbox was swept for memberships we hold and were not showing; five were missing and three claims did not survive the sweep
Every message in nicholas@csoai.org for 2026 was read by header, and the bodies were searched server-side for each body by name. Five things we hold had no row and now have one: Open Invention Network, LOT Network, the EU AI Pact, our comments to BSI committee ART/1, and the mcpservers.org listing. Three did not survive. MLCommons has no membership record at all — the only message naming it is one we wrote about a measurement we published concerning them. OpenML got as far as a verification request and no further. Glama's listings are real but have no public URL a stranger can open. Those three are recorded under Named, and not listed, with the reason, because a membership we cannot show is not the same as one we do not have, and neither may be displayed as current.
- Row addedopen-invention-network
Open Invention Network lists CSOAI LTD on its public community of licensees
The OIN 2.0 License Agreement was signed on 2026-08-15 and OIN's public page names us. It is a royalty-free patent cross-licence over the Linux System definition: a patent non-aggression arrangement, not a standards body and not an opinion about anything we measure.
- Row addedlot-network
LOT Network's public member directory lists CSOAI LTD
LOT Network wrote "Welcome CSOAI LTD to LOT Network" on 2026-08-23. Like the OIN row this is a patent arrangement — licence-on-transfer against patent assertion entities — and nothing about AI governance.
https://lotnet.com/members/?dir=1&name_directory_startswith=C
- Row addedeu-ai-pact
The Commission's AI Office recorded us as having joined the AI Pact on 2026-08-20
Its mail opens "Thank you for having recently joined the AI Pact". An earlier note of ours had reasoned that the AI Pact probably did not apply to a measurement company; the mailbox says we joined it, so the note was wrong and the row is the correction. We have not signed the voluntary pledges and the Commission's public page does not name us, so the row is private evidence and claims neither.
private evidence INBOX 7036 (EU-AI-PACT@ec.europa.eu, 2026-08-20) and INBOX 7035 (2026-08-20)
- Row addedbsi-art1-comments
BSI passed fourteen of our comments on a draft British Standard to the manager of committee ART/1
The comments on draft BS ISO/IEC 4213 (project 2024-01986) were sent on 2026-09-15 and acknowledged the same day. The row says contributor, not member: commenting on a public draft is open to anyone, and we have not been nominated to ART/1.
private evidence INBOX 8363 (AdminStart@bsigroup.com, 2026-09-15) and INBOX 7116 (2026-08-22)
- Row addedmcpservers-org
The mcpservers.org directory approved the Council of AI GSPC server on 2026-09-05
Recorded as private evidence rather than a public URL: mcpservers.org answers HTTP 403 to automated clients, and the only place our name appears in that response is the URL we ourselves asked for, echoed back in the challenge. A name that comes from our own request proves nothing about the page.
private evidence INBOX 7848 (contact@mcpservers.org, 2026-09-05)
- Evidence re-checked
Every public evidence URL in the manifest was re-fetched and answered with our name
scripts/memberships-check.mjs was run against the live web. Every public-evidence row answered HTTP 200 and named Council of AI, CSOAI or Templeman, except the US Treasury row, which is corrected below. Private-evidence rows were schema-validated and not fetched, because nothing on the network can confirm them; the manifest says so on each one. The check's own --selftest passed first, so the run is one that could have failed.
command
node scripts/memberships-check.mjs - Row correctedus-treasury-genius-docket
Evidence moved from regulations.gov to the Federal Register document, same docket
regulations.gov answers HTTP 403 to every non-browser client, so the row was failing its own check for a reason that had nothing to do with the filing. The evidence is now Federal Register document 2026-16796, published 2026-08-18, which names docket TREAS-DO-2026-0496 and carries the closing date. The comment is still submitted at regulations.gov and the row still says PENDING: nothing has been filed.
- Row addedopenaire
OpenAIRE harvested the Zenodo deposit; the record names Council of AI
A query to OpenAIRE for DOI 10.5281/zenodo.21991105 returns one research product naming Council of AI, CSOAI and Templeman. Harvesting is automatic and the record's own status field read UNDER_CURATION, so the row is indexing, not review.
https://explore.openaire.eu/search/publication?pid=10.5281%2Fzenodo.21991105
- Recorded
The named-and-not-listed list now carries the bodies we are not eligible for, with the reason
Absence from the table used to be a gap. It is now an answer. The European Commission's General-Purpose AI Code of Practice is limited to providers of general-purpose AI models and we provide none. OECD.AI's Network of Experts is nominated by countries, not applied to. GPAI membership is held by countries. LF AI & Data's free tier excludes for-profit companies. The IETF has no membership at all. Each of those is recorded with its source rather than left blank.
- Row addedw3c-agent-conformance
Joined the W3C Agent Conformance and Benchmarking Community Group on behalf of csoai ltd
The join page reported that the organisation had already signed the group's Contributor License Agreement, and the public participants page names us the same day. Community Groups are free and open; this is participation, not W3C Membership.
- Row addedw3c-aikr
Became a participant in the W3C AI KR Community Group representing csoai ltd
The W3C Accounts Team recorded the participation at 04:27 UTC. The group has adopted nothing of ours and W3C has reviewed nothing of ours.
- Recordedbank-of-england-code-of-practice
Consultation response sent to the Bank of England on the systemic stablecoin Code of Practice
Sent to the address the Bank published for the consultation, with Date and Message-ID headers. The Bank publishes no acknowledgement we can link to, so the row is marked private evidence. A response is a submission, not recognition.
private evidence Sent 499 (2026-09-22, Message-ID <1509486989.87654.1790069007934@privateemail.com>)
- Row addedlinux-foundation
Linux Foundation membership agreement completed by all parties
DocuSign reported the envelope completed by all parties on 2026-09-21. The member portal record M-018884 (login required) gives the tier as Silver. The public members page did not name us on 2026-09-22, so the row is marked private evidence. Membership is a paid participation tier, not an endorsement of anything we publish.
private evidence INBOX 8955 (the Linux Foundation, 2026-09-21: one DocuSign envelope carrying the membership agreement for both the Open Secure AI Alliance and the Linux Foundation memberships) and INBOX 8987 (DocuSign, 2026-09-21 22:56 UTC: 'All parties have completed')
- Row addedosaia
Became a member of the Open Secure AI Alliance
The participation agreement was completed by all parties via DocuSign, and the Alliance's onboarding mail opened 'Thank you for becoming a member', following an application received on 2026-09-18. The Alliance publishes no member list, so the evidence is private. The note CSOAI published to the Alliance's SAFE discussion is our own; we have no record of SAFE adopting or acknowledging it.
private evidence INBOX 8987 (DocuSign completed, 2026-09-21), INBOX 8988 (2026-09-21) and INBOX 8859 (2026-09-18)
- Recordeddif
DIF asked which name to display for our Contributor Member listing; we answered the same day
The Contributor agreement was completed in the name of CSOAI LTD on 2026-08-18. DIF publishes no member roster we could find — identity.foundation/members answered 404 on 2026-09-22 — so no public page confirms this yet and the row says so.
private evidence INBOX 8945 (DIF Membership, 2026-09-21) and Sent 487 (2026-09-21)
This log is the committed artifact rendered, as of , unsigned and saying so. An entry cannot appear here without being in the bytes first, and every entry that names a row names one the manifest actually has — scripts/memberships-check.mjs fails when it does not.
What each entry does and does not mean
Each answer is the manifest row again, in plain words. If a row and an answer ever disagree, the row is right and the answer is the defect.
Is Council of AI a W3C member?
No. Council of AI takes part in W3C Community Groups as a participant, representing csoai ltd, starting with the AI KR Community Group on 2026-09-22; the public participants page at https://www.w3.org/community/aikr/participants is the evidence. Community Groups are free and open, so this is participation, not W3C Membership, and it carries no W3C endorsement or review of anything we publish.
Does an IETF Internet-Draft mean the IETF endorses it?
No. Council of AI has one individual-submission Internet-Draft, draft-templeman-scitt-framing-space, posted on 2026-09-05 at https://datatracker.ietf.org/doc/draft-templeman-scitt-framing-space/. Individual submissions are posted without review or sponsorship, carry the boilerplate that they are not endorsed by the IETF, and have not been adopted by any working group; there is no such thing as IETF membership.
Is Council of AI a C2PA member?
Yes, at the Contributor Member tier: CSOAI LTD is on the public roster at https://c2pa.org/membership/ under Contributor Members, following a membership contract completed on 2026-08-06. Contributor is the entry tier with no steering role, and membership does not mean C2PA has reviewed or approved anything Council of AI has built.
Is Council of AI a member of the Decentralized Identity Foundation?
Council of AI holds a DIF Contributor Member agreement completed on 2026-08-18, and DIF's membership team confirmed the listing name with us on 2026-09-21. The only evidence is private correspondence, because DIF publishes no member roster we could find, so this row is marked private evidence. It is membership, not adoption of anything we publish by any DIF working group.
Is Council of AI a member of the Linux Foundation?
Yes. The Linux Foundation membership agreement was completed by all parties via DocuSign on 2026-09-21; the Foundation's member portal gives the tier as Silver (record M-018884, login required). The evidence is private: the Foundation's public members page did not list us on 2026-09-22. Membership is a paid participation tier, not an endorsement by the Foundation or by any of its projects.
Is Council of AI a member of the Open Secure AI Alliance?
Yes. The Alliance's participation agreement was completed by all parties via DocuSign on 2026-09-21, and the Alliance's onboarding mail that day welcomed CSOAI LTD as a member. The evidence is private correspondence, because the Alliance publishes no member list. The note CSOAI published to the Alliance's SAFE discussion is our own; we have no record of SAFE adopting or acknowledging it. Membership is not an endorsement.
Has Council of AI joined the EU AI Pact?
Yes. The European Commission's AI Office wrote on 2026-08-20 thanking Council of AI for having joined the AI Pact and invited us to its community. The evidence is that correspondence rather than a public page, because the Commission's AI Pact page did not name us when checked on 2026-09-22. We have not signed the AI Pact's voluntary pledges, so this is participation in the community and not a signatory claim, and it says nothing about whether any AI system complies with the AI Act.
Does being in the MCP Registry mean the servers are endorsed?
No. Servers under io.github.CSOAI-ORG are in the official MCP Registry, and the registry API at https://registry.modelcontextprotocol.io/v0/servers?search=io.github.CSOAI-ORG returns them. Entries are self-published under a GitHub namespace; the registry reviews and ranks nothing, and a listing says nothing about whether any client uses them.
Do the ORCID, DOI and Wikidata entries mean the work is peer reviewed?
No. They are identifiers: an ORCID iD for the founder (https://orcid.org/0009-0001-3869-1068), a Zenodo DOI for a published methodology record (https://doi.org/10.5281/zenodo.21991104), and a Wikidata item for the organisation (https://www.wikidata.org/wiki/Q141128616). Each makes the thing citable and findable; none of them is peer review, notability, or endorsement.
Has NIST or the Bank of England endorsed Council of AI?
No. Council of AI has filed public comments with NIST (on AI 200-2, AI 300-1 and SP 800-239) and a consultation response with the Bank of England on its draft Code of Practice for sterling systemic stablecoin issuers, the last of these on 2026-09-22. Each is a filing from us to a regulator, evidenced by the dated, message-identified mail in our own records; none has been published by the regulator at a URL we can cite, and a filing is never recognition, adoption or endorsement.
Has Council of AI filed with the US Treasury on the GENIUS Act docket?
Not yet. A comment on Treasury's GENIUS Act rule, Federal Register document 2026-16796 at https://www.federalregister.gov/documents/2026/08/18/2026-16796/genius-act-regulations-on-payment-stablecoin-issuance-offer-and-sale, docket TREAS-DO-2026-0496, is drafted and will be submitted by hand at regulations.gov; until a tracking number exists this entry is marked PENDING and claims nothing. Comments close on 2026-10-19.
Is Council of AI a member of the Open Invention Network?
Yes. CSOAI LTD signed the OIN 2.0 License Agreement on 2026-08-15 and is named on Open Invention Network's public list of licensees at https://openinventionnetwork.com/community-of-licensees/. That is a royalty-free patent cross-licence covering the Linux System definition — a patent non-aggression arrangement, not a standards body and not an endorsement of anything Council of AI measures or publishes.
How this page is kept honest
- One committed manifest, /interop/memberships.json, is the only source for the strip on the home page, the footer line, this table and the FAQ.
- A row exists only when a stranger can open its evidence, or a dated, message-identified mail exists and the row says so. Bodies with neither — and bodies we are not eligible for — are named above under Named, and not listed, with the reason and its source.
- Every change to the manifest is recorded, dated, in /interop/memberships-updates.json and rendered above. A table that only shows its current state cannot be audited; the log is the trace.
scripts/memberships-check.mjsre-fetches every public evidence URL and exits non-zero when one stops answering 200 with our name; its--selftestproves it goes red on a bogus row.- Nothing here is a score. We measure AI systems; we do not grade the bodies we take part in, and they do not grade us by listing us.