domains / families / security / cross-platform-contract-propagation-audit

cross-platform-contract-propagation-audit

authentic

Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.

When to use

• Use when adding or changing a field, enum value, status, capability, or feature flag shared by multiple components.
• Use when database, backend, API, Web, Android, iOS, jobs, events, or analytics may interpret the same value differently.
• Use when a change must preserve existing records, older clients, or a default-off rollout.
• Use when a change looks complete in one endpoint but may be missing from alternate entry points or generated models.

When not to use

• Static evidence cannot prove runtime configuration, deployed schema state, generated-code freshness, or client behavior that was not exercised.
• Repository access may omit private services, analytics schemas, remote flags, or older released clients; mark those edges `unknown`.
• This skill finds propagation and semantic gaps, not every security, performance, or product-design defect.
• A complete graph does not prove the underlying business rule is correct.

Skill page

Source