Re: the demo of the APIless method of orchestration

Hi Paola,

Thanks for the follow-up. I want to address each point clearly:

1. MVCIC demo was shared, and you cut it short.
During the TPAC breakout session (Oct 2025), I began walking through the 
API-less orchestration demo. The recording shows you stopping it due to 
the five-minute slot: “OK, about time to stop. We now reached our third 
five-minute slot for recording.”

That’s why you didn’t see the full run—there wasn’t enough time/interest 
allocated and you cut me out starting my explanation (to present nothing).

You even acknowledge it here:

"Inspired by Daniel's fast outputting AI powered machine, although still
needing much refinement, jotted down some thoughts towards the possiblity
of AI powered web standards generator *possibly still science fiction, but
since reality is moving so fast."

https://lists.w3.org/Archives/Public/public-aikr/2025Nov/0006.html

But then you never properly attributed my work - Please, be honest, do 
not steal peoples work this way, stop being dissimulated, please.

2. The notebook has been open and duly credited since day one.
As stated earlier, the NotebookLM is just a personal study aid with 
links to all original docs. You’ve had edit rights since it was created, 
and every entry cites the original source. I’ve now added a prominent 
disclaimer reminding readers that official contributions must go through 
the CG tools.

Here's a print screen, since you do not have time to click a link and 
read a phrase someone shares.


3. Attribution timeline matters.

MVCIC (docs/multi_vibe_orchestration in the K3D repo) was first shared 
on Oct 9 (AIKR list) and Oct 30 (internal list).
Your Human Process of Web Standards Generation doc is stamped Created 
Nov 10, 2025.
The new “AI-Driven Web Standards Specification” CG was proposed Nov 17 
and launched Nov 28 (see 
https://www.w3.org/community/blog/2025/11/17/proposed-group-ai-driven-web-standards-specification-community-group/ 
and https://www.w3.org/community/aiwss/).
Given that sequence, it’s hard to treat the AI-driven standards 
initiative as unrelated to work already discussed in AIKR.
4. MVCIC isn’t “outside scope.”
MVCIC is documented with explicit KR vocabularies, reproducible 
workflows, and KR alignment notes already in the AIKR mailing list and 
wiki. If there are specific labels or formats you’d like, point me to 
them—I’ll adapt accordingly. The code itself lives in 
https://github.com/danielcamposramos/Knowledge3D/ under 
docs/multi_vibe_orchestration. It’s been public since October.

5. The LLM Council repo is newer.
Karpathy’s repo (https://github.com/karpathy/llm-council) was published 
in late November, so it couldn’t have been the basis for your Nov 10 
technical note. That further supports the need for proper attribution of 
earlier work already in this CG.



I hope that clarifies the timeline. I’ll be happy to repost the MVCIC 
demo links (or run them live) if needed—just let me know if this time 
you’re available.

Best,
Daniel