> ## 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.

# Integration docs crosswalk

> Last updated: 2026-03-23 Audience: Developers and spec authors maintaining cross-core boundaries.

**Last updated:** 2026-03-23\
**Audience:** Developers and spec authors maintaining cross-core boundaries.

## Naming convention

Files named `{SPEC-ID}-{slug}-INTEGRATION.md` in this folder describe **integration surfaces** for that spec (dependencies, events, APIs, data). The **canonical requirements** remain in `specs/{core}/specs/`.

## Canonical contracts (read first)

* [PLATFORM\_INTEGRATION\_LAYERS.md](./PLATFORM_INTEGRATION_LAYERS.md)
* [EVENT\_CONTRACTS.md](./EVENT_CONTRACTS.md)
* [API\_CONTRACTS.md](./API_CONTRACTS.md)
* [CROSS\_CORE\_INTEGRATIONS.md](./CROSS_CORE_INTEGRATIONS.md)

## Maintenance checklist (per stub or quarterly)

1. **Spec link:** Top of file points to `specs/{core}/specs/{SPEC-ID}-*.md` (file must exist).
2. **No duplicate law:** If the stub only repeats EVENT\_CONTRACTS/API\_CONTRACTS tables, replace with a short pointer paragraph + links.
3. **Broken links:** Run `npm run validate-docs` after moves; fix relative links to other integration files or move references to the spec.

## Known gaps (fix when touching related specs)

* Some older stubs link to sibling `*-INTEGRATION.md` files that were never added; prefer linking the **spec** under `specs/cl/specs/` (or the relevant core) instead.
* **Data dictionary** for new tables: register in [../standards/DATA\_DICTIONARY.md](../standards/DATA_DICTIONARY.md), not a file in `integrations/`.

## Count

There are on the order of **190+** integration markdown files here; use repo search for `INTEGRATION.md` when locating a feature.