A note about this build log entry: I published this after the week it covers. DevNitro reconstructed a draft from work-related entries in my journal, Git commit history, and time tracking. I reviewed, edited, and approved the final post. The story reflects what I knew and built at the time.

From the Backlog to the Build Log

Week of May 22 - May 28, 2026

What I Worked On

Here is the line I keep coming back to: your developers have AI, but your organization does not. A single agent has no sense of what your company cares about. This week I started giving it one.

I built a Persona system. Personas are additive lenses that shape how the agent reasons, things like Security, CTO, CEO, and a Challenger that argues against the plan. They do not override sound engineering, they add perspective. A security lens makes the agent notice a leaked secret. A CTO lens makes it think about on-call burden. And they are governed: personas are set by company, team, and project policy and inherit down the hierarchy, so the agent cannot simply decide to ignore the security lens your organization turned on.

On top of that, I built an Advisory Board. For a high-stakes decision, it spawns a sub-agent for each enabled persona, lets them evaluate independently or debate, and then synthesizes a recommendation. It is a board meeting for a decision, run in parallel by the platform. Fittingly, I tracked the whole thing as its own issue (DN1477) and had DevNitro help build it.

None of that would hold together without the other big piece of the week: a major resolution refactor. I unified how everything resolves through the org, team, project, and user hierarchy, AI providers and models, memories, agents, skills, commands, git settings, blueprints, and now personas, all through one scope system with ancestor-aware enablement and a shared ScopeHelper. This is the closest thing yet to an org chart for the AI: what it knows and how it decides depends on where in your organization the work sits. It is the natural extension of the organizational memory and roles work from earlier this year.

What the AI Did Well

The scope refactor touched nearly every subsystem, and the agent carried it with tests: persona resolution by project, inherited-persona filtering by parent scope, and auto-opt-out when a provider or blueprint is re-enabled. It also built full-text conversation search across the API, CLI, and UI, with auto-generated conversation summaries so search actually returns something readable, and a CommitGuard skill that checks a change before it is committed.

What Needed Correction

Governance is where the bugs hide. The first cut of the create-and-edit pages for skills, commands, and agents only allowed company scope, when the whole point was to scope them to a team, a project, or a user. The persona modal and the system persona catalog both had resolution bugs where the right personas would not show up. And the Advisory Board needed operational tuning. This was needed because it runs a sub-agent per persona, it is genuinely slow, so I had to move it to the long-running tools and give it a fifteen-minute timeout instead of letting it look like a hang.

I also added a regression skill: when the agent finishes a feature, it can generate integration tests that protect that feature from future breakage. Teaching it to leave tests behind is how you keep speed from turning into fragility.

What Shipped

DevNitro has additive personas as always-on lenses, governed by company, team, and project policy, and an Advisory Board that convenes a sub-agent per persona and synthesizes a recommendation. A unified resolution system routes providers, models, memories, agents, skills, commands, git settings, blueprints, and personas through the org hierarchy. There is full-text conversation search with auto summaries, a CommitGuard skill, and a regression-test skill.

The Numbers

Category Hours
Product / Features 44h 34m
Content 7h 23m
Community 2h 49m
Testing 2h 26m
Business 2h 11m
Deploy / Infra 0h 27m
Total 59h 50m

Almost forty-five hours of product, most of it split between personas and the resolution refactor. Those two are really one idea: the organization, not just the individual, should shape what the AI does.

An individual with AI keeps all the context and judgment in their own head. An organization with AI encodes its priorities so every agent inherits them. Personas and an advisory board, governed by your hierarchy, are how DevNitro gives your company a voice in the work. That is the difference Intelligent Engineering is built to make.

Curious how this site was built?
Watch the 5-minute walkthrough at devnitro.com →

An AI built this blog (but not this post)

This entire blog system (domain models, database, services, UI, auth, etc.) was built by DevNitro on its own in 95 minutes. I recorded every second.

    We respect your privacy. Unsubscribe at any time.

    Built with Kit