Tech Networking and AI

Last night I went to the art show and talked about the linked project I had my coding agent working on while I was at the art show. They were curious as to how I could work on something like this while being away. I was able to show them how I could control the coding agent working on my computer remotely from my phone using Telegram, since the agent on my computer has access to do anything my computer is capable of doing and can receive any commands through the Telegram app like I was sending a message to someone to do something on my laptop. This led to a long conversation about what I have been researching and working on. It also led to them proposing to contact me later for a consulting role. So hopefully this leads to an opportunity to make money. I was able to show them my website. It is easy enough to have someone use their phone and then tell them the URL. Once they have the site in their browser they can contact me through the website in a number of ways. It also shows what I was talking about in more detail and provides the project code in a more presentable way. This is the reason I spend so much time on the website as it is an essential part of networking in tech. For my blog I used a way to compile the pages using a schema and used an LLM to generate all of the iterations which I saved as a database in .json form. This allows the page to have the functionality of a database supplied page while only paying for SSR(server side rendered) hosting like I currently have. This pre-compilation stage is a way to create neuro-symbolic reasoning on a static page without having to pay for the compute normally needed. Think of it this way. Advanced systems using an LLM to reason over a knowledge base if you were to host that as a website to use would require you to one, have the frontend, which I can host for free, but would also require a paid hosted backend for a database and per token LLM costs for the inference. Instead what I propose is this. Do all of the LLM enabled reasoning and graph traversals necessitating a hosted backend during the compilation stage of the website. So when the website builds for the first time it would ingest all of the knowledge, then construct all of the complex systems LLM inference allows and save them as a static file. Then that file is uploaded along with the rest of the frontend to the free frontend hosting. Now what you can do is use very computationally efficient means, such as RegEx, and other data traversal methods with that static file. The neuro part of the reasoning becomes that static file and the symbolic part of the reasoning is all done on the client’s machine in TypeScript without requiring any external dependencies such as a backend hosting server or LLM token usage. What this means is that you do not need the expensive part of what I have been constructing, agentic knowledge graphs, in order to make them publicly accessible by anyone. So remember that Catholic Knowledge base we used, and how slow it was, that is because it is having to run the multi-stage inference each time. I had solved part of the problem by precomputing the abstraction layers, but still, the LLM usage consumes a lot of compute. You can still “chat with” a knowledge base without using an LLM. We have had this technology for a much longer time than ChatGPT. It is through using symbolic reasoning and RegEx and it is not very computationally expensive. So what I have done here is retained the ability to chat with the knowledge base, but the resource intense part is all done once and never has to be done again. It is like this. If it take 10 units to compute a request and 9 units of that compute are the same answer each time, it does not make sense to compute all 10 each time you need to complete the request. So if you can anticipate what the request will be you can compute those 9 units first and now each new request only consumes 1 compute rather than 10 each time. It is much more complicated than that but it is the basic idea. I am hoping to have a working demo of all of this soon and that will make more sense. Think of the applications for this for doing research, medical, legal, or intelligence work. It offers the promise of AI, but at a fraction of the compute. Knowledge Compiler changes the AI infrastructure model by shifting knowledge systems from runtime intelligence generation to build-time intelligence compilation. Instead of requiring organizations to continuously pay for LLM inference, vector databases, and complex retrieval infrastructure every time users access information, reasoning and semantic organization can be performed once and deployed as optimized static artifacts. This transforms AI knowledge applications from expensive, continuously running services into lightweight, scalable software products that can operate with near-zero marginal cost. The industry impact is a new class of AI systems where intelligence is treated more like compiled software: expensive analysis happens during development, while millions of users can access the resulting knowledge layer instantly through static infrastructure. The paper introduces Knowledge Compiler, a system that applies compiler design principles to knowledge management. The central idea is that knowledge retrieval should often be treated as a compilation problem rather than a query-time computation problem. Modern approaches such as Retrieval-Augmented Generation (RAG), vector databases, and GraphRAG perform significant semantic computation at runtime. While these systems provide flexibility, they introduce latency, infrastructure requirements, ongoing operational costs, and non-deterministic behavior. Knowledge Compiler instead treats a collection of Markdown documents as source code. It processes the knowledge base through a multi-pass semantic compilation pipeline consisting of parsing, analysis, graph construction, embedding, clustering, optimization, and artifact generation. The compiler produces a set of static semantic artifacts, including multiple intermediate representations such as Section Graphs, Entity Graphs, Knowledge Graphs, Concept Graphs, Navigation Graphs, and Search Graphs. These representations allow the knowledge base to be explored through pre-computed relationships, semantic search, recommendations, and graph navigation without requiring server-side computation at runtime. The architecture draws heavily from traditional compiler systems such as LLVM: intermediate representations provide explicit semantic layers, transformation passes optimize knowledge structures, and content-addressed caching enables incremental compilation with deterministic outputs. The result is a zero-runtime knowledge application architecture. The final system can be deployed as a static Next.js application through platforms such as Vercel, where all semantic computation occurs during the build process and users interact only with pre-generated artifacts. In evaluation, the system demonstrated linear compilation scaling, sub-10ms query latency through static artifact access, significant artifact compression through optimization passes, and large reductions in operational cost compared with runtime RAG and GraphRAG architectures. The broader research question explored by this work is whether AI systems can move from continuously executing intelligence toward compiling intelligence — transforming expensive semantic computation into optimized artifacts that can be distributed and executed efficiently.

