docs(blueprint-03): fix diagram alignment (topology -> LR, threats -> single subgraph)#50
Merged
Merged
Conversation
Two layout problems on the Blueprint 03 page caused the diagrams to look misaligned vs the rest of the blueprints set: 1. Topology diagram (TB): customer subgraphs sat at root level *below* the provider AKS subgraph, so arrows from customer laptops back up into the AKS App Gateway in the middle of the provider box looked like spaghetti. Switched to flowchart LR so customers sit on the left, provider AKS on the right, and the customer arrows flow naturally left-to-right into the App Gateway. 2. Hardware-isolated sandbox diagram (TB): three ATK adversary nodes were floating at root level alongside the Host and Attest subgraphs, which made mermaid spread them awkwardly across the rendered area. Wrapped them in a single 'Threats' subgraph at the top of the diagram and converted the Pod direction from LR to TB so openclaw and router stack vertically (matching the layout convention used in blueprints 01/02/04). ATK -> defended-element edges changed from undirected (-.-) to directed (-.->) so the threat arrow direction is unambiguous. Pure layout / alignment fix. Same content, same colour palette, same classDefs, same theme directive. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pallakatos
added a commit
that referenced
this pull request
May 12, 2026
Two layout problems on the Blueprint 03 page caused the diagrams to look misaligned vs the rest of the blueprints set: 1. Topology diagram (TB): customer subgraphs sat at root level *below* the provider AKS subgraph, so arrows from customer laptops back up into the AKS App Gateway in the middle of the provider box looked like spaghetti. Switched to flowchart LR so customers sit on the left, provider AKS on the right, and the customer arrows flow naturally left-to-right into the App Gateway. 2. Hardware-isolated sandbox diagram (TB): three ATK adversary nodes were floating at root level alongside the Host and Attest subgraphs, which made mermaid spread them awkwardly across the rendered area. Wrapped them in a single 'Threats' subgraph at the top of the diagram and converted the Pod direction from LR to TB so openclaw and router stack vertically (matching the layout convention used in blueprints 01/02/04). ATK -> defended-element edges changed from undirected (-.-) to directed (-.->) so the threat arrow direction is unambiguous. Pure layout / alignment fix. Same content, same colour palette, same classDefs, same theme directive. Co-authored-by: Pal Lakatos-Toth <pallakatos@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Tiny follow-up to #49: the Blueprint 03 page still looked misaligned relative to the rest of the set. Two specific causes, both addressed here.
Threatssubgraph and changed the innerPoddirection from LR to TB so openclaw + router stack vertically (matches 01/02/04 convention). ATK edges are now directed (-.->) for unambiguous threat-arrow direction.Pure layout / alignment fix — no content, palette, or classDef changes.