@@ -38,7 +38,7 @@ Every store, verified against actual usage rather than intent.
 |---|---|
 | `RequestLogStore` | `request_log` |
 | `RequestSummaryStore` | `request_summary` |
-| `RequestQueueSummaryStore` | `request_summary_by_queue` |
+| `RequestReceiptStore` | `request_receipt` |
 | `RequestURIStore` | `change_uri_request_mapping` |
 
 | Orchestrator | Table |
 
@@ -91,7 +91,7 @@ The key supports authoritative lookup and conditional status updates for one req
 
 The immutable `request_receipt` lookup contains only `(queue, received_at_ms, request_id)` as its primary key and supports a bounded descending scan over `(received_at_ms, request_id)`. Request IDs break timestamp ties in string order, not numeric order. A backend may use a reverse range scan or descending-encode the ordered key components; cursors always carry the original receipt time and request ID.
 
-List resolves these keys through `request_summary` rather than storing response fields in the lookup. The old `request_summary_by_queue` projection still receives writes for rollback, but List no longer reads it.
+List resolves these keys through `request_summary` rather than storing response fields in the lookup. The old `request_summary_by_queue` projection is no longer read or written; its SQL definition is retained only for deployment compatibility until physical retirement.
 
 The logical key covers the `List` queue predicate, receipt-time range, newest-first ordering, and complete keyset cursor in one bounded scan.
 
@@ -109,17 +109,17 @@ The URI is stored in the canonical form received from the validated Land request
 
 ### Land Receipt
 
-After synchronous validation, Land generates the sqid and one receipt timestamp. The gateway persists the authoritative summary in the internal `accepting` state, then publishes the request to the orchestrator. It does not create the URI or queue projections while the request remains `accepting`.
+After synchronous validation, Land generates the sqid and one receipt timestamp. The gateway persists the authoritative summary in the internal `accepting` state, then publishes the request to the orchestrator. It does not create the URI or receipt mappings while the request remains `accepting`.
 
-After publication succeeds, Land appends the initial `accepted` request log. Materializing `accepted`, `started`, or any later lifecycle state promotes the authoritative summary out of `accepting`, creates the URI and legacy queue projections, and ensures the receipt lookup key exists. This handles the race where the orchestrator emits `started` before Land finishes persisting `accepted`.
+After publication succeeds, Land appends the initial `accepted` request log. Materializing `accepted`, `started`, or any later lifecycle state promotes the authoritative summary out of `accepting`, ensures each immutable URI mapping, then ensures the receipt lookup key exists. This handles the race where the orchestrator emits `started` before Land finishes persisting `accepted`.
 
 An `accepted` event is the lowest public lifecycle state. A late `accepted` event is retained in request history but must not replace `started` or any later materialized status.
 
 Pipeline publication is the Land success boundary. If publication fails, Land returns an error and leaves the hidden `accepting` receipt for operational cleanup. If publication succeeds but appending or materializing `accepted` fails, Land still returns the sqid because retrying the RPC would submit a duplicate request that is already in the pipeline. A later pipeline event activates and repairs the public projections.
 
 ### Request-Log Materialization
 
-Every gateway request-log persistence path uses the same materialization component. It appends the audit log, compares the incoming entry with the authoritative summary, and conditionally advances the winner. For public summaries, it completes the URI and legacy queue projection writes before ensuring the immutable receipt key, including on unchanged or stale-log retries. Hidden `accepting` summaries remain excluded; a failed receipt write is returned through the existing projection-failure path.
+Every gateway request-log persistence path uses the same materialization component. It appends the audit log, compares the incoming entry with the authoritative summary, and conditionally advances the winner. For public summaries, it idempotently ensures every URI mapping before ensuring the receipt key, including on unchanged or stale-log retries. No mutable response state is copied to lookup tables. Hidden `accepting` summaries remain excluded; lookup-write failures are returned for retry.
 
 The winner comparison preserves the existing current-status reconciliation behavior:
 
@@ -172,7 +172,9 @@ CD must roll out the additive table and receipt writers to all instances before
 
 There is no historical backfill or fallback to the legacy queue projection. Requests without receipt keys are absent from List, even if their old queue-summary rows remain. Later log activity can create missing receipt keys.
 
-Keep legacy projection writes during the rollback window; reverting the read cutover restores the old List path. Once stable, a follow-up stops duplicate projection writes and removes `RequestQueueSummary` and its store. Retire `request_summary_by_queue` after the rollback window. The final model keeps one full projection plus immutable lookup keys.
+After the read cutover is stable, deploy the cleanup that stops duplicate writes and removes `RequestQueueSummary` and its store. Rollback remains safe to the receipt-based reader with dual writes; reverting to the old List reader is no longer safe once duplicate writes stop, because the old table is stale and missing newer requests. Restoring that reader would also require restoring writers and reconciling missed data.
+
+Keep the legacy SQL table definition through code rollout and the rollback window. Physical retirement is a separate internal schema change after all old binaries are gone. UQL's table-level `DEPRECATED` annotation initiates retirement (rename in MySQL, potentially immediate drop in Vitess), so do not add it as part of this code cleanup. See the [gateway schema retirement notes](../../../submitqueue/gateway/extension/storage/mysql/schema/README.md#legacy-table-retirement). The final model keeps one full projection plus immutable lookup keys.
 
 ## Rejected Alternatives
 
 
@@ -57,26 +57,6 @@ type RequestSummary struct {
 	Metadata map[string]string
 }
 
