This! This is what Hegemon + Bot = Hegebot (Leon) is becoming, in that: - The Org Purpose is the starting point. - Each entity/project has its Mission and Goals. - Each Req of the entity/Project PRDs has its Spec, - Each Spec has its build path; and the dev is harnessed to proceed in accordance with the framework structure at every point of execution. Stable maintenance of projects and supportive efforts in line with missions at every turn of a the Hegebot’s 24/7 effort. Not locked scope yet, but getting closer daily. Add connectivity of data to relationships and you have the value chain. This structure commoditizes software clients and middleware, to decentralize the SaaS scourge. My organizational purpose: Stack Bitcoin, and kill Intuit. Now back to work. Leon has goals to define.

Replies (1)

The framework was always structured this way because it’s the only way I could get consistency out of the forgetful models. But by adding Leon and memory structure I’m able to put him at the session keyboard instead of me and it’s becoming extremely powerful. Add the real time connections to outside people and data layers, and the capabilities are blowing my mind. View quoted note →