svc-tenders Cluster Stack Order Map

Purpose

This note documents the comment-stack ordering used under the dense route-cluster headers in svc-tenders after Cleanup Sprint 43.

Focus:

• the repeated explanatory layer order
• where the order was aligned
• where extra notes intentionally remain outside the shared stack

Labels used here:

• VERIFIED
• REAL
• TRANSITIONAL

Shared Stack Order

VERIFIED

Where the full stack exists, the dominant order is now:

1. intro line
2. auth surface
3. dependency touchpoint
4. dominant sequence
5. dominant response shape
6. dominant error surface