undefined | Better HN

0 pointsdanielcasper29d ago0 comments

Honestly, the thing I'm most excited for is building video games, figuring out how to help myself and other folks find the right kind of work (especially our own), and seeing how the rest of the parts of human neuroanatomy fit into CoreTex (like the angular gyrus for enhanced multimodal meaning). Making the analog of the mind was the most fun part, and I learned so much from it! Now, when I look at my daugher, I understand why her mirror neurons work the way they do, and how her Broca's area is forming during the period of hyper-plasticity. Makes me cry.

As for immediate use cases - I think the most powerful thing right now is just the ability to play with the config with system and agents. You can easily compose with them, give it a prompt, no lock in to any single provider. And the review gates are nice. Code gen is still experimental and will be finicky.

I think what CoreTex is uniquely poised for is being the most lightweight and easily extended "control center" of various AI systems. That's why I doubled down on UNIX philosophy, inherent security, and minimal dependencies for maximal portability. I want this thing to work on any system, take a bullet, and still stay up to help you control AI + complete your goals.

Thanks for your question!

0 comments

2 comments · 1 top-level

JSRR199129d ago· 1 in thread

I like what you said about 'take a bullet' and 'still stay up'

Real brains don't run on respond cycles. Do you see this getting a heartbeat system or is there anything implemented / planned to make it a persistent daemon?

like it could check different surfaces for deviation for useful discoveries, or problems that need to be remediated, or even browse Hackernews for exciting new tech to learn about and grow!

danielcasperOP29d ago

It is currently a daemon with the /.ctx live command. That will turn on the watchdog process, the webhook listener, the file system listener, and all the other passive systems.

One of the more interesting features I want to implement is the "distributed spine." I want CoreTex to live on multiple machines, offloading particular parts of computation to say - the gaming computer with the GPU running higher local models, sensory data being routed from embedded systems, and a low-power alternative for it to sync to. When the gaming computer turns off, the low power unit will promote itself to primary CoreTex for overnight watching / sleeping / dreaming, then revoke control back to the primary computer when it turns back on. In this sense, CoreTex will be a distributed system, increasing its stability and uptime.

You should be able to use this for anything, really, given its UNIX philosophy and OSS.

j / k navigate · click thread line to collapse