Enji GuardGovern the debt AI leaves in your team's understanding
The dangerous debt is not only in the code, it is in the gap between code that runs and people who understand why. Guard gives engineering leaders recurring visibility into all three kinds of debt.
1 repo · setup in about 5 minutes · no card, no commitment
01
Three kinds of debt, not one
Technical debt is code that is hard to change. Cognitive debt is a codebase nobody fully understands. Intent debt is lost knowledge of why something was built the way it was. Architecture drift appears when the code keeps moving but that shared understanding does not. AI accelerates all of it, and only the first piece shows up in most tools.
02
Why AI makes cognitive debt worse
When an agent writes a module in seconds, no engineer carries its design in their head. The code exists, but the understanding never formed. Multiply that across a codebase and every change starts needing a careful, expensive human re-discovery.
03
Governance through recurring audits
Technical debt governance only works when the debt is visible. Guard makes the invisible measurable for the people accountable for it:
- Where understanding is thin and risk concentrates
- Modules changing often that nobody clearly owns
- Missing context that keeps agents from working safely
- Debt trends over time, not a single snapshot
04
Keep the repo legible to humans and agents
Guard turns findings into reviewable issues and helps keep agent docs current, so understanding is rebuilt as the code changes, not lost with every fast commit. Leadership gets a defensible view of where the risk actually is.
Quick questions
Is this just technical debt with a fancier name?
No. Technical debt is code that is hard to change. Cognitive and intent debt are about lost understanding of how the system works and why it was built that way, which compiles fine and most tools never see.
How do you measure something as fuzzy as lost understanding?
Through proxies: where understanding is thin, modules nobody clearly owns, complexity that keeps rising, and how all of it trends, rather than a single number.
Does it help capture architecture decisions, like ADRs?
Yes. Guard is built to spot where the why behind the code has gone missing or stale, including architecture decision records and the context around them. As cognitive-debt governance ships, those gaps become reviewable issues or doc updates instead of living only in someone's head.
Who is this page for?
Engineering leaders accountable for a codebase they no longer fully see. Guard makes drift and lost context visible enough to discuss, prioritize, and turn into reviewable follow-up work.
Get visibility into the debt that hides.
Connect a repo and get your first governance report in a few minutes. No card.