Motivation

Business Needs

Currently, Blueprint Chat wraps Bedrock's Claude inference endpoints. We have a lambda proxying our Bedrock resoures to track usage and enforce API-limits to our LLM inference usage across Blueprint. The current system works for normal inference calls, however, we have seen low adoptions rates due to the widespread use of other tools such as ChatGPT or. Claude.

We need to provide a Blueprint specific user experience so there is higher adoption rates for our tooling. In order to do achieve this, we propose the following changes to Blueprint Chat:

• All of our resources are scattered across multiple sources such as Drive, Notion, Wiki, Github. We need a search functionality that given a query it will retrieve the most relevant documents.
• Connect the LLM as the natural language interface between the user and the search API.
• Display the search results in Blueprint Chat. (Note, the user should be able to click on a resource and redirect to it.

Goal

Transform Blueprint Chat from a basic Bedrock Claude wrapper into an integrated knowledge assistant that connects with internal resources (Drive, Notion, Wiki, GitHub). The system should help members query organizational knowledge naturally, retrieve relevant documents, and navigate results directly from chat.

Project Roadmap

Phase 1: Foundation & Infrastructure

Objective: Strengthen existing backend and prepare for integrations.

• Audit existing Lambda + Bedrock Gateway for usage tracking and scalability

• Add structured logging and metrics