argo-cd
23,410 artifacts read ·
180 contributors ·
5 structural dimensions
78% delivery conversion ·
2 maintainers carry 80% of closures ·
no surveys, no source code
Hidden structures in the artifact trail.
23,410 artifacts across 180 contributors. Each visualization reads from the record your organization already produces: no surveys, no interviews, no access to source code.
Creation vs. closure over 24 months.
The gap is growing. Each planning cycle starts with more unresolved work than the last.
When work happens.
Core contributor activity concentrates in UTC-5 to UTC-8 working hours. Weekend activity is minimal. This is a weekday project.
From creation to resolution.
The record the organization produces simply by working.
20 artifacts selected across state, age, and contributor concentration. Every finding ships with the artifacts behind it.
| TITLE | STATE | USER | COMMENTS | LABELS | DAYS |
|---|
Coordination failure leaves fingerprints in the vocabulary.
The verbs in the trail say which game is being played. Word choice reveals maintenance orientation and structural drift 6–18 months before any lagging indicator moves.
Term frequency across all 23,410 artifacts. Defense vocabulary (chore, bump, fix) dominates offense vocabulary (feat, add, launch).
T02 and T03 are structural drains that recur regardless of sprint prioritization. → MAINTENANCE GRAVITY
Living cluster map.
Each particle is an artifact. Circle size reflects corpus prevalence. Click a cluster to inspect term distribution. T03 carries the highest structural risk at 29% prevalence and 200–240 day average close time.
5 CLUSTERS · PARTICLE PROJECTION
TERM DISTRIBUTION
Config & Integration · Communication Sink
Linguistic Drift
→ MAINTENANCE GRAVITY“Fix, error, bump” is a team playing defense. “Add, create, ship” is a team playing offense. At 62% maintenance toil by topic weight, argo-cd is playing defense.