rzen
bab456c08d
A lane folds to a fixed slim vertical strip carrying its glyph, its card-count badge and its title turned on its side, and the strip is deliberately not part of the window's division: the expanded lanes' units divide what is left once each folded strip's fixed width has come off the top, so folding a lane is a re-divide trigger of the Show/Hide Trash family — the window never moves and the siblings grow into what the lane gave up. The state is a first-class lane frontmatter key, `collapsed: true`, and document state exactly as `width` is: the files are the board, so an agent folds a lane by writing one key. Absent means expanded, expanding removes the key rather than writing `false` (the remove-at-default family beside a one-unit `width`, the empty rename's `title` and the None well's `background`), and the lane's `width` rides along untouched so expanding restores the lane the user had. The read is `width`'s leniency one type over — a boolean scalar or a quoted boolean word reads as itself, everything else has no reading at all and renders as expanded, bytes preserved either way. Toggling is the header's always-visible collapse chevron, the lane context menu's single Collapse Lane / Expand Lane row, and a plain click anywhere on the strip; a modified click on the strip stays the ordinary selection grammar, so a folded lane is still selectable by pointer. The title reads bottom-up and is justified to the top of the room below the strip's chrome (owner ruling 2026-08-08), truncating against the strip's own height. While folded the lane draws no cards at all, which is what makes every exclusion true by construction rather than by a guard per gesture: no card face means no marquee target and no navigation frame, and no registered grid means the masonry's drop zones have nothing to resolve against. What did need code is the half that names absolute destinations — the option-arrow jumps and the arrow seed scan past a folded lane, the lane domain's down-arrow is inert on one, and New Card skips it (a selection inside one falls through to the last-active lane, the stale selection's rule). A drop on the strip appends at the lane's end, cards and Finder files alike, with an accent edge standing in for the shadow the strip has no masonry to open; there is no hover-to-auto- expand yet. Lane reorder works on the strip, and a dragged folded lane carries its fold, so its shadow and its replica are the strip rather than its units. The write is `writeLaneWidths` clause for clause — one `updateIndex` bracket, the same stamp behaviour, the same three do-nothing paths — with two new `WriteOperation` cases and two new undo verbs rather than one of each, because a banner or an Edit-menu row that said "resize" after Collapse Lane would name a control the user never touched. Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
Lanework — Design Documents
A ground-up rewrite of the Kanban app, to ship as Lanework on the Mac App Store. The old repo (../../Kanban, one level above this repository — not the rewrite's own Kanban/ source folder, which shares the codename) was a pathfinder — it never shipped, but it is the reference implementation and the source of hard-won decisions. This design starts from a clean slate and keeps only what earned its place. The rewrite keeps the internal codename Kanban (bundle id dev.rzen.indie.Kanban).
Each document covers one aspect of the design. Within each:
- Decisions — settled, either carried over from the old app or newly made.
- Changes from Kanban — where this rewrite deliberately diverges.
- Open questions — flagged for iteration; nothing here is implicitly settled.
Index
| Doc | Aspect |
|---|---|
| 00-vision.md | What Lanework is, who it's for, goals and non-goals |
| 01-storage-format.md | On-disk contract: folders, frontmatter, ordering, the materialized trash |
| 02-architecture.md | App structure: source of truth, stores, watchers, concurrency |
| 03-board-ui.md | Board window: layout, lanes, cards, styling, templates |
| 04-interactions.md | Selection, drag & drop, keyboard, clipboard, search |
| 05-card-window.md | The card window: Markdown preview/edit, attachments |
| 06-history-undo.md | Git-backed undo/redo and history — retired 2026-08-08 (git excised, strategy/01-git-excision.md; Undo routing migrated to 13) |
| 07-sync-collab.md | Board modes and git-rails sync — retired 2026-08-08 as written; successor: the ops-based sync service workstream |
| 08-agent-integration.md | AI agents as first-class users of the board |
| 09-templates.md | Board templates: inventory and definition format |
| 10-accessibility.md | VoiceOver, text scaling, visual accommodations |
| 11-command-nexus.md | The command Nexus — every command and action: bindings, contexts, customizability |
| 12-editions.md | The tiers — mooted 2026-08-08: one version, everything free, tier machinery excised; Pro returns with the iPhone/sync era as a fresh pass (the doc is record: entitlement mechanics, distribution, the git rows) |
| 13-native-undo.md | macOS-native undo/redo — the history substrate (sole since 2026-08-08); owns Undo routing |
| 14-git-operations.md | Extracted pathfinder git-operations conclusions — retired 2026-08-08 (superseded record) |
Deferred design iterations
The card window (05-card-window.md), toolbar (03-board-ui.md ▸ Toolbar), styling controls (03-board-ui.md ▸ Styling ▸ Controls), and comments (01 ▸ Enhanced schema + 05 ▸ The comments column — designed 2026-07-29, shipping post-2.0) each had their focused pass and are settled.
The authoritative list of open design passes is the findings board (Lanework Redesign.kanban ▸ Issues to Resolve) — this section stopped enumerating by hand after drifting twice. Standing examples as of 2026-07-29: the attachment-undo staging design and the EchoLedger foreign-undo bridge (both flagged in 13-native-undo.md), Teams' tracker integration (no design yet), the fail-fast decision surface (01 ▸ Refuse), and the drop-release settle presentation (03 ▸ Motion — deliberately last in line).
Wishlist
Ideas worth keeping but outside the committed design live in ../WISHLIST.md.
Terminology
The rewrite adopts lane as the canonical term for what the old app called a column (it's in the name: Lane-work). "Column" survives only when referring to the old app or to interior card-grid columns inside a wide lane.