Solutions
Ideas packaged around real problems with working implementations, from prompt systems to browser-native AI.
AI is becoming part of the interface between people, software and information. AIBussin is where I build and test practical systems around that shift — then write down what survives contact with reality.
AIBussin is not primarily a news blog or a tutorial feed. It is the place where practical AI ideas are developed into working systems, reusable solutions, experiments, technical books, tools, prompts and articles — with each form feeding the others.
Ideas packaged around real problems with working implementations, from prompt systems to browser-native AI.
Long-form, first-principles treatments of agents, context, memory, language, retrieval and AI engineering.
Interactive applications — prompt libraries, builders and working sessions — for doing the work, not just reading about it.
Experiments, technical notes and ongoing explorations that support the larger systems and books.
Not every project follows a rigid process, but a recurring pattern connects most of the work here: prototype an idea, test it against reality, keep what the evidence supports, and turn the durable result into something other people can use.
Start from a precise question about how an AI mechanism behaves, not from a tool looking for a use.
Prototype with code, measure what happens, and revise. Failures are recorded, not hidden.
Turn what works into a working system with explicit state, boundaries and observable behavior.
Publish the durable result in the form that fits: a solution page, a book chapter, or a tool.
The books work through difficult subjects — agents, context, memory, language, embeddings, browser AI, debugging — from first principles. Each one is developed alongside the experiments and systems it describes.
Engineering Intelligence Into a Reliable Process
How does model intelligence become reliable engineering?
Build from a callable model to explicit context, durable state, controlled actions, independent verification, and a deterministic runtime that decides what happens next.
Read the book →
What happens when the browser itself becomes the AI runtime?
Build browser-native AI from the capability boundary upward: local models, observability, WebMCP tools, agent security, and a user-owned browser policy engine.
Read the book →Solutions are the differentiator of this site: each one connects a real problem to its mechanism, implementation and supporting evidence.
Start from the depth you need, then move between explanation and application.
AIBussin is part of a small ecosystem of independent sites. They overlap deliberately — each exists because it answers a different question.
Open the solution library for something usable today, or a book for the full mechanism behind it.