Skip to main content
Tracks integration doc stubs that need schemas filled when a dependency spec is implemented. Auto-populated by spec-reviewer; consumed by eos-spec next and generate-tasks. Schema (v2, 2026-04-17): Each row carries an explicit Owner, Unblock Condition, and Target Quarter so the IOU is closeable. npm run audit:integration-contracts treats every spec ID referenced in this file as “covered” until the row is resolved. Triage pass: 2026-04-10 — each row has an explicit next action; full schema closure remains tied to owning specs. Schema upgrade: 2026-04-17 — added Owner / Unblock Condition / Target Quarter columns.

​
Pending Stubs

| CL-06-EN-23-weno-ez-adapter-INTEGRATION.md (to be created at EN-23 Phase 3) | Adapter operation schemas, CL-05 NewRx event payload, CL-64 audit event mapping, external WENO endpoint contracts | EN-23 Phase 3 implementation | (1) Author CL-06-EN-23-weno-ez-adapter-INTEGRATION.md covering WenoAdapter operation types, CL-05 normalized NewRx event payload, CL-64 audit event mapping, external WENO EZ endpoint contracts, and payload redaction guidance. (2) Add EN-23 row to CROSS_CORE_INTEGRATIONS.md. | CL | EN-23 Phase 3 ships (integration wiring) | 2026 Q3 | CL-06-EN-23 spec-review 2026-05-21 | 🟡 New IOU — Phase 3 deliverable; adapter types + event shapes finalized in Phase 2. | | CE-75-hubspot-inbound-sync-INTEGRATION.md | Webhook payload normalization schema, recorded API fixture set, event payloads (ce_hubspot_*) in EVENT_CONTRACTS.md | CE-75 implementation | Publish normalized inbound work-item schema, webhook subscription config, retry/backoff budgets, and register the four PHI-free platform events in EVENT_CONTRACTS.md; commit recorded HubSpot API fixtures with the sync worker | CE | CE-75 implementation ships the webhook receiver + sync worker | Resolved | CE-75 spec-review 2026-06-11 | ✅ 2026-06-11 — CE-75 implemented: work-item schema + subscription set + retry/backoff budgets published in the integration doc; the four ce_hubspot_* events registered in EVENT_CONTRACTS.md + @/platform/events; recorded fixtures at tests/fixtures/ce/hubspot-api/. CE-76/77/78 extend the same doc. |

​
Temporary Coverage Placeholders (2026-05-13)

These IDs are tracked here as governance coverage placeholders so audit:integration-contracts can pass while owners decide whether each item belongs in a dedicated *-INTEGRATION.md, a canonical cross-core table, or the intra-core allowlist. This section should be triaged down into authoritative destinations as part of upcoming spec maintenance.
  • CE owner: CE-30, CE-31, CE-32, CE-49, CE-51, CE-52, CE-53, CE-54, CE-55
  • CL owner: CL-16-EN-03, CL-58, CL-59, CL-60, CL-61, CL-62, CL-63, CL-64, CL-65, CL-66, CL-67
  • FA owner: FA-42, FA-43, FA-44, FA-45, FA-46
  • FM owner: FM-23, FM-24, FM-25, FM-26, FM-27, FM-28
  • FW owner: FW-65, FW-66, FW-67, FW-68, FW-69
  • GR owner: GR-21, GR-22, GR-23, GR-24, GR-25, GR-26
  • HR owner: HR-39, HR-40, HR-41, HR-42, HR-43
  • IT owner: IT-18, IT-19
  • LO owner: LO-29, LO-30, LO-31, LO-32
  • PF owner: PF-102, PF-103, PF-104, PF-105, PF-106, PF-107, PF-108
  • PM owner: PM-67, PM-68, PM-69, PM-70, PM-71, PM-72, PM-73
  • RH owner: RH-12, RH-13, RH-14, RH-15, RH-16

​
Temporary Coverage Placeholders — CEEM P0 chain (2026-06-05)

