Work intelligence that classifies what you actually do (innovation, maintenance, glue, tech-debt, firefighting), so you can see your trajectory, your automation risk, and the skills worth growing into.
Productivity looks fine until you ask what kind of work got done, and who is being automated out of a job they still appear busy in.
Sign in with GitHub. Read-only, scoped to repositories you choose. Nothing leaves the pipeline and nothing trains a model. More sources come next: Linear, Jira, Slack, calendar.
Every commit, PR, and review is classified semantically (innovation, maintenance, glue, tech-debt, firefighting) with a confidence score and a one-sentence rationale you can audit.
Watch your mix change over weeks. See automation risk on specific kinds of work. Get suggested skill shifts grounded in what you already do well, not a generic career map.
Two views of the same data. Different incentives. Zero leakage from the personal to the team side.
Your work mix over weeks and months. See whether you're drifting toward maintenance or deepening in new capability, before anyone else notices.
A rolling score grounded in template density, novelty, and cross-module coupling. Specific patterns flagged, not vibes, so you can act on them.
Career moves rooted in what you already do well, not a generic map. If you review a lot of infra PRs, that's signal, and we tell you where to point it.
These are not tactics. They shape every design decision and every feature we refuse.
Your data lands in your view before anyone else's. The personal dashboard is the product; team views are an aggregation on top, never the other way around.
No individual rankings visible to managers. No top-performer lists. Teams see distributions, not names, by design, not by policy toggle.
Classification reads the actual work (diffs, messages, PR descriptions) and explains itself. We do not trust Jira labels to describe reality.
Reviews, mentoring, design docs, unblocking. First-class contributions, not footnotes. The threads that hold teams together deserve to show up in the weave.
Software commits are the densest, most structured signal of knowledge work, which makes engineering the right place to prove the method. The same classification layer maps cleanly onto product, design, analytics, and operations.