[x3d-public] MCCF Issues

[John Carlson]

1. Have Claude generate a prompt for you.

2. Use skills to reduce token:  https://skills.sh/  Requires agents.  I
have been exploring ollama, pi and Gemma4 (many models) for local processing

3. Take advantage of X3D MCP if you can.

John

On Wed, Apr 22, 2026 at 2:21 PM Len Bullard via x3d-public <
x3d-public at web3d.org> wrote:

> MCCF Progress:
>
> 1. Using Claude, a new chat loses state precariously.   What worked
> smoothly in first chat goes to hell in new chat.  Because chat context
> windoww are limited, am forced into new chat which is the 50 FIrst Dates
> problem.  I can use the GitHub to recover state but it is not a perfect
> solution.
>
>
> https://aiartistinprocess.blogspot.com/2026/04/the-seed-crystal-how-artists-can.html
>
> 2.  Rate limits on downloads from GitHub force copying into Claude chat
> window.  Second session limits are much lower so time is lost waiting
> for resets.  Frustrating.
>
> 3.  Much session time is wasted because Claude makes lots of mistakes
> with the coding and in the successive chats as the project grows more
> complex this compounds.  Corrections take several tries and each attempt
> has to be retested by me.  It is confident of fixes but wrong. Claude
> can corrupt code.  Keep old working versions. Frustrating.
>
> 4.  If Claude is pulling from GitHub and I am testing the local files it
> gives to me, it is easy to desync and collide.  This did not occur
> during first chat session.  A nightmare.
>
> AI coding is productive but can be expensive.   It is not all it is
> cracked up to be.  YMMV.
>
> 5.  Working with W3DC projects can be hit or miss.  Working groups are
> not as responsive as ten years ago and that is likely because it is a
> much smaller group.  X_Lite is polymorphic because it is handling
> multiple formats.  A 3D swiss army knife.  At minimum this means API
> calls are not as documented in standard.  Product documentation as far
> as I can tell does not include the product specific API calls.  Two
> implications:
>
> a.  If a developer is not "in the know" they will waste time and
> resources.
>
> b.  AI will not be "in the know" because it scrapes for training data
> and sparse data or legacy non-currrent data is used for training.  It
> can't keep up.  Results of a and b are frustration, wasted time and
> wasted money.  Caveat emptor.
>
> 6.  A Harvard researcher forked the Github.  The good news is interest
> in an open source project.  The bad news is he inherited all of the SAI
> problems.  It is a prototype and those are the risks with open source.
> We shall see if code contributions are made back to the original
> project.   Fortunately everything is time stamped so YMMV.
>
> 7.  Reddit articles show that others including Anthropic are researching
> the emotional attractors in Claude.  Because affective layers are part
> of every Foundation LLM, this is good news.  It validates what we set
> out to work on with the MCCF.  The math approach we are using is likely
> unique because I require a dynamic system.  It is working and we benefit
> from the published results of other researchers.  MCCF is very
> expressive and pretty much on target for tools to explore emotional
> vectors, domains and trajectories in LLMa.  The HumanML work twenty
> years ago paid off.  I suspect the use of X3D for visualization for MCCF
> is likely unique.  Because my goals for this project are not explicitly
> the same, I anticipate divergence.  That's fine.
>
> Time to go do something else for a few hours.
>
> len
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20260422/a7eaa75c/attachment-0001.html>