Status Unknown

Owner: Module 18 status app watches; Module 01 owns runtime response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors.

Owner: Module 18 status app watches; Module 01 owns runtime response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors.

Owner: Module 18 status app watches; Module 03 owns runtime response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors.

Owner: Module 18 status app watches; Module 12 owns held-lead response. | Retry: Application-level held-lead retry sweep is explicit; platform Lambda/EventBridge retry and DLQ config remain unknown in repo evidence. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, both EventBridge rules, and recent Lambda Errors; broker held-lead queues remain an app/admin surface.

Owner: Module 18 status app watches; Module 08 owns send/render response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors; no-op/send proof still comes from job logs.

Owner: Module 18 status app watches; Module 13 owns compliance/send response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors; dry-run/send proof remains job-log evidence.

Owner: Module 18 status app watches; Module 14 owns data freshness response. | Retry: Handler serves cached last-good values on provider/data failures; platform Lambda/EventBridge retry and DLQ config remain unknown in repo evidence. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors; /mortgage-rates smoke proves user-facing fallback.

Owner: Module 18 status app watches; Module 04 owns notification response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, all EventBridge notification rules, and recent Lambda Errors; send correctness still needs dry-run/preview evidence.

Owner: Module 18 status app watches; Module 04 owns digest response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, EventBridge rule state, and recent Lambda Errors; send correctness still needs preview evidence.

Owner: Module 18 status app watches; Module 13 owns DBPR data response. | Retry: Handler raises unrecoverable failures so Lambda/EventBridge can surface retries/errors; exact platform retry and DLQ config remain unknown in repo evidence. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, weekly EventBridge rule state, and recent Lambda Errors; sync-log/SNS evidence proves data freshness.

Owner: Module 18 status app watches; Module 13 owns DBPR trades response. | Retry: Unknown/pending because exact live role, DLQ, and retry config are explicitly not in idx-api Terraform state. | DLQ: Unknown/pending; aws-idx-api/terraform/dbpr_trades.tf says exact live role/DLQ/schedule are not in this state. | Health: Status app checks Lambda state, weekly EventBridge rule state, and recent Lambda Errors; sync-log evidence proves data freshness.

Owner: Module 18 status app watches; Module 13 owns contractor data response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks Lambda state, weekly EventBridge rule state, and recent Lambda Errors; sync-log evidence proves data freshness.

Owner: Module 18 owns runtime and status response. | Retry: EventBridge/Lambda retry and DLQ configuration not confirmed in repo; treat as unknown until AWS audit proves it. | DLQ: No DLQ is cataloged for this runtime in the current repo evidence. | Health: Status app checks cron-runner Lambda state, EventBridge rule state, and recent Lambda Errors; generatedAt freshness proves end-to-end writes.

Owner: Module 18 status app watches; Module 08 owns render queue response. | Retry: SQS redrives failed render messages after maxReceiveCount=3 before DLQ; worker image rollback is the first recovery path. | DLQ: idx-api-reels-dlq is monitored by a separate status row; visible messages should stay at 0. | Health: Status app checks ECS service ACTIVE with desired tasks running; DLQ row checks queue failures separately.

Owner: Module 18 status app watches; Module 08 owns redrive/root-cause response. | Retry: Main queue redrives to this DLQ after maxReceiveCount=3; failures need worker fix before redrive/drain. | DLQ: This row is the idx-api-reels-dlq monitor; nonzero visible messages are degraded. | Health: Status app checks CloudWatch SQS ApproximateNumberOfMessagesVisible over the recent metric window.

Owner: Module 18 status app watches queue state; 3D Tours lane owns job response and spend gates. | Retry: Batch job definition retries once on EC2 host reclamation; SQS intake redrives after maxReceiveCount=5 per infra/tour-recon, but DLQ status row is pending. | DLQ: retm-tour-recon job intake DLQ is authored in infra/tour-recon as ${queue_name}-dlq; public status row is pending live/queue-name verification. | Health: Status app checks Batch queue ENABLED/VALID; intake DLQ and per-job progress remain pending/route surfaces.