Platform Rules
Rules that keep the Mesh coherent as it grows—consistent identity, predictable navigation, and repeatable delivery.
Identity rules (must)
- Use the name: JLT-Lane Engineering Mesh.
- Always provide a MeshHub link: /engineering-mesh ↗
- Keep the tagline consistent: Cloud Confidence. Delivered.
Navigation rules (must)
Every service site must link to the core planes:
- MeshHub
- Docs
- Consulting
- Blogs / Projects (where relevant)
Content rules (should)
- Posts should include at least one Implementation Path link to Docs or Projects.
- Prefer stable canonical URLs; avoid duplicate content—link instead.
- Use consistent terminology: MeshHub, Knowledge Service, Narrative Service, Proof Service.
Operational rules (should)
- Each service deploys independently.
- Changes must not break cross-site navigation.
- Keep pages reproducible: deterministic builds, guardrails, validation scripts.
Versioning rules (recommended)
- Maintain a lightweight changelog per service.
- Tag platform milestones from MeshHub announcements.