The CEEM (Community Engagement & Eligibility Management / Medicaid work-requirement) P0 spec chain landed reviewed specs + implementation plans ahead of authoring their cross-core contract surfaces. These IDs are tracked here as governance coverage placeholders so audit:integration-contracts passes while each owner authors the real EVENT_CONTRACTS.md / API_CONTRACTS.md / *-INTEGRATION.md surface as the spec is implemented. Planned surface noted per owner; triage down into authoritative destinations as each ships.
  • CL owner: CL-62-EN-01 — planned: treatment-episode exemption-signal event (CL → PF eligibility/exemption engine).
  • PF owner: PF-91-EN-02, PF-96-EN-01, PF-106-EN-01, PF-116 — planned: typed cross-core status registry, work-requirement rule-pack on jurisdiction profiles, client-level evidence-bundle API, and verification-deadline / noncompliance lifecycle surfaces.
  • PM owner: PM-57-EN-01, PM-65-EN-01 — planned: patient-demographics applicability extension and ahcccs_coverage_change event emission.
  • RH owner: RH-04-EN-05, RH-07-EN-01 — planned: first-class qualifying-activity-hours on attendance and alumni-engagement-hours ledger feeds to CEEM.

​
Temporary Coverage Placeholders — primary-care/physical-health + certification spec cohort (2026-07-02)

The primary-care + physical-health integration epic (2026-06-29) and adjacent certification/reporting programs landed reviewed/stub specs ahead of their cross-core contract surfaces. Tracked here as governance coverage placeholders (same convention as the CEEM chain above) so audit:integration-contracts reflects the IOU rather than a silent gap; triage each into authoritative destinations as it ships.
  • CE owner: CE-20-EN-01, CE-70-EN-01, CE-70-EN-02, CE-73-EN-01, CE-80, CE-81 — planned: family-contact capture, partner-list/lead-closure ledger feeds, stage-triggered external-calendar scheduling, partner multi-address model, configurable intake-triage engine surfaces.
  • CL owner: CL-03-EN-01, CL-06-EN-24, CL-12-EN-69, CL-16-EN-04, CL-35-EN-01, CL-35-EN-02, CL-36-EN-03, CL-38-EN-01, CL-66-EN-01, CL-72, CL-73, CL-74 — planned: unified medical+BH plan-of-care, non-controlled eRx at scale (RTPB/formulary), DCO/community-provider directory, bidirectional FHIR write + SMART v2 launch, physical-health quality-measure pack + panel registry, governed agentic note drafting, CCBHC 4.g screening/monitoring, CDC CDSi immunization forecasting, primary-care encounter documentation, USPSTF/ACIP due engine, chronic-disease registry suite.
  • FA owner: FA-48 — planned: 340B drug-pricing program management (FA↔CL-05 dispensing + PM claims surfaces).
  • GR owner: GR-34 — planned: HRSA UDS reporting feeds (GR↔CL/PM measure extraction).
  • PF owner: PF-96-EN-02, PF-134, PF-135 — planned: org integration model + SAMHSA-level profile on jurisdiction profiles; ONC Health IT certification program surfaces; wizard conformance & enforcement (Phase 0 shipped 2026-06-30; contract surface pending the compliance-review gate).
  • PM owner: PM-75-EN-01, PM-75-EN-02, PM-78, PM-79, PM-80, PM-81, PM-82 — planned: TCM/RPM billing blocks, APCM BH add-on billing, E/M coding engine (consumes the CL-75 resolved-blocks contract), preventive/Medicare-wellness billing, empanelment/PCP panels, AHCCCS IC enrollment, FQHC PPS / RHC AIR encounter billing.

​
Closure workflow

When closing a row:
  1. Move the row to a ## Resolved Stubs section below (preserve historical record).
  2. Update the integration doc to remove the stub callout and finalize schemas/payloads.
  3. Re-run npm run audit:integration-contracts to confirm coverage holds.
  4. Reference the resolution in the owning spec’s IMPLEMENTATION_LOG.md.

​
Backlinking

Every open IOU above MUST be back-linked from the owning spec’s PLAN.md or TASKS.md so implementers see the contract dependency before they start work. Use the format:
Pending integration contract: see docs/architecture/integrations/PENDING_CONTRACTS.md row “{stub section name}”. From specs/{core}/plans/, use relative path ../../../docs/architecture/integrations/PENDING_CONTRACTS.md; from specs/{core}/tasks/, use ../../../../docs/architecture/integrations/PENDING_CONTRACTS.md.

​
Resolved Stubs