Posts tagged "system design"

A lossiness ledger and test strategy for keeping a useful canonical model without silently erasing provider-specific meaning.

An adapter contract and test suite for translating provider pagination, identity, nulls, versions, errors, retries, deletion, and capabilities—not only field names.

A practical field-ownership matrix for deciding which system may write each value before loops, silent overwrites, and deletion conflicts enter a bidirectional sync.

A decision and failure matrix for combining low-latency webhooks with polling and reconciliation so an integration can recover from missed, duplicate, or reordered events.

A reference flow for keeping user identity, tenant, audience, and allowed actions attached to every AI tool call without trusting the model to enforce permissions.