Waves Out-of-Scope Domain Spec Review

Version: v0.1
Status: S0-12 complete (initial extraction)

Purpose

Document reviewed requirements for currently out-of-scope domains so deferrals are explicit, traceable, and reversible.

Requirements observed:
- OTA push transport modes, confirmed/unconfirmed delivery semantics, and security requirements (WTLS on secure paths) are normative.
- PAP/PPG include strict request/notification/status handling and entity ordering rules.
Spec:
- WAP-235*, WAP-247*, WAP-249*, WAP-250, WAP-251
Current posture:
- deferred/out-of-scope for Waves MVP.
AC for future enablement:
- Push session model and delivery-state machine defined before implementation.
- PAP and PPG contracts documented with error/result notification behavior.

Requirements observed:
- Provisioning content/security model, bootstrap trust mechanisms, and smart-card provisioning file rules are normative and substantial.
Spec:
- WAP-182..186 and SIN overlays
Current posture:
- deferred/out-of-scope for Waves MVP.
AC for future enablement:
- Security method + MAC/PIN flow model specified end-to-end.
- SIM/WIM provisioning read/update policy explicitly documented.

Requirements observed:
- SI/SL/CO behavior, MMS transaction and encapsulation flows, and sync protocol requirements impose separate application frameworks.
Spec:
- WAP-167*, WAP-168*, WAP-175*, WAP-205, WAP-206, WAP-209, WAP-234
Current posture:
- deferred/out-of-scope for Waves MVP.
AC for future enablement:
- Message lifecycle, queueing, and replacement semantics formalized in dedicated contracts.
- Push/MMS/Sync dependency layering defined before feature development.

Requirements observed:
- WTA session security, permission model, and telephony event/function bindings are strict and carrier/network dependent.
Spec:
- WAP-266, WAP-268, WAP-228, WAP-255, WAP-269, WAP-270
Current posture:
- deferred/out-of-scope for Waves MVP.
AC for future enablement:
- Permission model and trusted-gateway constraints captured in host security policy.
- Network-specific telephony adapters defined per target profile.

Requirements observed:
- WAP CSS and XHTML MP user-agent conformance are extensive and represent a separate rendering track.
Spec:
- WAP-239*, WAP-244, WAP-277
Current posture:
- deferred/out-of-scope for current WAP 1.x runtime-first milestone.
AC for future enablement:
- Rendering-mode decision (WML-centric vs XHTMLMP dual mode) made explicitly.
- WCSS parser/cascade support matrix defined before coding.

Requirements observed:
- Caching model updates, USSD transport profile, pictogram semantics, persistent storage API, and EFI model each add significant independent scope.
Spec:
- WAP-120, WAP-204*, WAP-213*, WAP-227, WAP-231
Current posture:
- transport-specific adjuncts are deferred/out-of-scope unless promoted; WAP-120 caching is separately mandatory in the selected WAE user-agent profile.
Scope rationale:
- WAP-120 is outside transport ownership, but its five selected user-agent rows are active compliance work under WAE-603.
- WAP-204 is deferred because GSM/USSD bearer behavior depends on carrier/tunnel-specific adaptation and is maintained as transport-adjacent context.
- WAP-213 is deferred because pictogram/render adjunct behavior is UX/display-specific and outside protocol-loop ownership.
- WAP-227/WAP-231 are deferred because persistence and EFI hooks create separate lifecycle and storage guarantees not yet in transport core scope.
AC for future enablement:
- Each capability activated only via explicit ticket with contract updates and test scope.

This review closes source-material ambiguity for out-of-scope domains; deferral is explicit and documented.
No implementation commitments are created by this document.