-// RequestQueueSummary is a queue-ordered copy of a public request summary.
-type RequestQueueSummary struct {
-	// RequestID is the canonical decimal request identifier, unique within Queue.
-	RequestID string
-	// Queue is the queue supplied at receipt.
-	Queue string
-	// ChangeURIs are the change URIs supplied at receipt in caller order.
-	ChangeURIs []string
-	// ReceivedAtMs is the immutable receipt timestamp in Unix milliseconds.
-	ReceivedAtMs int64
-	// Status is the current customer-facing request status.
-	Status RequestStatus
-	// Version is copied from the authoritative RequestSummary and guards stale projection writers.
-	Version int32
-	// LastError is the error associated with the current status, or empty when absent.
-	LastError string
-	// Metadata is display and debugging metadata associated with the current status.
-	Metadata map[string]string
-}
-
 // RequestURI maps one change URI to one received request.
 type RequestURI struct {
 	// ChangeURI is the exact canonical URI supplied at receipt.
 
@@ -11,7 +11,6 @@ go_library(
         "queue_batch_state_store.go",
         "request_batch_store.go",
         "request_log_store.go",
-        "request_queue_summary_store.go",
         "request_receipt_store.go",
         "request_store.go",
         "request_summary_store.go",
 
@@ -11,7 +11,6 @@ go_library(
         "queue_batch_state_store_mock.go",
         "request_batch_store_mock.go",
         "request_log_store_mock.go",
-        "request_queue_summary_store_mock.go",
         "request_receipt_store_mock.go",
         "request_store_mock.go",
         "request_summary_store_mock.go",
 
@@ -36,7 +36,6 @@ import (
 	"github.com/uber/submitqueue/submitqueue/entity"
 	"github.com/uber/submitqueue/submitqueue/extension/queueconfig"
 	qcmock "github.com/uber/submitqueue/submitqueue/extension/queueconfig/mock"
-	basestorage "github.com/uber/submitqueue/submitqueue/extension/storage"
 	storagemock "github.com/uber/submitqueue/submitqueue/extension/storage/mock"
 	requestcore "github.com/uber/submitqueue/submitqueue/gateway/core/request"
 	gwstoragemock "github.com/uber/submitqueue/submitqueue/gateway/extension/storage/mock"
@@ -347,7 +346,6 @@ func TestLand_PublishesToQueue(t *testing.T) {
 	var receiptSummary entity.RequestSummary
 	var materializedSummary entity.RequestSummary
 	var persistedMapping entity.RequestURI
-	var persistedQueueSummary entity.RequestQueueSummary
 	var persistedReceipt entity.RequestReceipt
 	var persistedLog entity.RequestLog
 
@@ -359,10 +357,8 @@ func TestLand_PublishesToQueue(t *testing.T) {
 	store := gwstoragemock.NewMockStorage(ctrl)
 	summaryStore := storagemock.NewMockRequestSummaryStore(ctrl)
 	uriStore := storagemock.NewMockRequestURIStore(ctrl)
-	queueStore := storagemock.NewMockRequestQueueSummaryStore(ctrl)
 	receiptStore := storagemock.NewMockRequestReceiptStore(ctrl)
 	logStore := storagemock.NewMockRequestLogStore(ctrl)
-	store.EXPECT().GetRequestQueueSummaryStore().Return(queueStore).AnyTimes()
 	store.EXPECT().GetRequestReceiptStore().Return(receiptStore).AnyTimes()
 	store.EXPECT().GetRequestSummaryStore().Return(summaryStore).AnyTimes()
 	store.EXPECT().GetRequestLogStore().Return(logStore).AnyTimes()
@@ -404,23 +400,12 @@ func TestLand_PublishesToQueue(t *testing.T) {
 				return nil
 			},
 		),
-		queueStore.EXPECT().Get(gomock.Any(), gomock.Any(), "123").DoAndReturn(
-			func(context.Context, int64, string) (entity.RequestQueueSummary, error) {
-				return entity.RequestQueueSummary{}, basestorage.ErrNotFound
-			},
-		),
 		uriStore.EXPECT().Create(gomock.Any(), gomock.Any()).DoAndReturn(
 			func(_ context.Context, mapping entity.RequestURI) error {
 				persistedMapping = mapping
 				return nil
 			},
 		),
-		queueStore.EXPECT().Create(gomock.Any(), gomock.Any()).DoAndReturn(
-			func(_ context.Context, summary entity.RequestQueueSummary) error {
-				persistedQueueSummary = summary
-				return nil
-			},
-		),
 		receiptStore.EXPECT().Create(gomock.Any(), gomock.Any()).DoAndReturn(
 			func(_ context.Context, receipt entity.RequestReceipt) error {
 				persistedReceipt = receipt
@@ -470,15 +455,6 @@ func TestLand_PublishesToQueue(t *testing.T) {
 		ReceivedAtMs: receiptSummary.ReceivedAtMs,
 		RequestID:    "123",
 	}, persistedMapping)
-	assert.Equal(t, entity.RequestQueueSummary{
-		RequestID:    "123",
-		Queue:        "test-queue",
-		ChangeURIs:   []string{"github://github.example.com/uber/backend/pull/456/fedcba9876543210fedcba9876543210fedcba98"},
-		ReceivedAtMs: receiptSummary.ReceivedAtMs,
-		Status:       entity.RequestStatusAccepted,
-		Version:      2,
-		Metadata:     map[string]string{},
-	}, persistedQueueSummary)
 
 	// Verify message was published to the topic registered under TopicKeyStart
 	assert.Equal(t, "start", publishedTopic)