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

Wishlist the board/lane/card nature idea

Browse Source 
Claude-Session: https://claude.ai/code/session_01SR4XGjmBE16ZUYWpfFHXwY
This commit is contained in:
rzen
2026-07-31 18:55:07 -04:00
parent c6b5f6b691
commit 9a35b52261
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
@@ -51,3 +51,7 @@ The loader's Defect stream carries coerce-tier fallbacks (field, path, raw text)
### 12. AI-aided software design template set ### 12. AI-aided software design template set
The Lanework build itself ran on three board archetypes — design corpus (topic lanes, atomic decision cards, open/parked/deferred/tbd labels), findings tracker (Contradictions/Gaps/Minor/Issues to Resolve/Resolved/Mooted, one card per finding, Resolved as living precedent), implementation masterplan (Backlog/Active/Done, Design constraints / Depends on / Done when bodies, one commit per card). Distilling them into bundled templates — including a seeded `CLAUDE.user.md` teaching agents the workflow (DESIGN/09's stray-copy rule already carries it through instantiation) — was considered 2026-07-31 and set aside: these are working artifacts, not release content yet. Designing a reusable template set becomes its own project in due time; the raw conventions live in the retired Redesign-board card (951ed5f1) and the boards themselves. The Lanework build itself ran on three board archetypes — design corpus (topic lanes, atomic decision cards, open/parked/deferred/tbd labels), findings tracker (Contradictions/Gaps/Minor/Issues to Resolve/Resolved/Mooted, one card per finding, Resolved as living precedent), implementation masterplan (Backlog/Active/Done, Design constraints / Depends on / Done when bodies, one commit per card). Distilling them into bundled templates — including a seeded `CLAUDE.user.md` teaching agents the workflow (DESIGN/09's stray-copy rule already carries it through instantiation) — was considered 2026-07-31 and set aside: these are working artifacts, not release content yet. Designing a reusable template set becomes its own project in due time; the raw conventions live in the retired Redesign-board card (951ed5f1) and the boards themselves.
### 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.