Operator Stream — Changelog
Authoritative artefact: this PR — documentation PR #75.
- Operator runbook at
process/sre/runbooks/amazon-creators-api-onboarding.mdcovering the end-to-end onboarding flow:- Account Holder persona: Creators API registration prerequisites, eligibility rules,
Arda CardsApplication creation, secure credential handover to devOps. No engineering assistance required. - devOps persona: per-partition 1Password vault provisioning (
Arda-{Dev,Stage,Demo,Prod}OAM, item titleAmazon Creators API, four fields), accessibility verification,amm.ymldeploy pipeline trigger per partition, per-partition smoke-test, end-to-end rollout choreography. - Ongoing operations: eligibility-loss monitoring (annual sales requirement, sponsored-affiliate-content rule), credential rotation, quota awareness (1 TPS per credential triple, 8640 calls/day).
- Account Holder persona: Creators API registration prerequisites, eligibility rules,
- BFF API reference page for
/api/amazon/import: request schema, response shape, error matrix (AUTHENTICATION_REQUIRED,INVALID_REQUEST,UNRECOGNIZED_AMAZON_URL,UNSUPPORTED_SHORT_LINK,UNSUPPORTED_AMAZON_LOCALE,AMAZON_RATE_LIMITED,AMAZON_UPSTREAM_UNAVAILABLE,INTERNAL_ERROR), authentication requirements, HTTP-status semantics (200 vs 206). - Project planning artefacts at
roadmap/in-progress/amazon-client-integration/(nowroadmap/completed/):goal.md,context-exploration.md,phases.md, four per-stream2-implementation/<stream>/task-plan.md, and3-deployment/deployment-plan.md.
Fixed (review-driven scope expansions inside the same PR)
Section titled “Fixed (review-driven scope expansions inside the same PR)”- Secrets-vault reference page clarified the
Arda-{Env}OAMpartition-vault convention (one vault per environment, scoped by usage rather than by uniqueness) and distinguished it from the workspace-wideArda-SystemsOAMvault (system-level secrets only). Required because the operator runbook references the partition vaults as the canonical source-of-truth. - Operator runbook documented the
OP_SERVICE_ACCOUNT_TOKENGitHub Org secret required byamm.yml, including required vault scope across all four partition vaults plusArda-SystemsOAM, a per-vault verification command, and rotation guidance. Added a matching Gate 1c to the deployment plan’s pre-deploy gates table. - Operator runbook § 9 (
Alpha001/prodregion) clarified thatus-east-2is auto-selected byamm.ymlin CI viapurpose-configuration-action, but localamm.shinvocations require an explicit--region us-east-2flag (the script does not auto-detect outside CI). Added a one-line example. (Subsequently subsumed by PDEV-452, which makesamm.shregion-aware end-to-end — the manual-flag guidance is preserved as a historical note for older script versions.) - BFF API reference and project goal corrected to reflect the proxy/adaptor framing: nullable fields, HTTP 206 for partial responses,
INVALID_REQUESTerror code added.
Project lifecycle (this PR)
Section titled “Project lifecycle (this PR)”- Project moved from
roadmap/in-progress/amazon-client-integration/toroadmap/completed/amazon-client-integration/(this commit). - Project-level
completion-report.mdauthored at the new location. - Per-stream
byproducts/subdirectories added for all four streams. phases.mdstatus table updated from “Drafted / Pending” to “Complete” with merged-PR cross-references.
Copyright: © Arda Systems 2025-2026, All rights reserved