Dev Team
WHO BUILDS IT. HOW IT IS BUILT.
Four people · roles as they actually are
The people who build ReportLog, and a plain account of how it is being built — including the part of the process most projects would rather not describe.
The team
Four people, September 2026Casey
Lead developerArchitecture: what gets built, what deliberately does not, and every constraint the archive holds to. Owns what ships.
Cedric
Developer · QADevelopment support and testing. Reviewing the prototype by hand, finding what does not hold, and rebuilding the parts that need it.
Nate
Developer · QADevelopment support and testing. Reviewing the prototype by hand, finding what does not hold, and rebuilding the parts that need it.
Tyler
Developer · QADevelopment support and testing. Reviewing the prototype by hand, finding what does not hold, and rebuilding the parts that need it.
How it is built
MethodThe prototype was architected by one person and written with an AI coding tool, over about a month. That was deliberate on both counts: it was the fastest way to get a whole working system in front of people, and at the start there was one person available to build it.
Nothing from that phase is treated as finished. The prototype exists to be taken over: every part of it gets human eyes, and the code is reviewed and refined by hand before any of it is called a release. That is the work happening now.
This is written down because of what the software claims. ReportLog asks you to check a record rather than trust the people holding it. A project making that argument does not get to be vague about how its own code came to exist.
Known limitations, precisely
NoteThe hand review is in progress, not finished, and the repository is not open yet — so none of the above can be checked by reading the source today. It can be the day the repository opens, which is the point of opening it.
ReportLog has not been through an outside security review.
Open source, and opening wider.