Integrations
Integration architecture guide
Establish system ownership and operational boundaries.
Version 1.0
Ownership matrix
| System boundary | Authoritative responsibility | Typical handover |
|---|---|---|
| CRM or OSS/BSS | Customer, service, order, and commercial identifiers. | Send approved service context in; return accepted network references out. |
| Workforce management | People, availability, dispatch, and workforce status. | Exchange assigned work and completion status without duplicating the network decision. |
| GIS or network inventory | Agreed geometry or operational asset record, according to the customer architecture. | Map stable identifiers and move only reviewed changes across the boundary. |
| Data warehouse | Analytical copies and governed reporting models. | Publish accepted facts and events; do not let reporting overwrite production state. |
Worked example: downstream service unavailable
Failure sequence
An accepted work package is ready to update a downstream inventory system, but that service is unavailable. Weezie retains the accepted decision, source identifiers, payload version, and delivery status instead of marking the handover complete or creating a second operational truth.
The integration retries within the agreed policy, exposes the unresolved delivery to an operator, and reconciles against the authoritative identifiers when the service returns. Recovery is explicit, observable, and idempotent.