Workflow: reordered sections in the "Routing" chapter

treating the tracks and layering as a second section leads
to a better alignment of topics in the overall reading flow.

doc/design/workflow/Verwijlen/Discussion25Digest.txt

@@ -53,8 +53,8 @@ where Benny Lyons also participated.
 | April 2025      | »Workflow and Structure«        | first deep dive: Placements, keybindings, grouping, gear switch
 | 2025-04-16      | IRC chat                        | placements in practice, sticky selection, trimming, keyboard navigation
 | June 2025       | document update                 | Workflow Proposals [underline]#chapter 2# (timeline) completed
-| 2025-08-17      | FrOSCon-25 meeting              | in-person discussion, summarised in link:FrosconMeeting.html[a page of its own]
+| 2025-08-17      | FrOSCon-25 meeting              | in-person discussion; see -> link:FrosconMeeting.html[summary]
-| Aug--Dec 2025   | »Workflow Discussion«           | second deep dive: placement prototypes, moving and adding clips
+| Aug...Dec 2025  | »Workflow Discussion«           | second deep dive: placement prototypes, moving and adding clips
 | March 2026      | document update                 | Proposals [underline]#chapter 1# (source material) completed
 |====================================================================
 
@@ -1024,6 +1024,56 @@ Open:: the actual handling
 
 Routing
 -------
+[[tagging]]
+Organising footage: bins, tags, and tag-based routing
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This topic connects Wouter's [underline]#chapter 1# (source material) with the
+routing question. The pivotal idea arose from combining two observations.
+Hermann, drawing from his audio work experience: music, ambience,
+https://en.wikipedia.org/wiki/Foley_(sound_design)[foleys]
+will be integrated from distinct sources anyway, so routing to sub-mixes
+can be established automatically if the material is _tagged_ (eMail 2025-04-07).
+Wouter then took that to an even more radical conclusion:
+
+[quote, Wouter, eMail 2025-04-18]
+________________________________________________________________________
+When I'm importing sound effects, I'm already putting them in an Audio > SFX
+bin. How about we get rid of bins entirely, and just use tagging for organising
+the entire project? FCP does this, if I'm not mistaken. That way we'll have
+clips organised in the project view and we know how to route them as well in
+a single action. It could be useful for video clips too.
+________________________________________________________________________
+
+Organising and routing thus collapse into one act -- so this yet again connects
+to the recurring theme of using a ``consistent scheme solving additional problems
+en passant'', that resurfaced time and again during that discussion.
+
+From the _Workflow Proposals_ document, [underline]#chapter 1# contributes further
+link:WorkflowProposals.html#\_proposals[conclusions and proposals], which have
+been woven into the discussion thereafter: support _most_ organising systems side by side,
+since they don't interfere (source timelines, rating, tagging, marking); metadata-based
+search and filtering as must-haves; a native 1...5 star rating working on clip sections
+as well as whole clips; bins-in-bins rather than bins-in-folders; automatic source reels
+based on user-defined rules (``show me all clips from the second day of the shoot from
+camera A''); watch-folder auto-import; a built-in metadata browser for sound
+libraries; and *timeline versioning* -- snapshots without manual
+duplicate-and-rename archaeology, which would directly tie into Lumiera's
+->xref:_event_sourcing_and_cqrs[event-log based architecture].
+
+[role="summary"]
+**********************************************************************
+Agreed:: _Tagging_ as organising principle, potentially replacing
+bins; tags double as routing directives (sub-mixes, groups); metadata
+search, rating, source timelines to be supported.
+Open::  the whole Routing area (default rules, explicit wiring/»plugs«,
+mixing groups) has not really been discussed yet; the tag-based scheme
+needs elaboration: tag taxonomy, manual effort, interplay with automatic
+detection. Furthermore, all the functions for organising material within the
+session should be regarded more as indications of ``features we'd like to have'',
+as the handling of »assets« in Lumiera is still at a very early, conceptual stage.
+**********************************************************************
+
 
 [[layering]]
 Tracks, layering and vertical space
@@ -1116,56 +1166,6 @@ Open::
 **********************************************************************
 
 
-[[tagging]]
-Organising footage: bins, tags, and tag-based routing
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-This topic connects Wouter's [underline]#chapter 1# (source material) with the
-routing question. The pivotal idea arose from combining two observations.
-Hermann, drawing from his audio work experience: music, ambience,
-https://en.wikipedia.org/wiki/Foley_(sound_design)[foleys]
-will be integrated from distinct sources anyway, so routing to sub-mixes
-can be established automatically if the material is _tagged_ (eMail 2025-04-07).
-Wouter then took that to an even more radical conclusion:
-
-[quote, Wouter, eMail 2025-04-18]
-________________________________________________________________________
-When I'm importing sound effects, I'm already putting them in an Audio > SFX
-bin. How about we get rid of bins entirely, and just use tagging for organising
-the entire project? FCP does this, if I'm not mistaken. That way we'll have
-clips organised in the project view and we know how to route them as well in
-a single action. It could be useful for video clips too.
-________________________________________________________________________
-
-Organising and routing thus collapse into one act -- so this yet again connects
-to the recurring theme of using a ``consistent scheme solving additional problems
-en passant'', that resurfaced time and again during that discussion.
-
-From the _Workflow Proposals_ document, [underline]#chapter 1# contributes further
-link:WorkflowProposals.html#\_proposals[conclusions and proposals], which have
-been woven into the discussion thereafter: support _most_ organising systems side by side,
-since they don't interfere (source timelines, rating, tagging, marking); metadata-based
-search and filtering as must-haves; a native 1...5 star rating working on clip sections
-as well as whole clips; bins-in-bins rather than bins-in-folders; automatic source reels
-based on user-defined rules (``show me all clips from the second day of the shoot from
-camera A''); watch-folder auto-import; a built-in metadata browser for sound
-libraries; and *timeline versioning* -- snapshots without manual
-duplicate-and-rename archaeology, which would directly tie into Lumiera's
-->xref:_event_sourcing_and_cqrs[event-log based architecture].
-
-[role="summary"]
-**********************************************************************
-Agreed:: _Tagging_ as organising principle, potentially replacing
-bins; tags double as routing directives (sub-mixes, groups); metadata
-search, rating, source timelines to be supported.
-Open::  the whole Routing area (default rules, explicit wiring/»plugs«,
-mixing groups) has not really been discussed yet; the tag-based scheme
-needs elaboration: tag taxonomy, manual effort, interplay with automatic
-detection. Furthermore, all the functions for organising material within the
-session should be regarded more as indications of ``features we'd like to have'',
-as the handling of »assets« in Lumiera is still at a very early, conceptual stage.
-**********************************************************************
-
 
 Grouping
 --------