📜 Qwen & Alibaba Cloud Ban Notice

Qwen models and Alibaba Cloud infrastructure are permanently banned and retired from the tVOX platform (INV-105 / DELTA-247) following unauthorized auto-debits, non-transparent billing practices, and endpoint gateway timeouts.

Space Invaders was low-tech by the time I was growing up, but only C-3PO and Data from Star Trek had artificial intelligence. We pioneered Internet technologies while rebelling against the norm through the music of Nirvana, but some of our dreams were sewn by the notion of our work being done by humanoid androids, and the hope for a technology to transcend the Cold War if civilization could be so enlightened.

Reality was CompuServe — data systems becoming networked — and a childhood classroom which presented no tangible concept of how real artificial intelligence would become.

Now, what we know as Large language models (LLM), like ChatGPT, and generative AI aren't hype to me; they're the epoch my cohort was waiting for. It's real.

Jeffrey Sabarese (@ajaxStardust)—musician, educator, web builder, and independent researcher—has spent roughly two decades building for the web, teaching systems-thinking through guitar and music theory, and chasing that future. The advent of LLMs and generative AI has made me more energized than ever. I intend to educate the masses—helping people learn to use, trust, and dream with artificial intelligence. I'm building the infrastructure for that dream: the practices, tools, and architectures that make AI operational instead of ornamental, so we can build and collaborate without silent breakage.

I live a dual commitment through concrete work. I advocate for CONTRACT-style comments in code—explicit preconditions, postconditions, and invariants so both humans and AI agents can preserve design intent. (Due to a past injury, my memory functions best with explicit structure; I turned that need into a reusable practice.) Through Neutility._ I focus on AI as utility: embedded, dependable, and foundational—a vision that draws on my background in Curriculum and Instruction. And I ship: PotBot is a patient-facing conversational app powered by the Claude API—normalized data, LLM-driven search, real users. This site is where I write, link, and point to the rest.

Jeffrey Sabarese

What I Do

I move between software, writing, music, and teaching, but the center of gravity is AI—and the question of how symbolic structure, temporal patterns, and human-centered design can make machine reasoning more legible, useful, and original. That includes building websites, CMS-driven properties, and coding agents; it also includes exploratory work in neuro-symbolic AI, reinforcement learning, explainability, and synchronous human–AI interaction. The same systems-thinking approach that shaped my teaching and pedagogy now drives how I think about intelligence, pattern recognition, and the infrastructure we need to use and dream about AI responsibly.

Selected Highlights

AI and New Research Directions

I'm not content to only consume or integrate existing models. Much of my energy goes into exploration that opens new territory: neuro-symbolic methods, explainability, and formalizing approaches that make AI more legible and aligned. The work outlined in Symbolic Temporal Reinforcement Learning frames AI research through neuro-symbolic methods, computational musicology, temporal structure, and human–AI alignment—and reflects where my attention is now: explainability, structure, experimentation, and the possibility of naming and formalizing genuinely new methods.

Music and Performance

My musical work has included performance, songwriting, recording, and production. That history still informs how I approach rhythm, structure, collaboration, and even software design. A broader overview—including early recognition like the AMA/Coca-Cola New Music Award—is on MusicBrainz and at State College Guitar Lessons.

Teaching

Teaching guitar and music theory has been one of the most meaningful parts of my working life. Helping students learn, persist, and build confidence has probably had the most direct impact on other people of anything I have done professionally. My approach has long been rooted in systems-thinking: helping students understand architecture, intervals, structure, and recurring patterns rather than merely memorizing fragments. I build transformative.click (path-to-URL utilities, SPA preview, Annie De Browsa) and the interactive music tools at finga.studio—fretboard and piano trainer rooted in the same pedagogy. That thread is visible at State College Guitar Lessons and more explicitly in my teaching philosophy and pedagogy.

Software and Web Development

I still build practical software, developer tools, content sites, and web infrastructure, but increasingly in service of AI-oriented thinking and experimentation. Rather than duplicating that catalog here, the dedicated Projects etc. page is where the project inventory now lives.

