Parity Boundaries

This page defines what counts as parity progress for expo-react-native-parity-v1.

In-scope

• Baseline API shape parity with Capacitor exports and helpers.
• Public type strictness (no parity-critical unknown placeholders).
• Runtime semantic validation evidence from Expo dev-build hosts on iOS and Android.
• Documented mismatch disposition for any gap discovered during parity validation.

Out-of-scope

• New runtime features not present in Capacitor baseline.
• Product expansion work framed as “parity”.
• Expo Go claims for native runtime parity.
• Device/OEM reliability guarantees beyond validated baseline scenarios.

Why this boundary exists

The package has separate layers with separate evidence types:

• JS surface parity tests validate exports and helper contracts.
• Runtime behavior claims require native host execution evidence.
• Plugin behavior is prebuild-time and cannot prove runtime app orchestration.

Combining those layers into one claim without evidence per layer would overstate what source currently guarantees.

If a request falls in out-of-scope, it must be deferred into a separate change proposal.