- From: Ron Itelman <ron@ronitelman.com>
- Date: Wed, 1 Apr 2026 09:57:01 -0600
- To: Michael Barnett <mbarnett@hmx.ai>
- Cc: "public-context-graph@w3.org" <public-context-graph@w3.org>
- Message-ID: <CAL582OepRcu5Zseoiv5RMZOypznDSu__ULMe-Nys+F2QxdAhPw@mail.gmail.com>
Hi everyone — great to see the energy from yesterday's kickoff. For those who missed it: *What we covered:* 1. The mathematical definition of context used in this group, how it relates to AI, and how it connects to the formal proofs. 2. Committee introductions and the program ahead. *How this group operates:* - The building blocks — the definition, the protocol, the canonical claim form — are the foundation. We're not spending group time debating them. We're giving them to you to build whatever you want with them, and providing mentorship. *Please see the illustration below if you haven't from the kickoff * - Our goal is to make implementing and understanding the Context Graph Protocol as seamless a developer experience as we can, and as clear an idea as any business leader can explain. - Anything outside that goal takes time away from the people who are here to build. As volunteers, time is our only commodity. My job is to protect yours. If this doesn't align with your goals, please reach out to me directly and I'll help you find a group that's a better fit. *What's next:* I've put together a spreadsheet tracking committees and members. Tell me which committee you'd like to join and I'll share it with you. Images attached. - If you're a developer and want a quickstart session (30 min) to create a Context Graph that runs locally using GitHub, let me know. If anyone wants to help extend it beyond Node (Python especially), we need you. - Juan Cruz and I are meeting to define 5-6 goals we can accomplish in 2 quarters. Ambitious — but do you really want to debate things for 2 years? Paper: https://zenodo.org/records/19351081 Protocol: https://w3c-context-graph-community-group.github.io/protocol/ Day 1. Started. Goal: Get the GitHub repo up. Task: Meet with Juan to standardize the best dev experience. [image: w3c context graph community group.png] [image: Ron-Itelman copy (21).png] [image: Screenshot 2026-04-01 at 9.28.49 AM.png] [image: Screenshot 2026-04-01 at 9.28.39 AM.png] [image: Screenshot 2026-04-01 at 9.28.49 AM.png] Ron On Wed, Apr 1, 2026 at 8:07 AM Michael Barnett <mbarnett@hmx.ai> wrote: > Ron, > > Please add me to committee "3. Business & Industry". I have use cases, > which do not yet contain a proper context graph capability; however, this > is the goal. Thank you for the protocol link, and I look forward to > learning about the building blocks and creating a robust capability. > > Regards, > > Mike > > > > <https://hmx.ai> > Explainable AI, > Human Centered > > Michael W. Barnett, Ph.D. > Founder & CTO > > +1 617 794 1401 > > 6 Liberty Square, #2331, Boston, MA 02109 > > Get CRex Add-in for Excel > <https://appsource.microsoft.com/en-us/product/office/WA200005695?tab=Overview> > > CRex Workbench & Server <https://github.com/HMXCorp/RedFlagsServer> > *LinkedIn* <https://www.linkedin.com/in/mwbarnett/> > > > > > > > > ------------------------------ > *From:* Ron Itelman <ron@ronitelman.com> > *Sent:* Wednesday, April 1, 2026 8:53 AM > *To:* public-context-graph@w3.org <public-context-graph@w3.org> > *Subject:* Kickoff Summary — Committees, Program, and Next Steps > > *If you are not subscribed to our calendar for event invites, please do so > (at bottom of email).* > > Hi everyone, > > Here's what happened at yesterday's kickoff and how to get involved. > > Committee chairs introduced: > > 1. Agentic AI — Alex Brown > 2. Knowledge Intelligence — Audrey Depeige > 3. Business & Industry — Anthony Marquardt > 4. APIs & JSON Schema — Juan Cruz Viotti > 5. Mathematics — Jacek Kowalski > 6. Decision Intelligence Interface — Dr. Lorien Pratt > > Reach out to me if you want to work with any of these committees. I'll > begin working with the Chairs to form a meeting where we can start! > > > The program: > We're building an open-source context graph on GitHub. You'll be able to > fork the repo, add your system, define your codebook, run the protocol > against another system, and commit your boundary log. No infrastructure > needed beyond a GitHub account. This will be ready in a few weeks. > > The purpose is to give you the building blocks to learn and take it > wherever you want to go. > > For devs: > > https://w3c-context-graph-community-group.github.io/protocol/ > > Hackathon starts in 6 weeks. More details coming soon. > > New paper published: > > Liquid Hypergraphs: A Context Graph Protocol is now on Zenodo. It contains > the formal proof, computable bounds, and six falsification criteria. Link: > https://zenodo.org/records/19351081 > > Next steps: > > - Join a committee > - If you are technical: Read the paper and/or protocol if you haven't > - Watch for the GitHub tooling announcement in the coming weeks > > Thanks to everyone who attended. If you missed it and have questions, just > reply. > > Subscribe to our calendar to automatically get invites > > *To subscribe, use this link:* > > > https://calendar.google.com/calendar/ical/c_db1de70c03fc4a76d5a3f4dc1d5145a6c469be2d9f148fd56019a9ca02933ea1@group.calendar.google.com/public/basic.ics > Then add it to your calendar: > > - *Google Calendar:* Settings → Add calendar → From URL → paste the > link above > - *Apple Calendar:* File → New Calendar Subscription → paste the link > above > - *Outlook:* Add calendar → Subscribe from web → paste the link above > > Once subscribed, you'll automatically see all our meetings with links and > details. > > *To view in your browser without subscribing: * > > https://calendar.google.com/calendar/embed?src=c_db1de70c03fc4a76d5a3f4dc1d5145a6c469be2d9f148fd56019a9ca02933ea1%40group.calendar.google.com&ctz=America%2FDenver > >
Attachments
- image/png attachment: Outlook-qwhjjzly.png
- image/png attachment: w3c_context_graph_community_group.png
- image/png attachment: Ron-Itelman_copy__21_.png
- image/png attachment: Screenshot_2026-04-01_at_9.28.49___AM.png
- image/png attachment: Screenshot_2026-04-01_at_9.28.39___AM.png
- image/png attachment: 06-Screenshot_2026-04-01_at_9.28.49___AM.png
Received on Wednesday, 1 April 2026 15:57:23 UTC