← The Apprenticeship

Guided tour · toward design-technology & AI-product roles

Engineering for designers

Engineering concepts for designers — how Koher’s tools are actually built, explained for people who design rather than engineer. The three-layer architecture and the code that carries the judgement, enough of the making to build and prototype an AI tool yourself. Leads toward design-technology, creative-technologist and AI-product roles.

A curated path — each step points at the exact passage, not just a page. Read it in order, or wander. Links open in a new tab so the map stays put.

1. The one commitment

   Everything the architecture serves, in a single page: keep a real outside in the room.

   →Why Koher exists

2. The three-layer architecture

   Qualification, rules, language — what each layer does, and what it must not do. This is the shape you would build inside.

   →Architecture — The Separation

3. Judgement lives in code

   Why the consequential judgement is deterministic code anyone can read, not a model’s verdict.

   →Keep a Real Outside — The two disciplines

4. Why the split is provable

   The engineering rationale — evaluation cannot be outsourced to the thing being evaluated.

   →The Proof of Hallucination — Architectural Implication

5. The architecture, shipped

   The tools where this already runs — read the code, pull back the curtain on a live one.

   →Open tools & demos

6. Do more with less

   The engineering ethic: small models doing remarkable things on constrained hardware.

   →Values — Doing More With Less

7. What you would release

   How the code goes out — MIT for the first three, AGPL after. The repositories you would contribute to.

   →Open Source & Licensing — The Split

8. The facet you would own

   UI components, SDC verification flows, or output novelties — a real, credited part of a live build.

   →Back to the apprenticeship