JLT Platform Documentation
This section documents the internal platform architecture, access-control model, resource boundaries, deployment flow, and system domains of the JLT platform.
If you are new to the platform, start with the recommended reading order below.
Platform Operating Model
The JLT platform is organized using a multi-plane operating model that separates governance, delivery, operations, documentation, and communication into distinct but connected operational planes.
- Identity Plane — Platform ownership and trust anchor
- Control Plane — Access control, routing, and governance
- Knowledge Plane — Documentation and standards
- Execution Plane — Delivery and implementation
- Operations Plane — Monitoring and lifecycle management
- Proof Plane — Evidence and delivered work
- Narrative Plane — Communication and system thinking
This section of the documentation focuses primarily on the Control Plane, which defines how access decisions are made, how resources are grouped, and how requests move through the platform.
Platform Control Flow
Every request in the JLT platform follows a defined control flow. Access decisions, system visibility, and operational procedures are connected as part of one platform lifecycle.
Who is making the request (role, user, subscription tier).
Entitlements and policies determine what actions are allowed.
Protected platform boundaries used for authorization decisions.
Docs, APIs, Automation Toolkit, Billing, and platform tools.
Metrics, logs, and dashboards provide system visibility.
Operational procedures for incidents, recovery, and maintenance.
CI/CD pipelines deliver and update the platform safely.