army-fanin

Fan-out is easy and increasingly commoditised. Every multi-agent flow ends at N worktrees, N diffs, one repository, and a human reconciling them in a terminal. Fan-in is where the work actually is.

What this adds that git cannot

Git supplies the diffs. It cannot tell you, for any given change:

• which agent produced it
• on which harness
• at what cost
• whether its tests passed

Without that provenance a fan-in view is git with a UI. Ship the provenance or do not ship the view.