Layer one
Species
Each team member appears as a paired structural identity: cognitive style, what they hold under pressure, the graft they're carrying.
Apple · Pear · Lemon · Plum · Olive
Structural Team Insight · API-ready
Give your agents the human substrate they're missing.
For operational leaders running AI-native stacks whose agents need to read the team underneath the work, not just the metrics. Sociometric readings, exposed as a live API endpoint.
API access·EU-hosted·Each reading private to its team
What it reads
Your dashboards tell your agents WHAT happened. The Sociographer tells them WHO it happened to, and WHY they're showing up the way they are.
Layer one
Each team member appears as a paired structural identity: cognitive style, what they hold under pressure, the graft they're carrying.
Apple · Pear · Lemon · Plum · Olive
Layer two
The environment under which a team operates: register, pace, climate, root-depth. Sociometry of fit at the team scale.
Layer three
The sap flow of the structure under load: how much life is moving through it, and how freely. The leading-indicator signal, exposed as a stream over the API.
Stop reading the symptoms. Start reading the structure your agents have been blind to.
A sample reading
One Team Composition Reading, rendered as it ships — and as your agents will consume it via API.
Team Composition Reading
Studio Halcyon reads in three structural notes. The leadership pair is Apple–Pear — what we name the Structured People Manager. They build steady, ship weekly, and trust the brief. The integrator on the cross-product surface is a Lemon–Olive — Strategic Orchestrator, the one who names what's missing before anyone else feels it and orchestrates the cross-functional moves that follow. The design surface is held by a Plum–Lemon pair — the Innovative Expert. Five people, three structural notes.
The soil they're planted in is built around weekly delivery cycles. Density runs Dense, Layers stay Single-layer (one product surface), Roots run Deep-rooted (quarterly execution). This works for the Apple–Pear leadership; they were made for these conditions. It does not work for the Lemon–Olive Strategic Orchestrator, who needs Loose Density and Spreading Roots to reach across products and into years. Three of five members register Flourishing, one Sustaining, one Sapping with an early-signal Flow flag.
For an agent consuming this reading, the actionable substrate is two soil dimensions: Roots (currently Deep-rooted / quarterly, structurally needs Spreading / yearly visibility for the integrator) and Layers (currently Single-layer / product-bounded, structurally needs Multi-layered / cross-product framing). The fix is not a person; the fix is a 90-day adjustment to two soil dimensions for one role. Your agents can act on that — and re-poll in six weeks to verify.
Read on for the recommended polling cadence, the team-level events that should trigger a Council Reading, and the API endpoints to wire into your agent stack…
More readings, one lens — Individual, Health State, Team Composition, Evolution, and more. See the full catalog →
Your agents have read the metrics for years. They have never read the structure underneath them.
From the Mycelium · on what agents have been missing
From the field
Existing tools measure the WHO, not the WHAT and WHY. That's the gap.
Thibault Werbrouck · Diagnostic recruiter · debrief, 25 March 2026