rzen/lanework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Wishlist board export and reporting

Browse Source 
Claude-Session: https://claude.ai/code/session_01SR4XGjmBE16ZUYWpfFHXwY
This commit is contained in:
rzen
2026-07-31 18:55:31 -04:00
parent 9a35b52261
commit c1d4d7be7b
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
WISHLIST.md
+4
View File
@@ -55,3 +55,7 @@ The Lanework build itself ran on three board archetypes — design corpus (topic
### 13. Board/lane/card "nature" — schema plus presentation ### 13. Board/lane/card "nature" — schema plus presentation
A nature is a combination of an object's schema and its presentation, configurable at board/lane/card level: a storyboard board (sketches per card, image-forward faces) and an agile ticket board (story/task types, status attributes rendered on faces) bracket the range. Deliberately not MVP (user-filed 2026-07-29, wishlisted 2026-07-31); a future design session starts from the corpus hooks: `kind` is kin but orthogonal (structural role vs domain flavor); the agile example lands on the reserved enhanced-schema keys (`labels`, `assignees`, `due`, `remote`/`remote-state`) and the Teams tracker story probably wants to be a nature rather than a mode; image-forward faces would be a nature-scoped, per-board reopening of the one-presentation rule (composing, not conflicting — the carousel stays dead); templates are the delivery vehicle (a nature may be what a template declares — pairs with #12); nature must live in frontmatter (files-first, no sidecars), inert-but-preserved in apps that don't know it, no edition-specific keys; the agent guide / seeded `CLAUDE.user.md` would teach per-nature conventions. A nature is a combination of an object's schema and its presentation, configurable at board/lane/card level: a storyboard board (sketches per card, image-forward faces) and an agile ticket board (story/task types, status attributes rendered on faces) bracket the range. Deliberately not MVP (user-filed 2026-07-29, wishlisted 2026-07-31); a future design session starts from the corpus hooks: `kind` is kin but orthogonal (structural role vs domain flavor); the agile example lands on the reserved enhanced-schema keys (`labels`, `assignees`, `due`, `remote`/`remote-state`) and the Teams tracker story probably wants to be a nature rather than a mode; image-forward faces would be a nature-scoped, per-board reopening of the one-presentation rule (composing, not conflicting — the carousel stays dead); templates are the delivery vehicle (a nature may be what a template declares — pairs with #12); nature must live in frontmatter (files-first, no sidecars), inert-but-preserved in apps that don't know it, no edition-specific keys; the agent guide / seeded `CLAUDE.user.md` would teach per-nature conventions.
### 14. Export and reporting — the board as a PDF-book or report
A board output as a PDF book or a report (user-filed 2026-07-29, wishlisted 2026-07-31; not MVP). Dovetails with #13: a nature plausibly implies its export shape — a storyboard board exports as a PDF book of sketches with captions, an agile-ticket board as a status report grouped by type/status; nature = how the board lives, export = how it leaves. Session orientation notes: scope (whole board / lane / selection / search subset; trash never exports; ranks vs nature-informed groupings); formats (PDF named; Markdown/HTML compilations near-free since bodies are Markdown and swift-markdown is in the tree; ⌘P → PDF as cheapest first door or red herring); export is a read (works under every read-only lock per the Save-as-Template precedent, never mutates, save-panel output outside the package — files-first stays absolute); attachments embedded vs referenced vs appendix (body-embedded relative image paths already resolve in Preview); long-running + cancellable copy-shaped work (in-progress row, Cancel, partial-output cleanup per the Duplicate precedent); on-screen styling vs print-first design language (the book case suggests print-first; nature parameterizes); edition placement undecided (a read feels base-worthy, report natures may tier); agents need no export but an agent-triggerable one may be worth a thought (pairs with #12).