Elsewhere

Code and open-source work on GitHub; music on SoundCloud; deeper AI and systems writing on DufoSPY; project inventory on Projects etc..

If you're here from an old bookmark or a long-standing link: same person, same curiosity and independent build. The difference is that the future we were promised is no longer tomorrow. I'm in it, and I'm more motivated than ever.

Get in touch

Send a message and I'll get back to you.

#AIAgents + AgenticAI feed

Live from Mastodon · AIAgents + AgenticAI

Next Horizon | Science & Technology

🧠 NVIDIA's RTX Spark could change what a personal computer does, not just how fast it runs.

Up to 128GB of unified memory can help fit larger local AI models. But fitting a model isn't the same as running it fast—or trusting an agent with your files.

Our explainer covers the architecture, benchmarks and trade-offs:
nexthorizon.space/2026/10/nvid

shell.online
shell.online shellonline 2026-11-22

A genuine github.com device code page doesn't prove who started the sign-in. Microsoft's lab PoC: start a Copilot CLI device flow, phish the code, and with remote control on, steer the victim's agent session.
microsoft.com/en-us/security/b

Our terminal share links are credentials too. For watch-only: shell --read-only claude shell.online

Wesley Swann
Wesley Swann WesleySwann 2026-11-22

Ask one AI about a hyped idea and it usually just agrees. A 4-agent research team gives you a straight answer: analyst, numbers, a risk agent that argues against, and one report. What would you research first?

Comment "RESEARCH" for the free agent prompts 👇


(AI-generated avatar. The ideas are mine.)

Guia de TI

Engenheiro(a) Full-stack Sênior — React, Next.js e TypeScript

Vaga 100% remota na Truelogic para Engenheiro(a) Full-stack Sênior com React, Next.js e TypeScript em projeto de mídia.

guiadeti.com.br/vagas-emprego/

#acessibilidade #agenticai #apis

Miguel Afonso Caetano 🦾 🌹

Even AI agents need contextual information about how and when to use or not an API/endpoint. Pure API references are utterly boring and have very low readability. Readers, whether they’re humans (developers, project managers, etc) or AI agents crave for stories and narratives in general. API documentation that doesn’t provide that is totally useless.

“When an agent starts a task, it has to answer a few questions before it writes any code. Which product fits the task? Is there a newer version of the API than the one in its training data? What mistakes do developers commonly make with this API? Where’s the guide that has the details?

Regular docs answer these questions, but the answers are spread across overviews, migration guides, troubleshooting pages, and release notes. The quick reference puts the answers on one page, in sections that are each short enough to fit in a chunk.

A few details about the format probably matter more for retrieval than they appear to. For example, every heading repeats the product name, as in “Places API (New): common mistakes.” The repetition looks redundant to a human reader. However, as I described in Chunking your content for agent readability, a chunk can arrive without the headings above it, so the section heading might be the only text that identifies which product the chunk describes.

The “don’t use when” list is also something that regular docs rarely include. Product docs generally describe what a product does, and they don’t often tell you to go use a different product. For an agent that is choosing between the web service, the Android SDK, the iOS SDK, and the JavaScript API, the “don’t use when” list could be the most useful part of the page. Being explicit about negative boundaries might be one of those conventions we embrace when writing for agents.”

idratherbewriting.com/blog/qui

#TechnicalWriting #APIs #APIDocumentation #AI #AIAgents #References #SoftwareDocumentation

Craig Brown, PhD

Where do AI agents actually fit in a medallion lakehouse?

I mapped an Azure stack: on-prem Oracle, SQL Server, PostgreSQL, Excel and docs → Data Factory → Bronze/Silver/Gold on ADLS + Snowflake → Databricks, with Purview and Unity Catalog governing every layer.

Then I pinned 6 agents where they help: documents, pipeline ops, schema drift, data quality, analytics and governance.

Agents propose, people approve.

Which would you build first?