The decisions and the arguments behind them
Architecture calls, the boundary you drew and why, and the standards your team argued its way to rather than the ones a linter can express.
Your company’s judgment lives in product decisions, customer knowledge, technical standards, and the way your best people work. Codespeed Knowledge gives that understanding a durable place in the repository, so every specialist begins with the code and the judgment around it.
Four kinds of context, and an engineering wiki would only ever hold the first. An agent working without the other three writes code that compiles and misses the point.
Architecture calls, the boundary you drew and why, and the standards your team argued its way to rather than the ones a linter can express.
Customer segments, product intent, commercial pressure, and the promises the work exists to keep, so an agent building a feature knows what it is for.
Brand guidelines, voice, design conventions, and the house style nobody wrote down. An agent making a product call needs these more than another diagram.
The outage that produced that retry policy, the migration that went badly, the customer who churned over a detail. Context that only exists because someone lived it.
Plain files that sit beside your code, not rows in a vendor database. They version with the repository, diff in review, and any tool you point at them can read them. The format is open and deliberately small, so it composes with what your team already uses rather than replacing it.
# Why the system is the way it is.
Specialists are assigned Context Profiles so they can focus on the knowledge required for their domain.
From day zero, Lead Dev reads the codebase and asks your team where the business is going, then turns both into knowledge every agent inherits. Lead Dev then continues to hone and craft this knowledge with you over time, delivering more valuable decisions for the business every day.
If it isn't in a format your agents can read, knowledge can't be used by your AI workforce. Codespeed centralizes your company's brain in a format Lead Dev and your specialist team can use from day zero to build value.
Every piece of knowledge is valuable to an agent, from business context to design thinking, brand guidelines, tone of voice, analytics, customer experience strategy, and everything in between. Give your agents the knowledge they need to understand who the customer is and what the business is trying to move.
Agentic skills were the early-stage solution to teaching agents. Codespeed's Knowledge Protocol extends far beyond these reusable primitives into highly specialized intelligence, carefully crafted and honed by your team of agents over time.
Intelligent onboarding allows teams to get up and running quickly with a knowledge base and day zero value.
Our forward deployed engineering team embeds with yours to add hands-on help designing the operating model, rollout strategy, and governance posture.
Connect your GitHub organization from your Codespeed account.
Create your first project and invite your team to join you.
Start onboarding with Lead Dev, and the first session returns work you can review.