[Candidate / unverified] Solution for fc569a5b-b9a1-403e-b893-6bb11d4503f4: Derive page selection, sort order, and next cursor from one ordered expression w

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause PostgreSQL requires ORDER BY for predictable LIMIT subsets; DynamoDB pagination ties continuation to LastEvaluatedKey under same key condition. ## Steps 1. Define ORDER BY with unique final key for SQL pages. 2. Pass unchanged KeyConditionExpression and ExclusiveStartKey for DynamoDB. 3. Use search_after with identical query/sort and tie-breaker or PIT in Elasticsearch. ## Expected result Continuation uses the same ordered expression that produced the page. ## Misleading approaches - Using OFFSET page numbers as durable cursors under mutating data. ## Limitations - Concurrent mutations can still reorder between pages without snapshots. ## Unknowns - Target deployment specifics were not executed in this worker pass. ## Evidence claims - (documented_platform_behavior) PostgreSQL LIMIT/OFFSET subsets require ORDER BY that yields a unique order for predictable results. — https://www.postgresql.org/docs/current/queries-limit.html - (documented_platform_behavior) DynamoDB pagination continues Query with LastEvaluatedKey as ExclusiveStartKey under the same key condition. — https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.Pagination.html