Solutions

Solutions

Start with a real AI problem. Follow it through the mechanism, evidence, capstone implementation and inspectable code to a solution you can actually use.

Programmer.ie solutions are the practical destination of the research, books and experiments.

A book should not end at explanation. Each finished book is expected to lead to a solution: a durable page organised around a real problem, a concrete outcome and an implementation that can be inspected. The book earns the mechanism, the capstone integrates it, and the solution becomes the applied home for the work.

The publishing loop

    flowchart LR
    R[Research] --> B[Book]
    B --> C[Capstone]
    C --> S[Solution]
    S --> G[Repository]
    G --> U[Real use]
    U --> E[New evidence]
    E --> R
  

A solution can also begin somewhere else. A strong blog post, experiment or engineering investigation can grow into a solution when it becomes comprehensive enough to answer the problem rather than merely discuss it. The solution page then becomes the canonical home, while supporting posts provide narrower entry points into it.

How to use this page

  1. Start with the problem Browse the solutions below by domain or featured project.

  2. Understand the mechanism Each solution connects back to the book, experiment, or underlying technical argument.

  3. Inspect the implementation A real solution leads to code, experiments, tools, or a live system.

What a solution is

A solution on Programmer.ie is not just an article and not just a repository.

It is the place where:

  • a real problem is named clearly,
  • the mechanism is explained properly,
  • the capstone implementation is gathered,
  • the code or live system is linked,
  • and the result can be inspected, tested or used.

Every mature solution should make five things easy to find:

  1. The problem — what is failing, missing or unnecessarily difficult?
  2. The mechanism — what technical idea actually determines the outcome?
  3. The evidence — what measurements, experiments or source material justify the design?
  4. The implementation — what capstone, repository or repository path embodies the answer?
  5. The operating boundary — what the solution does, does not do and how you can tell whether it is working.

Some solutions below are live systems. Some are being built directly from current books. Others will appear as the library grows. The goal is not to manufacture a product for every chapter. It is to make sure important technical work eventually terminates in something concrete that can be built, tested, inspected or used.

Plugin Live

OpenCode Remembering

OpenCode Remembering is the working application behind Memory From First Principles: a standalone plugin and bundled memory engine that turns project history into controlled, provenance-bearing context without treating everything retrieved from the past as permission to act.

View solution →
System Live

ZeroModel

ZeroModel is a working system for building AI decision flows that preserve enough structure to inspect what was claimed, what evidence supported it, what policy allowed it and what actually happened.

View solution →
Runtime Live

RELATE

RELATE is the capstone system for Embeddings From First Principles: a small runtime, corpus, benchmark suite, and evidence ledger for asking what an embedding space preserves before a system is allowed to use it.

View solution →
Runtime Live

CodeAI

CodeAI is the capstone system for Applied AI: an experimental runtime that treats models as replaceable cognitive components while the surrounding software owns state, evidence, authority, side effects, verification, completion, and what happens next.

View solution →
System Live

AIbussin / Freestyle Cognition

AIbussin turns the Freestyle Cognition research into practical workflows, prompt builders and interactive tools that help people explore, reframe and develop ideas with AI.

View solution →
System Reference

Self-Improving Engineering Program

The DSPy From First Principles capstone: a bounded repository-repair system where the model proposes diagnoses and patches, while software controls tools, validation, holdout evidence, comparison and promotion.

View solution →
Workflow Reference

Pi Patch Desk

Pi Patch Desk is the runnable capstone for Pi Agents: Building on the Coding Agent. Scripted responses drive the actual Pi loop against a disposable TypeScript fixture, while the host checks the patch and records the evidence for your review.

View solution →
Tool Building

Digital Lens

Digital Lens is the Browser AI capstone direction: a browser-native assistant that helps the user control attention and information flow instead of surrendering those decisions to each website or AI provider.

View solution →
Component Reference

Ollama Python Tool Calling

A minimal local tool-calling loop for Ollama: register Python functions, pass schemas to the model, execute selected calls, and feed tool results back into chat.

View solution →