Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a connector for a customer-style system and create the production rollout package around it. Requirements: (1) authenticate with least privilege; (2) sync incrementally with a cursor and stable source IDs; (3) validate a typed schema and route bad records to a visible error path; (4) make writes or upserts idempotent; (5) handle retries, rate limits, and timeouts; (6) expose health metrics such as last success, sync lag, processed records, failed records, and API errors; (7) write a release plan with feature flag/canary or shadow mode, health checks, rollback, and customer communication.
Least-privilege auth, incremental sync, stable IDs, schema validation, idempotency, retry/backoff, and rate-limit behavior are implemented or convincingly simulated.
Health metrics, failed-record handling, logs, dashboards or dashboard-ready outputs, and troubleshooting notes make failures visible and recoverable.
Rollout plan includes approver, blast-radius control, feature flag/canary or shadow mode, validation checks, rollback, and clear customer communication.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A production-grade connector and rollout plan ## Goal Build a connector for a customer-style system and create the production rollout package around it. Requirements: (1) authenticate with least privilege; (2) sync incrementally with a cursor and stable source IDs; (3) validate a typed schema and route bad records to a visible error path; (4) make writes or upserts idempotent; (5) handle retries, rate limits, and timeouts; (6) expose health metrics such as last success, sync lag, processed records, failed records, and API errors; (7) write a release plan with feature flag/canary or shadow mode, health checks, rollback, and customer communication. ## Acceptance criteria - [ ] Connector correctness: Least-privilege auth, incremental sync, stable IDs, schema validation, idempotency, retry/backoff, and rate-limit behavior are implemented or convincingly simulated. - [ ] Operational visibility: Health metrics, failed-record handling, logs, dashboards or dashboard-ready outputs, and troubleshooting notes make failures visible and recoverable. - [ ] Release discipline: Rollout plan includes approver, blast-radius control, feature flag/canary or shadow mode, validation checks, rollback, and clear customer communication. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.