CodeNSM
Sign in Get started →
[ LIVE DEMO / DEVELOPERS ]

Where time creates value

CodeNSM maps runtime health to the people shipping it: which work lands on the keystone code that carries the product, which lands on fragile or dormant code — and each developer's highest-leverage next move.

A fictional five-person team — think of them as the AI coding personas that wrote this codebase. Their portfolios are real telemetry: every function (and all its iterations) is attributed to the persona who'd own it.

This is CodeNSM watching its own codebase — live, anonymized · names-only mode Get started free → How CodeNSM works
? How to read this office roles & states, in plain English
Roles — what kind of worker each function is
Project ManagerRoutes work to the right people — controllers, views, dispatchers.
Specialist EngineerDoes the actual skilled work — computation, scoring, business rules.
Records Clerk (reads)Fetches files from the cabinets — reads from the database.
Records Clerk (writes)Files paperwork into the cabinets — writes to the database.
Security & ComplianceChecks credentials and paperwork — auth, validation, permissions.
External LiaisonTalks to the outside world — third-party APIs, webhooks, HTTP.
Comms RunnerCarries messages out — email, Slack, notifications, publishing.
TranslatorTurns one language into another — serialization, parsing, formatting.
Floor SupervisorWatches the floor — health checks, status, metrics, monitoring.
FacilitiesKeeps the office clean — cleanup, expiry, retries, flushing, logging.
AssociateVersatile hands — no dominant role signal yet.
States — how each worker is doing right now
Fithealthy Snoozingunused 14+ days Growing fatlow value, barely used Stressedslow under load Injury-proneerror rate above 5% Quiet expertrare but critical Top performercarries outsized value
gluecrafter
Backend — platform & plumbing
Auth, cleanup, monitoring, the unglamorous load-bearing walls.
99% value alignment

share of the codebase's total contribution carried by gluecrafter's functions

high-value work16%
debt-risk code2%
vanilla glue0%
297 commits 1926 lines 23078506 calls 100% reliability 0.0 avg ms
Top 3 things to work on
  1. A quarter of your commits touch code that's now dormant — check demand before building; delete what didn't land.
  2. Over half the functions you touch have no test coverage signal — add characterization tests as you go.
  3. Keep investing where you are — your work concentrates on healthy, value-bearing code.
View portfolio →
pixelmoth
Frontend engineer
Owns everything the user sees — pages, views, routing.
0% value alignment

share of the codebase's total contribution carried by pixelmoth's functions

high-value work9%
debt-risk code1%
vanilla glue0%
273 commits 3733 lines 74924 calls 100% reliability 46.5 avg ms
Top 3 things to work on
  1. A quarter of your commits touch code that's now dormant — check demand before building; delete what didn't land.
  2. Little of your work lands on the functions that carry the product's value — re-anchor your queue on the top contributors.
  3. Over half the functions you touch have no test coverage signal — add characterization tests as you go.
View portfolio →
shelfwright
Data & storage
The records room: reads, writes, migrations, cabinets.
0% value alignment

share of the codebase's total contribution carried by shelfwright's functions

high-value work11%
debt-risk code4%
vanilla glue0%
159 commits 2545 lines 36385 calls 100% reliability 2.0 avg ms
Top 3 things to work on
  1. A quarter of your commits touch code that's now dormant — check demand before building; delete what didn't land.
  2. Over half the functions you touch have no test coverage signal — add characterization tests as you go.
  3. Keep investing where you are — your work concentrates on healthy, value-bearing code.
View portfolio →
portsmith
API & integrations
Everything that talks to the outside world, in either direction.
0% value alignment

share of the codebase's total contribution carried by portsmith's functions

high-value work5%
debt-risk code7%
vanilla glue34%
92 commits 1208 lines 26254 calls 100% reliability 2.7 avg ms
Top 3 things to work on
  1. A quarter of your commits touch code that's now dormant — check demand before building; delete what didn't land.
  2. Little of your work lands on the functions that carry the product's value — re-anchor your queue on the top contributors.
  3. Over half the functions you touch have no test coverage signal — add characterization tests as you go.
View portfolio →
kernelweaver
Backend — core IP
The deep-logic specialist: scoring, engines, the defendable code.
0% value alignment

share of the codebase's total contribution carried by kernelweaver's functions

high-value work5%
debt-risk code2%
vanilla glue0%
232 commits 3120 lines 10295 calls 100% reliability 11.7 avg ms
Top 3 things to work on
  1. A quarter of your commits touch code that's now dormant — check demand before building; delete what didn't land.
  2. Little of your work lands on the functions that carry the product's value — re-anchor your queue on the top contributors.
  3. Over half the functions you touch have no test coverage signal — add characterization tests as you go.
View portfolio →

// Method: every tracked function is assigned to the fictional engineer who'd own that kind of work (frontend, core IP, plumbing, integrations, storage), then scored against its current runtime state — top performer, fragile, dormant, vanilla glue — and contribution share. Here a "commit" is a function and all its iterations. Coaching, not surveillance: it steers effort toward the code that carries the product, never a performance grade in isolation.

What unlocks with a real GitHub link: real names and commits instead of nicknames — value alignment from actual commit history, cost × value ROI quadrants (churn × iterations vs runtime value), and deterministic top-3 coaching bullets per developer. A fine-grained read-only token is all it takes.

Get started free →