Current outcome: I have started building this site and am reviewing the work I can publish, one project at a time.
When I opened the folders behind this site, most of what I found was ordinary working material: drafts, code, test runs, and email threads. A few folders ended with something public, such as a paper or a dataset the provider later corrected. Many ended with a rejected submission or a build I stopped. I wanted the archive to show those endings clearly.
That means keeping some failed and unfinished work. I will say what I tried, what evidence remains, and where the work stopped. The hours and files belong to the record, but they are not the result.
Turning scattered records into one account
Most projects are spread across chat logs, code, email, documents, and submission portals. I group the records by the question I was trying to answer, then return to the underlying files and write one account of the decisions I made. Private correspondence stays private. Tool output appears only when it helps explain a result or reproduce a check.
Why a project stopped
A neat lesson written later can distort what happened. I keep the documented stopping reason separate from my interpretation now. Anything that may be resubmitted or patented remains private, as do peer review and material that requires someone else’s consent.
If a project ended without an outside result, that is the outcome I record. Reusable code or a better decision rule may still be worth carrying into the next attempt, but neither changes the ending.
Who I hope will find it useful
Someone considering working with me should be able to see how I narrow a problem and check the evidence. If another person is working on a similar problem, I hope the record will save them from at least one dead end I have already tested.
Each post will show its current status and the date I last verified it. If a result changes, I will add a correction record instead of quietly deleting the earlier account. For now, I am checking the projects that can be made public and moving them over one at a time.