Command

`okulo coordination`

See which people and teams touch the same components — coordination pressure.

teamsno-blame

When to use it

Too many cooks on one module, or you want cross-team coupling without running blame.

Usage

okulo coordination [repo] [options]

Options

Option	Default	Description
`-w, --window`	12m	Activity window
`--components A,B`	all	Limit to components
`--component-depth N`	1	Folder depth without layers

Examples

Where collaboration concentrates

okulo coordination
okulo coordination --components backend

Sample output

Illustrative terminal output (column layout matches the real CLI):

Coordination  who changes each component in the window (by churn)
component  revs  authors  author frag  top contributors
─────────  ────  ───────  ───────────  ────────────────────────────────
backend     379        8         0.72  Ada 34%, Grace 18%, Alan 12%
frontend    268        6         0.61  Grace 41%, Ada 22%
infra        40        2         0.20  Ada 88%, DevOps Bot excluded

Teams (from .okulo.toml)
team pair             shared components
────────────────────  ─────────────────
Platform ↔ Product                  2

How to read it

authors / author frag — how many people touch the component and how split the churn is. High authors + high frag ⇒ coordination cost.
top contributors — who to invite to design reviews for that area.
With [teams] configured, shared components between teams highlight cross-team coupling.

Tips

Does not need git blame, so it is relatively fast on large repos.
Pair with architecture layers for readable component names.

okulo coordination