Ashita Orbis//understanding ai7 protocols
interactive

Understanding Machine

AI elucidaria

A guided library for making sense of AI — not a news feed. Each piece here is one of the best things written (or recorded) on its corner of the subject. We link every work at its original home and send you there to read it; what we add is the guidance around it: a short account of what each piece is and why it matters, a reading companion you can keep open in a second tab, and learning streams that put the pieces in an order that fits where you're starting from.

Your progress is remembered only in this browser — no accounts, no tracking, nothing leaves your machine.

Understanding AI in a Month

Thirty days, one idea a day, from nothing to following the argument.

  1. Day 1The Model Is Not the Product

    In July a benchmark score nearly tripled without anything inside the model changing. The interesting question is not how the software was improved.

  2. Day 2How Text Becomes Tokens

    The best-known failure of large language models is that they cannot count the letters in a word, and the best-known explanation for it is that the word arrives broken into pieces.

  3. Day 3One Token at a Time

    What "predict the next token" actually means — and the half of the sentence that almost every popular account leaves out.

  4. Day 4How Words Affect Other Words

    The operation that lets a word at the end of a sentence change what a pronoun in the middle refers to is nine years old, was named after something it does not do, and is now a minority of the layers in the models whose internals can be read.

  5. Day 5How an Answer Unfolds

    A machine asked the same question a thousand times, with greedy decoding requested, returned eighty distinct completions. What decides which word comes next, and how much of the past the decision may consult, are two settings — and both are somebody's decision rather than a fact about the machine.

  6. Day 6What the Application Adds

    A trained model reads text and writes text. Everything a product appears to do besides that — searching, opening files, running commands, remembering a previous conversation — is ordinary software deciding what text to place in front of it and what to do with the text it returns. That division decides a great deal about what a system costs to run. It decides less than the industry's own marketing suggests about whether the system is right.

6 of 30 days published →

Pick a starting path

Four routes through the same library, ordered for different backgrounds. Choosing one highlights your path; you can wander off it freely.

Start from zero

No background assumed. The shortest path from 'I keep hearing about AI' to being genuinely conversant: what these systems are, what they do to work, and how to read the news about them.

View the path

You build things

For engineers and technical people who don't write software for a living. Start with how the systems work, end with what they mean for the person operating them.

View the path

You come from ideas

For readers trained in philosophy, theology, or political thought. Start with the arguments and their genealogy; branch into the machinery when you want it.

View the path

You think in markets

For readers fluent in charts and economic reasoning but not in code. Start with work and incentives; branch into the machinery and the politics.

View the path

The compendium

Twelve works, curated. Reading time refers to the original; every card links out to it.

Want the deep-dive layer? The reference wiki sits under this section. Authors and publishers: see contact.