# How these fit together

Source: https://sonpiaz.com/stack

Updated: 2026-09-12

Five products that are really one loop. Agents run in Mandeck, call Kyma for models, build things that need distribution, and Build to Own teaches the whole circuit.

There are more projects on this site than one person should have. The reason is
not ambition. Each one started as a problem inside the one before it, and the
shortest way to describe the whole set is as a loop rather than a list.

## The loop

<figure class="diagram">
<svg viewBox="0 0 420 660" role="img" aria-label="Five products arranged as a loop: Build to Own teaches builders, who run agents in Mandeck, which call Kyma API for models, which produce things that need distribution through Affitor and open-affiliate, and what works becomes the Build to Own syllabus." xmlns="http://www.w3.org/2000/svg" style="max-width:100%;height:auto">
  <defs>
    <marker id="ar" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
      <path d="M0,1 L9,5 L0,9 z" fill="currentColor"/>
    </marker>
    <marker id="ar-a" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
      <path d="M0,1 L9,5 L0,9 z" fill="#4f8ef7"/>
    </marker>
  </defs>
  <g fill="none" stroke="currentColor" stroke-width="1.25">
    <rect x="80" y="20"  width="260" height="56" rx="4"/>
    <rect x="80" y="148" width="260" height="56" rx="4"/>
    <rect x="80" y="276" width="260" height="56" rx="4"/>
    <rect x="80" y="404" width="260" height="56" rx="4"/>
    <rect x="80" y="532" width="260" height="56" rx="4"/>
    <line x1="210" y1="76"  x2="210" y2="144" marker-end="url(#ar)"/>
    <line x1="210" y1="204" x2="210" y2="272" marker-end="url(#ar)"/>
    <line x1="210" y1="332" x2="210" y2="400" marker-end="url(#ar)"/>
    <line x1="210" y1="460" x2="210" y2="528" marker-end="url(#ar)"/>
    <path d="M80,560 L30,560 L30,48 L76,48" stroke="#4f8ef7" marker-end="url(#ar-a)"/>
  </g>
  <g fill="currentColor" font-family="ui-sans-serif, system-ui, sans-serif">
    <text x="96" y="44"  font-size="13" font-weight="600">Build to Own</text>
    <text x="96" y="62"  font-size="11" opacity="0.6">teaches the whole circuit</text>
    <text x="96" y="172" font-size="13" font-weight="600">Mandeck</text>
    <text x="96" y="190" font-size="11" opacity="0.6">the room the agents run in</text>
    <text x="96" y="300" font-size="13" font-weight="600">Kyma API</text>
    <text x="96" y="318" font-size="11" opacity="0.6">one key, a hundred models</text>
    <text x="96" y="428" font-size="13" font-weight="600">What gets built</text>
    <text x="96" y="446" font-size="11" opacity="0.6">watch-cli, Haynoi, Pheme, Kapt</text>
    <text x="96" y="556" font-size="13" font-weight="600">Affitor, open-affiliate</text>
    <text x="96" y="574" font-size="11" opacity="0.6">tracking, terms, payouts</text>
    <text x="222" y="114" font-size="11" opacity="0.75">graduates run agents</text>
    <text x="222" y="242" font-size="11" opacity="0.75">calls for models</text>
    <text x="222" y="370" font-size="11" opacity="0.75">returns answers</text>
    <text x="222" y="498" font-size="11" opacity="0.75">needs distribution</text>
    <text x="38" y="606" font-size="11" fill="#4f8ef7">what works becomes the syllabus</text>
  </g>
</svg>
<figcaption>People enter through the program and leave running the stack. The blue arrow is what makes it a loop.</figcaption>
</figure>

**1. Learn the circuit.** [Build to Own](/projects/build-to-own) takes a builder from a real problem to a paid product in four weeks.

**2. Run the agents.** [Mandeck](/projects/mandeck) holds many coding agents on one screen and lets them hand work to each other.

**3. Call the models.** [Kyma API](/projects/kyma) gives those agents one key for a hundred models, with uptime you can check.

**4. Build something.** The side projects came out of this step: [watch-cli](/projects/watch-cli), [Haynoi](/projects/haynoi), [Pheme](/projects/pheme), [Kapt](/projects/kapt).

**5. Reach people.** [Affitor](/projects/affitor) tracks and pays partners, [open-affiliate](/projects/open-affiliate) publishes the terms, [affiliate-skills](/projects/affiliate-skills) gives an agent the playbook. What works goes back into the syllabus.

## Where the loop is weak

Step 3 is the weak link, and pretending otherwise would make this page useless.
A two sided market is hard to start from the middle, and the open source pieces
around it get plenty of attention without converting it: affiliate-skills is the
most starred thing I have written and still does not turn many readers into users.

Steps 1, 2 and 4 hold. Agents run, models answer, and the first cohort finished
with real work handed in. Step 3 gets solved by someone using the other four,
not by rebuilding the middleman.

## Why this matters if you only read one page

Every product here is the answer to a question the previous one asked. That is
worth more than any of them individually, because it means the tools are tested
by each other every day rather than by a demo.