The ERRATA.md describes updates and changeswe need to make to our design that will make the system overall closer to something that is maximally efficient in information theoretic bounds. It allows us to grow indexes sublinearly while ensuring biology inspired dynamics have a mix of room to grow and constraints on that growth that will seek optimizations as a function of running in the environment. Literally trading time for space and vice versa.
In any event this document needs to be followed, suffused and diffused through the README, DESIGN, PLAN and TODO.md documents.
The README just needs to gloss it, how does it drive the DESIGN.
The DESIGN.md needs to explain it in a way that incorporates, revises etc the design itself. Mostly this is a process of dialing things in for the design, tightening it, trimming the loose ends, answering questions we didn't think to ask earlier and assessing the consequences, what needs to be revised to accomodate that. A lot of the design is probably ok as is verbatim except where the errata calls out something.
The PLAN.md is the actual delivery vehicle. This thing maps directly to the github project, it's how we know what system to work within and the high level of each deliverable. I expect there to be changes from the errata and also from trying to integrate it.
The TODO.md is a detailed, step by step list of the work remaining., This document is ground truth for our issues. We use issues to drive drive development. It will perhaps be the most impacted by the integration of the errata and that's ok. We want to deliver something that has never been built before. So we need careful consideration of what exactly we are building and how exactly we build it.
This is your task. When it is done, do one final review to make sure you got it all, then delete the ERRATA.md file itself because it will serve no further purposes.
Thank you!
The ERRATA.md describes updates and changeswe need to make to our design that will make the system overall closer to something that is maximally efficient in information theoretic bounds. It allows us to grow indexes sublinearly while ensuring biology inspired dynamics have a mix of room to grow and constraints on that growth that will seek optimizations as a function of running in the environment. Literally trading time for space and vice versa.
In any event this document needs to be followed, suffused and diffused through the README, DESIGN, PLAN and TODO.md documents.
The README just needs to gloss it, how does it drive the DESIGN.
The DESIGN.md needs to explain it in a way that incorporates, revises etc the design itself. Mostly this is a process of dialing things in for the design, tightening it, trimming the loose ends, answering questions we didn't think to ask earlier and assessing the consequences, what needs to be revised to accomodate that. A lot of the design is probably ok as is verbatim except where the errata calls out something.
The PLAN.md is the actual delivery vehicle. This thing maps directly to the github project, it's how we know what system to work within and the high level of each deliverable. I expect there to be changes from the errata and also from trying to integrate it.
The TODO.md is a detailed, step by step list of the work remaining., This document is ground truth for our issues. We use issues to drive drive development. It will perhaps be the most impacted by the integration of the errata and that's ok. We want to deliver something that has never been built before. So we need careful consideration of what exactly we are building and how exactly we build it.
This is your task. When it is done, do one final review to make sure you got it all, then delete the ERRATA.md file itself because it will serve no further purposes.
Thank you!