> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# LO (Leadership Operating System) — Integration Overview

> Version: 1.0.0 Last Updated: 2026-04-10 Owner: LO

**Version:** 1.0.0\
**Last Updated:** 2026-04-10\
**Owner:** LO

***

## Purpose

This document is the **entry point** for LO cross-core integration. LO publishes leadership workflow data (rocks, milestones, meetings, issues) and consumes HR/FA signals where specs require alignment (e.g. goals, compensation).

**Canonical event catalog:** See [`EVENT_CONTRACTS.md`](./EVENT_CONTRACTS.md) — search for `lo_events`, LO-14, LO-15, and the “Planned Events (LO-\*)” sections.

***

## Realtime / Notify Channel

* **`lo_events`** — Postgres `pg_notify` channel for leadership milestones and action status (see EVENT\_CONTRACTS.md § LO-14 / LO-15). Consumers use Supabase Realtime or edge workers where implemented; many flows remain **planned** until LO Phase 2+.

***

## Key Specs

| Spec                                                                                      | Topic                                                                                 |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [LO-16 Goals Event Integration](../../../specs/lo/specs/LO-16-goals-event-integration.md) | Goal ↔ event bridge (align with `publishEvent` / `fw_domain_events` where applicable) |
| [LO-14 Action Dependencies](../../../specs/lo/specs/LO-14-action-dependencies.md)         | Unblocked / dependency resolution events                                              |
| [LO-15 Enhanced Action Status](../../../specs/lo/specs/LO-15-enhanced-action-status.md)   | Status transition events                                                              |

***

## Platform Integration Layer

* **Events:** Prefer **`publishEvent`** from `@/platform/events` for new domain events that must be durable and auditable; align payload shapes with `EVENT_CONTRACTS.md` before shipping.
* **Auth / org:** Standard `useOrganization`, RLS, and PF permissions — no direct core-to-core imports (constitution §1).

***

## Related Documents

* [`EVENT_CONTRACTS.md`](./EVENT_CONTRACTS.md) — LO event blocks and planned LO-01–LO-09 families
* [`PLATFORM_INTEGRATION_LAYERS.md`](./PLATFORM_INTEGRATION_LAYERS.md) — PF integration rules
* [`CROSS_CORE_INTEGRATIONS.md`](./CROSS_CORE_INTEGRATIONS.md) — Encounter and cross-core diagrams (LO adjacent: org strategy, not clinical)