External integration and local-first design
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
External API adapters and local-first behavior must preserve identity and state authority across disconnection and reconnection.
External integration is a boundary between semantic authorities, not simply a protocol adapter. Source chapters distinguish model Actions, published services and translations to outside APIs or datasets. Identity, context, consistency and error handling must remain explicit when crossing the boundary.
Engineering rules
- Map foreign identifiers and concepts rather than equating names mechanically.
- Expose a stable modeled business capability at the boundary.
- Handle retries, partial failures and eventual synchronization explicitly.
- Protect the invariant-owning side from accidental semantics imported by an adapter.
Chapter outline (original LaTeX headings)
- Integration as a Boundary Problem
- Synchronous Integration
- Asynchronous Integration
- Database Integration
- Message and Event Integration
- Agents and External Execution
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/integration-with-external-systems.tex.