payments-api

Proactive drift-scan cycle. Reads all active OBCs and Issues, identifies divergences, and repairs what can be automated. Runs across the entire active backlog, not for a specific OBC.

Read all active OBCs and compare declared state with backlogs and external tools. Produces a divergence list. Does not repair — only identifies gaps.

Event-driven cycle triggered by a product decision. Captures the decision as an OBC, attaches a Work Item, promotes it through the backlog hierarchy, and closes it when the OBC reaches Operational. Runs for a specific OBC.

Create or update an OBC from the decision that triggered the Diligence Sync cycle. Use when an Assessment decision, Discovery experiment, or Operation signal requires canonical state to be recorded before Work Items are created.

Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.

Classify divergences from Scan and register them as pending Diligence items with severity and corrective action. Does not repair — only signals.

Execute corrections identified by Flag — update OBCs, create missing Work Items, close orphaned ones. Never touches product code or creates implementation PRs.

Verify or create a Work Item in the external backlog referencing the OBC, operation, and journey. Use after Capture has stabilized the canonical OBC state.

Execute implementation work with TDD. Use when changing code, behavior, contracts, tests, or release artifacts as part of a ProdOps-backed task.

Execute ProdOps exploratory engineering. Use when exploring, experimenting, implementing disposable code, creating endpoints or integrations, updating contracts, building prototypes, validating hypotheses, refining OBCs, preparing BDDs, updating Reliability Plan or Event Storming, updating the Validation Workbench, or turning uncertainty into Downstream-ready work.

Fazer deploy de uma branch de experimento em um ambiente de sandbox real na nuvem, sem o rigor Downstream. Use quando um experimento precisa validar comportamento contra um provedor externo real que não pode ser exercitado localmente.

Execute the ProdOps TDD cycle. Use after bootstrap to implement a behavior change through red, green, and yellow phases.

Close the Work Item when the OBC reaches Operational state and update management artifacts. Use when the Release Trail confirms the delivery is complete.

Advance an OBC through the backlog hierarchy (Icebox → Iteration Backlog → Iteration Plan), checking prerequisites at each transition. Use after Attach has confirmed a Work Item exists.

Orchestrate Inspect → Reconcile → Verify to align the GitHub Workspace with the Canonical Specification. Entry point for any caller (Bootstrap, Diligence Async, Diligence Sync). Never runs standalone as a third cycle.

Read the Canonical Specification and the Actual Workspace state via GitHub API. Produce a Drift Report. Does not create or update anything.

Create or update Labels, Template project, and Managed project to match the Canonical Specification. Tries every API path. On API failure, creates a tracking Issue. Never leaves a gap without a trail entry. Never touches manual projects. Idempotent.

Confirm that the GitHub repository state matches the Canonical Specification across all 4 categories. Reads Views via GraphQL. Updates the sync manifest with the verified conformance state. Produces the Conformance Report.

Guide committed work to readiness and execute CI Sync, CI Async, or the full governed ProdOps delivery flow.

Approve and close a release stage. Use when moving a release forward after validation, quality gates, and operational readiness are complete.

Prepare deploy, pull request, or release readiness. Use when packaging completed work for review, release, deployment, handoff, final quality gates, TDD evidence review, security checks, or PR preparation.

Synchronize a work branch with its base or align ProdOps artifacts with the current implementation. Use when fetching remote changes, resolving conflicts, updating from main, or when BDD Features, Event Storming, architecture, or the Release Trail are stale.

Align ProdOps artifacts with the current implementation. Use when BDD Features, Event Storming, architecture diagrams, or the Release Trail are stale relative to what was implemented in Hack.

Promote a completed upstream experiment to the Downstream delivery flow. Use after the Decision Package is complete and the Product Manager + Tech Lead have approved the capability for delivery.

Validate release behavior with evidence, metrics, SLOs, and operational signals. Use when proving that an OBC, BDD scenario, or Reliability Plan item is satisfied.

Validate, debug, and modify this repository's payment sandbox without drifting from existing architecture. Use when Codex needs to run the payments-api backend and Vite Validation Workbench, build or inspect payment payloads, validate POST /invoices or POST /payments, diagnose CORS/provider/storage failures, update prompts/skill metadata, or make changes that must follow the repo's NestJS, event, provider, storage, testing, and Vite patterns.

Close technical work with quality gates. Use before considering a task complete, especially after implementation or artifact updates.

Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.

Execute ProdOps Downstream readiness and CI Sync, CI Async, or the complete delivery flow.

Execute implementation work with TDD. Use when changing code, behavior, contracts, tests, or release artifacts as part of a ProdOps-backed task.

Execute ProdOps exploratory engineering. Use when exploring, experimenting, implementing disposable code, creating endpoints or integrations, updating contracts, building prototypes, validating hypotheses, refining OBCs, preparing BDDs, updating Reliability Plan or Event Storming, updating the Validation Workbench, or turning uncertainty into Downstream-ready work.

Prepare the local environment required by a ProdOps execution before Git flow, tests, or implementation begin.

Prepare a governed ProdOps Delivery task before implementation. Use when starting Downstream work to verify context, branch, environment, and required artifacts before Hack.

Close technical work with quality gates. Use before considering a task complete, especially after implementation or artifact updates.

Approve and close a release stage. Use when moving a release forward after validation, quality gates, and operational readiness are complete.

Prepare deploy, pull request, or release readiness. Use when packaging completed work for review, release, deployment, handoff, final quality gates, TDD evidence review, security checks, or PR preparation.

Synchronize a work branch with its base or align ProdOps artifacts with the current implementation. Use when fetching remote changes, resolving conflicts, updating from main, or when BDD Features, Event Storming, architecture, or the Release Trail are stale.

Validate release behavior with evidence, metrics, SLOs, and operational signals. Use when proving that an OBC, BDD scenario, or Reliability Plan item is satisfied.

Stage and commit completed implementation work. Use after tests are green, lint is clean, and the Release Trail has been updated.

Synchronize the feature branch with its base. Use when the branch is behind origin, has conflicts to resolve, or needs to incorporate upstream changes before Finish.