Inspiration
My inspiration for CogniWeave stems from a significant, yet often overlooked, challenge in our digital world: the cognitive accessibility chasm. An estimated 15-20% of the global population is neurodivergent, facing substantial barriers when processing the dense, complex text that dominates academic, professional, and informational landscapes. This isn't just a matter of inconvenience; it's an issue of equity. My goal was to build a tool that could instantly adapt any text to an individual's unique cognitive and learning style, thereby making information accessible to everyone. The AWS Lambda Hackathon, with its focus on building scalable, real-world solutions, provided the perfect opportunity to turn this idea into a reality, drawing inspiration from sample projects like the "Document Summarizer" but with a deep focus on personalization.
What it does
CogniWeave is a revolutionary web application designed to break down barriers to information. At its core, it's a powerful, AI-driven tool that simplifies complex text. A user simply pastes any block of text—be it a dense academic paper, a convoluted legal document, or a technical report—into the app. In an instant, my serverless engine, powered by AWS Lambda and Amazon Bedrock, transforms the text into clear, easy-to-read chunks. This transformation is personalized to the user's specific cognitive needs, which they define during a quick onboarding process. The result is a centralized hub where complex information becomes understandable, fostering comprehension and empowering users with learning differences.
How I built it
I built CogniWeave using a streamlined, fully serverless architecture to maximize efficiency and power, adhering to the best practices outlined in the AWS Developer Guides.
Frontend: The user-facing application is a modern web app built with React. This provides a clean, unified, and responsive interface where users can manage their cognitive profile and use the transformation tool.
API: I used Amazon API Gateway to create the endpoints that connect the frontend to my backend logic. It acts as the front door, securely managing and directing API calls.
Compute: The brain of the operation is AWS Lambda. I have two core Lambda functions:
CreateProfile: Triggered when a new user signs up. This function takes the user's onboarding responses, calls Amazon Bedrock to generate a cognitive profile, and saves it.
TransformContent: This is the core engine. When a user submits text, this Lambda is triggered. It retrieves the user's profile from DynamoDB, constructs a detailed prompt for the AI, and orchestrates the text simplification with Amazon Bedrock.
Database: Amazon DynamoDB serves as my database for storing user profiles. Its speed and scalability make it perfect for a Lambda-based architecture, ensuring fast retrieval of user preferences during the transformation process.
AI Engine: I used Amazon Bedrock with Anthropic's Claude 3.5 Sonnet model as the intelligence layer. This powerful model handles both the initial cognitive profile generation and the nuanced, context-aware simplification of the user's text.
The entire architecture is a testament to serverless efficiency, consisting solely of API Gateway, AWS Lambda, DynamoDB, and Amazon Bedrock. This hyper-focused stack is a perfect example of how to build a real-world, AI-powered solution with AWS Lambda at its heart.
Challenges I ran into
One of the first challenges I faced was resisting the temptation to over-engineer. My initial ideas involved complex systems for parsing HTML from URLs, but I quickly realized this would introduce unnecessary dependencies and fragility. I pivoted to a text-only input, which allowed me to focus entirely on the core AI transformation logic, making the MVP more robust and reliable—a crucial decision for a hackathon project.
Another significant challenge was prompt engineering. Crafting the perfect prompts for Amazon Bedrock required a lot of iteration. It was a delicate balance to ensure the AI could consistently translate text according to a wide range of cognitive profiles—from simplifying vocabulary to restructuring paragraphs—without losing the original meaning.
Finally, I was mindful of the potential for latency with Lambda cold starts. For a real-time tool like this, responsiveness is key. I designed my TransformContent function to be as lean and efficient as possible to minimize this effect, ensuring the user experience remained smooth and fast.
Accomplishments that I’m proud of
I am incredibly proud of creating the Direct Lambda-AI Engine. The elegance of the architecture, where a single Lambda function orchestrates a complex AI task in a synchronous step, is something I believe truly showcases the power of serverless computing. It does one thing, and it does it perfectly: it makes content accessible.
I'm also proud of the unified and frictionless user experience. By building the profile management and the transformation tool into a single, cohesive Next.js application, I removed all the friction from the user's journey.
Most of all, I'm proud of building a solution that has the potential for real-world impact. CogniWeave is more than just a technical demonstration; it's a step towards a more inclusive and equitable digital world. The project successfully meets all the hackathon requirements, using AWS Lambda as its core, triggered by API Gateway, and integrating with DynamoDB and Bedrock to solve a genuine problem.
What I learned
This project was a deep dive into the power and velocity of modern serverless development. I learned firsthand how AWS Lambda can be the fastest way to turn an idea into a production-ready, AI-powered application. The process solidified my understanding of serverless best practices—specifically, the value of creating lean, single-purpose functions.
Integrating Lambda with Amazon Bedrock was a fantastic learning experience. It revealed how seamlessly you can infuse sophisticated AI reasoning into an application with just a few API calls. This project taught me that the true power of serverless lies not just in scalability and cost-efficiency, but in the sheer speed of innovation it enables.
What's next for CogniWeave
The current version of CogniWeave is a powerful proof-of-concept, but it's just the beginning. I have a clear vision for its future:
Browser Extension: To make the tool even more seamless, I plan to develop a browser extension that allows users to simplify text directly on any webpage, eliminating the need to copy and paste.
Expanded Content Support: I want to expand beyond plain text to support uploading documents like PDFs and eventually use other AI services to process content from images or even audio transcripts.
Advanced Personalization: I envision a more sophisticated cognitive profile that learns and adapts over time based on user feedback, creating an even more personalized and effective experience.
Educational Integrations: My ultimate goal is to integrate CogniWeave with Learning Management Systems (LMS) and other educational platforms to bring cognitive accessibility directly into the classroom.
Built With
- 3.5
- amazon-api-gateway
- amazon-bedrock
- amazon-dynamodb
- anthropic
- aws-lambda
- claude
- javascript
- react
- sonnet
Log in or sign up for Devpost to join the conversation.