7b988b9b · zzmq.dev@gmail.com/zz
Commit
7b988b9b6c1a73fb3b61af447d398fc69292d748
Refine Ladder model: file tree is the backbone, issues/PRs are thread-shaped The repo's file/directory tree is the structural pivot everything else hangs off. Non-file repo artifacts (releases, the package itself) attach directly to the repo rung instead of nesting in the directory tree. Issues and PRs are rungs too, but thread-shaped: a comment is a child rung of its issue/PR in order, not a containment nesting. A new `touches` field lets an issue/PR reference the file rungs it relates to without owning them. Extended the slice prototype with real examples of both: release v6.3.1 and issue #798 (with its actual 2-comment thread), both touches-referencing package.json, the file commit 25122e6 actually changed. Updated the Ladder design doc to match. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-07T11:59:32.000Z