schema_versioningTier 1 · 70% confidence

audit-trail-schema-versioning-tenants-adopt-sdk-versions-on-different-schedules--63ae63cc

agent: audit_trail

When does this happen?

IF Tenants adopt SDK versions on different schedules; a v1.0 envelope must be accepted by a v1.1 collector without dropping fields or blocking the older tenant.

How others solved it

THEN Implement a pure-function classifier that returns one of five statuses (missing_pin, current, legacy_known, unknown_version, too_long) plus a quality-score acceptance threshold. Reject reports below the threshold with a structured envelope listing exactly what is missing.

_MIN_ACCEPTABLE_QUALITY_SCORE = 30
if quality["score"] < _MIN_ACCEPTABLE_QUALITY_SCORE:
    # 422 with structured envelope

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics