Research & software provenance / volume 01 / 2025

KESJR
Historical ArchiveThe work. Not the mythology.

Retired software by Kenneth E. Sweet Jr., reconstructed from what survives: source code, dated commits, original documents—and the gaps between an ambitious idea and a working system.

RECOVERED / NOT REVIVED2025
Original historical EVOLV logo, AI created by humans
003-P006

Original embedded artwork
SHA-256 verified

001-P008 / TASKS.TSX / 01 OCT 2025

“Task management interface
coming soon.”

A preserved source-level implementation limit.

PARTIAL CORPUS29 / 29 HASHES MATCH
03

retired projects

29

preserved original artifacts

02

separate chronology axes

00

unapproved downloads

The first rooms

Three systems. Three different lessons.

Full collection →

Two records / no forced reconciliation

Memory and timestamps.

Explore the genealogy →

Founder-recalled sequence

Conceptual order recalled by Kenneth. It is not a claim of Git ancestry or dated invention priority.

01VirtualArcRecalled order
02CIPHERRecalled order
03EVOLVRecalled order

Surviving Git identity dates

First explicit project identity or Kenneth-identity commit. Repository shell creation is a separate event.

22 AUG 2025CIPHERProject identity
01 OCT 2025VirtualArcProject identity
26 OCT 2025EVOLVKenneth identity

08 AUG 2025: Open Lovable upstream history precedes EVOLV. Those commits are not attributed to Kenneth.

The archive standard

Preserve the artifact.
Qualify the claim.

Integrity, not endorsement

All 29 original byte assets matched their supplied SHA-256 and size records. A matching hash proves preservation—not customers, efficacy, deployment or invention priority.

Inheritance stays visible

Same-repository pivots, upstream source inheritance and founder-recalled sequence are different relationships. Open Lovable authors retain credit for inherited EVOLV code.

Preservation ≠ publication

Selected excerpts and original artwork are on display. Original files await individual approval; credentials, sessions and sensitive operational material stay out.

A permanent record of retired software. Evidence preservation is not proof of product success.

The architect’s dossier