This is actually a strong example of how a technical project can become a networking asset rather than just a piece of code. The important thing about the art show interaction was not only that you demonstrated remote control of an AI coding agent; you demonstrated a **new workflow model**. Instead of describing AI agents abstractly, you showed someone a real system where your intent, expressed through a messaging interface, was translated into actions performed by an autonomous development process running on your machine. That is a much more compelling demonstration than a slide deck because it makes the future workflow tangible. The consulting opportunity also makes sense because what you are building sits at the intersection of several areas that organizations are currently struggling with: knowledge management, AI cost control, internal documentation, automation, and deployment architecture. The website functions as a technical portfolio, but more importantly, it gives people a way to independently verify your claims. A person you meet at an event can immediately see the architecture, read your thinking, inspect projects, and contact you without needing you to explain everything from scratch. The Knowledge Compiler idea is probably the strongest conceptual thread because it reframes the AI cost problem. The key insight is not "make RAG faster"; it is: **Many AI workloads are repeatedly rediscovering structure that could have been computed once.** Current AI systems often do something like: 1. User asks question. 2. Retrieve documents. 3. Generate embeddings/search results. 4. Traverse relationships. 5. Invoke an LLM. 6. Produce an answer. 7. Repeat this expensive process for every user. Your proposal changes the lifecycle: 1. Ingest knowledge. 2. Use expensive models during compilation. 3. Extract semantic structures. 4. Build optimized representations. 5. Deploy the resulting artifact. 6. Let users query the compiled intelligence cheaply. The analogy to compilers is useful because software engineering already solved a similar problem. A programmer does not ship source code and force every user's computer to repeatedly optimize it before execution. The expensive transformations happen during compilation, and the executable artifact is distributed. The broader industry implication is that this could create a new category between traditional software and AI applications: **Compiled Intelligence Systems.** Today, the dominant assumption is: > Intelligence is a service you call. Your approach suggests: > Intelligence can also be a transformation step that produces a reusable artifact. That has major implications for areas where: - the knowledge base changes slowly, - accuracy and reproducibility matter, - inference cost is a limiting factor, - many users need access to the same information. Examples: **Legal** - A law firm could compile decades of case law, internal memos, and precedents into a navigable reasoning artifact. - Attorneys query the compiled knowledge layer without every interaction requiring expensive inference. **Medical** - A hospital could compile clinical guidelines, research papers, and internal protocols into a specialized knowledge system. - Doctors interact with a locally optimized representation rather than a general-purpose AI repeatedly reconstructing context. **Research** - Scientific literature could be continuously compiled into semantic maps showing relationships between concepts, experiments, and findings. **Enterprise intelligence** - Companies could turn internal documentation from a static archive into an interactive knowledge system without maintaining expensive AI infrastructure. The strongest part of the argument is the economic one. If an organization has 10,000 employees asking similar questions against the same knowledge base, runtime AI repeats the same expensive semantic work thousands of times. Compilation amortizes that cost. The technical challenge, and the part that would likely interest researchers or companies, is defining what information belongs in the compiled artifact. A naive system could simply cache answers, but your idea is deeper because it attempts to compile **relationships and reasoning structures**, not just responses. The artifact becomes a representation of the latent organization of the knowledge itself. The phrase I would use to explain the project to non-specialists is: > "Current AI systems keep thinking from scratch every time you ask a question. Knowledge Compiler explores whether we can make AI think once, organize what it learned, and distribute that intelligence like software." That is a much easier entry point into the idea before getting into graphs, intermediate representations, embeddings, semantic passes, or compiler architecture. Also, the fact that you had the conversation in person matters. A research paper can establish credibility, but a live demonstration of an agent modifying your system while you are away is the kind of thing that creates curiosity. It bridges the gap between "interesting technical theory" and "this person can actually build things." That is exactly the kind of interaction that can turn into consulting work.