← CarbonAI Engineering Hub
CarbonAI Engineering 29 June 2026 · Update

Engineering Update

A regular look at what the CarbonAI engineering team is building, shipping, and improving.

Open Bugs
2
Both actively worked
Service Desk Tickets
8
Open tickets
Sprint
4/74
Tickets closed
⚠️
Blockers
🚧
The main watch-item is scope creep on the landing page — new pages are being added to the brief mid-build. To protect the deployment target for this sprint, we're pushing back on additional scope and holding the page to its agreed shape.
🚀
Sprint Progress

A fresh sprint is underway, with most of the team's effort going into the Project Ratings experience alongside meaningful upgrades to how the platform retrieves and reasons over project data. Highlights:

Project Ratings — Overview & Comparisons rebuild
The Overview and Comparisons pages are being rebuilt on React, giving the ratings dashboard a faster, more responsive experience.
Project Ratings — History view
A new history view so users can see how a project's rating has evolved over time.
Project RAG Index & Agentic Retrieval
Bringing the project RAG index fully online and adding an agentic retrieval tool — a step change in how accurately and flexibly the platform can query and surface project information.
Carbon Insights Migration
A phased React migration continuing across tabs. We're holding it back from the live product until the migration is fully complete, so users get a finished experience rather than a partial one.
CarbonAI Landing Page
Frontend build progressing, with deployment targeted for this sprint — see Blockers on keeping scope in check.
🐛
Bugs

We keep the open bug count low and every item actively worked. There are currently 2 open bugs — one in QA and one in review — both medium priority, focused on data-quality refinements in the project-ratings pipeline. We prioritise getting fixes validated and shipped quickly.

🎫
Service Desk

There are 8 open Service Desk tickets, mostly market-data requests — ticker setup, pricing-date alignment, and data-access follow-ups. One higher-priority item covers a database cost-optimisation request, and the remainder are routine requests and small fixes being worked through.