AgentBIAgent with Business Intelligence for DTC sites

Back to the knowledge base

OPS-6

Compatibility check for protocol field changes

Published:2026-11-18Views:0

When fields in UCP or a site's public descriptor are added or renamed, existing tools and checklist items may still read the old structure — capabilities are declared but unreadable. Checking compatibility before adopting a change turns external tracking into action.

Compare new fields against current parsing logic item by item: are required fields still present, is there a compatibility window for renames, can old fields still be read? Rely on official docs, not third-party interpretation. For affected checklist items, re-verify locally or in a sandbox and update the definition only after readability is confirmed.

Tracking accumulates facts only; no conclusion or direction change follows a single observation. This article offers no interpretation or verdict on any protocol, only a way to check compatibility.

Official references

2026-11-22