AI has raised the ceiling on how fast good teams can ship. Reaching it takes scaffolding: practices that let people and agents work together, grounding that stops agents guessing, and gates that prove what reaches production. Dendro Logic builds that scaffolding, starting from your business goals and measuring every step.
01 · What we do
Most agent mistakes are guesses about code the agent never read. We build team knowledge bases and grounding packs that hand an agent the repo's real surface, the cross-repo contracts, the known gotchas and the past tickets before it writes a line. Every answer cites its source.
How it works →A delivery flow from discovery to release for teams where agents write the code. Engineers own the plan and the acceptance tests. Agents do the legwork in small slices. Nothing is done until a different model has reviewed it and the end-to-end test is green.
How it works →Baselines before changes. PR turnaround in working hours, review coverage, time waiting in QA, revert rate. We set up the measures, change one thing at a time, and keep what moves the number. People spend their time on decisions, not on legwork an agent can do.
How it works →Specialisms
02 · The loop
AI now explores code and writes it faster than any person. So on a live product the loop runs from a customer email to production on its own, and human time goes to the three moments where domain knowledge and experience change the outcome.
Agents run every stage. People step in at three points.
03 · How it came together
None of this was designed in one go. Each piece closed a gap the previous one exposed, and together they put the loop a long way beyond a vanilla agent session: the same models, made accurate and consistent by what surrounds them.
04 · Approach
Every piece of work names the business objective it serves. Then we benchmark: a baseline before anything changes and the same measure after, so the evidence decides what stays. It works the same on a team moving to agent-assisted delivery, a platform getting ready for peak load, or a new end-to-end delivery system. The name comes from dendrology, reading a tree's history in its rings. We read any problem or process the same way, in a system or in a team.
454 PRs
Merged in twelve days on a live product by the agent loop, with a median of 0.6 hours from opened to merged.
How the loop works →0 reverts
Across those 454 pull requests and six production releases. Speed only counts if what ships stays shipped, and the gates are what keep it there.
The agent delivery work →06 · Writing
454 Pull Requests in Twelve Days
What the Agent Does Not Know to Look For
The Cheapest Model That Can Safely Do the Job
The Drawing Office and the Yard
Closing the Loop to Full Autonomy
Shipping While We Sleep
Resumption-First Memory: Design Rules for Agentic Systems
Surviving Claude Compaction: How to Make Your Sessions Outlive Their Context Window07 · Contact
Tell us what you're building, where you want to get to, or what you'd like to know. We reply to everything.