Vision

We can now build self-aware applications that understand their own structure and can evolve through AI collaboration. The system converts unstructured information into documentation, and then into executable specification following which code can be generated as the implementation of that specification. It sits as a layer on top of agentic code tools. Documentation as code.

bro (business requirement optimizer) is a tool that helps you

• make meaning from your vibes - babble, ramble or any type of word scramble, bro will take the messy thoughts from your mind and turn them into a coherent, structured thesis of value. Yes, bro can also turn it into a cool graph.
• keep track of the big picture - you keep throwing shit at the wall, bro comes in between and makes sure shit that makes sense, sticks - and sticks in the right place. And stays stuck, until there’s different better shit to replace it. Now you’re throwing shit like tracer bullets.
• focus on what matters - you wanted to change the world, but you seem to be mostly changing the code written by a language model. Why, aren’t you feeling scammed? Don’t worry about it, that’s why bro exists. Now you focus on the problem, and bro will help you handle the rest. In fact, bro will make sure you spend time on the problem so that even if you’re reinventing the wheel, you’re at least making it yours.
• build (for the) better - you know you don’t know everything, yet sometimes you have to pretend to, just to get things moving. With bro, you can stay honest, keep track of what’s real and measurable, what’s a good or a bad guess, and what’s hot garbage. And then, bro helps you act on it with the snap of a finger (given enough compute ofc).

Value-Centric Philosophy: Users focus exclusively on business value and user outcomes. Technical implementation details are handled automatically through AI agent execution of genome specifications. The system transforms application development from a technical craft to a strategic design process, enabling systematic creation of self-aware applications through conversation and conceptual modeling.

Core Principles

1. Self-Description: Applications contain complete knowledge of their own structure and behavior. A meta-application allows for structured evolution of the application.
2. Purposeful pointers: Changes flow seamlessly from documentation to code. Grokking becomes trivial, sniping becomes easier with a target lock.
3. Opinionated Ontology: Applications are understood and implemented through a modern mix of industry best practices. Never strictly speaking.
4. Primitive progression: Complexity is managed from the start, at the highest possible level. Descriptions are dissected into details, and through transcription, translation and task management, converted into basic building blocks which are composed back up.
5. AI-Accessible: Design the system to accomodate the most challenged AI models.

System Architecture

3 Layer Life Model

1. Genome Layer - Transcription: Abstract description of what the application is and does (documentation as code). Input: Unstructured info. Output: Formal specs.