AI

How they connect

ยท Intent

This is the shape the four tools are meant to make.

  fixturegen                evalset                   runlog
 ------------            ------------             ------------
 generates    --------->  grades the   --------->  shows what
 fixtures                 run against              happened,
                          those fixtures           step by step
                               |
                               |
                          skilldiff
                         ------------
                          compares two
                          versions and
                          catches drift

Read plainly: fixturegen feeds evalset, runlog shows the run, skilldiff catches drift.

Why this is labelled intent and not architecture

Because it came from a brief, not from code.

The house rule is that facts come from primary sources: code, data files, official text. Meetings, briefs and recollection are sources of intent. They tell you what someone meant to build, which is genuinely useful and completely different from what got built.

Not written yet, waiting on P-4, P-5, P-6, P-7, P-8

Any spec or shipped code for fieldpack, runlog, evalset, fixturegen or skilldiff. None was found in the calabrodesign repo or in the linked calabro-mcp pointer as of 2026-09-21. Until one exists, the diagram above is a proposal and this page says so.

Checked 2026-09-21.

What the diagram is not saying

It does not say the interfaces between these four exist. It does not say what a fixture looks like on the wire, what a grader receives, or what runlog is given to display. Those are the questions a real architecture diagram answers, and this one answers none of them.

The engineering desk has the two documents that would: the trace event schema and the fixture contract. Both are also empty, and for the same reason.

What would make this page real

  1. A spec or a shipped interface for each of the four, so each box is something rather than a name.
  2. The contract on each arrow: what crosses it, in what shape, and what happens when the shape is wrong.
  3. The failure direction. What happens to evalset when fixturegen is broken, and what runlog shows when evalset never reported.
  4. The date the shape was settled, which is the one thing a diagram almost never carries and always should.

Point three is the one that separates an architecture diagram from an org chart with arrows.