Repository navigation
V0-07: Reconnect tiling and kanban to durable projections - #26
Merged
Merged
Conversation
Tiling and kanban are two ways of reading the same committed Notes. Both consume one projection of the active Thinking Workspace — pinned first, stable creation order, narrowed by any active search — and both place the same Note card, so mutation policy has one home and a view can only decide where a Note appears, never what may be done to it. Tiling arranges each page by repeated halving, alternating direction with depth. Kanban gives one column per Note Type present, in the fixed order the durable interface declares. Neither stores a coordinate, a page, a column, or the view choice itself, so a restart reconstructs both views from SQLite alone. Search now narrows both views instead of rendering a separate list of snippets, so a found Note is never a second copy of the thinking. Closes #8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8.
What this does
Tiling and kanban are two ways of reading the same committed Notes. Both consume one projection of the active Thinking Workspace and both place the same Note card, so a view can decide where a Note appears but never what may be done to it.
src/note-views.ts(new) holds every arrangement decision as pure functions over committed Notes: the active-Workspace result set (pinned first, stable creation order, narrowed by any search), the tiling pages and their halving arrangement, the kanban columns, and whether a selection survives a view switch.src/App.tsxgains a view chooser and the two layouts. The Note card became one closure both layouts place, so mutation policy has a single home.NOTE_TYPESdeclares, so no empty or stale column can appear.Decisions worth reviewing
noteId; Note content is always read from the committed Note, so a found Note is never a second copy of the thinking. Note Type and matched Labels still show, on the Note card itself.taskis one of fourteen equal Note Types and enrichment is not in V0.role="article", notrole="listitem". Neither view nests a card directly under its group, so list semantics would have claimed an ownership that does not exist in the DOM.Testing
src/note-views.test.ts— the projections as pure outcomes from a committed snapshot: Workspace isolation, pinned order, search narrowing, page filling, arrangement of one and many Notes, column order and grouping, selection preservation.src/App.test.tsx— through the DOM: edit in one view and read it in the other, grouping by Note Type, selection kept across a switch and let go when the Note leaves, search filtering with pinned order in both views, empty/one-Note/many-Note states, and a restart. No test asserts a pixel, a size, or an animation.npm run checkpasses (typecheck, lint, vitest, cargo test, Tauri smoke build).Notes for review
The pre-implementation audit is at
docs/v0/audits/08-tiling-kanban.md. ScopedfallowreportsAppand the Note card as large, complex functions; both are the pre-existing shape of the surface rather than something this slice introduced, and splitting the card is what would duplicate mutation policy.🤖 Generated with Claude Code