[Docs] Illustrate cloud/identity/organizations with Orbital Labs and Stellar Dynamics examples

[leecalcote]

Closes #968

Adds an 'Example: The Orbital Labs Ecosystem' section to cloud/identity/organizations illustrating multi-tenancy across three tiers: Constellation Cloud (MSP/provider), Orbital Labs (startup tenant), and Stellar Dynamics (enterprise tenant). Includes a cross-org access explainer and link to the narrative reference.

Depends on: #979 (narrative page)

Changes

• Added three-card org overview (Constellation Cloud, Orbital Labs, Stellar Dynamics)
• Added cross-organization access explanation
• Added link to /cloud/about narrative reference

Test plan

• hugo --quiet builds clean
• Cards render at /cloud/identity/organizations/
• Link to /cloud/about works (after [Docs] Establish Five and Orbital Labs as continuous docs narrative (issue #457) #979 merges)

[github-actions]

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2026-04-29 04:16 UTC

[gemini-code-assist]

Code Review

This pull request establishes a continuous narrative for the Layer5 Cloud documentation, introducing a cast of characters and organizations to provide consistent examples across the site. The changes include a new 'About' section, a research plan for further integration, and the addition of mascot assets. My feedback focuses on improving the portability of the implementation plan by removing hardcoded absolute paths and ensuring consistency in character and team naming across the design specifications.

[gemini-code-assist]

This file contains multiple shell commands with hardcoded absolute paths, such as /Users/l/code/docs. This practice is not portable and tightly couples the plan to a specific user's machine setup. It also leaks user and directory information. These paths should be replaced with relative paths (e.g., assuming commands are run from the repo root) or environment variables to make the plan generic and usable by any contributor.

Suggested change

	mkdir -p /Users/l/code/docs/static/images/five
	mkdir -p static/images/five

[gemini-code-assist]

The team with access to the stellar-main workspace is listed as "Marcus's team". For consistency with the 'Team & Org Hierarchy' table in this same document (line 94), this should be specified as the 'Platform' team.

Suggested change

	| `stellar-main` | Stellar Dynamics | Marcus's team | Enterprise org, cross-org scenarios |
	| `stellar-main` | Stellar Dynamics | Platform | Enterprise org, cross-org scenarios |

[gemini-code-assist]

There's an inconsistency in the 'Integration Map'. For the cloud/security/roles section, the characters are listed as 'Dr. Aiko, Zara', but the scenario is 'Provider Admin → Org Admin → Team Admin chain'. According to the cast list, Maya Chen is the Org Admin. The character list should likely be 'Dr. Aiko, Maya, Zara' to accurately reflect the roles in the scenario.

Suggested change

	| `cloud/security/roles` | Dr. Aiko, Zara | Provider Admin → Org Admin → Team Admin chain | business-mode.svg | Medium | Open |
	| `cloud/security/roles` | Dr. Aiko, Maya, Zara | Provider Admin → Org Admin → Team Admin chain | business-mode.svg | Medium | Open |