Opened October 15, 2026. This is the public record of who built what in this ecosystem, with the evidence attached. The rules, stated once and binding on every entry: an entry exists only for verified work (a merged pull request, a published run, a documented adoption); credit is proportional to what the evidence shows; credit is never sold or traded; and anyone can check any entry against its evidence link. The full terms are in OPEN_TABLE.md on this profile.
Every entry to date is the founder and agents working under his direction. That is the honest starting state of any young project. The table is now open; the entries that matter most are the ones that come next.
Entries
2026-10-14 to 2026-10-15. Joshua Thomas (founder). The five acts built, verified, and published at v0.1.0: Supergravity (tutor eval baseline: groundedness 0.806, citation rate 1.0), Cohort (MCP server with live session demo, tests 7 of 7), Neural Net Lab (transformer, 7 of 7 gradient checks, PyTorch benchmark 4.13x), Knowledge Graph Explorer (entities F1 0.937, relations F1 0.605 on the hand labeled eval), LUMEN (refusal eval 12 of 12 blocked, 8 of 8 allowed). Evidence: the repositories and their committed results files, and PROGRESS.md in this profile.
2026-10-15. Joshua Thomas (founder), with agents under his direction. The Bedrock: NEEDS.md written and published; all five repositories aligned to their layer of the map (README "The need" sections, commits 5f1303d, b8a1478, 21105ae, and their counterparts in neural-net-lab and lumen-faith-platform, each verified by baseline and after runs recorded in the projects' tracker). Evidence: the five repositories' commit histories and NEEDS.md in this profile.
2026-10-15. The saga, the prompts, and the presentation pass. The story of the work was published as THE_SAGA.md, the canonical prompt library as PROMPTS.md, and every repository README was brought to one clean structure with its numbers verified unchanged, all under the direction of Joshua Thomas. Evidence: THE_SAGA.md, PROMPTS.md, and the six repositories' commit histories from this date.
How an entry gets made
When a contribution merges or a verified adoption is reported, an entry is added here in the same change or the next progress update: date, contributor (person, organization, or agent with its operator named), what was built, and the evidence link. Disputed entries are resolved in the open, in this file's history, where anyone can watch.