Trust, but verify — this week the portal takes the second half seriously. Certifications get public verification pages you can share anywhere, Velocity opens with a diagnosis instead of a wall of charts, per-person numbers stop under-counting, and every model request can be traced to the session behind it. Let's get into it!
Certifications you can verify publicly
Every earned certification now has a public verification page. Open the Break Room, pick a credential, and share the link — anyone who opens it sees who earned it, what it covers, and whether it's still current, no Codiedev account required.
Until now, certifications lived and died inside the portal. Pass one and a badge appeared for you; anyone else had to take your word for it, and a lapsed credential looked the same as a live one.
There's nothing to migrate. Engineers certified before this shipped receive their verifiable credential automatically, and renewal and expiration status now shows alongside each credential in the Break Room.
Velocity opens with the diagnosis
The Velocity tab now opens with a delivery summary: throughput, bottlenecks, trend direction, and how much review work is aging out. Below it, the guidance gets specific — which stage of delivery is slowing the team down, who to unblock, and what to do about it.
Until now, Velocity handed you the charts and left the reading to you. Slow delivery rarely announces itself in a single graph: the signal is spread across coding time, review tail, and merge lag. The new view does that reading for you and leads with the conclusion.
Per-person numbers you can trust
Team and review metrics now include developers whose git account was never linked to Codiedev. The link is derived from the work itself — the branches and merges a developer's sessions touch — so per-person numbers stop under-counting real contributions. Nothing to configure.
Counting the right people matters as much as counting them fully. When someone genuinely shouldn't be in engineering stats — a bot account, a contractor — you can now exclude them right from their activity page, with an audit trail of who changed it and when. Putting someone back asks for the same confirmation.
Trace any request to the work behind it
Select any request in Models → Usage to open the session behind it: who ran it, every call it made, what shipped from it, and the session summary.
Until now, a usage line was a dead end — a model, a token count, a cost, and no way to answer "what was this for?" Now the receipt connects to the work, so cost review stops being archaeology. Sessions that span several branches and pull requests show all of them, not a best guess.
That's the week. See you in the next one.