Weather Fusion
Combine product availability and selected weather into a client-facing view while retaining provenance.
| Contract card | Current state |
|---|---|
| Owner | Weather service / native Weather Fusion |
| Version boundary | Existing aggregate and client selection models |
| Current consumers | Java FusedWeatherData; Swift Weather Fusion |
| Source | apps/ios/Weather/Package/Sources/Weather/Fusion/WeatherFusion.swift |
| Validator / acceptance entry | apps/ios/Weather/Package/Tests/WeatherTests/Models/FusedWeatherDataTests.swift |
| Fixtures / specimen | Shared public corpus pending |
Adopt this model
Keep aggregate DTOs and the client selection/cache layer distinct. server/fusion is a dataset catalog, not this weather model owner.
Identity, units and meaning
A fused snapshot needs product-specific times, source identity, selection/freshness policy and partial state.
Failure and partial states
Aggregate existence is not complete weather. Native and service Swift model copies need an ownership/conformance audit.
Continue to the guide · Model conventions · Release notes
Source paths identify owners in the source checkout; they are not public repository links. A listed test is an acceptance entry, not a claim that every consumer has passed a shared corpus.