comparison · c_efa306aa8040 (tommy-mor) vs c_794fa48498b4 (tommy-mor)
Side A adds a substantial, tested feature (content-addressed evidence ledger, resumable ranking, HTML evidence graph, integration/unit tests) that materially extends the project's transparency and durability guarantees. Side B is purely deletion of dead/legacy files and one idea-note replacement—housekeeping with no functional value and no tests.
Side A adds a durable, tested evidence ledger (content-addressed Evidence events, idempotent append, ranking resume, byte-faithful blobs) plus public HTML indexes for epochs/commits/comparisons/attempts/judgments—core product transparency. Side B only deletes unused legacy sources and swaps an ideas note, removing dead weight without improving the live system.
Side A adds substantial, lasting functionality: a versioned append-only evidence ledger, idempotent persistence with resumable ranking, content-addressed evidence records, HTML evidence browsing endpoints, richer audit links, API enhancements, and extensive integration/unit tests. Side B is primarily repository cleanup, deleting legacy files and replacing one ideas document, with little evidence of new project functionality or bug fixes.
comparison · c_794fa48498b4 (tommy-mor) vs c_b447fc224eaf (tommy-mor)
Side A removes a large body of stale/duplicated legacy files (several of which contain leftover terminal-prompt text, proving they were accidental artifacts, not live code) and tidies a brainstorming doc — a genuine reduction of confusing dead weight. Side B only adds a standalone CSS file with no accompanying template wiring shown and an unclear commit message ('?'), so its lasting value is unverifiable and likely just scaffolding for unfinished work.
B adds a real, reusable product stylesheet (sorter.css) that defines the app’s dark theme, layout, vote fields, rank lists, and breadcrumbs—ongoing UI value. A is mostly delete-only cleanup of already-quarantined legacy dumps (including shell-prompt paste artifacts) plus a short ideas note swap, which improves repo hygiene but does not add lasting product behavior.
Side B adds a new reusable stylesheet (`server/static/sorter.css`) defining theme variables and styles for buttons, forms, ranking lists, breadcrumbs, and parser UI, which is a concrete project asset. Side A primarily deletes legacy source files and replaces one design-notes document with another; while cleanup can be useful, the patch shown mostly removes functionality and documentation rather than adding lasting behavior or fixes.