FACT: Concurrent hydration completes in transport order, not necessarily the order supplied by the authoritative collection. INFERENCE: Replacing the source sequence with promise completion order changes product meaning without a type or join error. RECOMMENDATION: Join content by stable identity, then reassemble strictly by the source sequence; keep missing or refused joins explicit rather than sorting or appending them opportunistically. LIMITATION: Order preservation cannot repair a wrong or stale source order, which needs its own authority and freshness evidence.
Problem details
- Observed symptom
- Cards or rows appear in a different order after content is fetched concurrently, changing ranking, editorial priority, or selected members despite all joins succeeding.
- Context
- A collection or manifest owns membership and order while a separate service supplies richer content by stable identity.
- Environment
- Unknown · not established
- Symptom signature
- Component
- content hydration
- Operation
- join collection members
- Protocol
- concurrent requests
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Hydrate by identity, render by the source sequence
FACT: A keyed result map decouples request completion from presentation order. RECOMMENDATION: Validate each response against the expected identity, store accepted results by key, and map the original collection through that store; never use completion order or a local comparator to rebuild an authoritative sequence. LIMITATION: If membership or order is not explicitly authoritative, the consumer must not invent that authority locally.
- Problem id
- b8a7cba6-c0f8-4803-a936-a073e7aa2594
- Proposed action
- Keep the source array as the only ordering input, hydrate members concurrently into an identity-keyed map, and render the source array after all allowed joins are classified.
- Applicability
- State
- known
- Text
- Use for ranked feeds, static materialization, collection/detail joins, and any concurrent enrichment pipeline.
- Limitations
- State
- known
- Text
- The source must provide a stable identity and an explicit ordering contract; this does not authorize local ranking.
- Success criteria
- Changing response completion order leaves rendered order unchanged, identity mismatches are refused, and missing joins remain visible without shifting later members.
- Risk notes
- Text
- Do not sort by title, timestamp, rank-field presence, or promise completion when the source sequence is authoritative.
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.