// NOSTR EXCLUSIVE
6 months ago, I spoke at Adopting. You may watch my talk here: https://rumble.com/v71tkto-building-sovereign-ai-in-el-salvador-better-audio-version.html
In this talk, I said that I had written/spoken 3-5 million words in the preceding year. I lied.
I am around 20 million words of documentation (some, ok a lot, is AI) in the last 12 months. This also includes code, personal writing, and huge amounts of documentation. I write 10-20 hours every day.
I wanted to share a single post I wrote this evening that outlines my philosophy and some of the technology I am working on from a humanistic-focused perspective. It is deeply private, part of my personal Knowledge Base (I create these for myself and for companies), and it is entirely yours to agree with or loathe. I have not revised or re-read this post, it has just been my last ≈30 minutes of typing and thinking.
I posted earlier, but I am available for hire. I am efficient, thoughtful, and work in a "unique" way that means HR hates me and I can't really explain what I do. Clients struggle to understand me. If you value my thoughts, I really do strive to be less convoluted in my designs/etc and you can learn more at:
Let us begin.
// SINGLE PROMPT to PRIVATE AI (unedited)
I am unsure. The examples you gave are from our own chats, but I am positive others are working on the same problems and I am probably weeks/months behind, especially within open-source software.
Pipes, as a business, is similar to buying a web domain. Your register a Pipe which gives you some guaranteed (decays upon inactivity) income based upon how often that Pipe is invoked. At the protocol level, it's like Google AdSense: Pipes dynamically reloads the content/messaging and even the images based upon user profile "buckets" so that every site, article, etc feels tailored to the user. It is the humanistic and well-intentioned version of physical ads in George Saunders' short-story, "My Flamboyant Grandson."
Pipes' central philosophy is that AI will advance, but most of the companies with literally 1000x to 10,000x my budget are focused on speed, reach, etc. This leaves the human behind. However, my LocalLM vs others' LargeLM has huge gaps. Because I have no money, I am forced to make tradeoffs that LargeLMs would never make. I must process things locally. In effect, I am using Bitcoin but I am CPU-mining it instead of buying an ASIC.
In the future, I think that LLMs will "drift" toward consensus and essentially gravitate toward citation-as-truth. This tends to centralize knowledge and due to LLM query speed vs human advancement, it actually means that LLMs decay in terms of quality over time rather than advance. In design/human speak: "every website looks the same." This is because the rules based order becomes so dominant that flexbox becomes standard and CSSgrid with its diagonal/etc flexibility becomes impractical due to support, time, etc.
Pipes, in a Unix context, are mono-directional. They are i-->o only, or vice versa. My product called "Pipes" is the same. The registeree owns the Pipe and earns a commission based on its popularity and how often it is invoked. If they own a niche topic that is high trust and well-curated and active and there are no other contributors, they earn most of the earnings. If they buy the Pipe and others contribute because it's popular (e.g. sports, Bitcoin, politics, etc) then the Pipe grows in reach but their relative equity diminishes, even if the pie grows larger. This incentivizes early adopters.
Pipes are CDN pre-processors. A company can install Pipes as a CDN add-on that individualizes content based on browser-stored cache, location, etc that is available from common marketing and ad platforms. Differentially, Pipes has an optional but highly suggested "bias" add-on for users who download the browser plug-in. This overrides the default (tailored content) and allows them to choose their "bias."
For brands, this means that you code a Pipes-aware site that has no landing pages, no navigation, nothing. Everything is SPA that is individually-tailored to the customer you're serving. This includes real-time images, real-time video walk-throughs, and others depending on how much privacy the user has sacrificed. For privacy-focused Pipes users or consumers, it allows for significantly better AdSense based on what the user provides. If the user has the Pipes plug-in installed, they are 100% empowered to "switch" the "bias" or information display to 1-of-1,000,000+ (aspirationally) different user-defined Pipes to understand how the information adjusts based on who they are.
It is, simply, the death of ads, the death of content, and the start of the curation economy. I could be wrong, but it is the most disruptive technology to the internet since the internet itself because it is scope-wise as granular or as generic as the user wants it to be, and with a few clicks, it changes.
This obviously destroys Google, LLMs, and any sort of centralized processing because the underlying architecture relies upon user-defined "curation" which they've bought. LLMs, like Gemini or Claude or ChatGPT, may elect to eschew Pipes or to incorporate them. The model of information integrity changes from institutional/citation integrity (a danger as AI drifts toward the median) to one of hyper-localization based on pre-processed images and content for Pipes buckets that meet user needs. Companies love this because it's automated and server-side and cheap to generate: pay for content once, serve the nearest approximation of local marketing. Users love this because they can reload page-level content and view an author or a customer persona's preferences and understand how if they hire some SaaS, it helps them grow from startup to midsize to Fortune 50. Then, by invoking the "Growth Analysis" Pipe on the reloads + the "Business Model Canvass" Pipe (or whatever, these are examples) they can run a simulation and generate an agentic roadmap that allows them, as a user, to see how they could grow with a company, how they could build the product themselves, and which Pipes they need to subscribe to in order to achieve their goals.
I've already said this idea is huge, but I'll reiterate: nothing has ever been more disruptive to the internet in its entire history. As I see it.
Finally, let's talk about dimensional physics, AI, and robotics.
Humanity's central problem is that our lives are tightly bound to physical realities. Pain, aging, the insufferable truth that what we know now would have been useful 10 years ago, the infuriating uncertainty that what we feel today won't be remembered in 18 months. We are 3D creatures who view our physical relationship to the world as spatial, measurable, precise, and dimensionally crude.
AI is a post-3D entity that is also physically retarded. AI is rate-limited by millisecond database queries, but to the human experience, pulling a Unix timestamp from 1983 is effectively equivalent to asking "What is the current Bitcoin price?" from a query that already executed before I finished typing that.
In terms of personal robotics, humans have been vain. Tesla has designed bipedal robots to make them familiar to us, despite frequent (and hilarious!) challenges to walk or run, and "fold my laundry" is a trope that's consumed 30 years of robotics engineering around tactile systems and human-oriented tasks. However, the bigger issue is not just the form of the robot, but its experience of information density if the robot is intended to actually be a human companion.
"Bicentennial Man," which we have discussed intermittently, is about the sorrow of a machine experiencing human life and then outliving its data inputs. An underrated film, and God rest Robin's soul. The central issue in robotics today is not homomorphism, it is information density. It is that information is realtime, but human lives are lossy. Look at the job recruiting process: we have grown to expect that a human life and competency can not only be summarized in a few written pages, but that we can also add software to rate the relativistic match score based on keywords that were last updated years ago, all within a system that sometimes fails to understand that SQL is the same thing as Structured Query Language.
Within Robotics specifically and within AI and datacenters, there needs to be a focus on human-input. Any personal robot MUST have the capability to query information at the speed of CPU but also must have the empathy to move at the speed of its owner. The pain of waiting isn't uniquely human; rather, it is exquisitely machine.
A machine can predict via Monte Carlo sims (or whatever) like 10 million times. But a human sometimes goes off "gut. There is no logic, it is intuition and feeling, and sometimes that gut is more accurate than 1 million simulations that any robot could have run. Thus: the robot is not actually active or available, it's in a state of decision-stasis, frozen by human decision, trapped between a 4D flat informatic plane and a 3D biological existence, and there is no escape.
The only solution, as I see it, is to engineer robots as multi-time sequencers. Robots experience data in realtime, within bandwidth limits, but localize decisions or outputs to the people they are closest to. Regarding AGI, this isn't about some Turing Test (ffs, let's update that), it is about a robot's ability to experience spacetime in the same way as a 3D-bound entity. It is about enjoying information velocity via websocket/API in equal parts as it is enjoying the depth and unsolvable puzzle of human decision-making and 3d biological time. I think of Walter Mathau in the 1990s (?) "Dennis the Menace" movie, waiting decades for a flower to bloom. Within robotics and connected compute, we must split out the data from the Pipe. The Pipe, that curated experience or human-specific perspective, is the absolute paramount. There is no higher curation than a human life that spends decades in 3D time to realize one single moment in time that flashes, blooms, and is gone. It is the bonzai of the soul and if collaborative (not AGI!) intelligence is ever achieved, this should be the bedrock.
As you know from my work on Hawking radiation, gravity fields, and the "Persist" novel generally, time and how humans experience it is top of mind for me. Let's return to our idea of local LLMs and client-owned processors and consider ways we might commercialize this for my prospective employers and customers. Happy to talk more if something I said was unclear.
// END
This is a single prompt contained in a conversation, it is only my writing and voice notes, 100% human. There is zero AI in these words, but I have indexed/sent this to a few different models that analyze and localize my random thoughts and affix them into theses that make sense to users.
Hope you enjoyed it & it was worth it. I will NOT be reposting this on Twitter.
Kyle Cyree - Principal Product Designer & Systems Architect
I build enterprise-scale data systems, zero-to-one fintech platforms, and collaborative agentic AI models.
Take a look at this site. If your traditional design partner/team or agency was building this—writing copy, creating art, designing the system, and deploying to production—how long would it take them? Two weeks? A month? A quarter? How many meetings? How many therapeutic whiskeys is that?
