CLI reference¶

This document is intentionally concise and auto-generated from the current argparse tree. For guided workflows and examples, see CLI examples and DAG debugging.

For pre-source-IO route checks, see Route capability certification.

For Airflow cache promotion, recovery, retention, output schemas, and exit codes, see the cache sync and recovery runbook. Cache mutation commands return 0 on success, 1 on an operational/recovery failure, 2 for invalid CLI usage, and 4 for a rejected safety policy or missing confirmation.

Use:

dpone docs update-cli-reference
dpone docs update-cli-reference --check

This section is auto-generated by dpone docs update-cli-reference.

`dpone doctor`¶

Usage: dpone doctor [--profile {local,ci,production}] [--format {text,json,md}]
Options:
--profile PROFILE
--format FORMAT

`dpone init`¶

Usage: dpone init [--format {text,json,md}] [--source-type SOURCE_TYPE] [--sink-type SINK_TYPE] [--source-connection SOURCE_CONNECTION] [--sink-connection SINK_CONNECTION] [--source-schema SOURCE_SCHEMA] [--source-table SOURCE_TABLE] [--target-schema TARGET_SCHEMA] [--target-table TARGET_TABLE] [--unique-key UNIQUE_KEY] [--out OUT] [--strategy STRATEGY] [{project,domain,pipeline}] ...
Options:
--format FORMAT
--source-type SOURCE_TYPE
--sink-type SINK_TYPE
--source-connection SOURCE_CONNECTION
--sink-connection SINK_CONNECTION
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-schema TARGET_SCHEMA
--target-table TARGET_TABLE
--unique-key UNIQUE_KEY
--out OUT
--strategy STRATEGY

`dpone init project`¶

Usage: dpone init project [--airflow] [--format {text,json,md}] [--layout {flat,domain-first}]
Options:
--airflow — Include Airflow files
--format FORMAT
--layout LAYOUT — Project authoring layout (default: flat compatibility)
Output and exit contract:
0: bounded result on stdout; stderr is empty.
1: validation or conflict result on stdout; stderr is empty.
2: structured application config error on stdout, or argparse syntax error on stderr.
4: structured security or safety violation on stdout; stderr is empty.
JSON failure entries conform to dpone.error.v1.

`dpone init domain`¶

Usage: dpone init domain --owner-team OWNER_TEAM --owner-contact OWNER_CONTACT --approver-team APPROVER_TEAM [--format {text,json,md}] name
Positional arguments:
name — Canonical domain id
Options:
--owner-team OWNER_TEAM — Owning team
--owner-contact OWNER_CONTACT — Owner contact
--approver-team APPROVER_TEAM — Approving GitHub team
--format FORMAT
Output and exit contract:
0: bounded result on stdout; stderr is empty.
1: validation or conflict result on stdout; stderr is empty.
2: structured application config error on stdout, or argparse syntax error on stderr.
4: structured security or safety violation on stdout; stderr is empty.
JSON failure entries conform to dpone.error.v1.

`dpone init pipeline`¶

Usage: dpone init pipeline [--airflow | --no-airflow] [--recipe RECIPE | --route ROUTE] [--profile PROFILE] [--answers ANSWERS] [--authoring {classic,flow,folder}] [--domain DOMAIN] [--from FROM_LOCATOR] [--to TO_LOCATOR] [--key UNIQUE_KEY] [--format {text,json,md}] name
Positional arguments:
name — Pipeline name
Options:
--airflow — Include Airflow self-service files
--no-airflow — Do not include this pipeline in Airflow
--recipe RECIPE — Built-in id or exact external recipe ref (id@MAJOR.MINOR.PATCH)
--route ROUTE — Scaffoldable source:sink:strategy route
--profile PROFILE — Exact external recipe profile ref (id@MAJOR.MINOR.PATCH)
--answers ANSWERS — Project-confined declarative YAML recipe answers
--authoring AUTHORING — Primary authoring mode (default: flow)
--domain DOMAIN — Domain id for domain-first projects
--from FROM_LOCATOR — Source locator: connection_ref:schema.table
--to TO_LOCATOR — Sink locator: connection_ref:schema.table
--key UNIQUE_KEY — Unique key for merge recipes
--format FORMAT
Output and exit contract:
0: bounded result on stdout; stderr is empty.
1: validation or conflict result on stdout; stderr is empty.
2: structured application config error on stdout, or argparse syntax error on stderr.
4: structured security or safety violation on stdout; stderr is empty.
JSON failure entries conform to dpone.error.v1.

`dpone plan`¶

Usage: dpone plan [--selector SELECTOR] [--apply-safe-schema] [--explain-strategy] [--format {text,json,md}] path
Positional arguments:
path
Options:
--selector SELECTOR
--apply-safe-schema
--explain-strategy
--format FORMAT

`dpone run`¶

Usage: dpone run [--selector SELECTOR] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] [--interval-start INTERVAL_START] [--interval-end INTERVAL_END] [--retry-attempts RETRY_ATTEMPTS] [--retry-backoff-seconds RETRY_BACKOFF_SECONDS] [--registry REGISTRY] [--sample SAMPLE] [--target {temporary}] [--select EXPR] [--exclude EXPR] [--state STATE] [--selectors SELECTORS] [--max-selected MAX_SELECTED] [--environment ENVIRONMENT] [--format {text,json,md}] path
Positional arguments:
path — YAML manifest path; safe-sample mode also accepts a canonical pipeline ID or directory
Options:
--selector SELECTOR — Process selector inside a batch manifest
--run-id RUN_ID — Explicit run id; defaults to process name
--dag-id DAG_ID — Run-state identity; defaults to DPONE_DAG_ID
--execution-date EXECUTION_DATE — Logical date (ISO-8601); defaults to DPONE_LOGICAL_DATE
--interval-start INTERVAL_START — Data interval start (ISO-8601); defaults to DPONE_INTERVAL_START
--interval-end INTERVAL_END — Data interval end (ISO-8601); defaults to DPONE_INTERVAL_END
--retry-attempts RETRY_ATTEMPTS — Retry failed process results this many times
--retry-backoff-seconds RETRY_BACKOFF_SECONDS — Sleep between failed attempts; defaults to no backoff
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--sample SAMPLE — Phase 1B safe sample row budget
--target TARGET — Phase 1B safe-run target policy
--select EXPR — Advanced: filter workloads (see Workload selectors docs)
--exclude EXPR — Advanced: exclude workloads after selection expansion
--state STATE — Advanced: local dpone.selection-state.v1 baseline for state:* selectors
--selectors SELECTORS — Advanced: named selector file (default: selectors.yaml)
--max-selected MAX_SELECTED — Advanced: hard selected workload limit (default: 10)
--environment ENVIRONMENT — Safe sample policy environment; defaults to development
--format FORMAT

`dpone test`¶

Usage: dpone test [--format {text,json,md}] [--output OUTPUT] target
Positional arguments:
target — Test file, pipeline id/path, or project root
Options:
--format FORMAT
--output OUTPUT — Atomically create a complete report or verify an identical one

`dpone resync`¶

Usage: dpone resync --run-id RUN_ID --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--partition PARTITION] [--artifact-dir ARTIFACT_DIR] [--yes] [--live-backend] [--connection-id CONNECTION_ID] [--connection-type {env,vault,airflow,params}] [--target-schema TARGET_SCHEMA] [--target-table TARGET_TABLE] [--staging-schema STAGING_SCHEMA] [--mount-point MOUNT_POINT] [--connection-path CONNECTION_PATH] [--format {text,json,md}]
Options:
--run-id RUN_ID
--source-type SOURCE_TYPE
--sink-type SINK_TYPE
--strategy STRATEGY
--partition PARTITION
--artifact-dir ARTIFACT_DIR
--yes — Mark replay as approved for execution
--live-backend — Execute through runtime SQL/Kafka replay backend when combined with --yes
--connection-id CONNECTION_ID — Target sink connection id used by the runtime replay backend
--connection-type CONNECTION_TYPE — Credential provider for --connection-id
--target-schema TARGET_SCHEMA — Target schema/database for DB replay backends
--target-table TARGET_TABLE — Target table or Kafka topic for live replay
--staging-schema STAGING_SCHEMA — Staging schema/database for DB replay backends
--mount-point MOUNT_POINT — Vault mount point when --connection-type vault is used
--connection-path CONNECTION_PATH — Vault path or provider-specific credential path
--format FORMAT

`dpone resume`¶

Usage: dpone resume [--from-stage FROM_STAGE] --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--artifact-dir ARTIFACT_DIR] [--yes] [--live-backend] [--connection-id CONNECTION_ID] [--connection-type {env,vault,airflow,params}] [--target-schema TARGET_SCHEMA] [--target-table TARGET_TABLE] [--staging-schema STAGING_SCHEMA] [--mount-point MOUNT_POINT] [--connection-path CONNECTION_PATH] [--format {text,json,md}] run_id
Positional arguments:
run_id
Options:
--from-stage FROM_STAGE
--source-type SOURCE_TYPE
--sink-type SINK_TYPE
--strategy STRATEGY
--artifact-dir ARTIFACT_DIR
--yes — Mark resume as approved for execution
--live-backend — Execute through runtime SQL/Kafka replay backend when combined with --yes
--connection-id CONNECTION_ID — Target sink connection id used by the runtime replay backend
--connection-type CONNECTION_TYPE — Credential provider for --connection-id
--target-schema TARGET_SCHEMA — Target schema/database for DB replay backends
--target-table TARGET_TABLE — Target table or Kafka topic for live replay
--staging-schema STAGING_SCHEMA — Staging schema/database for DB replay backends
--mount-point MOUNT_POINT — Vault mount point when --connection-type vault is used
--connection-path CONNECTION_PATH — Vault path or provider-specific credential path
--format FORMAT

`dpone run-report`¶

Usage: dpone run-report --run-id RUN_ID --pipeline PIPELINE [--rows ROWS] [--out-dir OUT_DIR] [--format {text,json,md}]
Options:
--run-id RUN_ID
--pipeline PIPELINE
--rows ROWS
--out-dir OUT_DIR
--format FORMAT

`dpone studio`¶

Usage: dpone studio [--host HOST] [--port PORT] [--serve] [--allow-remote] [--cors-origin CORS_ORIGINS] [--format {text,json,md}]
Options:
--host HOST
--port PORT — TCP port from 1 to 65535
--serve — Start the local HTTP API server and block
--allow-remote — Allow a non-loopback development bind with token and exact CORS origins
--cors-origin CORS_ORIGINS — Exact allowed remote UI origin; repeat for multiple origins
--format FORMAT

`dpone certify`¶

Usage: dpone certify [--format {markdown,json}] {routes,self-service,route-capabilities} ...
Options:
--format FORMAT

`dpone certify routes`¶

Usage: dpone certify routes --commit-sha COMMIT_SHA [--evidence-dir EVIDENCE_DIR] --output-dir OUTPUT_DIR [--max-age-hours MAX_AGE_HOURS] [--allow-unverified] [--format {md,json}]
Options:
--commit-sha COMMIT_SHA — Exact source commit expected in release provenance
--evidence-dir EVIDENCE_DIR — Explicit bounded evidence set directory; repeat for independent deployments
--output-dir OUTPUT_DIR — Create-only matrix artifact directory
--max-age-hours MAX_AGE_HOURS — Maximum vendor-live bundle age
--allow-unverified — Exit 0 after publishing when status is UNVERIFIED (still exits non-zero on FAIL)
--format FORMAT

`dpone certify self-service`¶

Usage: dpone certify self-service --commit-sha COMMIT_SHA [--usability-study USABILITY_STUDY] [--reference-deployment REFERENCE_DEPLOYMENT] --output-dir OUTPUT_DIR [--max-age-hours MAX_AGE_HOURS] [--allow-unverified] [--format {md,json}]
Options:
--commit-sha COMMIT_SHA — Exact source commit under study
--usability-study USABILITY_STUDY — Privacy-safe usability study JSON
--reference-deployment REFERENCE_DEPLOYMENT — Explicit bounded production proof directory; repeat for independent deployments
--output-dir OUTPUT_DIR — Create-only certification artifact directory
--max-age-hours MAX_AGE_HOURS — Maximum route proof age
--allow-unverified — Exit 0 after publishing when overall_status is UNVERIFIED (still exits non-zero on FAIL)
--format FORMAT

`dpone certify route-capabilities`¶

Usage: dpone certify route-capabilities --manifest MANIFEST --scenario {preflight_only,small_live,do_14789_kam_mes_sales_benchmark} --output OUTPUT [--run-id RUN_ID] [--selector SELECTOR] [--route ROUTE] [--object-prefix OBJECT_PREFIX] [--keep-artifacts] [--format {md,json}]
Options:
--manifest MANIFEST — Path to a YAML manifest
--scenario SCENARIO
--output OUTPUT — Output directory for certification artifacts
--run-id RUN_ID
--selector SELECTOR
--route ROUTE — Route id to benchmark; repeat for a matrix
--object-prefix OBJECT_PREFIX — Object-storage prefix template with {run_id} and {route_id}
--keep-artifacts
--format FORMAT

`dpone schema-plan`¶

Usage: dpone schema-plan --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--mode {strict,additive,widening}] [--on-type-change {fail,new_column}] [--new-column-prefix NEW_COLUMN_PREFIX] [--ddl-mode {online,safe_window,plan_only,manual_approval}] [--lock-timeout-seconds LOCK_TIMEOUT_SECONDS] [--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS] [--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL] [--apply-safe] [--plan-only] [--allow-drop] [--fail-on-breaking] [--format {text,json}]
Options:
--source SOURCE — Path to source columns JSON
--target TARGET — Path to target columns JSON
--table TABLE — Qualified target table, e.g. dbo.orders
--dialect DIALECT
--mode MODE
--on-type-change ON_TYPE_CHANGE
--new-column-prefix NEW_COLUMN_PREFIX
--ddl-mode DDL_MODE
--lock-timeout-seconds LOCK_TIMEOUT_SECONDS
--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS
--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL
--apply-safe — Alias for documenting runtime parity; CLI remains plan-only
--plan-only — Render plan without applying DDL (default CLI behavior)
--allow-drop
--fail-on-breaking
--format FORMAT

`dpone recipe`¶

`dpone recipe list`¶

Usage: dpone recipe list [--source SOURCE] [--sink SINK] [--strategy STRATEGY] [--format {text,json}]
Options:
--source SOURCE — Filter by source endpoint family
--sink SINK — Filter by sink endpoint family
--strategy STRATEGY — Filter by load strategy
--format FORMAT

`dpone recipe show`¶

Usage: dpone recipe show [--format {text,json}] ref
Positional arguments:
ref
Options:
--format FORMAT

`dpone recipe pin`¶

Usage: dpone recipe pin [--format {text,json}] artifact
Positional arguments:
artifact
Options:
--format FORMAT

`dpone recipe validate`¶

Usage: dpone recipe validate [--format {text,json}]
Options:
--format FORMAT

`dpone check`¶

Usage: dpone check [--connections | --live] [--environment ENVIRONMENT] [--format {text,json}] [--select EXPR] [--exclude EXPR] [--state STATE] [--selectors SELECTORS] [--max-selected MAX_SELECTED] target
Positional arguments:
target — Pipeline id, domain/pipeline shorthand, directory, or pipeline.yaml path
Options:
--connections — Phase 1B connection handshakes
--live — Phase 1B bounded live preflight
--environment ENVIRONMENT — Environment name for binding/registry checks
--format FORMAT
--select EXPR — Advanced: filter workloads (see Workload selectors docs)
--exclude EXPR — Advanced: exclude workloads after selection expansion
--state STATE — Advanced: local dpone.selection-state.v1 baseline for state:* selectors
--selectors SELECTORS — Advanced: named selector file (default: selectors.yaml)
--max-selected MAX_SELECTED — Advanced: hard selected workload limit (default: 1000)
Output and exit contract:
0: bounded check result on stdout; stderr is empty.
1: validation failure with dpone.error.v1 entries on stdout; stderr is empty.
2: structured application config error on stdout, or argparse syntax error on stderr.
3: live dependency unavailable with a structured result on stdout; stderr is empty.
4: structured security or safety violation on stdout; stderr is empty.
5: redacted internal error with trace id on stdout; stderr is empty.

`dpone fix`¶

Usage: dpone fix (--plan | --apply) [--format {text,json}] target
Positional arguments:
target — Pipeline directory or pipeline.yaml path
Options:
--plan — Show the safe authoring-source fix plan
--apply — Apply the safe authoring-source fix plan
--format FORMAT

`dpone cdc-plan`¶

Usage: dpone cdc-plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --schema SCHEMA --table TABLE [--slot-name SLOT_NAME] [--publication-name PUBLICATION_NAME] [--capture-instance CAPTURE_INSTANCE] [--format {text,json}]
Options:
--backend BACKEND
--schema SCHEMA
--table TABLE
--slot-name SLOT_NAME
--publication-name PUBLICATION_NAME
--capture-instance CAPTURE_INSTANCE
--format FORMAT

`dpone backfill`¶

`dpone backfill plan`¶

Usage: dpone backfill plan [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] [--advisor] [--advisor-evidence ADVISOR_EVIDENCE] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT
--advisor — Attach a conservative performance recommendation
--advisor-evidence ADVISOR_EVIDENCE — JSON evidence artifact with load_steps/chunks/matrix_report; can be repeated

`dpone backfill run`¶

Usage: dpone backfill run [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] [--execute] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT
--run-id RUN_ID — Explicit run id; defaults to process name
--dag-id DAG_ID
--execution-date EXECUTION_DATE
--execute — Actually load pending chunks (default: dry-run plan)

`dpone backfill resume`¶

Usage: dpone backfill resume [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT
--run-id RUN_ID — Explicit run id; defaults to process name
--dag-id DAG_ID
--execution-date EXECUTION_DATE

`dpone backfill status`¶

Usage: dpone backfill status [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT

`dpone backfill retry-failed`¶

Usage: dpone backfill retry-failed [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT
--run-id RUN_ID — Explicit run id; defaults to process name
--dag-id DAG_ID
--execution-date EXECUTION_DATE

`dpone backfill cancel`¶

Usage: dpone backfill cancel [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] --reason REASON --requested-by REQUESTED_BY path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT
--reason REASON — Human-readable cancellation reason
--requested-by REQUESTED_BY — Operator or automation requesting cancellation

`dpone backfill doctor`¶

Usage: dpone backfill doctor [--selector SELECTOR] [--column COLUMN] [--from WINDOW_FROM] [--to WINDOW_TO] [--step STEP] [--kind {date,timestamp,integer}] [--inner-mode {partition_replace,replace,incremental_merge,full_refresh}] [--parallel-workers PARALLEL_WORKERS] [--max-chunks MAX_CHUNKS] [--state-dir STATE_DIR] [--backfill-id BACKFILL_ID] [--predicate-dialect {generic,clickhouse,mssql,postgres}] [--registry REGISTRY] [--format {text,json,md}] path
Positional arguments:
path — Path to a YAML manifest with sink.strategy.mode: backfill
Options:
--selector SELECTOR — Process selector inside a batch manifest
--column COLUMN — Override backfill.chunk.column
--from WINDOW_FROM — Override backfill.chunk.from
--to WINDOW_TO — Override backfill.chunk.to
--step STEP — Override backfill.chunk.step (Nh/Nd/Nw/Nmo/Ny or integer)
--kind KIND — Override chunk boundary kind
--inner-mode INNER_MODE — Override backfill.inner_mode
--parallel-workers PARALLEL_WORKERS — Override parallel chunk workers
--max-chunks MAX_CHUNKS — Override the chunk count guard
--state-dir STATE_DIR — Ledger directory (default .dpone/backfill)
--backfill-id BACKFILL_ID — Pin an explicit campaign id / ledger key
--predicate-dialect PREDICATE_DIALECT — Render generated chunk predicates for a SQL dialect
--registry REGISTRY — Path to a sources registry YAML (can be repeated)
--format FORMAT

`dpone state`¶

`dpone state inspect`¶

Usage: dpone state inspect --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] identity
Positional arguments:
identity
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT

`dpone state reset`¶

Usage: dpone state reset --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] [--yes] identity
Positional arguments:
identity
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT
--yes

`dpone state export`¶

Usage: dpone state export --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] identity
Positional arguments:
identity
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT

`dpone state replay-from`¶

Usage: dpone state replay-from --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] --offset OFFSET [--yes] identity
Positional arguments:
identity
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT
--offset OFFSET
--yes

`dpone state rewind`¶

Usage: dpone state rewind --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] --to TO [--reason REASON] [--approved-by APPROVED_BY] [--yes] [--evidence-output EVIDENCE_OUTPUT] [--strict] identity
Positional arguments:
identity
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT
--to TO — Target watermark value to rewind to
--reason REASON — Business reason recorded in the rewind evidence
--approved-by APPROVED_BY — Approver identity required for execution
--yes — Confirm the destructive rewind
--evidence-output EVIDENCE_OUTPUT — Write rewind evidence JSON to this path
--strict — Exit non-zero while the rewind stays in preview mode (for CI gating)

`dpone state compare`¶

Usage: dpone state compare --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] left right
Positional arguments:
left
right
Options:
--backend BACKEND
--state-type STATE_TYPE
--format FORMAT

`dpone normalize`¶

`dpone normalize preview`¶

Usage: dpone normalize preview --sample SAMPLE --root-table ROOT_TABLE [--config CONFIG] [--nested-level NESTED_LEVEL] [--limit LIMIT] [--format {text,json,md}] [--output OUTPUT]
Options:
--sample SAMPLE — Local JSON, JSONL/NDJSON, CSV, or TSV row sample
--root-table ROOT_TABLE — Root normalized table name
--config CONFIG — Optional normalization config JSON/YAML file
--nested-level NESTED_LEVEL — Override normalization.nested_level
--limit LIMIT — Maximum sample rows to read
--format FORMAT
--output OUTPUT — Optional output file path

`dpone normalize infer`¶

Usage: dpone normalize infer --sample SAMPLE --root-table ROOT_TABLE [--config CONFIG] [--nested-level NESTED_LEVEL] [--limit LIMIT] [--format {text,json,md}] [--output OUTPUT]
Options:
--sample SAMPLE — Local JSON, JSONL/NDJSON, CSV, or TSV row sample
--root-table ROOT_TABLE — Root normalized table name
--config CONFIG — Optional normalization config JSON/YAML file
--nested-level NESTED_LEVEL — Override normalization.nested_level
--limit LIMIT — Maximum sample rows to read
--format FORMAT
--output OUTPUT — Optional output file path

`dpone normalize lint`¶

Usage: dpone normalize lint --root-table ROOT_TABLE --config CONFIG [--format {text,json,md}] [--output OUTPUT] [--fail-on-error]
Options:
--root-table ROOT_TABLE — Root normalized table name
--config CONFIG — Normalization config JSON/YAML file
--format FORMAT
--output OUTPUT — Optional output file path
--fail-on-error — Return exit code 2 when lint errors exist

`dpone normalize certify`¶

Usage: dpone normalize certify [--output-dir OUTPUT_DIR] [--root-table ROOT_TABLE] [--row-count ROW_COUNT] [--format {text,json,md}]
Options:
--output-dir OUTPUT_DIR — Evidence output directory
--root-table ROOT_TABLE
--row-count ROW_COUNT
--format FORMAT

`dpone normalize benchmark`¶

Usage: dpone normalize benchmark [--output-dir OUTPUT_DIR] [--root-table ROOT_TABLE] [--row-count ROW_COUNT] [--max-rows MAX_ROWS] [--format {text,json,md}]
Options:
--output-dir OUTPUT_DIR — Evidence output directory
--root-table ROOT_TABLE
--row-count ROW_COUNT
--max-rows MAX_ROWS
--format FORMAT

`dpone normalize stress`¶

Usage: dpone normalize stress [--output-dir OUTPUT_DIR] [--root-table ROOT_TABLE] [--row-count ROW_COUNT] [--max-rows MAX_ROWS] [--spill-output-format {jsonl,ndjson,json_each_row,tsv}] [--format {text,json,md}]
Options:
--output-dir OUTPUT_DIR — Evidence output directory
--root-table ROOT_TABLE
--row-count ROW_COUNT
--max-rows MAX_ROWS
--spill-output-format SPILL_OUTPUT_FORMAT
--format FORMAT

`dpone connectors`¶

`dpone connectors list`¶

Usage: dpone connectors list [--format {text,json,md}]
Options:
--format FORMAT

`dpone connectors certify`¶

Usage: dpone connectors certify [--format {markdown,json}] [--artifact-dir ARTIFACT_DIR] [--report-only] [--profile {static,local_live,vendor_live}] [--capability CAPABILITIES]
Options:
--format FORMAT
--artifact-dir ARTIFACT_DIR
--report-only — Always exit zero after rendering the report
--profile PROFILE
--capability CAPABILITIES

`dpone connectors scaffold`¶

Usage: dpone connectors scaffold [--root ROOT] [--connector-type {api,database,event,file}] [--capability {source,sink,state}] [--native-capability {stream_export,file_export,object_export,stream_staging_load,file_staging_load,object_staging_load}] [--no-certification] [--format {text,json,md}] name
Positional arguments:
name
Options:
--root ROOT
--connector-type CONNECTOR_TYPE
--capability CAPABILITIES
--native-capability NATIVE_CAPABILITIES
--no-certification
--format FORMAT

`dpone ops`¶

`dpone ops artifact-index`¶

Usage: dpone ops artifact-index [--output-dir OUTPUT_DIR] [--root ROOT] [--release RELEASE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--root ROOT
--release RELEASE
--format FORMAT

`dpone ops certification-run`¶

Usage: dpone ops certification-run [--artifact-dir ARTIFACT_DIR] [--source SOURCE] [--sink SINK] [--strategy STRATEGY] [--row-count ROW_COUNT] [--format {md,json}]
Options:
--artifact-dir ARTIFACT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--row-count ROW_COUNT
--format FORMAT

`dpone ops certification-history`¶

Usage: dpone ops certification-history [--history-dir HISTORY_DIR] --release RELEASE --current-report CURRENT_REPORT [--previous-report PREVIOUS_REPORT] [--format {md,json}]
Options:
--history-dir HISTORY_DIR
--release RELEASE
--current-report CURRENT_REPORT
--previous-report PREVIOUS_REPORT
--format FORMAT

`dpone ops connector-badges`¶

Usage: dpone ops connector-badges [--output-dir OUTPUT_DIR] [--history-index HISTORY_INDEX] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--history-index HISTORY_INDEX
--format FORMAT

`dpone ops contract-check`¶

Usage: dpone ops contract-check --rows-json ROWS_JSON --contract-json CONTRACT_JSON [--mode {fail,warn}] [--format {md,json}]
Options:
--rows-json ROWS_JSON
--contract-json CONTRACT_JSON
--mode MODE
--format FORMAT

`dpone ops quarantine-export`¶

Usage: dpone ops quarantine-export [--dir DIR] --run-id RUN_ID [--format {md,json}]
Options:
--dir DIR
--run-id RUN_ID
--format FORMAT

`dpone ops quarantine-replay`¶

Usage: dpone ops quarantine-replay [--dir DIR] --run-id RUN_ID [--yes] [--format {md,json}]
Options:
--dir DIR
--run-id RUN_ID
--yes — Deprecated: generic replay requires a route-specific resolver and sink executor
--format FORMAT

`dpone ops package-start`¶

Usage: dpone ops package-start [--dir DIR] --run-id RUN_ID --target TARGET [--chunk-id CHUNK_ID] [--format {md,json}]
Options:
--dir DIR
--run-id RUN_ID
--target TARGET
--chunk-id CHUNK_ID
--format FORMAT

`dpone ops package-commit`¶

Usage: dpone ops package-commit [--dir DIR] --load-id LOAD_ID --rows-loaded ROWS_LOADED [--state-after-json STATE_AFTER_JSON] [--format {md,json}]
Options:
--dir DIR
--load-id LOAD_ID
--rows-loaded ROWS_LOADED
--state-after-json STATE_AFTER_JSON
--format FORMAT

`dpone ops rollback-plan`¶

Usage: dpone ops rollback-plan --sink {mssql,postgres,clickhouse,bigquery} --target TARGET --load-id LOAD_ID [--strategy STRATEGY] [--format {md,json}]
Options:
--sink SINK
--target TARGET
--load-id LOAD_ID
--strategy STRATEGY
--format FORMAT

`dpone ops rollback-apply`¶

Usage: dpone ops rollback-apply --plan-json PLAN_JSON [--yes] [--format {md,json}]
Options:
--plan-json PLAN_JSON
--yes
--format FORMAT

`dpone ops rollback-execute`¶

Usage: dpone ops rollback-execute --sink {mssql,postgres,clickhouse,bigquery} --target TARGET --load-id LOAD_ID [--strategy STRATEGY] [--require-backup] [--yes] [--format {md,json}]
Options:
--sink SINK
--target TARGET
--load-id LOAD_ID
--strategy STRATEGY
--require-backup
--yes
--format FORMAT

`dpone ops marketplace`¶

Usage: dpone ops marketplace [--format {md,json}]
Options:
--format FORMAT

`dpone ops evidence-bundle`¶

Usage: dpone ops evidence-bundle [--artifact-dir ARTIFACT_DIR] --run-id RUN_ID --source SOURCE --sink SINK --strategy STRATEGY --rows-json ROWS_JSON --contract-json CONTRACT_JSON [--row-count ROW_COUNT] [--format {md,json}]
Options:
--artifact-dir ARTIFACT_DIR
--run-id RUN_ID
--source SOURCE
--sink SINK
--strategy STRATEGY
--rows-json ROWS_JSON
--contract-json CONTRACT_JSON
--row-count ROW_COUNT
--format FORMAT

`dpone ops evidence-chain`¶

Usage: dpone ops evidence-chain [--chain-dir CHAIN_DIR] --release RELEASE --artifact-index ARTIFACT_INDEX [--previous-entry PREVIOUS_ENTRY] [--format {md,json}]
Options:
--chain-dir CHAIN_DIR
--release RELEASE
--artifact-index ARTIFACT_INDEX
--previous-entry PREVIOUS_ENTRY
--format FORMAT

`dpone ops evidence-chain-verify`¶

Usage: dpone ops evidence-chain-verify [--chain-dir CHAIN_DIR] [--format {md,json}]
Options:
--chain-dir CHAIN_DIR
--format FORMAT

`dpone ops go-live-gate`¶

Usage: dpone ops go-live-gate --bundle-json BUNDLE_JSON [--format {md,json}]
Options:
--bundle-json BUNDLE_JSON
--format FORMAT

`dpone ops policy-evaluate`¶

Usage: dpone ops policy-evaluate --bundle-json BUNDLE_JSON --policy-json POLICY_JSON [--format {md,json}]
Options:
--bundle-json BUNDLE_JSON
--policy-json POLICY_JSON
--format FORMAT

`dpone ops diff`¶

Usage: dpone ops diff --source-rows-json SOURCE_ROWS_JSON --target-rows-json TARGET_ROWS_JSON --key KEY [--compare-columns COMPARE_COLUMNS] [--sample-limit SAMPLE_LIMIT] [--format {md,json}]
Options:
--source-rows-json SOURCE_ROWS_JSON
--target-rows-json TARGET_ROWS_JSON
--key KEY — Comma-separated business key columns
--compare-columns COMPARE_COLUMNS — Comma-separated columns to compare; defaults to all non-key columns
--sample-limit SAMPLE_LIMIT
--format FORMAT

`dpone ops security-audit`¶

Usage: dpone ops security-audit [--manifest-json MANIFEST_JSON] [--log-text LOG_TEXT] [--format {md,json}]
Options:
--manifest-json MANIFEST_JSON
--log-text LOG_TEXT
--format FORMAT

`dpone ops slo-evaluate`¶

Usage: dpone ops slo-evaluate --metrics-json METRICS_JSON --objectives-json OBJECTIVES_JSON [--format {md,json}]
Options:
--metrics-json METRICS_JSON
--objectives-json OBJECTIVES_JSON
--format FORMAT

`dpone ops incident-pack`¶

Usage: dpone ops incident-pack [--artifact-dir ARTIFACT_DIR] --incident-id INCIDENT_ID --title TITLE [--severity SEVERITY] [--artifact ARTIFACT] [--format {md,json}]
Options:
--artifact-dir ARTIFACT_DIR
--incident-id INCIDENT_ID
--title TITLE
--severity SEVERITY
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops release-gate`¶

Usage: dpone ops release-gate [--artifact-dir ARTIFACT_DIR] --release RELEASE [--artifact ARTIFACT] [--format {md,json}]
Options:
--artifact-dir ARTIFACT_DIR
--release RELEASE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops release-rc-collect`¶

Usage: dpone ops release-rc-collect [--output-dir OUTPUT_DIR] --release RELEASE --previous-release PREVIOUS_RELEASE --package-version PACKAGE_VERSION --base-branch BASE_BRANCH --head-branch HEAD_BRANCH [--pull-request-json PULL_REQUEST_JSON] [--pr-json PR_JSON] [--artifact ARTIFACT] [--require-artifact REQUIRE_ARTIFACT] [--finalizer-output-dir FINALIZER_OUTPUT_DIR] [--mode {pre_merge,post_merge}] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR — Release RC collector output directory
--release RELEASE
--previous-release PREVIOUS_RELEASE
--package-version PACKAGE_VERSION
--base-branch BASE_BRANCH
--head-branch HEAD_BRANCH
--pull-request-json PULL_REQUEST_JSON — Path to gh pr view --json ... output; repeat in base-to-head order
--pr-json PR_JSON — Short alias for --pull-request-json
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require-artifact REQUIRE_ARTIFACT — Required release RC evidence domain; can be repeated
--finalizer-output-dir FINALIZER_OUTPUT_DIR
--mode MODE — Mode to embed in the generated release-rc-finalize command
--format FORMAT

`dpone ops release-rc-finalize`¶

Usage: dpone ops release-rc-finalize [--output-dir OUTPUT_DIR] --release RELEASE --previous-release PREVIOUS_RELEASE --package-version PACKAGE_VERSION --merge-train-json MERGE_TRAIN_JSON [--mode {pre_merge,post_merge}] [--artifact ARTIFACT] [--require-artifact REQUIRE_ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--previous-release PREVIOUS_RELEASE
--package-version PACKAGE_VERSION
--merge-train-json MERGE_TRAIN_JSON — Path to merge_train.json in base-to-head order
--mode MODE — pre_merge validates clean open PRs; post_merge requires every PR to be merged
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require-artifact REQUIRE_ARTIFACT — Required release RC evidence domain; can be repeated
--format FORMAT

`dpone ops production-maturity`¶

Usage: dpone ops production-maturity [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required evidence domain; can be repeated
--format FORMAT

`dpone ops industrial-readiness`¶

Usage: dpone ops industrial-readiness [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--require REQUIRE] [--case CASE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required evidence domain; can be repeated
--case CASE — Required matrix case as source:sink:strategy; can be repeated
--format FORMAT

`dpone ops connection-doctor`¶

Usage: dpone ops connection-doctor [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--tool TOOL] [--optional-tool OPTIONAL_TOOL] [--env ENV] [--optional-env OPTIONAL_ENV] [--python-import PYTHON_IMPORT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--tool TOOL — Required executable name; repeat as needed
--optional-tool OPTIONAL_TOOL — Optional executable name that should emit a warning when missing
--env ENV — Required environment variable name
--optional-env OPTIONAL_ENV — Optional environment variable name
--python-import PYTHON_IMPORT — Required Python import/module name
--format FORMAT

`dpone ops source-discover`¶

Usage: dpone ops source-discover [--output-dir OUTPUT_DIR] --source SOURCE --schema-json SCHEMA_JSON [--dataset DATASET] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--schema-json SCHEMA_JSON — Path to exported source schema JSON
--dataset DATASET
--format FORMAT

`dpone ops route-bootstrap`¶

Usage: dpone ops route-bootstrap [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --dataset DATASET [--source-discovery-json SOURCE_DISCOVERY_JSON] [--manifest-id MANIFEST_ID] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--dataset DATASET
--source-discovery-json SOURCE_DISCOVERY_JSON — Path to source_discovery.json
--manifest-id MANIFEST_ID — Manifest process id to use in the generated draft
--format FORMAT

`dpone ops route-doctor`¶

Usage: dpone ops route-doctor [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required artifact name; repeat as needed
--format FORMAT

`dpone ops route-conformance`¶

Usage: dpone ops route-conformance {run,live-run,summarize,release-gate} ...

`dpone ops route-conformance run`¶

Usage: dpone ops route-conformance run [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--dataset-profile DATASET_PROFILE] [--rows ROWS] [--columns COLUMNS] [--chunk-size CHUNK_SIZE] [--seed SEED] [--include-nested] [--no-schema-evolution] [--require-schema-evolution] [--min-rows MIN_ROWS] [--min-columns MIN_COLUMNS] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--dataset-profile DATASET_PROFILE
--rows ROWS
--columns COLUMNS
--chunk-size CHUNK_SIZE
--seed SEED
--include-nested
--no-schema-evolution
--require-schema-evolution
--min-rows MIN_ROWS
--min-columns MIN_COLUMNS
--format FORMAT

`dpone ops route-conformance live-run`¶

Usage: dpone ops route-conformance live-run [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--adapter ADAPTER] [--dataset-profile DATASET_PROFILE] [--rows ROWS] [--columns COLUMNS] [--chunk-size CHUNK_SIZE] [--seed SEED] [--include-nested] [--no-schema-evolution] [--require-schema-evolution] [--min-rows MIN_ROWS] [--min-columns MIN_COLUMNS] [--drift {none,value,row_count,contract}] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--adapter ADAPTER
--dataset-profile DATASET_PROFILE
--rows ROWS
--columns COLUMNS
--chunk-size CHUNK_SIZE
--seed SEED
--include-nested
--no-schema-evolution
--require-schema-evolution
--min-rows MIN_ROWS
--min-columns MIN_COLUMNS
--drift DRIFT
--format FORMAT

`dpone ops route-conformance summarize`¶

Usage: dpone ops route-conformance summarize [--output-dir OUTPUT_DIR] [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops route-conformance release-gate`¶

Usage: dpone ops route-conformance release-gate [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops route-readiness`¶

Usage: dpone ops route-readiness [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--format FORMAT

`dpone ops route-schema-evolution`¶

Usage: dpone ops route-schema-evolution [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --schema-evolution-json SCHEMA_EVOLUTION_JSON [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--schema-evolution-json SCHEMA_EVOLUTION_JSON — Path to cdc_schema_evolution_evidence.json
--format FORMAT

`dpone ops route-reconciliation-repair`¶

Usage: dpone ops route-reconciliation-repair [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --source-rows-json SOURCE_ROWS_JSON --target-rows-json TARGET_ROWS_JSON --key KEY [--compare-column COMPARE_COLUMN] [--delete-column DELETE_COLUMN] [--source-boundary SOURCE_BOUNDARY] [--target-boundary TARGET_BOUNDARY] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--source-rows-json SOURCE_ROWS_JSON — JSON list or object with rows for source rows
--target-rows-json TARGET_ROWS_JSON — JSON list or object with rows for target rows
--key KEY — Key column; repeat for composite keys
--compare-column COMPARE_COLUMN — Column to compare; repeat as needed
--delete-column DELETE_COLUMN — Source delete marker column
--source-boundary SOURCE_BOUNDARY
--target-boundary TARGET_BOUNDARY
--format FORMAT

`dpone ops route-data-quality`¶

Usage: dpone ops route-data-quality [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--artifact ARTIFACT] [--require REQUIRE] [--min-score MIN_SCORE] [--warning-score WARNING_SCORE] [--max-exception-ratio MAX_EXCEPTION_RATIO] [--max-quarantine-rows MAX_QUARANTINE_ROWS] [--max-exception-age-hours MAX_EXCEPTION_AGE_HOURS] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required data quality evidence domain; can be repeated
--min-score MIN_SCORE — Minimum route DQ score required to pass
--warning-score WARNING_SCORE — Score below this value emits a warning
--max-exception-ratio MAX_EXCEPTION_RATIO — Maximum allowed failed/quarantined row ratio
--max-quarantine-rows MAX_QUARANTINE_ROWS — Maximum allowed quarantine rows
--max-exception-age-hours MAX_EXCEPTION_AGE_HOURS — Maximum allowed age for open route exceptions
--format FORMAT

`dpone ops route-refresh-plan`¶

Usage: dpone ops route-refresh-plan [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --dataset DATASET --reason {initial_backfill,manual_resync,dq_repair,schema_backfill,retention_gap,range_replay} --window-kind {integer,timestamp,partition,state} --start START --end END [--chunk-size CHUNK_SIZE] [--max-chunks MAX_CHUNKS] [--partition PARTITION] [--current-state CURRENT_STATE] [--target-state TARGET_STATE] [--destructive] [--require-approval] [--approval-granted] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--dataset DATASET
--reason REASON
--window-kind WINDOW_KIND
--start START
--end END
--chunk-size CHUNK_SIZE
--max-chunks MAX_CHUNKS
--partition PARTITION
--current-state CURRENT_STATE
--target-state TARGET_STATE
--destructive
--require-approval
--approval-granted
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required refresh evidence domain; can be repeated
--format FORMAT

`dpone ops route-refresh-execute`¶

Usage: dpone ops route-refresh-execute [--output-dir OUTPUT_DIR] --route-refresh-plan-json ROUTE_REFRESH_PLAN_JSON --runner-id RUNNER_ID [--execute] [--executor EXECUTOR] [--executor-config-json EXECUTOR_CONFIG_JSON] [--source SOURCE] [--sink SINK] [--strategy STRATEGY] [--max-chunks MAX_CHUNKS] [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--route-refresh-plan-json ROUTE_REFRESH_PLAN_JSON — Path to route_refresh_plan.json
--runner-id RUNNER_ID
--execute — Execute chunks with a configured backend
--executor EXECUTOR — Optional executor backend selector
--executor-config-json EXECUTOR_CONFIG_JSON — Executor config JSON path for the selected backend
--source SOURCE — Optional expected source route id
--sink SINK — Optional expected sink route id
--strategy STRATEGY — Optional expected strategy
--max-chunks MAX_CHUNKS
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops route-refresh-capture-snapshots`¶

Usage: dpone ops route-refresh-capture-snapshots [--output-dir OUTPUT_DIR] --route-refresh-execution-json ROUTE_REFRESH_EXECUTION_JSON [--source-rows-json SOURCE_ROWS_JSON] [--sink-rows-json SINK_ROWS_JSON] --runner-id RUNNER_ID [--executor EXECUTOR] [--executor-config-json EXECUTOR_CONFIG_JSON] --key KEY --boundary-column BOUNDARY_COLUMN --column COLUMN [--type TYPE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--route-refresh-execution-json ROUTE_REFRESH_EXECUTION_JSON — Path to route_refresh_execution.json
--source-rows-json SOURCE_ROWS_JSON — Credential-free source rows JSON for snapshot capture
--sink-rows-json SINK_ROWS_JSON — Credential-free sink rows JSON for snapshot capture
--runner-id RUNNER_ID
--executor EXECUTOR — Optional backend selector, for example mssql_clickhouse
--executor-config-json EXECUTOR_CONFIG_JSON — Backend config JSON path for the selected reader backend
--key KEY — Key column; repeat for composite keys
--boundary-column BOUNDARY_COLUMN
--column COLUMN — Compared column; repeat in route order
--type TYPE — Column type hint as name=type
--format FORMAT

`dpone ops route-refresh-verify`¶

Usage: dpone ops route-refresh-verify [--output-dir OUTPUT_DIR] --route-refresh-execution-json ROUTE_REFRESH_EXECUTION_JSON --source-snapshot-json SOURCE_SNAPSHOT_JSON --sink-snapshot-json SINK_SNAPSHOT_JSON --runner-id RUNNER_ID --key KEY --boundary-column BOUNDARY_COLUMN --column COLUMN [--type TYPE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--route-refresh-execution-json ROUTE_REFRESH_EXECUTION_JSON — Path to route_refresh_execution.json
--source-snapshot-json SOURCE_SNAPSHOT_JSON — Path to source route_refresh_snapshot.json
--sink-snapshot-json SINK_SNAPSHOT_JSON — Path to sink route_refresh_snapshot.json
--runner-id RUNNER_ID
--key KEY — Key column; repeat for composite keys
--boundary-column BOUNDARY_COLUMN
--column COLUMN — Compared column; repeat in route order
--type TYPE — Column type hint as name=type
--format FORMAT

`dpone ops route-run-supervisor`¶

Usage: dpone ops route-run-supervisor [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --run-id RUN_ID --dataset DATASET [--manifest MANIFEST] [--run-mode {evidence_only,evidence-only,route_refresh,route-refresh}] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--run-id RUN_ID
--dataset DATASET
--manifest MANIFEST — Manifest path used for the supervised run
--run-mode RUN_MODE — Evidence contract mode for this supervised route run
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required evidence domain; can be repeated
--format FORMAT

`dpone ops route-live-certification`¶

Usage: dpone ops route-live-certification [--output-dir OUTPUT_DIR] --release RELEASE --source SOURCE --sink SINK --strategy STRATEGY [--profile {local_live,real_local,type_matrix_certification,native_transfer,vendor_live}] [--row-count ROW_COUNT] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--source SOURCE
--sink SINK
--strategy STRATEGY
--profile PROFILE
--row-count ROW_COUNT
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required live evidence domain; can be repeated
--format FORMAT

`dpone ops route-certify`¶

Usage: dpone ops route-certify [--output-dir OUTPUT_DIR] --release RELEASE --source SOURCE --sink SINK --strategy STRATEGY [--profile {oss_ci,local_live,vendor_live}] [--artifact ARTIFACT] [--release-set RELEASE_SET] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--source SOURCE
--sink SINK
--strategy STRATEGY
--profile PROFILE — Certification profile; vendor_live requires route_live_evidence_bundle
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--release-set RELEASE_SET — Content-valid release-set used to bind a six-dimensional matrix claim into this bundle
--require REQUIRE — Additional route certification evidence domain; can be repeated
--format FORMAT

`dpone ops route-attestation-build`¶

Usage: dpone ops route-attestation-build --route-id ROUTE_ID --route-certification-bundle ROUTE_CERTIFICATION_BUNDLE --deployment-set DEPLOYMENT_SET [--authorization-profile AUTHORIZATION_PROFILE] --issued-at ISSUED_AT --not-before NOT_BEFORE --expires-at EXPIRES_AT --output OUTPUT [--format {json,md}]
Options:
--route-id ROUTE_ID
--route-certification-bundle ROUTE_CERTIFICATION_BUNDLE
--deployment-set DEPLOYMENT_SET
--authorization-profile AUTHORIZATION_PROFILE
--issued-at ISSUED_AT — Offset-aware issue time, for example 2026-07-15T10:00:00Z
--not-before NOT_BEFORE — Offset-aware validity start
--expires-at EXPIRES_AT — Offset-aware expiry
--output OUTPUT — Create-only output JSON path
--format FORMAT

`dpone ops route-attestation-verify`¶

Usage: dpone ops route-attestation-verify --attestation ATTESTATION --sigstore-bundle SIGSTORE_BUNDLE --route-certification-bundle ROUTE_CERTIFICATION_BUNDLE --policy POLICY --deployment-set DEPLOYMENT_SET [--output-dir OUTPUT_DIR] [--format {json,md}]
Options:
--attestation ATTESTATION
--sigstore-bundle SIGSTORE_BUNDLE
--route-certification-bundle ROUTE_CERTIFICATION_BUNDLE
--policy POLICY
--deployment-set DEPLOYMENT_SET
--output-dir OUTPUT_DIR — Create-only verification receipt directory
--format FORMAT

`dpone ops route-certify-release`¶

Usage: dpone ops route-certify-release [--output-dir OUTPUT_DIR] --release RELEASE [--profile {oss_ci,local_live,vendor_live}] [--route-bundle ROUTE_BUNDLE] [--route ROUTE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--profile PROFILE — Release profile; vendor_live requires vendor_live route bundles
--route-bundle ROUTE_BUNDLE — Route bundle as route_case_id=/path/to/route_certification_bundle.json
--route ROUTE — Required route case id override; repeat to build a custom release matrix
--format FORMAT

`dpone ops route-release-finalize`¶

Usage: dpone ops route-release-finalize [--output-dir OUTPUT_DIR] --release RELEASE [--profile {oss_ci,local_live,vendor_live}] [--bundle-root BUNDLE_ROOT] [--route-bundle ROUTE_BUNDLE] [--route ROUTE] [--history-dir HISTORY_DIR] [--baseline-json BASELINE_JSON] [--max-age-hours MAX_AGE_HOURS] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--profile PROFILE
--bundle-root BUNDLE_ROOT — Root to scan for route bundles
--route-bundle ROUTE_BUNDLE — Explicit route bundle override as route_case_id=/path/to/route_certification_bundle.json
--route ROUTE — Required route case id override
--history-dir HISTORY_DIR
--baseline-json BASELINE_JSON — Previous finalizer, history index, or route release JSON baseline
--max-age-hours MAX_AGE_HOURS
--format FORMAT

`dpone ops route-rc-orchestrator`¶

Usage: dpone ops route-rc-orchestrator [--output-dir OUTPUT_DIR] --release RELEASE --source SOURCE --sink SINK --strategy STRATEGY [--profile {local_live,real_local,type_matrix_certification,native_transfer,vendor_live}] [--row-count ROW_COUNT] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--source SOURCE
--sink SINK
--strategy STRATEGY
--profile PROFILE
--row-count ROW_COUNT
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required release evidence domain; can be repeated
--format FORMAT

`dpone ops route-rc-execute`¶

Usage: dpone ops route-rc-execute --orchestration-json ORCHESTRATION_JSON [--output-dir OUTPUT_DIR] [--execute] [--timeout-seconds TIMEOUT_SECONDS] [--max-attempts MAX_ATTEMPTS] [--redact REDACT] [--format {md,json}]
Options:
--orchestration-json ORCHESTRATION_JSON — Path to route_rc_orchestration.json
--output-dir OUTPUT_DIR
--execute — Run commands from the orchestration receipt; omit for dry-run planning
--timeout-seconds TIMEOUT_SECONDS
--max-attempts MAX_ATTEMPTS
--redact REDACT — Additional literal secret value to redact
--format FORMAT

`dpone ops route-release-gate`¶

Usage: dpone ops route-release-gate [--output-dir OUTPUT_DIR] --release RELEASE --source SOURCE --sink SINK --strategy STRATEGY [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--source SOURCE
--sink SINK
--strategy STRATEGY
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--require REQUIRE — Additional required evidence domain; can be repeated
--format FORMAT

`dpone ops route-execution-ledger`¶

Usage: dpone ops route-execution-ledger [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --dataset DATASET --run-id RUN_ID --stage {planned,extracting,loaded_to_staging,finalized,quality_checked,state_committed} --status {planned,running,succeeded,failed,skipped,committed} --runner-id RUNNER_ID [--source-boundary SOURCE_BOUNDARY] [--sink-boundary SINK_BOUNDARY] [--idempotency-key IDEMPOTENCY_KEY] [--lease-ttl-seconds LEASE_TTL_SECONDS] [--artifact ARTIFACT] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--dataset DATASET
--run-id RUN_ID
--stage STAGE
--status STATUS
--runner-id RUNNER_ID
--source-boundary SOURCE_BOUNDARY
--sink-boundary SINK_BOUNDARY
--idempotency-key IDEMPOTENCY_KEY
--lease-ttl-seconds LEASE_TTL_SECONDS
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--store-backend STORE_BACKEND — Ledger persistence backend for steps and leases
--store-uri STORE_URI — Backend-specific store location; for sqlite this is the database file path
--format FORMAT

`dpone ops route-state-promote`¶

Usage: dpone ops route-state-promote [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY --dataset DATASET --run-id RUN_ID --ledger-json LEDGER_JSON --proposed-state PROPOSED_STATE --source-boundary SOURCE_BOUNDARY --sink-boundary SINK_BOUNDARY --idempotency-key IDEMPOTENCY_KEY --commit-token COMMIT_TOKEN --target TARGET [--fencing-token FENCING_TOKEN] [--rows-applied ROWS_APPLIED] [--events-applied EVENTS_APPLIED] [--state-backend {local_json,sqlite}] [--state-uri STATE_URI] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--dataset DATASET
--run-id RUN_ID
--ledger-json LEDGER_JSON — Path to route_execution_ledger.json
--proposed-state PROPOSED_STATE
--source-boundary SOURCE_BOUNDARY
--sink-boundary SINK_BOUNDARY
--idempotency-key IDEMPOTENCY_KEY
--commit-token COMMIT_TOKEN
--target TARGET
--fencing-token FENCING_TOKEN
--rows-applied ROWS_APPLIED
--events-applied EVENTS_APPLIED
--state-backend STATE_BACKEND — State persistence backend for promoted source state
--state-uri STATE_URI — Backend-specific state-store location; for sqlite this is the database file path
--format FORMAT

`dpone ops route-transport-certification`¶

Usage: dpone ops route-transport-certification --manifest MANIFEST [--artifact-dir ARTIFACT_DIR] [--profile {static,local_live,vendor_live}] [--format {md,json}]
Options:
--manifest MANIFEST — Manifest path used to build the route decision
--artifact-dir ARTIFACT_DIR
--profile PROFILE
--format FORMAT

`dpone ops release-summary`¶

Usage: dpone ops release-summary [--output-dir OUTPUT_DIR] --release-id RELEASE_ID --replay-chain-dir REPLAY_CHAIN_DIR --matrix-suite MATRIX_SUITE --matrix-chain-dir MATRIX_CHAIN_DIR --connector-suite CONNECTOR_SUITE --connector-chain-dir CONNECTOR_CHAIN_DIR [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release-id RELEASE_ID
--replay-chain-dir REPLAY_CHAIN_DIR
--matrix-suite MATRIX_SUITE
--matrix-chain-dir MATRIX_CHAIN_DIR
--connector-suite CONNECTOR_SUITE
--connector-chain-dir CONNECTOR_CHAIN_DIR
--format FORMAT

`dpone ops release-verify`¶

Usage: dpone ops release-verify --release RELEASE [--package PACKAGE] [--github-repository GITHUB_REPOSITORY] [--runtime-image RUNTIME_IMAGE] [--skip-github-release] [--skip-pypi] [--skip-runtime-image] [--install-smoke] [--install-extra INSTALL_EXTRA] [--install-python INSTALL_PYTHON] [--timeout-seconds TIMEOUT_SECONDS] [--poll-interval-seconds POLL_INTERVAL_SECONDS] [--command-timeout-seconds COMMAND_TIMEOUT_SECONDS] [--output OUTPUT] [--format {md,json}]
Options:
--release RELEASE — Release tag or version, for example v0.24.0
--package PACKAGE
--github-repository GITHUB_REPOSITORY
--runtime-image RUNTIME_IMAGE
--skip-github-release
--skip-pypi
--skip-runtime-image
--install-smoke — Run uvx --from PACKAGE dpone --version
--install-extra INSTALL_EXTRA — Optional package extra used by --install-smoke
--install-python INSTALL_PYTHON — Optional Python version passed to uvx, for example 3.11
--timeout-seconds TIMEOUT_SECONDS — Total wait time; 0 means a single attempt
--poll-interval-seconds POLL_INTERVAL_SECONDS
--command-timeout-seconds COMMAND_TIMEOUT_SECONDS
--output OUTPUT — Optional JSON/Markdown evidence output path
--format FORMAT

`dpone ops release-orchestrator`¶

Usage: dpone ops release-orchestrator [--output-dir OUTPUT_DIR] --release RELEASE [--root ROOT] [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--root ROOT
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops release-promote`¶

Usage: dpone ops release-promote [--output-dir OUTPUT_DIR] --release RELEASE --from-env FROM_ENV --to-env TO_ENV [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--from-env FROM_ENV
--to-env TO_ENV
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops env-drift`¶

Usage: dpone ops env-drift [--output-dir OUTPUT_DIR] --source-env SOURCE_ENV --target-env TARGET_ENV --source SOURCE --target TARGET [--allowlist-path ALLOWLIST_PATH] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source-env SOURCE_ENV
--target-env TARGET_ENV
--source SOURCE
--target TARGET
--allowlist-path ALLOWLIST_PATH
--format FORMAT

`dpone ops change-request`¶

Usage: dpone ops change-request [--output-dir OUTPUT_DIR] --change-id CHANGE_ID --release RELEASE --target-env TARGET_ENV --risk-level {low,medium,high,critical} --requested-by REQUESTED_BY [--approver APPROVER] [--expires-at EXPIRES_AT] [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--change-id CHANGE_ID
--release RELEASE
--target-env TARGET_ENV
--risk-level RISK_LEVEL
--requested-by REQUESTED_BY
--approver APPROVER
--expires-at EXPIRES_AT
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops approval-record`¶

Usage: dpone ops approval-record [--output-dir OUTPUT_DIR] --change-request CHANGE_REQUEST --actor ACTOR --decision {approved,rejected} [--comment COMMENT] [--quorum-required QUORUM_REQUIRED] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--change-request CHANGE_REQUEST
--actor ACTOR
--decision DECISION
--comment COMMENT
--quorum-required QUORUM_REQUIRED
--format FORMAT

`dpone ops deployment-record`¶

Usage: dpone ops deployment-record [--output-dir OUTPUT_DIR] --deployment-id DEPLOYMENT_ID --environment ENVIRONMENT --actor ACTOR --approval-record APPROVAL_RECORD --status {succeeded,completed,failed,partial} [--post-check POST_CHECK] [--rollback-artifact ROLLBACK_ARTIFACT] [--started-at STARTED_AT] [--finished-at FINISHED_AT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--deployment-id DEPLOYMENT_ID
--environment ENVIRONMENT
--actor ACTOR
--approval-record APPROVAL_RECORD
--status STATUS
--post-check POST_CHECK — Post-deploy check as name=true|false
--rollback-artifact ROLLBACK_ARTIFACT
--started-at STARTED_AT
--finished-at FINISHED_AT
--format FORMAT

`dpone ops post-deploy-verify`¶

Usage: dpone ops post-deploy-verify [--output-dir OUTPUT_DIR] --deployment-record DEPLOYMENT_RECORD [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--deployment-record DEPLOYMENT_RECORD
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops release-close`¶

Usage: dpone ops release-close [--output-dir OUTPUT_DIR] --release RELEASE --closed-by CLOSED_BY --post-deploy-verify POST_DEPLOY_VERIFY [--notes NOTES] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--closed-by CLOSED_BY
--post-deploy-verify POST_DEPLOY_VERIFY
--notes NOTES
--format FORMAT

`dpone ops docs-publish-pack`¶

Usage: dpone ops docs-publish-pack [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops manifest-bundle`¶

Usage: dpone ops manifest-bundle [--output-dir OUTPUT_DIR] --bundle-id BUNDLE_ID [--file FILE] [--redact] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--bundle-id BUNDLE_ID
--file FILE — File reference as name=/path/to/file
--redact
--format FORMAT

`dpone ops runbook-pack`¶

Usage: dpone ops runbook-pack [--output-dir OUTPUT_DIR] --runbook-id RUNBOOK_ID --title TITLE [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--runbook-id RUNBOOK_ID
--title TITLE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops run-registry`¶

Usage: dpone ops run-registry [--output-dir OUTPUT_DIR] --run-result RUN_RESULT [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--run-result RUN_RESULT
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--format FORMAT

`dpone ops lineage-export`¶

Usage: dpone ops lineage-export [--output-dir OUTPUT_DIR] --run-registry-entry RUN_REGISTRY_ENTRY [--namespace NAMESPACE] [--input INPUT] [--output OUTPUT] [--event-type {auto,START,COMPLETE,FAIL}] [--airflow-evidence-bundle AIRFLOW_EVIDENCE_BUNDLE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--run-registry-entry RUN_REGISTRY_ENTRY
--namespace NAMESPACE
--input INPUT — Input dataset as namespace=name
--output OUTPUT — Output dataset as namespace=name
--event-type EVENT_TYPE
--airflow-evidence-bundle AIRFLOW_EVIDENCE_BUNDLE — Optional final Airflow evidence bundle used for run correlation
--format FORMAT

`dpone ops benchmark-baseline`¶

Usage: dpone ops benchmark-baseline [--output-dir OUTPUT_DIR] --metrics-json METRICS_JSON --baseline-json BASELINE_JSON [--allowed-regression-ratio ALLOWED_REGRESSION_RATIO] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--metrics-json METRICS_JSON
--baseline-json BASELINE_JSON
--allowed-regression-ratio ALLOWED_REGRESSION_RATIO
--format FORMAT

`dpone ops certification-automation-plan`¶

Usage: dpone ops certification-automation-plan [--output-dir OUTPUT_DIR] [--profile {mock_contract,mock_local,vendor_live}] [--row-count ROW_COUNT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--profile PROFILE
--row-count ROW_COUNT
--format FORMAT

`dpone ops dbt-lineage`¶

Usage: dpone ops dbt-lineage [--output-dir OUTPUT_DIR] --manifest MANIFEST [--run-results RUN_RESULTS] [--run-registry-entry RUN_REGISTRY_ENTRY] [--namespace NAMESPACE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--manifest MANIFEST — Path to dbt target/manifest.json
--run-results RUN_RESULTS — Path to dbt target/run_results.json
--run-registry-entry RUN_REGISTRY_ENTRY — Optional dpone run registry entry JSON
--namespace NAMESPACE
--format FORMAT

`dpone ops integration-matrix-report`¶

Usage: dpone ops integration-matrix-report --artifact-dir ARTIFACT_DIR --output-dir OUTPUT_DIR [--format {md,json}]
Options:
--artifact-dir ARTIFACT_DIR
--output-dir OUTPUT_DIR
--format FORMAT

`dpone ops certification-suite`¶

Usage: dpone ops certification-suite [--output-dir OUTPUT_DIR] --suite-id SUITE_ID [--release-id RELEASE_ID] --certification-report CERTIFICATION_REPORT [--benchmark-baseline BENCHMARK_BASELINE] [--lineage-report LINEAGE_REPORT] [--dbt-lineage-report DBT_LINEAGE_REPORT] [--evidence-bundle EVIDENCE_BUNDLE] [--strategy-certification-bundle STRATEGY_CERTIFICATION_BUNDLE] [--require-benchmark] [--require-lineage] [--require-dbt-lineage] [--require-evidence] [--require-strategy-certification] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--suite-id SUITE_ID
--release-id RELEASE_ID
--certification-report CERTIFICATION_REPORT
--benchmark-baseline BENCHMARK_BASELINE
--lineage-report LINEAGE_REPORT
--dbt-lineage-report DBT_LINEAGE_REPORT
--evidence-bundle EVIDENCE_BUNDLE
--strategy-certification-bundle STRATEGY_CERTIFICATION_BUNDLE
--require-benchmark
--require-lineage
--require-dbt-lineage
--require-evidence
--require-strategy-certification
--format FORMAT

`dpone ops certification-pack`¶

Usage: dpone ops certification-pack [--output-dir OUTPUT_DIR] --pack-id PACK_ID [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--pack-id PACK_ID
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required evidence artifact name
--format FORMAT

`dpone ops route-certification-pack`¶

Usage: dpone ops route-certification-pack [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK --strategy STRATEGY [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--artifact ARTIFACT — Evidence reference as name=/path/to/file
--format FORMAT

`dpone ops cdc-handoff`¶

Usage: dpone ops cdc-handoff [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK [--strategy STRATEGY] --source-dataset SOURCE_DATASET --target-dataset TARGET_DATASET [--artifact ARTIFACT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--source-dataset SOURCE_DATASET
--target-dataset TARGET_DATASET
--artifact ARTIFACT — CDC evidence reference as name=/path/to/file
--format FORMAT

`dpone ops cdc-apply-certification`¶

Usage: dpone ops cdc-apply-certification [--output-dir OUTPUT_DIR] --source SOURCE --sink SINK [--strategy STRATEGY] --source-dataset SOURCE_DATASET --target-dataset TARGET_DATASET --fixture-json FIXTURE_JSON [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source SOURCE
--sink SINK
--strategy STRATEGY
--source-dataset SOURCE_DATASET
--target-dataset TARGET_DATASET
--fixture-json FIXTURE_JSON — Credential-free CDC apply fixture JSON
--format FORMAT

`dpone ops cdc-observability-evidence`¶

Usage: dpone ops cdc-observability-evidence [--output-dir OUTPUT_DIR] --handoff-json HANDOFF_JSON --apply-certification-json APPLY_CERTIFICATION_JSON --metrics-json METRICS_JSON [--slo-json SLO_JSON] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--handoff-json HANDOFF_JSON — Path to cdc_handoff.json
--apply-certification-json APPLY_CERTIFICATION_JSON — Path to cdc_apply_certification.json
--metrics-json METRICS_JSON — Path to normalized CDC telemetry JSON
--slo-json SLO_JSON — Optional CDC SLO profile JSON
--format FORMAT

`dpone ops cdc-recovery-evidence`¶

Usage: dpone ops cdc-recovery-evidence [--output-dir OUTPUT_DIR] --handoff-json HANDOFF_JSON --apply-certification-json APPLY_CERTIFICATION_JSON --observability-json OBSERVABILITY_JSON --scenario-json SCENARIO_JSON [--policy-json POLICY_JSON] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--handoff-json HANDOFF_JSON — Path to cdc_handoff.json
--apply-certification-json APPLY_CERTIFICATION_JSON — Path to cdc_apply_certification.json
--observability-json OBSERVABILITY_JSON — Path to cdc_observability.json
--scenario-json SCENARIO_JSON — Path to CDC fault-injection scenario JSON
--policy-json POLICY_JSON — Optional CDC recovery policy JSON
--format FORMAT

`dpone ops cdc-quarantine-inspect`¶

Usage: dpone ops cdc-quarantine-inspect [--output-dir OUTPUT_DIR] --quarantine-json QUARANTINE_JSON [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--quarantine-json QUARANTINE_JSON — Path to cdc_poison_quarantine.json
--format FORMAT

`dpone ops cdc-replay-execute`¶

Usage: dpone ops cdc-replay-execute [--output-dir OUTPUT_DIR] [--mode {local,live}] --quarantine-json QUARANTINE_JSON --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--max-events MAX_EVENTS] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--mode MODE
--quarantine-json QUARANTINE_JSON — Path to cdc_poison_quarantine.json
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--sink-connection-id SINK_CONNECTION_ID — Sink connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--max-events MAX_EVENTS — Maximum quarantined events to replay
--format FORMAT

`dpone ops cdc-compare-repair`¶

Usage: dpone ops cdc-compare-repair --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--output-dir OUTPUT_DIR] [--mode {local,live}] [--column COLUMN] [--source-rows-json SOURCE_ROWS_JSON] [--target-rows-json TARGET_ROWS_JSON] [--source-connection-id SOURCE_CONNECTION_ID] [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--max-rows MAX_ROWS] [--max-diffs MAX_DIFFS] [--format {md,json}]
Options:
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--output-dir OUTPUT_DIR
--mode MODE
--column COLUMN — Source payload column to compare; repeatable
--source-rows-json SOURCE_ROWS_JSON — Local source rows JSON list or object with rows
--target-rows-json TARGET_ROWS_JSON — Local target rows JSON list or object with rows
--source-connection-id SOURCE_CONNECTION_ID — Source connection id for live mode
--sink-connection-id SINK_CONNECTION_ID — Sink connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--max-rows MAX_ROWS
--max-diffs MAX_DIFFS
--format FORMAT

`dpone ops cdc-repair-execute`¶

Usage: dpone ops cdc-repair-execute --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--output-dir OUTPUT_DIR] [--mode {local,live}] --repair-plan-json REPAIR_PLAN_JSON [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--max-actions MAX_ACTIONS] [--format {md,json}]
Options:
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--output-dir OUTPUT_DIR
--mode MODE
--repair-plan-json REPAIR_PLAN_JSON — Path to cdc_repair_plan.json
--sink-connection-id SINK_CONNECTION_ID — Sink connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--max-actions MAX_ACTIONS — Maximum repair actions to execute
--format FORMAT

`dpone ops cdc-retention-check`¶

Usage: dpone ops cdc-retention-check --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--output-dir OUTPUT_DIR] [--mode {local,live}] [--committed-offset COMMITTED_OFFSET] [--min-available-offset MIN_AVAILABLE_OFFSET] [--high-watermark HIGH_WATERMARK] [--current-offset CURRENT_OFFSET] [--retention-seconds RETENTION_SECONDS] [--source-connection-id SOURCE_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--capture-instance CAPTURE_INSTANCE] [--format {md,json}]
Options:
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--output-dir OUTPUT_DIR
--mode MODE
--committed-offset COMMITTED_OFFSET — Last durable CDC offset token
--min-available-offset MIN_AVAILABLE_OFFSET — Local mode source retention lower bound
--high-watermark HIGH_WATERMARK — Local mode source current high watermark
--current-offset CURRENT_OFFSET — Local mode source current offset; defaults to high watermark
--retention-seconds RETENTION_SECONDS — Optional local mode retention duration
--source-connection-id SOURCE_CONNECTION_ID — Source connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--capture-instance CAPTURE_INSTANCE — SQL Server CDC capture instance for mssql_cdc
--format FORMAT

`dpone ops cdc-resync-plan`¶

Usage: dpone ops cdc-resync-plan --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--output-dir OUTPUT_DIR] --retention-report-json RETENTION_REPORT_JSON --rows-json ROWS_JSON [--max-rows MAX_ROWS] [--format {md,json}]
Options:
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--output-dir OUTPUT_DIR
--retention-report-json RETENTION_REPORT_JSON — Path to cdc_retention_check.json
--rows-json ROWS_JSON — Snapshot rows JSON list or object with rows
--max-rows MAX_ROWS — Maximum snapshot rows to include in the plan
--format FORMAT

`dpone ops cdc-resync-execute`¶

Usage: dpone ops cdc-resync-execute --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--output-dir OUTPUT_DIR] [--mode {local,live}] --resync-plan-json RESYNC_PLAN_JSON [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--max-actions MAX_ACTIONS] [--format {md,json}]
Options:
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--output-dir OUTPUT_DIR
--mode MODE
--resync-plan-json RESYNC_PLAN_JSON — Path to cdc_resync_actions.json
--sink-connection-id SINK_CONNECTION_ID — Sink connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--max-actions MAX_ACTIONS — Maximum resync actions to execute
--format FORMAT

`dpone ops cdc-schema-evolution-evidence`¶

Usage: dpone ops cdc-schema-evolution-evidence [--output-dir OUTPUT_DIR] --handoff-json HANDOFF_JSON --apply-certification-json APPLY_CERTIFICATION_JSON --observability-json OBSERVABILITY_JSON --recovery-json RECOVERY_JSON --schema-change-json SCHEMA_CHANGE_JSON [--policy-json POLICY_JSON] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--handoff-json HANDOFF_JSON — Path to cdc_handoff.json
--apply-certification-json APPLY_CERTIFICATION_JSON — Path to cdc_apply_certification.json
--observability-json OBSERVABILITY_JSON — Path to cdc_observability.json
--recovery-json RECOVERY_JSON — Path to cdc_recovery_evidence.json
--schema-change-json SCHEMA_CHANGE_JSON — Path to CDC schema change and plan JSON
--policy-json POLICY_JSON — Optional CDC schema evolution policy JSON
--format FORMAT

`dpone ops cdc-schema-apply`¶

Usage: dpone ops cdc-schema-apply [--output-dir OUTPUT_DIR] --schema-change-json SCHEMA_CHANGE_JSON --sink {clickhouse} --target-dataset TARGET_DATASET [--mode {dry_run,apply}] [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--typed-refresh] [--cdc-dataset CDC_DATASET] [--unique-key UNIQUE_KEY] [--column COLUMN] [--require-approval] [--fail-on-parse-errors] [--max-parse-error-ratio MAX_PARSE_ERROR_RATIO] [--quarantine-dataset QUARANTINE_DATASET] [--schema-drift-mode {off,warn_additive,strict}] [--quality-sample-limit QUALITY_SAMPLE_LIMIT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--schema-change-json SCHEMA_CHANGE_JSON — Path to CDC schema change JSON
--sink SINK
--target-dataset TARGET_DATASET — Target serving dataset as database.table
--mode MODE
--sink-connection-id SINK_CONNECTION_ID — Sink connection id; required for --mode apply
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--typed-refresh — Refresh typed materialization after applying DDL
--cdc-dataset CDC_DATASET — ClickHouse CDC log dataset for typed refresh
--unique-key UNIQUE_KEY — Unique key column for typed refresh
--column COLUMN — Typed column as name=ClickHouseType for typed refresh
--require-approval
--fail-on-parse-errors
--max-parse-error-ratio MAX_PARSE_ERROR_RATIO
--quarantine-dataset QUARANTINE_DATASET — Optional ClickHouse table for typed parse quarantine rows
--schema-drift-mode SCHEMA_DRIFT_MODE
--quality-sample-limit QUALITY_SAMPLE_LIMIT
--format FORMAT

`dpone ops cdc-promotion-gate`¶

Usage: dpone ops cdc-promotion-gate [--output-dir OUTPUT_DIR] --apply-certification-json APPLY_CERTIFICATION_JSON --handoff-json HANDOFF_JSON --observability-json OBSERVABILITY_JSON --recovery-json RECOVERY_JSON --schema-evolution-json SCHEMA_EVOLUTION_JSON [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--apply-certification-json APPLY_CERTIFICATION_JSON — Path to cdc_apply_certification.json
--handoff-json HANDOFF_JSON — Path to cdc_handoff.json
--observability-json OBSERVABILITY_JSON — Path to cdc_observability.json
--recovery-json RECOVERY_JSON — Path to cdc_recovery_evidence.json
--schema-evolution-json SCHEMA_EVOLUTION_JSON — Path to cdc_schema_evolution.json
--format FORMAT

`dpone ops cdc-runtime-run`¶

Usage: dpone ops cdc-runtime-run [--output-dir OUTPUT_DIR] [--mode {local,live}] --source SOURCE --sink SINK --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY [--events-json EVENTS_JSON] [--checkpoint-json CHECKPOINT_JSON] [--source-connection-id SOURCE_CONNECTION_ID] [--sink-connection-id SINK_CONNECTION_ID] [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--state-schema STATE_SCHEMA] [--state-table STATE_TABLE] [--capture-instance CAPTURE_INSTANCE] [--change-tracking-key CHANGE_TRACKING_KEY] [--max-changes MAX_CHANGES] [--poison-mode {fail_closed,quarantine_and_continue}] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--mode MODE
--source SOURCE
--sink SINK
--backend BACKEND
--pipeline-name PIPELINE_NAME
--source-schema SOURCE_SCHEMA
--source-table SOURCE_TABLE
--target-dataset TARGET_DATASET
--unique-key UNIQUE_KEY — Unique key column; repeatable
--events-json EVENTS_JSON — Path to bounded CDC events JSON for local mode
--checkpoint-json CHECKPOINT_JSON — Path to local durable checkpoint JSON for local mode
--source-connection-id SOURCE_CONNECTION_ID — Source connection id for live mode
--sink-connection-id SINK_CONNECTION_ID — Sink connection id for live mode
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point for live mode
--credentials-path CREDENTIALS_PATH — Optional credentials path for live mode
--state-schema STATE_SCHEMA — SQL-backed CDC offset state schema for live mode
--state-table STATE_TABLE — SQL-backed CDC offset state table for live mode
--capture-instance CAPTURE_INSTANCE — SQL Server CDC capture instance override
--change-tracking-key CHANGE_TRACKING_KEY — SQL Server Change Tracking primary key column; repeatable; defaults to --unique-key
--max-changes MAX_CHANGES
--poison-mode POISON_MODE
--format FORMAT

`dpone ops safe-sample-runtime-run`¶

Usage: dpone ops safe-sample-runtime-run --plan-json PLAN_JSON [--pipeline-source PIPELINE_SOURCE] [--process-name PROCESS_NAME] [--enable-live-copy] [--binding-set BINDING_SET] [--connection-registry CONNECTION_REGISTRY] [--credential-runtime CREDENTIAL_RUNTIME] [--route-attestation ROUTE_ATTESTATION] [--route-attestation-bundle ROUTE_ATTESTATION_BUNDLE] [--route-certification-bundle ROUTE_CERTIFICATION_BUNDLE] [--route-attestation-policy ROUTE_ATTESTATION_POLICY] [--output-dir OUTPUT_DIR] [--cache-root CACHE_ROOT] [--format {md,json}]
Options:
--plan-json PLAN_JSON — Path to dpone.safe-sample-execution-plan.v1 JSON
--pipeline-source PIPELINE_SOURCE — Optional pipeline.yaml used to assemble a route-certified safe-sample copier
--process-name PROCESS_NAME — Optional process name inside --pipeline-source
--enable-live-copy — Opt in to credential-resolving certified sample copy execution
--binding-set BINDING_SET — Runtime binding-set YAML/JSON; required with --enable-live-copy
--connection-registry CONNECTION_REGISTRY — Runtime connection-registry YAML/JSON; required with --enable-live-copy
--credential-runtime CREDENTIAL_RUNTIME — Runtime credential-runtime YAML/JSON; required with --enable-live-copy
--route-attestation ROUTE_ATTESTATION — Signed deployment-bound route-attestation JSON
--route-attestation-bundle ROUTE_ATTESTATION_BUNDLE — Detached Sigstore bundle for --route-attestation
--route-certification-bundle ROUTE_CERTIFICATION_BUNDLE — Immutable route-certification evidence bundle
--route-attestation-policy ROUTE_ATTESTATION_POLICY — Platform-owned exact-identity verification policy
--output-dir OUTPUT_DIR
--cache-root CACHE_ROOT — Local materialized dpone cache root
--format FORMAT

`dpone ops cdc-materialize-clickhouse`¶

Usage: dpone ops cdc-materialize-clickhouse [--output-dir OUTPUT_DIR] --cdc-dataset CDC_DATASET --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY --sink-connection-id SINK_CONNECTION_ID [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--delete-mode {exclude_deleted,tombstone}] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--cdc-dataset CDC_DATASET — ClickHouse CDC log dataset as table or database.table
--target-dataset TARGET_DATASET — ClickHouse serving target as table or database.table
--unique-key UNIQUE_KEY — Unique key column; repeatable
--sink-connection-id SINK_CONNECTION_ID — ClickHouse connection id
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--delete-mode DELETE_MODE
--format FORMAT

`dpone ops cdc-materialize-clickhouse-typed`¶

Usage: dpone ops cdc-materialize-clickhouse-typed [--output-dir OUTPUT_DIR] --cdc-dataset CDC_DATASET --target-dataset TARGET_DATASET --unique-key UNIQUE_KEY --column COLUMN --sink-connection-id SINK_CONNECTION_ID [--credentials-source {env,vault,airflow,params}] [--credentials-mount-point CREDENTIALS_MOUNT_POINT] [--credentials-path CREDENTIALS_PATH] [--delete-mode {exclude_deleted,tombstone}] [--fail-on-parse-errors] [--max-parse-error-ratio MAX_PARSE_ERROR_RATIO] [--quarantine-dataset QUARANTINE_DATASET] [--schema-drift-mode {off,warn_additive,strict}] [--quality-sample-limit QUALITY_SAMPLE_LIMIT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--cdc-dataset CDC_DATASET — ClickHouse CDC log dataset as table or database.table
--target-dataset TARGET_DATASET — Typed ClickHouse serving target
--unique-key UNIQUE_KEY — Unique key column; repeatable
--column COLUMN — Projected typed column as name=ClickHouseType; repeatable
--sink-connection-id SINK_CONNECTION_ID — ClickHouse connection id
--credentials-source CREDENTIALS_SOURCE
--credentials-mount-point CREDENTIALS_MOUNT_POINT — Optional credentials mount point
--credentials-path CREDENTIALS_PATH — Optional credentials path
--delete-mode DELETE_MODE
--fail-on-parse-errors — Fail closed when typed projection parse failures exceed --max-parse-error-ratio
--max-parse-error-ratio MAX_PARSE_ERROR_RATIO
--quarantine-dataset QUARANTINE_DATASET — Optional ClickHouse table for typed parse quarantine rows
--schema-drift-mode SCHEMA_DRIFT_MODE
--quality-sample-limit QUALITY_SAMPLE_LIMIT
--format FORMAT

`dpone ops recovery-plan`¶

Usage: dpone ops recovery-plan [--state-dir STATE_DIR] [--lock-dir LOCK_DIR] [--load-package-dir LOAD_PACKAGE_DIR] [--output-dir OUTPUT_DIR] [--format {md,json}]
Options:
--state-dir STATE_DIR
--lock-dir LOCK_DIR
--load-package-dir LOAD_PACKAGE_DIR
--output-dir OUTPUT_DIR
--format FORMAT

`dpone ops reconcile`¶

Usage: dpone ops reconcile [--output-dir OUTPUT_DIR] --source-rows-json SOURCE_ROWS_JSON --target-rows-json TARGET_ROWS_JSON --key KEY [--compare-columns COMPARE_COLUMNS] [--delete-column DELETE_COLUMN] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--source-rows-json SOURCE_ROWS_JSON
--target-rows-json TARGET_ROWS_JSON
--key KEY — Comma-separated key columns
--compare-columns COMPARE_COLUMNS — Comma-separated compare columns
--delete-column DELETE_COLUMN — Source delete marker/timestamp column
--format FORMAT

`dpone ops observability-pack`¶

Usage: dpone ops observability-pack [--output-dir OUTPUT_DIR] [--service-name SERVICE_NAME] [--dashboard-title DASHBOARD_TITLE] [--alert ALERT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--service-name SERVICE_NAME
--dashboard-title DASHBOARD_TITLE
--alert ALERT — Alert threshold as metric.max=value or metric.min=value
--format FORMAT

`dpone ops deploy-render`¶

Usage: dpone ops deploy-render [--output-dir OUTPUT_DIR] --target {docker-compose,k8s-cronjob,airflow,dagster} --manifest MANIFEST [--selector SELECTOR] [--image IMAGE] [--schedule SCHEDULE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--target TARGET
--manifest MANIFEST
--selector SELECTOR
--image IMAGE
--schedule SCHEDULE
--format FORMAT

`dpone ops staging-evidence`¶

Usage: dpone ops staging-evidence [--output-dir OUTPUT_DIR] --manifest MANIFEST --sink {mssql,postgres,clickhouse,bigquery} --target-table TARGET_TABLE [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--manifest MANIFEST — Path to object storage staging manifest JSON
--sink SINK
--target-table TARGET_TABLE
--format FORMAT

`dpone ops catalog-publish`¶

Usage: dpone ops catalog-publish [--output-dir OUTPUT_DIR] --run-registry-entry RUN_REGISTRY_ENTRY [--namespace NAMESPACE] [--input INPUT] [--output OUTPUT] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--run-registry-entry RUN_REGISTRY_ENTRY
--namespace NAMESPACE
--input INPUT — Input dataset as namespace=name
--output OUTPUT — Output dataset as namespace=name
--format FORMAT

`dpone ops live-certification-plan`¶

Usage: dpone ops live-certification-plan [--output-dir OUTPUT_DIR] [--profile {local_live,real_local,type_matrix_certification,native_transfer,vendor_live}] [--row-count ROW_COUNT] [--include-vendor-live] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--profile PROFILE
--row-count ROW_COUNT
--include-vendor-live
--format FORMAT

`dpone ops managed-credentials-readiness`¶

Usage: dpone ops managed-credentials-readiness [--output-dir OUTPUT_DIR] [--profile PROFILE] [--required-env REQUIRED_ENV] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--profile PROFILE
--required-env REQUIRED_ENV — Required environment variable name; can be repeated
--format FORMAT

`dpone ops benchmark-slo-gate`¶

Usage: dpone ops benchmark-slo-gate [--output-dir OUTPUT_DIR] --metrics-json METRICS_JSON --baseline-json BASELINE_JSON --objectives-json OBJECTIVES_JSON [--allowed-regression-ratio ALLOWED_REGRESSION_RATIO] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--metrics-json METRICS_JSON
--baseline-json BASELINE_JSON
--objectives-json OBJECTIVES_JSON
--allowed-regression-ratio ALLOWED_REGRESSION_RATIO
--format FORMAT

`dpone ops performance-certification`¶

Usage: dpone ops performance-certification [--output-dir OUTPUT_DIR] [--profile PROFILE] [--row-count ROW_COUNT] --metrics-json METRICS_JSON [--minimum-json MINIMUM_JSON] [--maximum-json MAXIMUM_JSON] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--profile PROFILE
--row-count ROW_COUNT
--metrics-json METRICS_JSON
--minimum-json MINIMUM_JSON
--maximum-json MAXIMUM_JSON
--format FORMAT

`dpone ops live-state-reconciliation`¶

Usage: dpone ops live-state-reconciliation [--output-dir OUTPUT_DIR] [--profile PROFILE] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--profile PROFILE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required evidence artifact name
--format FORMAT

`dpone ops release-evidence-pack`¶

Usage: dpone ops release-evidence-pack [--output-dir OUTPUT_DIR] --release RELEASE [--profile PROFILE] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--profile PROFILE
--artifact ARTIFACT — Artifact reference as name=/path/to/file
--require REQUIRE — Required evidence artifact name
--format FORMAT

`dpone ops pre-release-checklist`¶

Usage: dpone ops pre-release-checklist [--output-dir OUTPUT_DIR] --release RELEASE [--release-type {patch,minor,major}] [--check CHECK] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--release RELEASE
--release-type RELEASE_TYPE
--check CHECK — Check result as name=true|false
--format FORMAT

`dpone ops object-storage budget`¶

Usage: dpone ops object-storage budget [--warn-usage-pct WARN_USAGE_PCT] [--block-usage-pct BLOCK_USAGE_PCT] [--orphan-ttl-hours ORPHAN_TTL_HOURS] [--failed-run-ttl-hours FAILED_RUN_TTL_HOURS] [--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS] [--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS] [--require-lifecycle-rule {off,warn,required}] --uri-prefix URI_PREFIX [--local-root-dir LOCAL_ROOT_DIR] [--connection-type CONNECTION_TYPE] [--connection-id CONNECTION_ID] [--limit BUCKET_LIMIT_BYTES] [--expected-run-bytes EXPECTED_RUN_BYTES] [--format {json,md}]
Options:
--warn-usage-pct WARN_USAGE_PCT
--block-usage-pct BLOCK_USAGE_PCT
--orphan-ttl-hours ORPHAN_TTL_HOURS
--failed-run-ttl-hours FAILED_RUN_TTL_HOURS
--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS
--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS
--require-lifecycle-rule REQUIRE_LIFECYCLE_RULE
--uri-prefix URI_PREFIX
--local-root-dir LOCAL_ROOT_DIR
--connection-type CONNECTION_TYPE
--connection-id CONNECTION_ID
--limit BUCKET_LIMIT_BYTES
--expected-run-bytes EXPECTED_RUN_BYTES
--format FORMAT

`dpone ops object-storage cleanup`¶

Usage: dpone ops object-storage cleanup [--warn-usage-pct WARN_USAGE_PCT] [--block-usage-pct BLOCK_USAGE_PCT] [--orphan-ttl-hours ORPHAN_TTL_HOURS] [--failed-run-ttl-hours FAILED_RUN_TTL_HOURS] [--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS] [--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS] [--require-lifecycle-rule {off,warn,required}] --uri-prefix URI_PREFIX [--local-root-dir LOCAL_ROOT_DIR] [--connection-type CONNECTION_TYPE] [--connection-id CONNECTION_ID] [--mode {dry-run,execute}] [--now NOW] [--format {json,md}]
Options:
--warn-usage-pct WARN_USAGE_PCT
--block-usage-pct BLOCK_USAGE_PCT
--orphan-ttl-hours ORPHAN_TTL_HOURS
--failed-run-ttl-hours FAILED_RUN_TTL_HOURS
--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS
--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS
--require-lifecycle-rule REQUIRE_LIFECYCLE_RULE
--uri-prefix URI_PREFIX
--local-root-dir LOCAL_ROOT_DIR
--connection-type CONNECTION_TYPE
--connection-id CONNECTION_ID
--mode MODE
--now NOW
--format FORMAT

`dpone ops object-storage lifecycle render`¶

Usage: dpone ops object-storage lifecycle render [--warn-usage-pct WARN_USAGE_PCT] [--block-usage-pct BLOCK_USAGE_PCT] [--orphan-ttl-hours ORPHAN_TTL_HOURS] [--failed-run-ttl-hours FAILED_RUN_TTL_HOURS] [--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS] [--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS] [--require-lifecycle-rule {off,warn,required}] --uri-prefix URI_PREFIX [--format {json,md}]
Options:
--warn-usage-pct WARN_USAGE_PCT
--block-usage-pct BLOCK_USAGE_PCT
--orphan-ttl-hours ORPHAN_TTL_HOURS
--failed-run-ttl-hours FAILED_RUN_TTL_HOURS
--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS
--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS
--require-lifecycle-rule REQUIRE_LIFECYCLE_RULE
--uri-prefix URI_PREFIX
--format FORMAT

`dpone ops object-storage lifecycle verify`¶

Usage: dpone ops object-storage lifecycle verify [--warn-usage-pct WARN_USAGE_PCT] [--block-usage-pct BLOCK_USAGE_PCT] [--orphan-ttl-hours ORPHAN_TTL_HOURS] [--failed-run-ttl-hours FAILED_RUN_TTL_HOURS] [--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS] [--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS] [--require-lifecycle-rule {off,warn,required}] --uri-prefix URI_PREFIX [--format {json,md}]
Options:
--warn-usage-pct WARN_USAGE_PCT
--block-usage-pct BLOCK_USAGE_PCT
--orphan-ttl-hours ORPHAN_TTL_HOURS
--failed-run-ttl-hours FAILED_RUN_TTL_HOURS
--lifecycle-expiration-days LIFECYCLE_EXPIRATION_DAYS
--abort-incomplete-multipart-days ABORT_INCOMPLETE_MULTIPART_DAYS
--require-lifecycle-rule REQUIRE_LIFECYCLE_RULE
--uri-prefix URI_PREFIX
--format FORMAT

`dpone orchestrate`¶

`dpone orchestrate run`¶

Usage: dpone orchestrate run --manifest MANIFEST [--selector SELECTOR] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] [--retry-attempts RETRY_ATTEMPTS] [--retry-backoff-seconds RETRY_BACKOFF_SECONDS] [--concurrency-key CONCURRENCY_KEY] [--lock-dir LOCK_DIR] [--state-dir STATE_DIR] [--lock-ttl-seconds LOCK_TTL_SECONDS] [--resume-policy {fail,resume,restart}] [--output-dir OUTPUT_DIR] [--registry REGISTRY] [--format {md,json}]
Options:
--manifest MANIFEST — Path to a YAML manifest
--selector SELECTOR — Process selector inside a batch manifest
--run-id RUN_ID — Explicit run id
--dag-id DAG_ID
--execution-date EXECUTION_DATE
--retry-attempts RETRY_ATTEMPTS
--retry-backoff-seconds RETRY_BACKOFF_SECONDS
--concurrency-key CONCURRENCY_KEY
--lock-dir LOCK_DIR
--state-dir STATE_DIR
--lock-ttl-seconds LOCK_TTL_SECONDS
--resume-policy RESUME_POLICY
--output-dir OUTPUT_DIR
--registry REGISTRY
--format FORMAT

`dpone observability`¶

`dpone observability metrics-export`¶

Usage: dpone observability metrics-export [--output-dir OUTPUT_DIR] [--run-report RUN_REPORT] [--metric METRIC] [--label LABEL] [--resource-attr RESOURCE_ATTR] [--service-name SERVICE_NAME] [--namespace NAMESPACE] [--airflow-evidence-bundle AIRFLOW_EVIDENCE_BUNDLE] [--format {md,json}]
Options:
--output-dir OUTPUT_DIR
--run-report RUN_REPORT — Path to JSON output from dpone run --format json
--metric METRIC — Custom numeric metric as name=value; can be repeated
--label LABEL — Metric label as key=value; can be repeated
--resource-attr RESOURCE_ATTR — OpenTelemetry resource attribute as key=value; can be repeated
--service-name SERVICE_NAME
--namespace NAMESPACE
--airflow-evidence-bundle AIRFLOW_EVIDENCE_BUNDLE — Optional final Airflow evidence bundle used for OpenTelemetry correlation
--format FORMAT

`dpone supply-chain`¶

`dpone supply-chain attest`¶

Usage: dpone supply-chain attest [--project-root PROJECT_ROOT] [--output-dir OUTPUT_DIR] --release RELEASE --subject SUBJECT --repository REPOSITORY --commit-sha COMMIT_SHA [--builder-id BUILDER_ID] [--signing-key SIGNING_KEY] [--signing-key-id SIGNING_KEY_ID] [--format {md,json}]
Options:
--project-root PROJECT_ROOT
--output-dir OUTPUT_DIR
--release RELEASE
--subject SUBJECT — Artifact file to include as provenance subject
--repository REPOSITORY
--commit-sha COMMIT_SHA
--builder-id BUILDER_ID
--signing-key SIGNING_KEY — Local HMAC signing key; prefer CI secret or Sigstore/GitHub attestation
--signing-key-id SIGNING_KEY_ID
--format FORMAT

`dpone supply-chain catalog-bundle-build`¶

Usage: dpone supply-chain catalog-bundle-build [--project-root PROJECT_ROOT] --kind {recipe_catalog,connection_registry} --source SOURCE --bundle-root BUNDLE_ROOT --publisher-id PUBLISHER_ID [--environment ENVIRONMENT] [--format {md,json}]
Options:
--project-root PROJECT_ROOT
--kind KIND
--source SOURCE
--bundle-root BUNDLE_ROOT
--publisher-id PUBLISHER_ID
--environment ENVIRONMENT
--format FORMAT

`dpone supply-chain catalog-bundle-verify`¶

Usage: dpone supply-chain catalog-bundle-verify --bundle-dir BUNDLE_DIR --sigstore-bundle SIGSTORE_BUNDLE --policy POLICY --trusted-root TRUSTED_ROOT --output OUTPUT [--format {md,json}]
Options:
--bundle-dir BUNDLE_DIR
--sigstore-bundle SIGSTORE_BUNDLE
--policy POLICY
--trusted-root TRUSTED_ROOT
--output OUTPUT
--format FORMAT

`dpone supply-chain extension-conformance`¶

Usage: dpone supply-chain extension-conformance [--project-root PROJECT_ROOT] --request REQUEST --output-dir OUTPUT_DIR [--format {md,json}]
Options:
--project-root PROJECT_ROOT
--request REQUEST
--output-dir OUTPUT_DIR
--format FORMAT

`dpone strategy`¶

`dpone strategy advise`¶

Usage: dpone strategy advise [--estimated-rows ESTIMATED_ROWS] [--changed-percent CHANGED_PERCENT] [--delete-percent DELETE_PERCENT] [--cdc-available] [--format {text,json,md}] path
Positional arguments:
path
Options:
--estimated-rows ESTIMATED_ROWS
--changed-percent CHANGED_PERCENT
--delete-percent DELETE_PERCENT
--cdc-available
--format FORMAT

`dpone strategy preflight`¶

Usage: dpone strategy preflight --source-type SOURCE_TYPE --sink-type SINK_TYPE [--fail-on-missing] [--format {text,json,md}]
Options:
--source-type SOURCE_TYPE
--sink-type SINK_TYPE
--fail-on-missing
--format FORMAT

`dpone strategy repair-plan`¶

Usage: dpone strategy repair-plan --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--failed-stage FAILED_STAGE] [--partition PARTITION] [--format {text,json,md}] run_id
Positional arguments:
run_id
Options:
--source-type SOURCE_TYPE
--sink-type SINK_TYPE
--strategy STRATEGY
--failed-stage FAILED_STAGE
--partition PARTITION
--format FORMAT

`dpone strategy certification-artifact`¶

Usage: dpone strategy certification-artifact [--artifact-dir ARTIFACT_DIR] [--format {text,json,md}]
Options:
--artifact-dir ARTIFACT_DIR
--format FORMAT

`dpone strategy certification-bundle`¶

Usage: dpone strategy certification-bundle --bundle-id BUNDLE_ID [--output-dir OUTPUT_DIR] [--replay-evidence REPLAY_EVIDENCE] [--matrix-artifact MATRIX_ARTIFACT] [--connector-artifact CONNECTOR_ARTIFACT] [--benchmark-artifact BENCHMARK_ARTIFACT] [--native-transfer-evidence NATIVE_TRANSFER_EVIDENCE] [--docs-link DOCS_LINK] [--format {text,json,md}]
Options:
--bundle-id BUNDLE_ID
--output-dir OUTPUT_DIR
--replay-evidence REPLAY_EVIDENCE
--matrix-artifact MATRIX_ARTIFACT
--connector-artifact CONNECTOR_ARTIFACT
--benchmark-artifact BENCHMARK_ARTIFACT
--native-transfer-evidence NATIVE_TRANSFER_EVIDENCE
--docs-link DOCS_LINK
--format FORMAT

`dpone strategy native-transfer-evidence`¶

Usage: dpone strategy native-transfer-evidence --run-id RUN_ID (--plan-json PLAN_JSON | --contract-json CONTRACT_JSON) [--payload PAYLOAD] [--output-dir OUTPUT_DIR] [--format {text,json,md}]
Options:
--run-id RUN_ID
--plan-json PLAN_JSON
--contract-json CONTRACT_JSON
--payload PAYLOAD — Artifact payload as artifact_name=path
--output-dir OUTPUT_DIR
--format FORMAT

`dpone perf`¶

`dpone perf advise`¶

Usage: dpone perf advise [--selector SELECTOR] [--format {text,json,md}] path
Positional arguments:
path
Options:
--selector SELECTOR
--format FORMAT

`dpone profile`¶

`dpone profile advise`¶

Usage: dpone profile advise [--row-count ROW_COUNT] [--column-count COLUMN_COUNT] [--estimated-bytes-per-row ESTIMATED_BYTES_PER_ROW] [--worker-profile WORKER_PROFILE] [--goal {balanced,performance,safety,cost}] [--target-chunk-bytes TARGET_CHUNK_BYTES] [--current-max-chunk-rows CURRENT_MAX_CHUNK_ROWS] [--format {text,json,md}] path
Positional arguments:
path
Options:
--row-count ROW_COUNT
--column-count COLUMN_COUNT
--estimated-bytes-per-row ESTIMATED_BYTES_PER_ROW
--worker-profile WORKER_PROFILE
--goal GOAL — Optimization intent for recommendations. Use performance to prefer larger safe windows.
--target-chunk-bytes TARGET_CHUNK_BYTES
--current-max-chunk-rows CURRENT_MAX_CHUNK_ROWS
--format FORMAT

`dpone profile wizard`¶

Usage: dpone profile wizard [--row-count ROW_COUNT] [--column-count COLUMN_COUNT] [--estimated-bytes-per-row ESTIMATED_BYTES_PER_ROW] [--worker-profile WORKER_PROFILE] [--goal {balanced,performance,safety,cost}] [--target-chunk-bytes TARGET_CHUNK_BYTES] [--current-max-chunk-rows CURRENT_MAX_CHUNK_ROWS] [--format {text,json,md}] --output OUTPUT path
Positional arguments:
path
Options:
--row-count ROW_COUNT
--column-count COLUMN_COUNT
--estimated-bytes-per-row ESTIMATED_BYTES_PER_ROW
--worker-profile WORKER_PROFILE
--goal GOAL — Optimization intent for recommendations. Use performance to prefer larger safe windows.
--target-chunk-bytes TARGET_CHUNK_BYTES
--current-max-chunk-rows CURRENT_MAX_CHUNK_ROWS
--format FORMAT
--output OUTPUT — YAML patch output path

`dpone runtime`¶

`dpone runtime storage gc`¶

Usage: dpone runtime storage gc --work-dir WORK_DIR [--older-than-seconds OLDER_THAN_SECONDS] [--dry-run] [--apply] [--format {json,md}]
Options:
--work-dir WORK_DIR
--older-than-seconds OLDER_THAN_SECONDS
--dry-run
--apply
--format FORMAT

`dpone runtime native-accel doctor`¶

Usage: dpone runtime native-accel doctor [--format {json,md,table}]
Options:
--format FORMAT

`dpone runtime native-accel benchmark`¶

Usage: dpone runtime native-accel benchmark --manifest MANIFEST [--rows ROWS] --output OUTPUT [--format {json,md,table}]
Options:
--manifest MANIFEST
--rows ROWS
--output OUTPUT
--format FORMAT

`dpone data`¶

`dpone data product slo plan`¶

Usage: dpone data product slo plan --manifest MANIFEST [--contract-gate CONTRACT_GATE] [--consumer-gate CONSUMER_GATE] [--consumer-certification CONSUMER_CERTIFICATION] [--assertion-gate ASSERTION_GATE] [--watch-certificate WATCH_CERTIFICATE] [--post-apply-certificate POST_APPLY_CERTIFICATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--contract-gate CONTRACT_GATE — Optional schema contract gate receipt
--consumer-gate CONSUMER_GATE — Optional schema contract consumer gate receipt
--consumer-certification CONSUMER_CERTIFICATION — Optional consumer certification receipt
--assertion-gate ASSERTION_GATE — Optional data product assertion gate receipt
--watch-certificate WATCH_CERTIFICATE — Optional release watch certificate
--post-apply-certificate POST_APPLY_CERTIFICATE — Optional post-apply certificate
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product slo evaluate`¶

Usage: dpone data product slo evaluate --plan PLAN [--registry REGISTRY] [--runtime-artifact RUNTIME_ARTIFACT] [--target-connection TARGET_CONNECTION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — SLO plan artifact
--registry REGISTRY — Optional evidence registry JSON/SQLite
--runtime-artifact RUNTIME_ARTIFACT — Optional runtime/run evidence JSON/YAML
--target-connection TARGET_CONNECTION — Optional read-only target connection JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product slo gate`¶

Usage: dpone data product slo gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — SLO evaluation artifact
--profile PROFILE — SLO gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product slo budget plan`¶

Usage: dpone data product slo budget plan --manifest MANIFEST [--slo-evaluation SLO_EVALUATION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--slo-evaluation SLO_EVALUATION — Optional latest SLO evaluation artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product slo budget evaluate`¶

Usage: dpone data product slo budget evaluate --plan PLAN [--history HISTORY] [--registry REGISTRY] [--observed-at OBSERVED_AT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Error-budget plan artifact
--history HISTORY — Optional SLO evaluation history JSON/YAML
--registry REGISTRY — Optional evidence registry JSON/SQLite
--observed-at OBSERVED_AT — Deterministic evaluation timestamp
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product slo budget gate`¶

Usage: dpone data product slo budget gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Error-budget evaluation artifact
--profile PROFILE — Error-budget gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product audit archive plan`¶

Usage: dpone data product audit archive plan --manifest MANIFEST [--bundle BUNDLE] [--registry REGISTRY] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--bundle BUNDLE — Optional schema migration bundle JSON/YAML
--registry REGISTRY — Optional evidence registry JSON/SQLite
--evidence-dir EVIDENCE_DIR — Optional directory with local evidence artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product audit archive run`¶

Usage: dpone data product audit archive run --plan PLAN [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Audit archive plan artifact
--execute — Write archive files
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product audit archive verify`¶

Usage: dpone data product audit archive verify --archive-run ARCHIVE_RUN [--format {text,json,md,table}] [--output OUTPUT]
Options:
--archive-run ARCHIVE_RUN — Audit archive run artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product audit retention plan`¶

Usage: dpone data product audit retention plan --manifest MANIFEST --archive-verification ARCHIVE_VERIFICATION [--legal-hold LEGAL_HOLD] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--archive-verification ARCHIVE_VERIFICATION — Archive verification artifact
--legal-hold LEGAL_HOLD — Optional legal hold artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product audit legal-hold apply`¶

Usage: dpone data product audit legal-hold apply --archive-run ARCHIVE_RUN --reason REASON [--authority-gate AUTHORITY_GATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--archive-run ARCHIVE_RUN — Audit archive run artifact
--reason REASON — Legal hold reason
--authority-gate AUTHORITY_GATE — Optional authority gate evidence
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product assertions plan`¶

Usage: dpone data product assertions plan --manifest MANIFEST [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product assertions evaluate`¶

Usage: dpone data product assertions evaluate --plan PLAN [--runtime-artifact RUNTIME_ARTIFACT] [--target-connection TARGET_CONNECTION] [--target-evidence TARGET_EVIDENCE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Assertion plan artifact
--runtime-artifact RUNTIME_ARTIFACT — Optional runtime/run evidence JSON/YAML
--target-connection TARGET_CONNECTION — Optional read-only target connection JSON/YAML
--target-evidence TARGET_EVIDENCE — Optional precomputed read-only target evidence JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product assertions gate`¶

Usage: dpone data product assertions gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Assertion evaluation artifact
--profile PROFILE — Assertion gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product assertions report`¶

Usage: dpone data product assertions report --evaluation EVALUATION [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Assertion evaluation artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product policy evaluate`¶

Usage: dpone data product policy evaluate --manifest MANIFEST [--bundle BUNDLE] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--bundle BUNDLE — Optional schema migration bundle JSON/YAML
--evidence-dir EVIDENCE_DIR — Optional directory with local evidence artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product policy waiver request`¶

Usage: dpone data product policy waiver request --evaluation EVALUATION --rule-id RULE_ID --reason REASON --expires-at EXPIRES_AT [--requested-by REQUESTED_BY] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Policy evaluation artifact
--rule-id RULE_ID — Failed or warning rule id to waive
--reason REASON — Waiver reason
--expires-at EXPIRES_AT — Waiver expiry timestamp
--requested-by REQUESTED_BY — Optional requester identity
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product policy waiver approve`¶

Usage: dpone data product policy waiver approve --request REQUEST --actor ACTOR --approval APPROVAL [--authority-check AUTHORITY_CHECK] [--approval-quorum APPROVAL_QUORUM] [--approved-at APPROVED_AT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--request REQUEST — Waiver request artifact
--actor ACTOR — Approving actor
--approval APPROVAL — Approval evidence JSON/YAML
--authority-check AUTHORITY_CHECK — Optional authority check artifact
--approval-quorum APPROVAL_QUORUM — Optional approval quorum artifact
--approved-at APPROVED_AT — Approval timestamp
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product policy gate`¶

Usage: dpone data product policy gate --evaluation EVALUATION [--waiver WAIVER] [--authority-gate AUTHORITY_GATE] [--profile {advisory,stage,prod_strict,regulated}] [--observed-at OBSERVED_AT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Policy evaluation artifact
--waiver WAIVER — Optional approved waiver artifact
--authority-gate AUTHORITY_GATE — Optional authority gate artifact
--profile PROFILE — Policy gate profile
--observed-at OBSERVED_AT — Timestamp used for waiver expiry checks
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product policy report`¶

Usage: dpone data product policy report --gate GATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Policy gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority registry build`¶

Usage: dpone data product authority registry build --manifest MANIFEST [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority check`¶

Usage: dpone data product authority check --registry REGISTRY --actor ACTOR --action ACTION --subject SUBJECT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--registry REGISTRY — Authority registry artifact
--actor ACTOR — Actor id
--action ACTION — Action grant, such as policy_waiver.approve
--subject SUBJECT — Subject evidence artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority quorum verify`¶

Usage: dpone data product authority quorum verify --registry REGISTRY --request REQUEST --approval APPROVAL [--format {text,json,md,table}] [--output OUTPUT]
Options:
--registry REGISTRY — Authority registry artifact
--request REQUEST — Waiver or release request artifact
--approval APPROVAL — Approval evidence JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority signature sign`¶

Usage: dpone data product authority signature sign --registry REGISTRY --artifact ARTIFACT --actor ACTOR [--format {text,json,md,table}] [--output OUTPUT]
Options:
--registry REGISTRY — Authority registry artifact
--artifact ARTIFACT — Evidence artifact to sign
--actor ACTOR — Signing actor
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority signature verify`¶

Usage: dpone data product authority signature verify --registry REGISTRY --artifact ARTIFACT --signature SIGNATURE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--registry REGISTRY — Authority registry artifact
--artifact ARTIFACT — Evidence artifact to verify
--signature SIGNATURE — Detached evidence signature artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority gate`¶

Usage: dpone data product authority gate [--authority-check AUTHORITY_CHECK] [--approval-quorum APPROVAL_QUORUM] [--signature SIGNATURE] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--authority-check AUTHORITY_CHECK — Authority check artifact
--approval-quorum APPROVAL_QUORUM — Approval quorum artifact
--signature SIGNATURE — Evidence signature artifact
--profile PROFILE — Authority gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product authority report`¶

Usage: dpone data product authority report --gate GATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Authority gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product compliance controls plan`¶

Usage: dpone data product compliance controls plan --manifest MANIFEST [--bundle BUNDLE] [--registry REGISTRY] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--bundle BUNDLE — Optional schema migration bundle JSON/YAML
--registry REGISTRY — Optional evidence registry JSON/SQLite
--evidence-dir EVIDENCE_DIR — Optional directory with local evidence artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product compliance controls evaluate`¶

Usage: dpone data product compliance controls evaluate --plan PLAN [--observed-at OBSERVED_AT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Compliance control plan artifact
--observed-at OBSERVED_AT — Optional timestamp for stale-evidence checks
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product compliance controls gate`¶

Usage: dpone data product compliance controls gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Compliance control evaluation artifact
--profile PROFILE — Compliance gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product compliance audit package`¶

Usage: dpone data product compliance audit package --gate GATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Compliance gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product governance export plan`¶

Usage: dpone data product governance export plan --manifest MANIFEST [--registry REGISTRY] [--evidence-dir EVIDENCE_DIR] [--targets TARGETS] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--registry REGISTRY — Optional evidence registry JSON/SQLite
--evidence-dir EVIDENCE_DIR — Directory with local evidence artifacts
--targets TARGETS — Comma-separated providers
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product governance export render`¶

Usage: dpone data product governance export render --plan PLAN --target TARGET [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Governance export plan artifact
--target TARGET — Provider target
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product governance publish`¶

Usage: dpone data product governance publish --payload PAYLOAD --provider PROVIDER [--connection CONNECTION] [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--payload PAYLOAD — Governance payload artifact
--provider PROVIDER — Provider target
--connection CONNECTION — Optional provider connection JSON/YAML
--execute — Validate an explicit publish execution
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product governance verify`¶

Usage: dpone data product governance verify --receipt RECEIPT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--receipt RECEIPT — Publish receipt artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access classify`¶

Usage: dpone data product access classify --manifest MANIFEST [--schema-contract SCHEMA_CONTRACT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--schema-contract SCHEMA_CONTRACT — Optional schema contract version artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access entitlements plan`¶

Usage: dpone data product access entitlements plan --manifest MANIFEST --classification CLASSIFICATION [--consumer-matrix CONSUMER_MATRIX] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--classification CLASSIFICATION — Access classification artifact
--consumer-matrix CONSUMER_MATRIX — Optional schema contract consumer matrix artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access enforcement plan`¶

Usage: dpone data product access enforcement plan --manifest MANIFEST --classification CLASSIFICATION --entitlement-plan ENTITLEMENT_PLAN --privacy-impact PRIVACY_IMPACT [--access-gate ACCESS_GATE] [--authority-gate AUTHORITY_GATE] --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--classification CLASSIFICATION — Access classification artifact
--entitlement-plan ENTITLEMENT_PLAN — Entitlement plan artifact
--privacy-impact PRIVACY_IMPACT — Privacy impact artifact
--access-gate ACCESS_GATE — Optional access gate artifact
--authority-gate AUTHORITY_GATE — Optional authority gate artifact
--target-connection TARGET_CONNECTION — Target connection JSON/YAML
--environment ENVIRONMENT — Environment name
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access enforcement apply`¶

Usage: dpone data product access enforcement apply --plan PLAN [--approval APPROVAL] [--target-connection TARGET_CONNECTION] [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Access enforcement plan artifact
--approval APPROVAL — Optional approval artifact
--target-connection TARGET_CONNECTION — Target connection JSON/YAML, required with --execute
--execute — Mutate target access state
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access enforcement certify`¶

Usage: dpone data product access enforcement certify --run RUN --drift-report DRIFT_REPORT [--target-connection TARGET_CONNECTION] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — Access enforcement run artifact
--drift-report DRIFT_REPORT — Access drift report artifact
--target-connection TARGET_CONNECTION — Optional target connection JSON/YAML
--profile PROFILE — Certification profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access enforcement report`¶

Usage: dpone data product access enforcement report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — Access enforcement certificate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access drift inspect`¶

Usage: dpone data product access drift inspect --plan PLAN --target-connection TARGET_CONNECTION [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Access enforcement plan artifact
--target-connection TARGET_CONNECTION — Target connection or access-state artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access gate`¶

Usage: dpone data product access gate --entitlement-plan ENTITLEMENT_PLAN --privacy-impact PRIVACY_IMPACT [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--entitlement-plan ENTITLEMENT_PLAN — Entitlement plan artifact
--privacy-impact PRIVACY_IMPACT — Privacy impact artifact
--profile PROFILE — Access governance profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product access report`¶

Usage: dpone data product access report --gate GATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Access gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product privacy impact assess`¶

Usage: dpone data product privacy impact assess --manifest MANIFEST --entitlement-plan ENTITLEMENT_PLAN [--authority-gate AUTHORITY_GATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--entitlement-plan ENTITLEMENT_PLAN — Entitlement plan artifact
--authority-gate AUTHORITY_GATE — Optional authority gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident report`¶

Usage: dpone data product incident report --evaluation EVALUATION --slo-gate SLO_GATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — SLO evaluation artifact
--slo-gate SLO_GATE — SLO gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident lifecycle open`¶

Usage: dpone data product incident lifecycle open --slo-evaluation SLO_EVALUATION --slo-gate SLO_GATE --budget-gate BUDGET_GATE [--existing-incident EXISTING_INCIDENT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--slo-evaluation SLO_EVALUATION — SLO evaluation artifact
--slo-gate SLO_GATE — SLO gate artifact
--budget-gate BUDGET_GATE — Error-budget gate artifact
--existing-incident EXISTING_INCIDENT — Optional existing incident lifecycle artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident lifecycle ack`¶

Usage: dpone data product incident lifecycle ack --incident INCIDENT --actor ACTOR [--format {text,json,md,table}] [--output OUTPUT]
Options:
--incident INCIDENT — Incident lifecycle artifact
--actor ACTOR — Acknowledging actor
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident lifecycle resolve`¶

Usage: dpone data product incident lifecycle resolve --incident INCIDENT --evidence EVIDENCE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--incident INCIDENT — Incident lifecycle artifact
--evidence EVIDENCE — Resolution evidence artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident route render`¶

Usage: dpone data product incident route render --incident INCIDENT --provider {slack,jira,pagerduty} [--format {text,json,md,table}] [--output OUTPUT]
Options:
--incident INCIDENT — Incident lifecycle artifact
--provider PROVIDER — Route provider
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product incident route dry-run`¶

Usage: dpone data product incident route dry-run --payload PAYLOAD --provider {slack,jira,pagerduty,webhook} [--format {text,json,md,table}] [--output OUTPUT]
Options:
--payload PAYLOAD — Incident route payload artifact
--provider PROVIDER — Route provider
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product release closeout gate`¶

Usage: dpone data product release closeout gate --slo-gate SLO_GATE --budget-gate BUDGET_GATE [--incident INCIDENT] [--watch-certificate WATCH_CERTIFICATE] [--post-apply-certificate POST_APPLY_CERTIFICATE] [--policy-gate POLICY_GATE] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--slo-gate SLO_GATE — SLO gate artifact
--budget-gate BUDGET_GATE — Error-budget gate artifact
--incident INCIDENT — Optional incident lifecycle artifact
--watch-certificate WATCH_CERTIFICATE — Optional release watch certificate
--post-apply-certificate POST_APPLY_CERTIFICATE — Optional post-apply certificate
--policy-gate POLICY_GATE — Optional data product policy gate artifact
--profile PROFILE — Release closeout profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product fleet evaluate`¶

Usage: dpone data product fleet evaluate --manifests MANIFESTS [--registry REGISTRY] [--observed-at OBSERVED_AT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifests MANIFESTS — Manifest path or glob pattern
--registry REGISTRY — Optional evidence registry JSON/SQLite
--observed-at OBSERVED_AT — Deterministic evaluation timestamp
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product fleet gate`¶

Usage: dpone data product fleet gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Fleet evaluation artifact
--profile PROFILE — Fleet gate profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product fleet report`¶

Usage: dpone data product fleet report --evaluation EVALUATION [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Fleet evaluation artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product fleet export`¶

Usage: dpone data product fleet export --evaluation EVALUATION --target {prometheus,opentelemetry,openlineage,datahub,json} [--format {text,json}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Fleet evaluation artifact
--target TARGET — Export target format
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product cost plan`¶

Usage: dpone data product cost plan --manifest MANIFEST [--bundle BUNDLE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--bundle BUNDLE — Optional schema migration bundle JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product cost evaluate`¶

Usage: dpone data product cost evaluate --plan PLAN [--registry REGISTRY] [--runtime-artifact RUNTIME_ARTIFACT] [--target-connection TARGET_CONNECTION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Cost plan artifact
--registry REGISTRY — Optional evidence registry JSON/SQLite
--runtime-artifact RUNTIME_ARTIFACT — Optional runtime/run evidence JSON/YAML
--target-connection TARGET_CONNECTION — Optional read-only target connection JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product cost gate`¶

Usage: dpone data product cost gate --evaluation EVALUATION [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Cost evaluation artifact
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product cost forecast`¶

Usage: dpone data product cost forecast --evaluation EVALUATION [--history HISTORY] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--evaluation EVALUATION — Cost evaluation artifact
--history HISTORY — Optional historical cost artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product cost report`¶

Usage: dpone data product cost report --gate GATE [--forecast FORECAST] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Cost gate artifact
--forecast FORECAST — Optional cost forecast artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product rollout plan`¶

Usage: dpone data product rollout plan --manifest MANIFEST [--bundle BUNDLE] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--bundle BUNDLE — Optional schema migration bundle JSON/YAML
--evidence-dir EVIDENCE_DIR — Optional directory with data product gate artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product rollout shadow-validate`¶

Usage: dpone data product rollout shadow-validate --plan PLAN --runtime-artifact RUNTIME_ARTIFACT [--baseline-runtime-artifact BASELINE_RUNTIME_ARTIFACT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Rollout plan artifact
--runtime-artifact RUNTIME_ARTIFACT — Candidate runtime/run evidence JSON/YAML
--baseline-runtime-artifact BASELINE_RUNTIME_ARTIFACT — Baseline runtime/run evidence JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product rollout ring gate`¶

Usage: dpone data product rollout ring gate --plan PLAN --ring RING [--shadow-validation SHADOW_VALIDATION] [--promotion PROMOTION] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Rollout plan artifact
--ring RING — Ring id to evaluate
--shadow-validation SHADOW_VALIDATION — Optional shadow validation artifact
--promotion PROMOTION — Prior rollout promotion artifact; repeatable
--evidence-dir EVIDENCE_DIR — Optional directory with data product gate artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product rollout promote`¶

Usage: dpone data product rollout promote --ring-gate RING_GATE --target-ring TARGET_RING [--authority-gate AUTHORITY_GATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--ring-gate RING_GATE — Source ring gate artifact
--target-ring TARGET_RING — Target ring id
--authority-gate AUTHORITY_GATE — Optional authority gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product rollout report`¶

Usage: dpone data product rollout report --promotion PROMOTION [--format {text,json,md,table}] [--output OUTPUT]
Options:
--promotion PROMOTION — Rollout promotion artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust lake index`¶

Usage: dpone data product trust lake index --manifests MANIFESTS [MANIFESTS ...] [--registry REGISTRY] [--bundle-dir BUNDLE_DIR] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifests MANIFESTS — Manifest path or glob; repeatable
--registry REGISTRY — Optional evidence registry JSON/SQLite
--bundle-dir BUNDLE_DIR — Optional schema migration bundle directory
--evidence-dir EVIDENCE_DIR — Optional directory with data product artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust query`¶

Usage: dpone data product trust query --index INDEX [--product-id PRODUCT_ID] [--domain DOMAIN] [--artifact-kind ARTIFACT_KIND] [--status STATUS] [--owner OWNER] [--max-results MAX_RESULTS] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--index INDEX — Evidence lake index artifact
--product-id PRODUCT_ID — Filter by data product id
--domain DOMAIN — Filter by trust evidence domain
--artifact-kind ARTIFACT_KIND — Filter by artifact kind
--status STATUS — Filter by evidence status
--owner OWNER — Filter by owner
--max-results MAX_RESULTS — Maximum refs to return
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust snapshot`¶

Usage: dpone data product trust snapshot --index INDEX --product-id PRODUCT_ID [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--index INDEX — Evidence lake index artifact
--product-id PRODUCT_ID — Data product id
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust gate`¶

Usage: dpone data product trust gate --snapshot SNAPSHOT [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--snapshot SNAPSHOT — Trust snapshot artifact
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust report`¶

Usage: dpone data product trust report --snapshot SNAPSHOT [--gate GATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--snapshot SNAPSHOT — Trust snapshot artifact
--gate GATE — Optional trust gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product trust export`¶

Usage: dpone data product trust export --snapshot SNAPSHOT [--target {json,datahub,openlineage,opa}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--snapshot SNAPSHOT — Trust snapshot artifact
--target TARGET
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation plan`¶

Usage: dpone data product remediation plan --manifest MANIFEST [--trust-snapshot TRUST_SNAPSHOT] [--trust-gate TRUST_GATE] [--bundle BUNDLE] [--registry REGISTRY] [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--trust-snapshot TRUST_SNAPSHOT — Optional Trust Center snapshot artifact
--trust-gate TRUST_GATE — Optional Trust Center gate artifact
--bundle BUNDLE — Optional schema migration bundle artifact
--registry REGISTRY — Optional evidence registry JSON/SQLite
--evidence-dir EVIDENCE_DIR — Optional directory with data product artifacts
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation runbook render`¶

Usage: dpone data product remediation runbook render --plan PLAN [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Remediation plan artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation gate`¶

Usage: dpone data product remediation gate --plan PLAN [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Remediation plan artifact
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation closeout`¶

Usage: dpone data product remediation closeout --plan PLAN [--evidence-dir EVIDENCE_DIR] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Remediation plan artifact
--evidence-dir EVIDENCE_DIR — Directory with fresh data product evidence
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation report`¶

Usage: dpone data product remediation report --gate GATE [--closeout CLOSEOUT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Remediation gate artifact
--closeout CLOSEOUT — Optional remediation closeout artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation execution plan`¶

Usage: dpone data product remediation execution plan --manifest MANIFEST --remediation-plan REMEDIATION_PLAN [--remediation-gate REMEDIATION_GATE] [--authority-gate AUTHORITY_GATE] [--parameters PARAMETERS] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--remediation-plan REMEDIATION_PLAN — Remediation plan artifact
--remediation-gate REMEDIATION_GATE — Optional remediation gate artifact
--authority-gate AUTHORITY_GATE — Optional authority gate artifact
--parameters PARAMETERS — Optional command placeholder parameters JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation execution run`¶

Usage: dpone data product remediation execution run --plan PLAN [--idempotency-key IDEMPOTENCY_KEY] [--lock LOCK] [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Remediation execution plan artifact
--idempotency-key IDEMPOTENCY_KEY — Required for --execute when configured
--lock LOCK — Optional acquired lock artifact
--execute — Actually execute prevalidated commands
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation execution certify`¶

Usage: dpone data product remediation execution certify --run RUN [--evidence-dir EVIDENCE_DIR] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — Remediation execution run artifact
--evidence-dir EVIDENCE_DIR — Directory with fresh data product evidence
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone data product remediation execution report`¶

Usage: dpone data product remediation execution report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — Remediation execution certificate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema`¶

`dpone schema plan`¶

Usage: dpone schema plan --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--mode {strict,additive,widening}] [--on-type-change {fail,new_column}] [--new-column-prefix NEW_COLUMN_PREFIX] [--ddl-mode {online,safe_window,plan_only,manual_approval}] [--lock-timeout-seconds LOCK_TIMEOUT_SECONDS] [--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS] [--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL] [--apply-safe] [--plan-only] [--allow-drop] [--fail-on-breaking] [--format {text,json}]
Options:
--source SOURCE — Path to source columns JSON
--target TARGET — Path to target columns JSON
--table TABLE — Qualified target table, e.g. dbo.orders
--dialect DIALECT
--mode MODE
--on-type-change ON_TYPE_CHANGE
--new-column-prefix NEW_COLUMN_PREFIX
--ddl-mode DDL_MODE
--lock-timeout-seconds LOCK_TIMEOUT_SECONDS
--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS
--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL
--apply-safe — Alias for documenting runtime parity; CLI remains plan-only
--plan-only — Render plan without applying DDL (default CLI behavior)
--allow-drop
--fail-on-breaking
--format FORMAT

`dpone schema explain`¶

Usage: dpone schema explain --source SOURCE --target TARGET --source-system {mssql,postgres,clickhouse} --sink-system {mssql,postgres,clickhouse} [--mode {strict,additive,widening}] [--on-type-change {fail,new_column}] [--allow-drop] [--format {text,json,md}]
Options:
--source SOURCE — Path to source columns JSON
--target TARGET — Path to target columns JSON
--source-system SOURCE_SYSTEM
--sink-system SINK_SYSTEM
--mode MODE
--on-type-change ON_TYPE_CHANGE
--allow-drop
--format FORMAT

`dpone schema approve`¶

Usage: dpone schema approve --ledger LEDGER --approver APPROVER [--output-dir OUTPUT_DIR] [--format {text,json}]
Options:
--ledger LEDGER — Path to schema change ledger JSON
--approver APPROVER — Approver identifier
--output-dir OUTPUT_DIR
--format FORMAT

`dpone schema infer`¶

Usage: dpone schema infer [--manifest MANIFEST] [--source SOURCE] [--rows ROWS] [--format {text,json,md}]
Options:
--manifest MANIFEST — Manifest path with source.options.columns and sink options
--source SOURCE — Optional source columns JSON
--rows ROWS — Optional JSON array or JSONL row sample file
--format FORMAT

`dpone schema physical-plan`¶

Usage: dpone schema physical-plan [--manifest MANIFEST] [--source SOURCE] [--table TABLE] [--sink {mssql,postgres,clickhouse,bigquery,kafka}] [--format {text,json,md}]
Options:
--manifest MANIFEST — Manifest path with sink.options.physical_design
--source SOURCE — Optional source columns JSON
--table TABLE — Qualified target table override
--sink SINK — Sink override
--format FORMAT

`dpone schema physical-diff`¶

Usage: dpone schema physical-diff --actual ACTUAL [--manifest MANIFEST] [--source SOURCE] [--table TABLE] [--sink {clickhouse}] [--format {text,json,md}]
Options:
--actual ACTUAL — Actual physical design JSON
--manifest MANIFEST — Manifest path with sink.options.physical_design
--source SOURCE — Optional source columns JSON
--table TABLE — Qualified target table override
--sink SINK — Sink override
--format FORMAT

`dpone schema type-matrix`¶

Usage: dpone schema type-matrix --source {clickhouse,mssql,mysql,postgres} --sink {bigquery,clickhouse,mssql,postgres} [--source-type SOURCE_TYPE] [--type-fidelity-json TYPE_FIDELITY_JSON] [--format {text,json,md}]
Options:
--source SOURCE
--sink SINK
--source-type SOURCE_TYPE — Source type to explain. Can be repeated. Defaults to the pair-specific production matrix.
--type-fidelity-json TYPE_FIDELITY_JSON — Optional inline JSON policy for pair-specific fidelity controls, for example temporal settings.
--format FORMAT

`dpone schema expand-contract`¶

Usage: dpone schema expand-contract --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--output-dir OUTPUT_DIR] [--format {text,json}]
Options:
--source SOURCE — Path to source columns JSON
--target TARGET — Path to target columns JSON
--table TABLE — Qualified target table
--dialect DIALECT
--output-dir OUTPUT_DIR
--format FORMAT

`dpone schema contract publish`¶

Usage: dpone schema contract publish --manifest MANIFEST [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--store-backend STORE_BACKEND
--store-uri STORE_URI — Contract registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract check`¶

Usage: dpone schema contract check --manifest MANIFEST --against AGAINST [--compatibility {backward,forward,full,none}] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--against AGAINST — Contract ref like analytics.orders@1.4.0 or artifact path
--compatibility COMPATIBILITY
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract gate`¶

Usage: dpone schema contract gate --manifest MANIFEST [--pack PACK] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--pack PACK — Optional migration pack JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract history`¶

Usage: dpone schema contract history --contract CONTRACT [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--contract CONTRACT — Contract id
--store-backend STORE_BACKEND
--store-uri STORE_URI — Contract registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract latest`¶

Usage: dpone schema contract latest --contract CONTRACT [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--contract CONTRACT — Contract id
--store-backend STORE_BACKEND
--store-uri STORE_URI — Contract registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers`¶

Usage: dpone schema contract consumers [--contract CONTRACT] [--version VERSION] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT] {lineage,discover,matrix,gate,test-kit} ...
Options:
--contract CONTRACT — Contract id
--version VERSION — Version or range selector
--store-backend STORE_BACKEND
--store-uri STORE_URI — Contract registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers lineage`¶

Usage: dpone schema contract consumers lineage --manifest MANIFEST [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers discover`¶

Usage: dpone schema contract consumers discover --manifest MANIFEST [--lineage LINEAGE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--lineage LINEAGE — Optional consumer lineage artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers matrix`¶

Usage: dpone schema contract consumers matrix --manifest MANIFEST --against AGAINST --consumers CONSUMERS [--lineage LINEAGE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--against AGAINST — Base contract ref or artifact path
--consumers CONSUMERS — Consumer inventory artifact
--lineage LINEAGE — Optional consumer lineage artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers gate`¶

Usage: dpone schema contract consumers gate --manifest MANIFEST --pack PACK --matrix MATRIX [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--pack PACK — Migration pack JSON path
--matrix MATRIX — Consumer matrix artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers test-kit plan`¶

Usage: dpone schema contract consumers test-kit plan --manifest MANIFEST --matrix MATRIX [--compatibility-view-plan COMPATIBILITY_VIEW_PLAN] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--matrix MATRIX — Consumer matrix artifact
--compatibility-view-plan COMPATIBILITY_VIEW_PLAN — Optional compatibility view plan artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers test-kit render`¶

Usage: dpone schema contract consumers test-kit render --kit KIT [--format {text,json,md,table,pytest}] [--output OUTPUT]
Options:
--kit KIT — Consumer test kit JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract consumers test-kit certify`¶

Usage: dpone schema contract consumers test-kit certify --kit KIT --result {passed,failed} [--result-artifact RESULT_ARTIFACT] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--kit KIT — Consumer test kit JSON/YAML
--result RESULT — Execution status
--result-artifact RESULT_ARTIFACT — Optional detailed result JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract views`¶

Usage: dpone schema contract views {plan,gate,report} ...

`dpone schema contract views plan`¶

Usage: dpone schema contract views plan --manifest MANIFEST --against AGAINST [--consumer-matrix CONSUMER_MATRIX] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--against AGAINST — Base contract ref or artifact path
--consumer-matrix CONSUMER_MATRIX — Optional consumer matrix artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract views gate`¶

Usage: dpone schema contract views gate --plan PLAN [--consumer-gate CONSUMER_GATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Compatibility view plan artifact
--consumer-gate CONSUMER_GATE — Optional consumer gate artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract views report`¶

Usage: dpone schema contract views report --plan PLAN [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Compatibility view plan artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract adoption`¶

Usage: dpone schema contract adoption {plan,status,gate,retire} ...

`dpone schema contract adoption plan`¶

Usage: dpone schema contract adoption plan --manifest MANIFEST --consumer-matrix CONSUMER_MATRIX [--compatibility-view-plan COMPATIBILITY_VIEW_PLAN] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--consumer-matrix CONSUMER_MATRIX — Consumer matrix artifact
--compatibility-view-plan COMPATIBILITY_VIEW_PLAN — Optional compatibility view plan artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract adoption status`¶

Usage: dpone schema contract adoption status --plan PLAN [--registry REGISTRY] [--consumer-certification CONSUMER_CERTIFICATION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — Adoption plan artifact
--registry REGISTRY — Optional evidence registry JSON
--consumer-certification CONSUMER_CERTIFICATION — Optional consumer certification artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract adoption gate`¶

Usage: dpone schema contract adoption gate --status STATUS [--profile {advisory,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--status STATUS — Adoption status artifact
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract adoption retire`¶

Usage: dpone schema contract adoption retire --gate GATE [--compatibility-view-plan COMPATIBILITY_VIEW_PLAN] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--gate GATE — Contract retirement gate artifact
--compatibility-view-plan COMPATIBILITY_VIEW_PLAN — Optional compatibility view plan artifact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema contract deprecate`¶

Usage: dpone schema contract deprecate --contract CONTRACT --column COLUMN --remove-after REMOVE_AFTER [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--contract CONTRACT — Contract id
--column COLUMN — Column or alias name
--remove-after REMOVE_AFTER — Removal date YYYY-MM-DD
--store-backend STORE_BACKEND
--store-uri STORE_URI — Contract registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema identity plan`¶

Usage: dpone schema identity plan --manifest MANIFEST [--source SOURCE] [--actual ACTUAL] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path with sink.options.schema_identity
--source SOURCE — Optional source columns JSON
--actual ACTUAL — Optional actual physical target state JSON
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema impact plan`¶

Usage: dpone schema impact plan --pack PACK [--manifest MANIFEST] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--manifest MANIFEST — Manifest path with sink.options.schema_impact
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema impact gate`¶

Usage: dpone schema impact gate --pack PACK --impact IMPACT [--approval APPROVAL] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--impact IMPACT — Schema impact plan JSON path
--approval APPROVAL — Approval artifact YAML/JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration plan`¶

Usage: dpone schema migration plan --manifest MANIFEST [--source SOURCE] [--table TABLE] [--sink {mssql,postgres,clickhouse,bigquery,kafka}] [--actual ACTUAL] [--strategy {block,online_safe,shadow}] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--source SOURCE — Optional source columns JSON
--table TABLE — Qualified target table override
--sink SINK — Sink override
--actual ACTUAL — Optional actual physical target state JSON
--strategy STRATEGY — Migration planning strategy; overrides physical_design.migration.strategy
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration baseline`¶

Usage: dpone schema migration baseline --manifest MANIFEST [--source SOURCE] [--table TABLE] [--sink {mssql,postgres,clickhouse,bigquery,kafka}] --actual ACTUAL [--ledger LEDGER] [--format {text,json,md}] [--output OUTPUT]
Options:
--manifest MANIFEST — Manifest path
--source SOURCE — Optional source columns JSON
--table TABLE — Qualified target table override
--sink SINK — Sink override
--actual ACTUAL — Actual physical target state JSON
--ledger LEDGER — Artifact ledger JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration apply`¶

Usage: dpone schema migration apply --plan PLAN [--actual ACTUAL] [--approval APPROVAL] [--phase PHASE] [--execute] [--target-connection TARGET_CONNECTION] [--environment ENVIRONMENT] [--environment-contract ENVIRONMENT_CONTRACT] [--promotion PROMOTION] [--bundle-gate BUNDLE_GATE] [--ledger LEDGER] [--format {text,json,md}] [--output OUTPUT]
Options:
--plan PLAN — Migration pack JSON path
--actual ACTUAL — Optional current actual state JSON for fingerprint verification
--approval APPROVAL — Optional approval artifact path
--phase PHASE — Apply one phase from a phased migration pack
--execute — Execute target DDL/DML instead of ledger-only apply
--target-connection TARGET_CONNECTION — Target connection JSON for --execute
--environment ENVIRONMENT — Promotion environment name for environment-bound apply
--environment-contract ENVIRONMENT_CONTRACT — Migration environments contract YAML/JSON
--promotion PROMOTION — Promotion receipt JSON/YAML required by guarded environments
--bundle-gate BUNDLE_GATE — Optional bundle gate receipt required by protected CI/CD flows
--ledger LEDGER — Artifact ledger JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration history`¶

Usage: dpone schema migration history [--ledger LEDGER] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--ledger LEDGER — Artifact ledger JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rollback`¶

Usage: dpone schema migration rollback (--plan PLAN | --pack-id PACK_ID) [--approval APPROVAL] [--ledger LEDGER] [--format {text,json,md}] [--output OUTPUT]
Options:
--plan PLAN — Migration pack JSON path
--pack-id PACK_ID — Applied pack id; requires a rollback plan in later target-backed mode
--approval APPROVAL — Optional approval artifact path
--ledger LEDGER — Artifact ledger JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration verify-env`¶

Usage: dpone schema migration verify-env --pack PACK --environment ENVIRONMENT --environment-contract ENVIRONMENT_CONTRACT [--actual ACTUAL] [--format {text,json,md}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--environment ENVIRONMENT — Environment name
--environment-contract ENVIRONMENT_CONTRACT — Migration environments contract YAML/JSON
--actual ACTUAL — Override actual physical state JSON for this verification
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration certify`¶

Usage: dpone schema migration certify --pack PACK --environment ENVIRONMENT --environment-contract ENVIRONMENT_CONTRACT [--actual ACTUAL] [--format {text,json,md}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--environment ENVIRONMENT — Environment name
--environment-contract ENVIRONMENT_CONTRACT — Migration environments contract YAML/JSON
--actual ACTUAL — Override actual physical state JSON for this certification
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration promote`¶

Usage: dpone schema migration promote --pack PACK --from FROM_ENVIRONMENT --to TO_ENVIRONMENT --certificate CERTIFICATE --environment-contract ENVIRONMENT_CONTRACT [--approval APPROVAL] [--format {text,json,md}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--from FROM_ENVIRONMENT — Certified source environment
--to TO_ENVIRONMENT — Target environment
--certificate CERTIFICATE — Environment certification receipt JSON/YAML
--environment-contract ENVIRONMENT_CONTRACT — Migration environments contract YAML/JSON
--approval APPROVAL — Optional promotion approval artifact JSON/YAML
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse plan`¶

Usage: dpone schema migration rehearse plan --pack PACK [--bundle BUNDLE] --environment ENVIRONMENT --target-connection TARGET_CONNECTION --output-dir OUTPUT_DIR [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--bundle BUNDLE — Optional bundle.json path
--environment ENVIRONMENT — Sandbox/stage environment name
--target-connection TARGET_CONNECTION — Target connection JSON path
--output-dir OUTPUT_DIR — Directory where rehearsal-plan.json is written
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse run`¶

Usage: dpone schema migration rehearse run --plan PLAN [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — rehearsal-plan.json path
--execute — Execute target DDL/DML; omitted means dry-run
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse certify`¶

Usage: dpone schema migration rehearse certify --run RUN [--fixture-build FIXTURE_BUILD] [--before-profile BEFORE_PROFILE] [--after-profile AFTER_PROFILE] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — rehearsal-run.json path
--fixture-build FIXTURE_BUILD — Optional fixture-build.json evidence
--before-profile BEFORE_PROFILE — Optional before data-profile.json evidence
--after-profile AFTER_PROFILE — Optional after data-profile.json evidence
--profile PROFILE — Rehearsal certification policy profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse report`¶

Usage: dpone schema migration rehearse report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — rehearsal-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse fixture plan`¶

Usage: dpone schema migration rehearse fixture plan --pack PACK --manifest MANIFEST [--policy POLICY] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--manifest MANIFEST — Route manifest YAML/JSON path
--policy POLICY — Optional fixture policy YAML/JSON path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse fixture build`¶

Usage: dpone schema migration rehearse fixture build --plan PLAN --target-connection TARGET_CONNECTION [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — fixture-plan.json path
--target-connection TARGET_CONNECTION — Sandbox target connection JSON/YAML path
--execute — Seed fixture rows into the sandbox target
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration rehearse fixture profile`¶

Usage: dpone schema migration rehearse fixture profile --fixture-build FIXTURE_BUILD --target-connection TARGET_CONNECTION --stage {before,after} [--format {text,json,md,table}] [--output OUTPUT]
Options:
--fixture-build FIXTURE_BUILD — fixture-build.json path
--target-connection TARGET_CONNECTION — Sandbox target connection JSON/YAML path
--stage STAGE — Profile stage
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration post-apply plan`¶

Usage: dpone schema migration post-apply plan --pack PACK [--bundle BUNDLE] --ledger LEDGER --manifest MANIFEST --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON/YAML path
--bundle BUNDLE — Optional migration bundle JSON/YAML path
--ledger LEDGER — Migration ledger JSON/YAML path
--manifest MANIFEST — Route manifest JSON/YAML path
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path
--environment ENVIRONMENT — Applied target environment
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration post-apply run`¶

Usage: dpone schema migration post-apply run --plan PLAN [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — post-apply-plan.json path
--execute — Execute read-only target checks
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration post-apply certify`¶

Usage: dpone schema migration post-apply certify --run RUN [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — post-apply-run.json path
--profile PROFILE — Post-apply certification policy profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration post-apply report`¶

Usage: dpone schema migration post-apply report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — post-apply-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration watch plan`¶

Usage: dpone schema migration watch plan --pack PACK --post-apply-certificate POST_APPLY_CERTIFICATE --manifest MANIFEST --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON/YAML path
--post-apply-certificate POST_APPLY_CERTIFICATE — Post-apply certificate JSON/YAML path
--manifest MANIFEST — Route manifest JSON/YAML path
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path
--environment ENVIRONMENT — Watched target environment
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration watch run`¶

Usage: dpone schema migration watch run --plan PLAN [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — watch-plan.json path
--execute — Execute read-only target watch samples
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration watch status`¶

Usage: dpone schema migration watch status --run RUN [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — watch-run.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration watch certify`¶

Usage: dpone schema migration watch certify --run RUN [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — watch-run.json path
--profile PROFILE — Watch certification policy profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration watch report`¶

Usage: dpone schema migration watch report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — watch-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration remediation plan`¶

Usage: dpone schema migration remediation plan --pack PACK --watch-certificate WATCH_CERTIFICATE --ledger LEDGER --manifest MANIFEST --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--backup-certificate BACKUP_CERTIFICATE] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON/YAML path
--watch-certificate WATCH_CERTIFICATE — Release watch certificate JSON/YAML path
--ledger LEDGER — Migration ledger JSON path
--manifest MANIFEST — Route manifest JSON/YAML path
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path
--environment ENVIRONMENT — Environment name
--backup-certificate BACKUP_CERTIFICATE — Optional backup certificate JSON/YAML for restore fallback
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration remediation apply`¶

Usage: dpone schema migration remediation apply --plan PLAN [--approval APPROVAL] [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — remediation-plan.json path
--approval APPROVAL — Approval JSON/YAML artifact for protected remediation
--execute — Execute target rollback/remediation operations
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration remediation certify`¶

Usage: dpone schema migration remediation certify --run RUN [--target-connection TARGET_CONNECTION] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--run RUN — remediation-run.json path
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path for future read-back checks
--profile PROFILE — Remediation certification policy profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration remediation report`¶

Usage: dpone schema migration remediation report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — remediation-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup plan`¶

Usage: dpone schema migration backup plan --pack PACK --manifest MANIFEST --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON/YAML path
--manifest MANIFEST — Route manifest JSON/YAML path
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path
--environment ENVIRONMENT — Environment name
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup create`¶

Usage: dpone schema migration backup create --plan PLAN [--approval APPROVAL] [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — backup-plan.json path
--approval APPROVAL — Approval JSON/YAML artifact for protected backups
--execute — Execute target backup operations
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup restore plan`¶

Usage: dpone schema migration backup restore plan --backup-run BACKUP_RUN --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--format {text,json,md,table}] [--output OUTPUT]
Options:
--backup-run BACKUP_RUN — backup-run.json path
--target-connection TARGET_CONNECTION — Sandbox target connection JSON/YAML path
--environment ENVIRONMENT — Sandbox environment name
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup restore run`¶

Usage: dpone schema migration backup restore run --plan PLAN [--execute] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--plan PLAN — restore-plan.json path
--execute — Execute target restore operations
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup certify`¶

Usage: dpone schema migration backup certify --backup-run BACKUP_RUN [--restore-run RESTORE_RUN] [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--backup-run BACKUP_RUN — backup-run.json path
--restore-run RESTORE_RUN — Optional restore-run.json path
--profile PROFILE — Backup certification policy profile
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration backup report`¶

Usage: dpone schema migration backup report --certificate CERTIFICATE [--format {text,json,md,table}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — backup-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery point record`¶

Usage: dpone schema migration recovery point record --backup-certificate BACKUP_CERTIFICATE --environment ENVIRONMENT [--mode {observe,gate}] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--backup-certificate BACKUP_CERTIFICATE — backup-certificate.json path
--environment ENVIRONMENT — Environment name
--mode MODE
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery point latest`¶

Usage: dpone schema migration recovery point latest --target TARGET --environment ENVIRONMENT [--profile {advisory,stage,prod_strict,regulated}] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment name
--profile PROFILE
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery point list`¶

Usage: dpone schema migration recovery point list [--target TARGET] [--environment ENVIRONMENT] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment name
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery chain verify`¶

Usage: dpone schema migration recovery chain verify --restore-point-id RESTORE_POINT_ID [--require-restore-rehearsal] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--restore-point-id RESTORE_POINT_ID — Restore point id
--require-restore-rehearsal
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery restore plan`¶

Usage: dpone schema migration recovery restore plan --restore-point-id RESTORE_POINT_ID --target-connection TARGET_CONNECTION --environment ENVIRONMENT [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--restore-point-id RESTORE_POINT_ID — Restore point id
--target-connection TARGET_CONNECTION — Target connection JSON/YAML path
--environment ENVIRONMENT — Sandbox/stage environment name
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery restore run`¶

Usage: dpone schema migration recovery restore run --plan PLAN [--execute] [--format {text,json,md}] [--output OUTPUT]
Options:
--plan PLAN — recovery-restore-plan.json path
--execute — Execute target restore operations
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery restore certify`¶

Usage: dpone schema migration recovery restore certify --restore-run RESTORE_RUN [--profile {advisory,stage,prod_strict,regulated}] [--format {text,json,md}] [--output OUTPUT]
Options:
--restore-run RESTORE_RUN — recovery-restore-run.json path
--profile PROFILE
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery restore report`¶

Usage: dpone schema migration recovery restore report --certificate CERTIFICATE [--format {text,json,md}] [--output OUTPUT]
Options:
--certificate CERTIFICATE — recovery-restore-certificate.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration recovery retention plan`¶

Usage: dpone schema migration recovery retention plan --target TARGET --environment ENVIRONMENT [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment name
--store-backend STORE_BACKEND
--store-uri STORE_URI — Recovery catalog path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration bundle build`¶

Usage: dpone schema migration bundle build --pack PACK [--impact IMPACT] [--environment-contract ENVIRONMENT_CONTRACT] [--certificate CERTIFICATE] [--rehearsal-certificate REHEARSAL_CERTIFICATE] [--post-apply-certificate POST_APPLY_CERTIFICATE] [--watch-certificate WATCH_CERTIFICATE] [--remediation-certificate REMEDIATION_CERTIFICATE] [--backup-certificate BACKUP_CERTIFICATE] [--contract-gate CONTRACT_GATE] [--consumer-gate CONSUMER_GATE] [--consumer-test-kit CONSUMER_TEST_KIT] [--consumer-certification CONSUMER_CERTIFICATION] [--compatibility-view-gate COMPATIBILITY_VIEW_GATE] [--contract-adoption-status CONTRACT_ADOPTION_STATUS] [--contract-retirement-gate CONTRACT_RETIREMENT_GATE] [--data-product-slo-gate DATA_PRODUCT_SLO_GATE] [--data-product-incident-report DATA_PRODUCT_INCIDENT_REPORT] [--data-product-error-budget-gate DATA_PRODUCT_ERROR_BUDGET_GATE] [--data-product-incident-lifecycle DATA_PRODUCT_INCIDENT_LIFECYCLE] [--data-product-release-closeout-gate DATA_PRODUCT_RELEASE_CLOSEOUT_GATE] [--data-product-fleet-gate DATA_PRODUCT_FLEET_GATE] [--data-product-fleet-report DATA_PRODUCT_FLEET_REPORT] [--data-product-reliability-export DATA_PRODUCT_RELIABILITY_EXPORT] [--data-product-route-delivery-receipt DATA_PRODUCT_ROUTE_DELIVERY_RECEIPT] [--data-product-assertion-gate DATA_PRODUCT_ASSERTION_GATE] [--data-product-assertion-report DATA_PRODUCT_ASSERTION_REPORT] [--data-product-policy-gate DATA_PRODUCT_POLICY_GATE] [--data-product-policy-report DATA_PRODUCT_POLICY_REPORT] [--data-product-waiver DATA_PRODUCT_WAIVER] [--data-product-authority-gate DATA_PRODUCT_AUTHORITY_GATE] [--data-product-approval-quorum DATA_PRODUCT_APPROVAL_QUORUM] [--data-product-evidence-signature DATA_PRODUCT_EVIDENCE_SIGNATURE] [--data-product-governance-export-payload DATA_PRODUCT_GOVERNANCE_EXPORT_PAYLOAD] [--data-product-governance-publish-receipt DATA_PRODUCT_GOVERNANCE_PUBLISH_RECEIPT] [--data-product-governance-publish-verification DATA_PRODUCT_GOVERNANCE_PUBLISH_VERIFICATION] [--data-product-compliance-gate DATA_PRODUCT_COMPLIANCE_GATE] [--data-product-audit-package DATA_PRODUCT_AUDIT_PACKAGE] [--data-product-audit-archive-verification DATA_PRODUCT_AUDIT_ARCHIVE_VERIFICATION] [--data-product-audit-retention-plan DATA_PRODUCT_AUDIT_RETENTION_PLAN] [--data-product-legal-hold DATA_PRODUCT_LEGAL_HOLD] [--data-product-access-gate DATA_PRODUCT_ACCESS_GATE] [--data-product-access-report DATA_PRODUCT_ACCESS_REPORT] [--data-product-privacy-impact-assessment DATA_PRODUCT_PRIVACY_IMPACT_ASSESSMENT] [--data-product-access-enforcement-certificate DATA_PRODUCT_ACCESS_ENFORCEMENT_CERTIFICATE] [--data-product-access-drift-report DATA_PRODUCT_ACCESS_DRIFT_REPORT] [--data-product-cost-gate DATA_PRODUCT_COST_GATE] [--data-product-cost-forecast DATA_PRODUCT_COST_FORECAST] [--data-product-cost-report DATA_PRODUCT_COST_REPORT] [--data-product-ring-gate DATA_PRODUCT_RING_GATE] [--data-product-shadow-validation DATA_PRODUCT_SHADOW_VALIDATION] [--data-product-rollout-promotion DATA_PRODUCT_ROLLOUT_PROMOTION] [--data-product-rollout-report DATA_PRODUCT_ROLLOUT_REPORT] [--data-product-trust-gate DATA_PRODUCT_TRUST_GATE] [--data-product-trust-report DATA_PRODUCT_TRUST_REPORT] [--data-product-trust-export DATA_PRODUCT_TRUST_EXPORT] [--recovery-point RECOVERY_POINT] [--recovery-chain-verification RECOVERY_CHAIN_VERIFICATION] [--fixture-build FIXTURE_BUILD] [--quality-profile QUALITY_PROFILE] [--promotion PROMOTION] [--approval APPROVAL] [--attest] --output-dir OUTPUT_DIR [--format {text,json,md}] [--output OUTPUT]
Options:
--pack PACK — Migration pack JSON path
--impact IMPACT — Schema impact plan JSON path
--environment-contract ENVIRONMENT_CONTRACT — Environment contract YAML/JSON path
--certificate CERTIFICATE — Environment certification receipt JSON/YAML
--rehearsal-certificate REHEARSAL_CERTIFICATE — Migration rehearsal certificate JSON/YAML
--post-apply-certificate POST_APPLY_CERTIFICATE — Migration post-apply certificate JSON/YAML
--watch-certificate WATCH_CERTIFICATE — Migration release watch certificate JSON/YAML
--remediation-certificate REMEDIATION_CERTIFICATE — Migration remediation certificate JSON/YAML
--backup-certificate BACKUP_CERTIFICATE — Migration backup certificate JSON/YAML
--contract-gate CONTRACT_GATE — Schema contract gate receipt JSON/YAML
--consumer-gate CONSUMER_GATE — Schema contract consumer gate receipt JSON/YAML
--consumer-test-kit CONSUMER_TEST_KIT — Schema contract consumer test kit JSON/YAML
--consumer-certification CONSUMER_CERTIFICATION — Schema contract consumer certification JSON/YAML
--compatibility-view-gate COMPATIBILITY_VIEW_GATE — Schema contract compatibility view gate receipt JSON/YAML
--contract-adoption-status CONTRACT_ADOPTION_STATUS — Schema contract adoption status JSON/YAML
--contract-retirement-gate CONTRACT_RETIREMENT_GATE — Schema contract retirement gate receipt JSON/YAML
--data-product-slo-gate DATA_PRODUCT_SLO_GATE — Data product SLO gate receipt JSON/YAML
--data-product-incident-report DATA_PRODUCT_INCIDENT_REPORT — Data product incident report JSON/YAML
--data-product-error-budget-gate DATA_PRODUCT_ERROR_BUDGET_GATE — Data product error-budget gate JSON/YAML
--data-product-incident-lifecycle DATA_PRODUCT_INCIDENT_LIFECYCLE — Data product incident lifecycle JSON/YAML
--data-product-release-closeout-gate DATA_PRODUCT_RELEASE_CLOSEOUT_GATE — Data product release closeout gate JSON/YAML
--data-product-fleet-gate DATA_PRODUCT_FLEET_GATE — Data product fleet gate JSON/YAML
--data-product-fleet-report DATA_PRODUCT_FLEET_REPORT — Data product fleet report JSON/YAML
--data-product-reliability-export DATA_PRODUCT_RELIABILITY_EXPORT — Data product reliability export JSON/YAML
--data-product-route-delivery-receipt DATA_PRODUCT_ROUTE_DELIVERY_RECEIPT — Data product route delivery receipt JSON/YAML
--data-product-assertion-gate DATA_PRODUCT_ASSERTION_GATE — Data product assertion gate JSON/YAML
--data-product-assertion-report DATA_PRODUCT_ASSERTION_REPORT — Data product assertion report JSON/YAML
--data-product-policy-gate DATA_PRODUCT_POLICY_GATE — Data product policy gate JSON/YAML
--data-product-policy-report DATA_PRODUCT_POLICY_REPORT — Data product policy report JSON/YAML
--data-product-waiver DATA_PRODUCT_WAIVER — Data product policy waiver JSON/YAML
--data-product-authority-gate DATA_PRODUCT_AUTHORITY_GATE — Data product authority gate JSON/YAML
--data-product-approval-quorum DATA_PRODUCT_APPROVAL_QUORUM — Data product approval quorum JSON/YAML
--data-product-evidence-signature DATA_PRODUCT_EVIDENCE_SIGNATURE — Data product detached evidence signature JSON/YAML
--data-product-governance-export-payload DATA_PRODUCT_GOVERNANCE_EXPORT_PAYLOAD — Data product governance payload JSON/YAML
--data-product-governance-publish-receipt DATA_PRODUCT_GOVERNANCE_PUBLISH_RECEIPT — Data product governance publish receipt
--data-product-governance-publish-verification DATA_PRODUCT_GOVERNANCE_PUBLISH_VERIFICATION — Data product governance publish verification JSON/YAML
--data-product-compliance-gate DATA_PRODUCT_COMPLIANCE_GATE — Data product compliance gate JSON/YAML
--data-product-audit-package DATA_PRODUCT_AUDIT_PACKAGE — Data product audit package JSON/YAML
--data-product-audit-archive-verification DATA_PRODUCT_AUDIT_ARCHIVE_VERIFICATION — Data product audit archive verification JSON/YAML
--data-product-audit-retention-plan DATA_PRODUCT_AUDIT_RETENTION_PLAN — Data product audit retention plan JSON/YAML
--data-product-legal-hold DATA_PRODUCT_LEGAL_HOLD — Data product legal hold JSON/YAML
--data-product-access-gate DATA_PRODUCT_ACCESS_GATE — Data product access gate JSON/YAML
--data-product-access-report DATA_PRODUCT_ACCESS_REPORT — Data product access report JSON/YAML
--data-product-privacy-impact-assessment DATA_PRODUCT_PRIVACY_IMPACT_ASSESSMENT — Data product privacy impact assessment JSON/YAML
--data-product-access-enforcement-certificate DATA_PRODUCT_ACCESS_ENFORCEMENT_CERTIFICATE — Data product access enforcement certificate JSON/YAML
--data-product-access-drift-report DATA_PRODUCT_ACCESS_DRIFT_REPORT — Data product access drift report JSON/YAML
--data-product-cost-gate DATA_PRODUCT_COST_GATE — Data product cost gate JSON/YAML
--data-product-cost-forecast DATA_PRODUCT_COST_FORECAST — Data product cost forecast JSON/YAML
--data-product-cost-report DATA_PRODUCT_COST_REPORT — Data product cost report JSON/YAML
--data-product-ring-gate DATA_PRODUCT_RING_GATE — Data product rollout ring gate JSON/YAML
--data-product-shadow-validation DATA_PRODUCT_SHADOW_VALIDATION — Data product shadow validation JSON/YAML
--data-product-rollout-promotion DATA_PRODUCT_ROLLOUT_PROMOTION — Data product rollout promotion JSON/YAML
--data-product-rollout-report DATA_PRODUCT_ROLLOUT_REPORT — Data product rollout report JSON/YAML
--data-product-trust-gate DATA_PRODUCT_TRUST_GATE — Data product Trust Center gate JSON/YAML
--data-product-trust-report DATA_PRODUCT_TRUST_REPORT — Data product Trust Center report JSON/YAML
--data-product-trust-export DATA_PRODUCT_TRUST_EXPORT — Data product Trust Center export JSON/YAML
--recovery-point RECOVERY_POINT — Migration recovery point JSON/YAML
--recovery-chain-verification RECOVERY_CHAIN_VERIFICATION — Migration recovery chain verification JSON/YAML
--fixture-build FIXTURE_BUILD — Migration rehearsal fixture-build JSON/YAML
--quality-profile QUALITY_PROFILE — Migration rehearsal data-profile JSON/YAML
--promotion PROMOTION — Promotion receipt JSON/YAML
--approval APPROVAL — Approval artifact JSON/YAML
--attest — Embed artifact digests and bundle attestation
--output-dir OUTPUT_DIR — Directory where bundle.json is written
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration bundle verify`¶

Usage: dpone schema migration bundle verify --bundle BUNDLE [--require-attestation] [--format {text,json,md}] [--output OUTPUT]
Options:
--bundle BUNDLE — bundle.json path
--require-attestation — Require attestation in bundle.json
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration bundle gate`¶

Usage: dpone schema migration bundle gate --bundle BUNDLE [--profile {advisory,pr_review,stage_certified,prod_strict,regulated}] [--policy POLICY] [--target-environment TARGET_ENVIRONMENT] [--trust-verification TRUST_VERIFICATION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--bundle BUNDLE — bundle.json path
--profile PROFILE — Built-in bundle gate profile
--policy POLICY — Optional custom bundle policy YAML/JSON
--target-environment TARGET_ENVIRONMENT — Expected promotion target environment
--trust-verification TRUST_VERIFICATION — Optional trusted provenance verification receipt JSON
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration bundle diff`¶

Usage: dpone schema migration bundle diff --base BASE --head HEAD [--base-gate BASE_GATE] [--head-gate HEAD_GATE] [--require-attestation] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--base BASE — Base bundle.json path
--head HEAD — Head bundle.json path
--base-gate BASE_GATE — Optional base bundle gate receipt JSON
--head-gate HEAD_GATE — Optional head bundle gate receipt JSON
--require-attestation — Require attestation in both bundles
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration bundle attest`¶

Usage: dpone schema migration bundle attest --bundle BUNDLE --output OUTPUT [--signing-key-env SIGNING_KEY_ENV] [--signing-key-id SIGNING_KEY_ID] --provenance-source PROVENANCE_SOURCE --repository REPOSITORY --commit-sha COMMIT_SHA --ref REF [--run-id RUN_ID] [--workflow WORKFLOW] [--actor ACTOR] [--run-url RUN_URL] [--builder-id BUILDER_ID] [--protected-ref] [--format {text,json,md}]
Options:
--bundle BUNDLE — bundle.json path
--output OUTPUT — provenance.json output path
--signing-key-env SIGNING_KEY_ENV — Environment variable containing local HMAC signing key
--signing-key-id SIGNING_KEY_ID — Signature key id written to provenance
--provenance-source PROVENANCE_SOURCE — CI/SCM source, e.g. github_actions
--repository REPOSITORY — Repository URL bound to provenance
--commit-sha COMMIT_SHA — Commit SHA bound to provenance
--ref REF — Git ref bound to provenance
--run-id RUN_ID — CI run id
--workflow WORKFLOW — CI workflow path or name
--actor ACTOR — CI actor
--run-url RUN_URL — CI run URL
--builder-id BUILDER_ID — Builder identity
--protected-ref — Mark the source ref as protected
--format FORMAT

`dpone schema migration bundle trust verify`¶

Usage: dpone schema migration bundle trust verify --bundle BUNDLE --provenance PROVENANCE [--policy POLICY] [--signing-key-env SIGNING_KEY_ENV] [--external-attestation EXTERNAL_ATTESTATION] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--bundle BUNDLE — bundle.json path
--provenance PROVENANCE — provenance.json path
--policy POLICY — Optional trust policy YAML/JSON
--signing-key-env SIGNING_KEY_ENV — Environment variable containing local HMAC verification key
--external-attestation EXTERNAL_ATTESTATION — External GitHub/Sigstore/Cosign verification receipt JSON/YAML; can be repeated
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration registry record`¶

Usage: dpone schema migration registry record --bundle BUNDLE [--gate GATE] [--trust TRUST] [--diff DIFF] [--contract-gate CONTRACT_GATE] [--consumer-gate CONSUMER_GATE] [--consumer-certification CONSUMER_CERTIFICATION] [--compatibility-view-gate COMPATIBILITY_VIEW_GATE] [--contract-retirement-gate CONTRACT_RETIREMENT_GATE] [--data-product-slo-gate DATA_PRODUCT_SLO_GATE] [--data-product-incident-report DATA_PRODUCT_INCIDENT_REPORT] [--data-product-error-budget-gate DATA_PRODUCT_ERROR_BUDGET_GATE] [--data-product-incident-lifecycle DATA_PRODUCT_INCIDENT_LIFECYCLE] [--data-product-release-closeout-gate DATA_PRODUCT_RELEASE_CLOSEOUT_GATE] [--data-product-fleet-gate DATA_PRODUCT_FLEET_GATE] [--data-product-fleet-report DATA_PRODUCT_FLEET_REPORT] [--data-product-reliability-export DATA_PRODUCT_RELIABILITY_EXPORT] [--data-product-route-delivery-receipt DATA_PRODUCT_ROUTE_DELIVERY_RECEIPT] [--data-product-assertion-gate DATA_PRODUCT_ASSERTION_GATE] [--data-product-assertion-report DATA_PRODUCT_ASSERTION_REPORT] [--data-product-policy-gate DATA_PRODUCT_POLICY_GATE] [--data-product-policy-report DATA_PRODUCT_POLICY_REPORT] [--data-product-waiver DATA_PRODUCT_WAIVER] [--data-product-authority-gate DATA_PRODUCT_AUTHORITY_GATE] [--data-product-approval-quorum DATA_PRODUCT_APPROVAL_QUORUM] [--data-product-evidence-signature DATA_PRODUCT_EVIDENCE_SIGNATURE] [--data-product-governance-export-payload DATA_PRODUCT_GOVERNANCE_EXPORT_PAYLOAD] [--data-product-governance-publish-receipt DATA_PRODUCT_GOVERNANCE_PUBLISH_RECEIPT] [--data-product-governance-publish-verification DATA_PRODUCT_GOVERNANCE_PUBLISH_VERIFICATION] [--data-product-compliance-gate DATA_PRODUCT_COMPLIANCE_GATE] [--data-product-audit-package DATA_PRODUCT_AUDIT_PACKAGE] [--data-product-audit-archive-verification DATA_PRODUCT_AUDIT_ARCHIVE_VERIFICATION] [--data-product-audit-retention-plan DATA_PRODUCT_AUDIT_RETENTION_PLAN] [--data-product-legal-hold DATA_PRODUCT_LEGAL_HOLD] [--data-product-access-classification DATA_PRODUCT_ACCESS_CLASSIFICATION] [--data-product-entitlement-plan DATA_PRODUCT_ENTITLEMENT_PLAN] [--data-product-privacy-impact-assessment DATA_PRODUCT_PRIVACY_IMPACT_ASSESSMENT] [--data-product-access-gate DATA_PRODUCT_ACCESS_GATE] [--data-product-access-report DATA_PRODUCT_ACCESS_REPORT] [--data-product-access-enforcement-certificate DATA_PRODUCT_ACCESS_ENFORCEMENT_CERTIFICATE] [--data-product-access-drift-report DATA_PRODUCT_ACCESS_DRIFT_REPORT] [--data-product-cost-gate DATA_PRODUCT_COST_GATE] [--data-product-cost-forecast DATA_PRODUCT_COST_FORECAST] [--data-product-cost-report DATA_PRODUCT_COST_REPORT] [--data-product-ring-gate DATA_PRODUCT_RING_GATE] [--data-product-shadow-validation DATA_PRODUCT_SHADOW_VALIDATION] [--data-product-rollout-promotion DATA_PRODUCT_ROLLOUT_PROMOTION] [--data-product-rollout-report DATA_PRODUCT_ROLLOUT_REPORT] [--data-product-trust-gate DATA_PRODUCT_TRUST_GATE] [--data-product-trust-report DATA_PRODUCT_TRUST_REPORT] [--data-product-trust-export DATA_PRODUCT_TRUST_EXPORT] [--data-product-remediation-gate DATA_PRODUCT_REMEDIATION_GATE] [--data-product-remediation-runbook DATA_PRODUCT_REMEDIATION_RUNBOOK] [--data-product-remediation-closeout DATA_PRODUCT_REMEDIATION_CLOSEOUT] [--data-product-remediation-report DATA_PRODUCT_REMEDIATION_REPORT] [--data-product-remediation-execution-plan DATA_PRODUCT_REMEDIATION_EXECUTION_PLAN] [--data-product-remediation-execution-run DATA_PRODUCT_REMEDIATION_EXECUTION_RUN] [--data-product-remediation-execution-certificate DATA_PRODUCT_REMEDIATION_EXECUTION_CERTIFICATE] [--data-product-remediation-execution-report DATA_PRODUCT_REMEDIATION_EXECUTION_REPORT] [--post-apply-certificate POST_APPLY_CERTIFICATE] [--watch-certificate WATCH_CERTIFICATE] [--remediation-certificate REMEDIATION_CERTIFICATE] [--backup-certificate BACKUP_CERTIFICATE] [--recovery-point RECOVERY_POINT] [--recovery-chain-verification RECOVERY_CHAIN_VERIFICATION] --environment ENVIRONMENT --stage {access_classified,access_drift_inspected,access_enforced,access_enforcement_certified,access_enforcement_planned,access_gate_passed,adoption_planned,applied,approval_quorum_verified,approved,assertion_gate_passed,assertion_incident_opened,assertions_evaluated,assertions_planned,audit_archive_verified,audit_archived,audit_package_rendered,authority_checked,authority_gate_passed,authority_registered,backup_certified,backup_created,backup_planned,capacity_forecasted,certified,closed,compatibility_view_planned,compatibility_view_retired,compatibility_view_served,compliance_evaluated,compliance_gate_passed,compliance_planned,consumer_certified,consumer_gate_passed,consumer_migrated,consumer_migrating,contract_checked,contract_gate_passed,contract_published,contract_retired,contract_retirement_ready,cost_evaluated,cost_gate_passed,cost_planned,cost_report_rendered,data_product_remediation_closed,data_product_remediation_executed,data_product_remediation_execution_certified,data_product_remediation_execution_planned,data_product_remediation_execution_report_rendered,data_product_remediation_gate_passed,data_product_remediation_planned,data_product_remediation_report_rendered,data_product_remediation_runbook_rendered,entitlements_planned,error_budget_evaluated,error_budget_gate_passed,error_budget_planned,evidence_signature_verified,evidence_signed,fleet_evaluated,fleet_gate_passed,fleet_release_frozen,governance_export_planned,governance_payload_rendered,governance_publish_verified,governance_published,incident_acknowledged,incident_mitigated,incident_opened,incident_resolved,incident_route_prepared,legal_hold_applied,planned,policy_evaluated,policy_gate_passed,privacy_impact_assessed,promoted,recovery_chain_verified,recovery_point_recorded,recovery_restore_rehearsed,rejected,release_closeout_passed,reliability_exported,remediated,remediation_planned,restore_rehearsed,retention_planned,reviewed,rollback_certified,rollout_held,rollout_planned,rollout_promoted,rollout_ring_gate_passed,rollout_rollback_recommended,shadow_validated,slo_evaluated,slo_gate_passed,slo_planned,trust_export_rendered,trust_gate_passed,trust_lake_indexed,trust_query_executed,trust_report_rendered,trust_snapshot_rendered,verified,waiver_approved,waiver_expired,waiver_requested,watched} [--actor ACTOR] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md}] [--output OUTPUT]
Options:
--bundle BUNDLE — bundle.json path
--gate GATE — Optional bundle gate receipt JSON/YAML
--trust TRUST — Optional trust verification receipt JSON/YAML
--diff DIFF — Optional bundle diff receipt JSON/YAML
--contract-gate CONTRACT_GATE — Optional schema contract gate receipt JSON/YAML
--consumer-gate CONSUMER_GATE — Optional schema contract consumer gate receipt JSON/YAML
--consumer-certification CONSUMER_CERTIFICATION — Optional consumer contract certification receipt JSON/YAML
--compatibility-view-gate COMPATIBILITY_VIEW_GATE — Optional compatibility view gate receipt JSON/YAML
--contract-retirement-gate CONTRACT_RETIREMENT_GATE — Optional contract retirement gate receipt JSON/YAML
--data-product-slo-gate DATA_PRODUCT_SLO_GATE — Optional data product SLO gate receipt JSON/YAML
--data-product-incident-report DATA_PRODUCT_INCIDENT_REPORT — Optional data product incident report JSON/YAML
--data-product-error-budget-gate DATA_PRODUCT_ERROR_BUDGET_GATE — Optional data product error-budget gate JSON/YAML
--data-product-incident-lifecycle DATA_PRODUCT_INCIDENT_LIFECYCLE — Optional data product incident lifecycle JSON/YAML
--data-product-release-closeout-gate DATA_PRODUCT_RELEASE_CLOSEOUT_GATE — Optional data product release closeout gate JSON/YAML
--data-product-fleet-gate DATA_PRODUCT_FLEET_GATE — Optional data product fleet gate JSON/YAML
--data-product-fleet-report DATA_PRODUCT_FLEET_REPORT — Optional data product fleet report JSON/YAML
--data-product-reliability-export DATA_PRODUCT_RELIABILITY_EXPORT — Optional data product reliability export JSON/YAML
--data-product-route-delivery-receipt DATA_PRODUCT_ROUTE_DELIVERY_RECEIPT — Optional data product route delivery receipt JSON/YAML
--data-product-assertion-gate DATA_PRODUCT_ASSERTION_GATE — Optional data product assertion gate JSON/YAML
--data-product-assertion-report DATA_PRODUCT_ASSERTION_REPORT — Optional data product assertion report JSON/YAML
--data-product-policy-gate DATA_PRODUCT_POLICY_GATE — Optional data product policy gate JSON/YAML
--data-product-policy-report DATA_PRODUCT_POLICY_REPORT — Optional data product policy report JSON/YAML
--data-product-waiver DATA_PRODUCT_WAIVER — Optional data product policy waiver JSON/YAML
--data-product-authority-gate DATA_PRODUCT_AUTHORITY_GATE — Optional data product authority gate JSON/YAML
--data-product-approval-quorum DATA_PRODUCT_APPROVAL_QUORUM — Optional data product approval quorum JSON/YAML
--data-product-evidence-signature DATA_PRODUCT_EVIDENCE_SIGNATURE — Optional data product evidence signature JSON/YAML
--data-product-governance-export-payload DATA_PRODUCT_GOVERNANCE_EXPORT_PAYLOAD — Optional governance payload JSON/YAML
--data-product-governance-publish-receipt DATA_PRODUCT_GOVERNANCE_PUBLISH_RECEIPT — Optional governance publish receipt
--data-product-governance-publish-verification DATA_PRODUCT_GOVERNANCE_PUBLISH_VERIFICATION — Optional governance publish verification JSON/YAML
--data-product-compliance-gate DATA_PRODUCT_COMPLIANCE_GATE — Optional data product compliance gate JSON/YAML
--data-product-audit-package DATA_PRODUCT_AUDIT_PACKAGE — Optional data product audit package JSON/YAML
--data-product-audit-archive-verification DATA_PRODUCT_AUDIT_ARCHIVE_VERIFICATION — Optional data product audit archive verification JSON/YAML
--data-product-audit-retention-plan DATA_PRODUCT_AUDIT_RETENTION_PLAN — Optional data product audit retention plan JSON/YAML
--data-product-legal-hold DATA_PRODUCT_LEGAL_HOLD — Optional data product legal hold JSON/YAML
--data-product-access-classification DATA_PRODUCT_ACCESS_CLASSIFICATION — Optional data product access classification
--data-product-entitlement-plan DATA_PRODUCT_ENTITLEMENT_PLAN — Optional data product entitlement plan
--data-product-privacy-impact-assessment DATA_PRODUCT_PRIVACY_IMPACT_ASSESSMENT — Optional data product privacy impact assessment JSON/YAML
--data-product-access-gate DATA_PRODUCT_ACCESS_GATE — Optional data product access gate JSON/YAML
--data-product-access-report DATA_PRODUCT_ACCESS_REPORT — Optional data product access report JSON/YAML
--data-product-access-enforcement-certificate DATA_PRODUCT_ACCESS_ENFORCEMENT_CERTIFICATE — Optional data product access enforcement certificate JSON/YAML
--data-product-access-drift-report DATA_PRODUCT_ACCESS_DRIFT_REPORT — Optional data product access drift report JSON/YAML
--data-product-cost-gate DATA_PRODUCT_COST_GATE — Optional data product cost gate JSON/YAML
--data-product-cost-forecast DATA_PRODUCT_COST_FORECAST — Optional data product cost forecast JSON/YAML
--data-product-cost-report DATA_PRODUCT_COST_REPORT — Optional data product cost report JSON/YAML
--data-product-ring-gate DATA_PRODUCT_RING_GATE — Optional data product rollout ring gate JSON/YAML
--data-product-shadow-validation DATA_PRODUCT_SHADOW_VALIDATION — Optional data product shadow validation JSON/YAML
--data-product-rollout-promotion DATA_PRODUCT_ROLLOUT_PROMOTION — Optional data product rollout promotion JSON/YAML
--data-product-rollout-report DATA_PRODUCT_ROLLOUT_REPORT — Optional data product rollout report JSON/YAML
--data-product-trust-gate DATA_PRODUCT_TRUST_GATE — Optional data product Trust Center gate JSON/YAML
--data-product-trust-report DATA_PRODUCT_TRUST_REPORT — Optional data product Trust Center report JSON/YAML
--data-product-trust-export DATA_PRODUCT_TRUST_EXPORT — Optional data product Trust Center export JSON/YAML
--data-product-remediation-gate DATA_PRODUCT_REMEDIATION_GATE — Optional data product remediation gate JSON/YAML
--data-product-remediation-runbook DATA_PRODUCT_REMEDIATION_RUNBOOK — Optional data product remediation runbook JSON/YAML
--data-product-remediation-closeout DATA_PRODUCT_REMEDIATION_CLOSEOUT — Optional data product remediation closeout JSON/YAML
--data-product-remediation-report DATA_PRODUCT_REMEDIATION_REPORT — Optional data product remediation report JSON/YAML
--data-product-remediation-execution-plan DATA_PRODUCT_REMEDIATION_EXECUTION_PLAN — Optional data product remediation execution plan JSON/YAML
--data-product-remediation-execution-run DATA_PRODUCT_REMEDIATION_EXECUTION_RUN — Optional data product remediation execution run JSON/YAML
--data-product-remediation-execution-certificate DATA_PRODUCT_REMEDIATION_EXECUTION_CERTIFICATE — Optional data product remediation execution certificate JSON/YAML
--data-product-remediation-execution-report DATA_PRODUCT_REMEDIATION_EXECUTION_REPORT — Optional data product remediation execution report JSON/YAML
--post-apply-certificate POST_APPLY_CERTIFICATE — Optional post-apply certificate JSON/YAML
--watch-certificate WATCH_CERTIFICATE — Optional release watch certificate JSON/YAML
--remediation-certificate REMEDIATION_CERTIFICATE — Optional remediation certificate JSON/YAML
--backup-certificate BACKUP_CERTIFICATE — Optional backup certificate JSON/YAML
--recovery-point RECOVERY_POINT — Optional recovery point JSON/YAML
--recovery-chain-verification RECOVERY_CHAIN_VERIFICATION — Optional recovery chain verification JSON/YAML
--environment ENVIRONMENT — Environment name
--stage STAGE — Evidence lifecycle stage
--actor ACTOR — Actor recorded in the evidence record
--store-backend STORE_BACKEND
--store-uri STORE_URI — Registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration registry history`¶

Usage: dpone schema migration registry history [--target TARGET] [--environment ENVIRONMENT] [--stage STAGE] [--status STATUS] [--from DATE_FROM] [--to DATE_TO] [--verify-artifacts] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment filter
--stage STAGE — Lifecycle stage filter
--status STATUS — Record status filter
--from DATE_FROM — Start date YYYY-MM-DD
--to DATE_TO — End date YYYY-MM-DD
--verify-artifacts — Reserved for slower future artifact recheck
--store-backend STORE_BACKEND
--store-uri STORE_URI — Registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration registry latest`¶

Usage: dpone schema migration registry latest [--target TARGET] [--environment ENVIRONMENT] [--stage STAGE] [--status STATUS] [--from DATE_FROM] [--to DATE_TO] [--verify-artifacts] [--include-blocked] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment filter
--stage STAGE — Lifecycle stage filter
--status STATUS — Record status filter
--from DATE_FROM — Start date YYYY-MM-DD
--to DATE_TO — End date YYYY-MM-DD
--verify-artifacts — Reserved for slower future artifact recheck
--include-blocked — Allow latest blocked record in result
--store-backend STORE_BACKEND
--store-uri STORE_URI — Registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration registry audit-report`¶

Usage: dpone schema migration registry audit-report [--target TARGET] [--environment ENVIRONMENT] [--from DATE_FROM] [--to DATE_TO] [--store-backend {local_json,sqlite}] [--store-uri STORE_URI] [--format {text,json,md,table}] [--output OUTPUT]
Options:
--target TARGET — Target key, e.g. clickhouse.analytics.orders
--environment ENVIRONMENT — Environment filter
--from DATE_FROM — Start date YYYY-MM-DD
--to DATE_TO — End date YYYY-MM-DD
--store-backend STORE_BACKEND
--store-uri STORE_URI — Registry path or SQLite database path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone schema migration review render`¶

Usage: dpone schema migration review render --bundle BUNDLE [--format {text,json,md}] [--output OUTPUT]
Options:
--bundle BUNDLE — bundle.json path
--format FORMAT
--output OUTPUT — Optional output artifact path

`dpone cdc`¶

`dpone cdc plan`¶

Usage: dpone cdc plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --schema SCHEMA --table TABLE [--slot-name SLOT_NAME] [--publication-name PUBLICATION_NAME] [--capture-instance CAPTURE_INSTANCE] [--format {text,json}]
Options:
--backend BACKEND
--schema SCHEMA
--table TABLE
--slot-name SLOT_NAME
--publication-name PUBLICATION_NAME
--capture-instance CAPTURE_INSTANCE
--format FORMAT

`dpone cdc replay-plan`¶

Usage: dpone cdc replay-plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --schema SCHEMA --table TABLE [--stored-offset STORED_OFFSET] --replay-from REPLAY_FROM [--replay-to REPLAY_TO] [--retention-min RETENTION_MIN] [--high-watermark HIGH_WATERMARK] [--artifact-uri ARTIFACT_URI] [--allow-rewind] [--format {md,json}]
Options:
--backend BACKEND
--pipeline-name PIPELINE_NAME
--schema SCHEMA
--table TABLE
--stored-offset STORED_OFFSET
--replay-from REPLAY_FROM
--replay-to REPLAY_TO
--retention-min RETENTION_MIN
--high-watermark HIGH_WATERMARK
--artifact-uri ARTIFACT_URI
--allow-rewind
--format FORMAT

`dpone hooks`¶

`dpone hooks execute`¶

Usage: dpone hooks execute [--selector SELECTOR] --phase {pre_hook,post_hook} [--hook-id HOOK_ID] [--dry-run] [--registry REGISTRY] [--format {json,text}] [--output OUTPUT] path
Positional arguments:
path — Path to a YAML manifest
Options:
--selector SELECTOR — Process selector inside a batch manifest
--phase PHASE
--hook-id HOOK_ID — Optional hook action id
--dry-run — Render selected hook action without executing it
--registry REGISTRY — Additional source registry YAML path
--format FORMAT
--output OUTPUT — Optional report output path

`dpone manifest`¶

`dpone manifest list`¶

Usage: dpone manifest list [--recursive] [--registry REGISTRY] path
Positional arguments:
path — Path to a YAML file or a directory
Options:
--recursive — Scan directories recursively
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest render`¶

Usage: dpone manifest render [--selector SELECTOR] [--all] [--registry REGISTRY] path
Positional arguments:
path — Path to a YAML manifest
Options:
--selector SELECTOR — Process selector inside a batch manifest
--all — Render all processes (batch)
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest explain`¶

Usage: dpone manifest explain [--selector SELECTOR] [--why WHY] [--item-provenance] [--patches] [--patches-mode {user,all}] [--patch-from PATCH_FROM] [--patch-to PATCH_TO] [--post-parse] [--why-parsed WHY_PARSED] [--format {text,json}] [--only ONLY] [--max-lines MAX_LINES] [--max-items MAX_ITEMS] [--registry REGISTRY] path
Positional arguments:
path — Path to a YAML manifest
Options:
--selector SELECTOR — Process selector inside a batch manifest
--why WHY — Explain why a specific config path has its value. Supports list indices, e.g. depends_on[2]. Can be repeated.
--item-provenance — Show per-item provenance for list fields (depends_on, transforms).
--patches — Show diff-friendly deep-merge patches per layer (copy/paste friendly).
--patches-mode PATCHES_MODE — Which layers to include in --patches output.
--patch-from PATCH_FROM — Compute a single patch from a given layer snapshot to another snapshot (or final).
--patch-to PATCH_TO — Target layer for --patch-from (default: final compiler config).
--post-parse — Explain post-parse normalization (how compiled dict becomes ETLProcessConfig/LoadConfig).
--why-parsed WHY_PARSED — Explain why a specific normalized path has its value (post-parse). Paths are inside a normalized tree: etl., load_config., dependencies[0].path, transforms[0].name, ... Can be repeated.
--format FORMAT — Output format
--only ONLY — Show only config changes for dot-path prefix (can be repeated), e.g. --only sink.options
--max-lines MAX_LINES — Max number of change lines to print (text mode)
--max-items MAX_ITEMS — Max number of list items to print (item-level provenance)
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest sparse-paths`¶

Usage: dpone manifest sparse-paths [--workload-root WORKLOAD_ROOT] [--include-global-overrides] [--include-env-overrides ENV] [--include-registry] [--registry REGISTRY] [--support-path SUPPORT_PATH] [--format {sparse,json}] path
Positional arguments:
path — Path to a YAML manifest
Options:
--workload-root WORKLOAD_ROOT — Workload root that bounds sparse path validation
--include-global-overrides — Include overrides/global.yaml
--include-env-overrides ENV — Include overrides/.yaml (can be repeated)
--include-registry — Include the workload registry/ directory
--registry REGISTRY — Include an explicit registry path (can be repeated)
--support-path SUPPORT_PATH — Include an extra manifest support file or directory (can be repeated)
--format FORMAT — Output format

`dpone manifest validate`¶

Usage: dpone manifest validate [--recursive] [--profile PROFILE] [--warn-only] [--registry REGISTRY] path
Positional arguments:
path — Path to a YAML file or a directory
Options:
--recursive — Scan directories recursively
--profile PROFILE — Built-in validation profile (e.g. landing_raw_v1). If omitted, will use manifest.validation block if present.
--warn-only — Exit 0 even if there are ERROR issues
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest lint-registry`¶

Usage: dpone manifest lint-registry [--recursive] [--require-field REQUIRE_FIELD] [--warn-only] [--registry REGISTRY] path
Positional arguments:
path — Path to a YAML file or a directory
Options:
--recursive — Scan directories recursively
--require-field REQUIRE_FIELD — Registry vars that must exist for each used (src_system, src_database) pair. Can be repeated.
--warn-only — Exit 0 even if there are ERROR issues
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest stats`¶

Usage: dpone manifest stats [--recursive] [--registry REGISTRY] path
Positional arguments:
path — Directory or manifest file
Options:
--recursive — Scan directories recursively
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest migrate`¶

Usage: dpone manifest migrate [--out-dir OUT_DIR] [--recursive] [--group-by {dataset,task_group,dataset_task_group}] [--dry-run] [--overwrite] [--no-infer-naming] [--naming-threshold NAMING_THRESHOLD] [--convention CONVENTION] [--registry REGISTRY] src
Positional arguments:
src — Source directory (legacy manifests) or a single YAML file
Options:
--out-dir OUT_DIR — Output directory for batch manifests (default: src dir)
--recursive — Scan directories recursively
--group-by GROUP_BY — Grouping strategy for batch manifests
--dry-run — Plan only; do not write files
--overwrite — Overwrite output files if they already exist
--no-infer-naming — Disable naming template inference
--naming-threshold NAMING_THRESHOLD — Min fraction of tables matching a pattern to enable naming templates (0..1)
--convention CONVENTION — Add convention: to generated batch manifests (e.g. landing_raw_v1). Convention provides default naming/metadata/validation; user config wins.
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone manifest verify`¶

Usage: dpone manifest verify --batch-dir BATCH_DIR [--recursive] [--group-by {dataset,task_group,dataset_task_group}] [--ignore-depends] [--ignore IGNORE] [--max-diffs MAX_DIFFS] [--out-json OUT_JSON] [--warn-only] [--registry REGISTRY] legacy
Positional arguments:
legacy — Legacy directory (or file) with single manifests
Options:
--batch-dir BATCH_DIR — Directory containing generated batch manifests
--recursive — Scan legacy directories recursively
--group-by GROUP_BY — Grouping strategy used during migration (must match)
--ignore-depends — Do not compare depends_on (useful if you rewrite dependencies manually)
--ignore IGNORE — Ignore a dot-path during comparison (can be repeated), e.g. --ignore sink.options
--max-diffs MAX_DIFFS — Max number of diffs to print per mismatched process
--out-json OUT_JSON — Write full report to a JSON file (useful for CI artifacts)
--warn-only — Exit 0 even if verification finds mismatches
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone migrate`¶

`dpone migrate authoring`¶

Usage: dpone migrate authoring [--from {classic,flow,folder}] --to {classic,flow,folder} (--plan | --apply) [--format {text,json}] target
Positional arguments:
target — Pipeline id, directory, or pipeline.yaml path
Options:
--from SOURCE_MODE — Assert the detected source mode
--to TARGET_MODE — Target authoring mode
--plan — Show the deterministic migration plan
--apply — Recompute and safely apply the migration
--format FORMAT

`dpone gitops`¶

`dpone gitops affected`¶

Usage: dpone gitops affected [--changed-files CHANGED_FILES [CHANGED_FILES ...]] [--changed-files-file CHANGED_FILES_FILE] [--from-ref FROM_REF] [--to-ref TO_REF] [--workload-root WORKLOAD_ROOT] [--manifest-glob MANIFEST_GLOB] [--include-global-overrides] [--include-env-overrides ENV] [--include-registry] [--registry REGISTRY] [--support-path SUPPORT_PATH] [--runner {generic,airflow,kubernetes_pod_operator,github_actions,dagster}] [--emit-plans] [--output-dir OUTPUT_DIR] [--output OUTPUT] [--format {json,markdown}]
Options:
--changed-files CHANGED_FILES — Repo-relative files changed by Git or CI
--changed-files-file CHANGED_FILES_FILE — Repo-relative newline-delimited changed-files list
--from-ref FROM_REF — Git ref used as the left side of git diff --name-only
--to-ref TO_REF — Git ref used as the right side of git diff --name-only
--workload-root WORKLOAD_ROOT — Workload root that bounds manifest discovery
--manifest-glob MANIFEST_GLOB — Manifest glob evaluated under the workload root
--include-global-overrides — Include overrides/global.yaml
--include-env-overrides ENV — Include overrides/.yaml
--include-registry — Include the workload registry/ directory
--registry REGISTRY — Include an explicit registry path
--support-path SUPPORT_PATH — Include an extra support file or directory
--runner RUNNER — Runner family used for suggested plan commands
--emit-plans — Write gitops.plan artifacts for impacted manifests
--output-dir OUTPUT_DIR — Repo-relative directory for emitted plan artifacts
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT — Output format

`dpone gitops airflow deps`¶

Usage: dpone gitops airflow deps --workload-set WORKLOAD_SET [--environment ENVIRONMENT] [--repo-root REPO_ROOT] [--format {md,json}]
Options:
--workload-set WORKLOAD_SET — GitOps workload-set root, for example gitops.yaml
--environment ENVIRONMENT — GitOps environment name
--repo-root REPO_ROOT — Repository root
--format FORMAT

`dpone gitops airflow render`¶

Usage: dpone gitops airflow render [--output-dir OUTPUT_DIR] --image IMAGE [--image-digest IMAGE_DIGEST] [--dpone-version DPONE_VERSION] [--python-version PYTHON_VERSION] [--airflow-provider-version AIRFLOW_PROVIDER_VERSION] [--tool TOOL] [--user USER] [--workdir WORKDIR] [--entrypoint ENTRYPOINT] [--image-contract IMAGE_CONTRACT] [--namespace NAMESPACE] [--service-account SERVICE_ACCOUNT] [--dag-id DAG_ID] [--task-id TASK_ID] [--outcome-mode {strict_fail,xcom_then_gate}] [--require-attestation] [--output OUTPUT] [--format {json,markdown}] bundle_path
Positional arguments:
bundle_path — Repo-relative gitops.bundle JSON path
Options:
--output-dir OUTPUT_DIR — Repo-relative output directory
--image IMAGE — Custom dpone runner image
--image-digest IMAGE_DIGEST — Optional immutable image digest for generated image contract
--dpone-version DPONE_VERSION — dpone version baked into the image
--python-version PYTHON_VERSION — Python version baked into the image
--airflow-provider-version AIRFLOW_PROVIDER_VERSION — apache-airflow-providers-cncf-kubernetes version
--tool TOOL — Executable expected in the image; repeatable
--user USER — Container user
--workdir WORKDIR — Container working directory
--entrypoint ENTRYPOINT — Container entrypoint path
--image-contract IMAGE_CONTRACT — Repo-relative image contract path
--namespace NAMESPACE — Kubernetes namespace for generated examples
--service-account SERVICE_ACCOUNT — Kubernetes service account for generated examples
--dag-id DAG_ID — Generated Airflow DAG id
--task-id TASK_ID — Generated Airflow task id
--outcome-mode OUTCOME_MODE — Pod exit strategy for final XCom outcomes
--require-attestation — Require bundle attestation before rendering
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow run-spec`¶

Usage: dpone gitops airflow run-spec [--output-path OUTPUT_PATH] [--evidence-output EVIDENCE_OUTPUT] --image IMAGE [--image-digest IMAGE_DIGEST] [--worktree WORKTREE] [--require-attestation] [--output OUTPUT] [--format {json,markdown}] bundle_path
Positional arguments:
bundle_path — Repo-relative gitops.bundle JSON path
Options:
--output-path OUTPUT_PATH — Repo-relative run-spec JSON artifact path
--evidence-output EVIDENCE_OUTPUT — Repo-relative runtime evidence artifact path
--image IMAGE — Custom dpone runner image
--image-digest IMAGE_DIGEST — Optional immutable image digest
--worktree WORKTREE — Repo-relative worktree path inside the runner pod
--require-attestation — Require bundle attestation
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow runtime-profile`¶

Usage: dpone gitops airflow runtime-profile [--run-spec-path RUN_SPEC_PATH] [--runtime-evidence-path RUNTIME_EVIDENCE_PATH] [--output-path OUTPUT_PATH] [--xcom-summary-path XCOM_SUMMARY_PATH] [--dag-factory-path DAG_FACTORY_PATH] [--outcome-gate-path OUTCOME_GATE_PATH] --image IMAGE [--image-digest IMAGE_DIGEST] [--namespace NAMESPACE] [--service-account SERVICE_ACCOUNT] [--cpu-request CPU_REQUEST] [--memory-request MEMORY_REQUEST] [--cpu-limit CPU_LIMIT] [--memory-limit MEMORY_LIMIT] [--artifact-sink-kind ARTIFACT_SINK_KIND] [--artifact-sink-path ARTIFACT_SINK_PATH] [--env ENV] [--label LABEL] [--annotation ANNOTATION] [--git-sync-repo GIT_SYNC_REPO] [--git-sync-ref GIT_SYNC_REF] [--git-sync-image GIT_SYNC_IMAGE] [--git-sync-depth GIT_SYNC_DEPTH] [--git-sync-filter {blob:none,tree:0}] [--git-sync-auth-mode {image,ssh_secret,https_secret}] [--git-sync-ssh-secret GIT_SYNC_SSH_SECRET] [--git-sync-ssh-key GIT_SYNC_SSH_KEY] [--git-sync-ssh-known-hosts-key GIT_SYNC_SSH_KNOWN_HOSTS_KEY] [--git-sync-https-secret GIT_SYNC_HTTPS_SECRET] [--git-sync-https-username-key GIT_SYNC_HTTPS_USERNAME_KEY] [--git-sync-https-password-key GIT_SYNC_HTTPS_PASSWORD_KEY] [--airflow-connection-bridge {k8s_secret,env,disabled}] [--airflow-connection-secret AIRFLOW_CONNECTION_SECRET] [--airflow-runtime-mode {runtime_only,airflow_image}] [--runner-policy {advisory,pr,release}] [--outcome-mode {strict_fail,xcom_then_gate}] [--output OUTPUT] [--format {json,markdown}] bundle_path
Positional arguments:
bundle_path — Repo-relative gitops.bundle JSON path
Options:
--run-spec-path RUN_SPEC_PATH — Repo-relative Airflow run-spec JSON path
--runtime-evidence-path RUNTIME_EVIDENCE_PATH — Repo-relative runtime evidence JSON path written by the runner
--output-path OUTPUT_PATH — Repo-relative runtime profile JSON artifact path
--xcom-summary-path XCOM_SUMMARY_PATH — Repo-relative planned XCom summary JSON artifact path
--dag-factory-path DAG_FACTORY_PATH — Repo-relative generated Airflow DAG factory path
--outcome-gate-path OUTCOME_GATE_PATH — Repo-relative generated Airflow outcome gate helper path
--image IMAGE — Custom dpone runner image
--image-digest IMAGE_DIGEST — Immutable custom dpone image digest
--namespace NAMESPACE — Kubernetes namespace for runner pods
--service-account SERVICE_ACCOUNT — Kubernetes service account for runner pods
--cpu-request CPU_REQUEST — Container CPU request
--memory-request MEMORY_REQUEST — Container memory request
--cpu-limit CPU_LIMIT — Container CPU limit
--memory-limit MEMORY_LIMIT — Container memory limit
--artifact-sink-kind ARTIFACT_SINK_KIND — Runtime artifact sink kind
--artifact-sink-path ARTIFACT_SINK_PATH — Repo-relative artifact sink path
--env ENV — Runner environment variable NAME=value; repeatable
--label LABEL — Kubernetes label KEY=value; repeatable
--annotation ANNOTATION — Kubernetes annotation KEY=value; repeatable
--git-sync-repo GIT_SYNC_REPO — Git repository URL for sparse git-sync initContainers
--git-sync-ref GIT_SYNC_REF — Git ref, branch, tag, or SHA for git-sync; defaults to HEAD
--git-sync-image GIT_SYNC_IMAGE — git-sync v4 image used by the sparse checkout initContainer
--git-sync-depth GIT_SYNC_DEPTH — git-sync shallow clone depth; 0 syncs full history
--git-sync-filter GIT_SYNC_FILTER — git-sync partial clone filter; requires git-sync v4.7.0+ for release profiles
--git-sync-auth-mode GIT_SYNC_AUTH_MODE — git-sync auth source; secret modes serialize only secret names and keys
--git-sync-ssh-secret GIT_SYNC_SSH_SECRET — Kubernetes Secret name with SSH key and known_hosts data
--git-sync-ssh-key GIT_SYNC_SSH_KEY — Secret key containing the SSH private key
--git-sync-ssh-known-hosts-key GIT_SYNC_SSH_KNOWN_HOSTS_KEY — Secret key containing SSH known_hosts data
--git-sync-https-secret GIT_SYNC_HTTPS_SECRET — Kubernetes Secret name with HTTPS username/password data
--git-sync-https-username-key GIT_SYNC_HTTPS_USERNAME_KEY — Secret key containing HTTPS username
--git-sync-https-password-key GIT_SYNC_HTTPS_PASSWORD_KEY — Secret key containing HTTPS password/token
--airflow-connection-bridge AIRFLOW_CONNECTION_BRIDGE — Bridge connection_type=airflow ids into runtime-only pods
--airflow-connection-secret AIRFLOW_CONNECTION_SECRET — Kubernetes Secret containing AIRFLOW_CONN_* URI values
--airflow-runtime-mode AIRFLOW_RUNTIME_MODE — Runner image contract mode for Airflow connection resolution
--runner-policy RUNNER_POLICY — Airflow runtime profile policy
--outcome-mode OUTCOME_MODE — Pod exit strategy for final XCom outcomes
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow pod-contract`¶

Usage: dpone gitops airflow pod-contract [--run-spec-path RUN_SPEC_PATH] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--output-path OUTPUT_PATH] [--pod-spec-path POD_SPEC_PATH] [--kpo-kwargs-path KPO_KWARGS_PATH] [--image-pull-secret IMAGE_PULL_SECRET] [--volume VOLUME] [--volume-mount VOLUME_MOUNT] [--env-from-configmap ENV_FROM_CONFIGMAP] [--env-secret ENV_SECRET] [--node-selector NODE_SELECTOR] [--toleration TOLERATION] [--label LABEL] [--annotation ANNOTATION] [--on-finish-action ON_FINISH_ACTION] [--get-logs | --no-get-logs] [--deferrable | --no-deferrable] [--outcome-mode {strict_fail,xcom_then_gate}] [--output OUTPUT] [--format {json,markdown}] bundle_path
Positional arguments:
bundle_path — Repo-relative gitops.bundle JSON path
Options:
--run-spec-path RUN_SPEC_PATH — Repo-relative Airflow run-spec JSON path
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative Airflow runtime profile JSON path
--output-path OUTPUT_PATH — Repo-relative pod contract JSON path
--pod-spec-path POD_SPEC_PATH — Repo-relative Kubernetes pod spec YAML path
--kpo-kwargs-path KPO_KWARGS_PATH — Repo-relative KubernetesPodOperator kwargs JSON path
--image-pull-secret IMAGE_PULL_SECRET — Kubernetes imagePullSecret name; repeatable
--volume VOLUME — Volume NAME=REPO_PATH; repeatable
--volume-mount VOLUME_MOUNT — Container mount NAME=/absolute/path[:ro|rw]; repeatable
--env-from-configmap ENV_FROM_CONFIGMAP — ConfigMap envFrom name; repeatable
--env-secret ENV_SECRET — Secret env NAME=secret:key; repeatable
--node-selector NODE_SELECTOR — Node selector KEY=value; repeatable
--toleration TOLERATION — Toleration KEY=value:Effect; repeatable
--label LABEL — Kubernetes label KEY=value; repeatable
--annotation ANNOTATION — Kubernetes annotation KEY=value; repeatable
--on-finish-action ON_FINISH_ACTION — KubernetesPodOperator on_finish_action
--get-logs, --no-get-logs — Enable KPO log streaming
--deferrable, --no-deferrable — Set KPO deferrable mode
--outcome-mode OUTCOME_MODE — Pod exit strategy for final XCom outcomes
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow pod-doctor`¶

Usage: dpone gitops airflow pod-doctor [--artifact-dir ARTIFACT_DIR] [--pod-contract-path POD_CONTRACT_PATH] [--pod-spec-path POD_SPEC_PATH] [--kpo-kwargs-path KPO_KWARGS_PATH] [--runner-policy {advisory,pr,release}] [--output OUTPUT] [--format {json,markdown}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory with pod-contract.json, pod-spec.yaml, and kpo-kwargs.json
--pod-contract-path POD_CONTRACT_PATH — Repo-relative pod contract JSON path
--pod-spec-path POD_SPEC_PATH — Repo-relative Kubernetes pod spec YAML path
--kpo-kwargs-path KPO_KWARGS_PATH — Repo-relative KubernetesPodOperator kwargs JSON path
--runner-policy RUNNER_POLICY — Airflow pod contract policy profile
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow connection-bridge-plan`¶

Usage: dpone gitops airflow connection-bridge-plan [--artifact-dir ARTIFACT_DIR] [--output-path OUTPUT_PATH] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--secret-manifest-path SECRET_MANIFEST_PATH] [--external-secret-path EXTERNAL_SECRET_PATH] [--env-example-path ENV_EXAMPLE_PATH] [--external-secret-store EXTERNAL_SECRET_STORE] [--external-secret-store-kind {SecretStore,ClusterSecretStore}] [--external-secret-remote-prefix EXTERNAL_SECRET_REMOTE_PREFIX] [--output OUTPUT] [--format {json,markdown}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--output-path OUTPUT_PATH — Repo-relative plan JSON path; defaults to /connection-bridge-plan.json
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative runtime-profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative pod-contract JSON path
--secret-manifest-path SECRET_MANIFEST_PATH — Repo-relative Kubernetes Secret skeleton path
--external-secret-path EXTERNAL_SECRET_PATH — Repo-relative ExternalSecret skeleton path
--env-example-path ENV_EXAMPLE_PATH — Repo-relative AIRFLOW_CONN_* env example path
--external-secret-store EXTERNAL_SECRET_STORE — ExternalSecret SecretStore name
--external-secret-store-kind EXTERNAL_SECRET_STORE_KIND — ExternalSecret SecretStore reference kind
--external-secret-remote-prefix EXTERNAL_SECRET_REMOTE_PREFIX — ExternalSecret remote key prefix for AIRFLOW_CONN_* values
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow cluster-doctor`¶

Usage: dpone gitops airflow cluster-doctor [--artifact-dir ARTIFACT_DIR] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--connection-bridge-plan-path CONNECTION_BRIDGE_PLAN_PATH] [--mode {plan,live}] [--runner-policy {advisory,pr,release}] [--timeout-seconds TIMEOUT_SECONDS] [--kubectl KUBECTL] [--external-secret EXTERNAL_SECRET] [--require-external-secret-ready] [--output OUTPUT] [--format {json,markdown}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative runtime-profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative pod-contract JSON path
--connection-bridge-plan-path CONNECTION_BRIDGE_PLAN_PATH — Repo-relative connection bridge plan JSON path
--mode MODE — Plan kubectl checks or execute them
--runner-policy RUNNER_POLICY — Cluster doctor policy
--timeout-seconds TIMEOUT_SECONDS — Per-command live cluster doctor timeout
--kubectl KUBECTL — kubectl executable name or wrapper
--external-secret EXTERNAL_SECRET — ExternalSecret name to check; repeatable
--require-external-secret-ready — Treat ExternalSecret readiness checks as release blockers
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow k8s-manifests`¶

Usage: dpone gitops airflow k8s-manifests [--artifact-dir ARTIFACT_DIR] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--connection-bridge-plan-path CONNECTION_BRIDGE_PLAN_PATH] [--manifest-output MANIFEST_OUTPUT] [--include-network-policy] [--gitops-controller {plain,argocd,flux}] [--output OUTPUT] [--format {json}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative runtime-profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative pod-contract JSON path
--connection-bridge-plan-path CONNECTION_BRIDGE_PLAN_PATH — Repo-relative connection bridge plan JSON path
--manifest-output MANIFEST_OUTPUT — Repo-relative Kubernetes manifest YAML output path
--include-network-policy — Include an opt-in allow-all-egress NetworkPolicy skeleton
--gitops-controller GITOPS_CONTROLLER — Add controller-aware metadata for Argo CD or Flux GitOps consumption
--output OUTPUT — Optional repo-relative JSON report output path
--format FORMAT — Output format

`dpone gitops airflow admission-check`¶

Usage: dpone gitops airflow admission-check [--artifact-dir ARTIFACT_DIR] [--manifest-path MANIFEST_PATH] [--pod-spec-path POD_SPEC_PATH] [--mode {plan,live}] [--runner-policy {advisory,pr,release}] [--timeout-seconds TIMEOUT_SECONDS] [--kubectl KUBECTL] [--output OUTPUT] [--format {json}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--manifest-path MANIFEST_PATH — Repo-relative Kubernetes manifest YAML path
--pod-spec-path POD_SPEC_PATH — Repo-relative pod-spec YAML path
--mode MODE — Plan commands or execute kubectl
--runner-policy RUNNER_POLICY — Admission policy
--timeout-seconds TIMEOUT_SECONDS — Per-command live admission timeout
--kubectl KUBECTL — kubectl executable name or wrapper
--output OUTPUT — Optional repo-relative JSON report output path
--format FORMAT — Output format

`dpone gitops airflow pack`¶

Usage: dpone gitops airflow pack [--workload WORKLOAD] [--workload-set WORKLOAD_SET] [--env ENV] [--artifact-dir ARTIFACT_DIR] [--bundle-path BUNDLE_PATH] [--image IMAGE] [--image-digest IMAGE_DIGEST] [--mode {plan,verify}] [--runner-policy {advisory,pr,release}] [--include-live-gates] [--output-path OUTPUT_PATH] [--output OUTPUT] [--format {json,markdown}]
Options:
--workload WORKLOAD — GitOps workload id for compact pack mode
--workload-set WORKLOAD_SET — Repo-relative GitOps workload-set YAML for compact pack mode
--env ENV — Environment scope for compact pack mode
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--bundle-path BUNDLE_PATH — Repo-relative bundle JSON path
--image IMAGE — Custom dpone runtime image used by Airflow workers
--image-digest IMAGE_DIGEST — Optional immutable image digest for planned runtime commands
--mode MODE — Plan steps or verify local artifacts
--runner-policy RUNNER_POLICY — Pack policy profile
--include-live-gates — Include credentialed live Kubernetes/Airflow gate commands in the report
--output-path OUTPUT_PATH — Repo-relative pack JSON path; defaults to /airflow-runtime-pack.json
--output OUTPUT — Optional repo-relative console output mirror path
--format FORMAT — Output format

`dpone gitops airflow reconcile`¶

Usage: dpone gitops airflow reconcile --workload-set WORKLOAD_SET [--changed-files CHANGED_FILES [CHANGED_FILES ...]] [--changed-files-file CHANGED_FILES_FILE] [--env ENV] [--output-dir OUTPUT_DIR] [--output OUTPUT] [--format {json,markdown}]
Options:
--workload-set WORKLOAD_SET — Repo-relative GitOps workload-set YAML
--changed-files CHANGED_FILES — Repo-relative changed files
--changed-files-file CHANGED_FILES_FILE — Repo-relative newline-delimited changed-files list
--env ENV — Environment scope
--output-dir OUTPUT_DIR — Repo-relative GitOps output root
--output OUTPUT — Optional repo-relative console output mirror path
--format FORMAT — Output format

`dpone gitops airflow release-materialize`¶

Usage: dpone gitops airflow release-materialize [--pack-root PACK_ROOT] [--cache-root CACHE_ROOT] [--xcom-sidecar-image XCOM_SIDECAR_IMAGE] [--dag-id DAG_ID] [--output OUTPUT] [--format {json,markdown}]
Options:
--pack-root PACK_ROOT — Repo-relative reconcile output containing packs and _dags/
--cache-root CACHE_ROOT — Local cache root for releases/
--xcom-sidecar-image XCOM_SIDECAR_IMAGE — Digest-pinned OCI ref required by strict init_fetch
--dag-id DAG_ID — Optional dag-spec id filter; repeatable. Default: all dag-specs under pack-root/_dags
--output OUTPUT — Optional repo-relative console output mirror path
--format FORMAT — Output format

`dpone gitops airflow publish`¶

Usage: dpone gitops airflow publish --workload-set WORKLOAD_SET [--env ENV] [--workload WORKLOAD] --git-sha GIT_SHA [--uri-prefix URI_PREFIX] [--latest-index-uri LATEST_INDEX_URI] [--pack-dir PACK_DIR] [--local-root-dir LOCAL_ROOT_DIR] [--connection-type {airflow,env,vault,params}] [--connection-id CONNECTION_ID] [--max-pack-bytes MAX_PACK_BYTES] [--max-index-bytes MAX_INDEX_BYTES] [--output OUTPUT] [--format {json}]
Options:
--workload-set WORKLOAD_SET
--env ENV
--workload WORKLOAD
--git-sha GIT_SHA
--uri-prefix URI_PREFIX
--latest-index-uri LATEST_INDEX_URI
--pack-dir PACK_DIR — Repo-relative directory with pre-built packs (//airflow-pack.json)
--local-root-dir LOCAL_ROOT_DIR — Local filesystem root for dry-run publish without S3 credentials
--connection-type CONNECTION_TYPE
--connection-id CONNECTION_ID
--max-pack-bytes MAX_PACK_BYTES
--max-index-bytes MAX_INDEX_BYTES
--output OUTPUT
--format FORMAT

`dpone gitops airflow artifact-index`¶

Usage: dpone gitops airflow artifact-index [--artifact-dir ARTIFACT_DIR] [--output-path OUTPUT_PATH] [--output OUTPUT] [--format {json,markdown}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--output-path OUTPUT_PATH — Repo-relative artifact-index JSON path; defaults to /artifact-index.json
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow preflight`¶

Usage: dpone gitops airflow preflight [--artifact-dir ARTIFACT_DIR] [--artifact-index-path ARTIFACT_INDEX_PATH] [--runner-policy {advisory,pr,release}] [--output OUTPUT] [--format {json,markdown}]
Options:
--artifact-dir ARTIFACT_DIR — Repo-relative Airflow artifact directory
--artifact-index-path ARTIFACT_INDEX_PATH — Repo-relative artifact-index JSON path used for freshness checks; defaults to /artifact-index.json
--runner-policy RUNNER_POLICY — Airflow preflight policy profile
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow outcome-gate`¶

Usage: dpone gitops airflow outcome-gate [--required-status REQUIRED_STATUS] [--output OUTPUT] [--format {json,markdown}] xcom_summary_path
Positional arguments:
xcom_summary_path — Repo-relative gitops.airflow_xcom_summary JSON path
Options:
--required-status REQUIRED_STATUS — Required final XCom status
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow k8s-smoke`¶

Usage: dpone gitops airflow k8s-smoke [--run-spec-path RUN_SPEC_PATH] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--image-contract-path IMAGE_CONTRACT_PATH] [--xcom-summary-path XCOM_SUMMARY_PATH] [--mode {plan,live}] [--runner-kind {kubernetes_pod_operator,kubernetes_executor}] [--runner-policy {advisory,pr,release}] [--smoke-name SMOKE_NAME] [--timeout-seconds TIMEOUT_SECONDS] [--kubectl KUBECTL] [--airflow-cmd AIRFLOW_CMD] [--output OUTPUT] [--format {json,markdown}]
Options:
--run-spec-path RUN_SPEC_PATH — Repo-relative Airflow run-spec JSON path
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative Airflow runtime profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative Airflow pod contract JSON path
--image-contract-path IMAGE_CONTRACT_PATH — Repo-relative custom dpone image contract JSON path
--xcom-summary-path XCOM_SUMMARY_PATH — Repo-relative final XCom summary JSON path
--mode MODE — Plan commands or execute them
--runner-kind RUNNER_KIND — Airflow Kubernetes runner kind being certified
--runner-policy RUNNER_POLICY — Airflow Kubernetes smoke policy
--smoke-name SMOKE_NAME — Stable Kubernetes smoke pod name prefix
--timeout-seconds TIMEOUT_SECONDS — Per-command live smoke timeout
--kubectl KUBECTL — kubectl executable name or wrapper
--airflow-cmd AIRFLOW_CMD — Airflow CLI executable name or wrapper
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow pod-watch`¶

Usage: dpone gitops airflow pod-watch [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--image-contract-path IMAGE_CONTRACT_PATH] [--runtime-evidence-path RUNTIME_EVIDENCE_PATH] [--xcom-summary-path XCOM_SUMMARY_PATH] [--pod-name POD_NAME] [--mode {plan,live}] [--runner-policy {advisory,pr,release}] [--expected-phase {Running,Succeeded,Failed,Any}] [--timeout-seconds TIMEOUT_SECONDS] [--log-tail-lines LOG_TAIL_LINES] [--kubectl KUBECTL] [--output OUTPUT] [--format {json,markdown}]
Options:
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative Airflow runtime profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative Airflow pod contract JSON path
--image-contract-path IMAGE_CONTRACT_PATH — Repo-relative custom dpone image contract JSON path
--runtime-evidence-path RUNTIME_EVIDENCE_PATH — Repo-relative runtime evidence JSON path
--xcom-summary-path XCOM_SUMMARY_PATH — Repo-relative final XCom summary JSON path
--pod-name POD_NAME — Kubernetes pod name; inferred from the pod contract when omitted
--mode MODE — Plan watch commands or execute them
--runner-policy RUNNER_POLICY — Airflow pod launch evidence policy
--expected-phase EXPECTED_PHASE — Expected observed Kubernetes pod phase
--timeout-seconds TIMEOUT_SECONDS — Per-command live watch timeout
--log-tail-lines LOG_TAIL_LINES — Base container log tail line count
--kubectl KUBECTL — kubectl executable name or wrapper
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow evidence-bundle`¶

Usage: dpone gitops airflow evidence-bundle [--bundle-path BUNDLE_PATH] [--run-spec-path RUN_SPEC_PATH] [--runtime-profile-path RUNTIME_PROFILE_PATH] [--pod-contract-path POD_CONTRACT_PATH] [--runtime-evidence-path RUNTIME_EVIDENCE_PATH] [--xcom-summary-path XCOM_SUMMARY_PATH] [--k8s-smoke-path K8S_SMOKE_PATH] [--pod-launch-evidence-path POD_LAUNCH_EVIDENCE_PATH] --dag-id DAG_ID --task-id TASK_ID --run-id RUN_ID --try-number TRY_NUMBER [--map-index MAP_INDEX] [--pod-name POD_NAME] [--pod-uid POD_UID] [--runner-policy {advisory,pr,release}] [--require-k8s-smoke] [--require-pod-launch-evidence] [--output OUTPUT] [--format {json,markdown}]
Options:
--bundle-path BUNDLE_PATH — Repo-relative bundle JSON path
--run-spec-path RUN_SPEC_PATH — Repo-relative Airflow run-spec JSON path
--runtime-profile-path RUNTIME_PROFILE_PATH — Repo-relative Airflow runtime profile JSON path
--pod-contract-path POD_CONTRACT_PATH — Repo-relative Airflow pod contract JSON path
--runtime-evidence-path RUNTIME_EVIDENCE_PATH — Repo-relative runtime evidence JSON path
--xcom-summary-path XCOM_SUMMARY_PATH — Repo-relative final XCom summary JSON path
--k8s-smoke-path K8S_SMOKE_PATH — Repo-relative optional Airflow Kubernetes smoke JSON path
--pod-launch-evidence-path POD_LAUNCH_EVIDENCE_PATH — Repo-relative optional pod-watch evidence JSON path
--dag-id DAG_ID — Airflow DAG id for this task attempt
--task-id TASK_ID — Airflow task id for this task attempt
--run-id RUN_ID — Airflow run id for this task attempt
--try-number TRY_NUMBER — Airflow try number
--map-index MAP_INDEX — Airflow mapped-task index, or -1 when unmapped
--pod-name POD_NAME — Observed Kubernetes pod name override
--pod-uid POD_UID — Observed Kubernetes pod UID override
--runner-policy RUNNER_POLICY — Airflow evidence bundle policy
--require-k8s-smoke — Block when k8s-smoke evidence is missing
--require-pod-launch-evidence — Block when pod-watch evidence is missing
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow run-spec-exec`¶

Usage: dpone gitops airflow run-spec-exec [--evidence-output EVIDENCE_OUTPUT] [--xcom-output XCOM_OUTPUT] [--output OUTPUT] [--format {json,markdown}] run_spec_path
Positional arguments:
run_spec_path — Repo-relative Airflow run-spec JSON path
Options:
--evidence-output EVIDENCE_OUTPUT — Repo-relative runtime evidence artifact path
--xcom-output XCOM_OUTPUT — Repo-relative final XCom summary artifact path
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow xcom-from-evidence`¶

Usage: dpone gitops airflow xcom-from-evidence --evidence-path EVIDENCE_PATH [--runtime-evidence-path RUNTIME_EVIDENCE_PATH] [--stderr-path STDERR_PATH] --xcom-output XCOM_OUTPUT [--status STATUS]
Options:
--evidence-path EVIDENCE_PATH — Runtime evidence JSON file path
--runtime-evidence-path RUNTIME_EVIDENCE_PATH — Path label stored in XCom summary
--stderr-path STDERR_PATH — Optional stderr file captured from the runtime command
--xcom-output XCOM_OUTPUT — Output path for /airflow/xcom/return.json
--status STATUS — Optional fallback status hint; evidence status remains authoritative when readable

`dpone gitops airflow evidence-verify`¶

Usage: dpone gitops airflow evidence-verify --run-spec-path RUN_SPEC_PATH [--require-all-steps] [--output OUTPUT] [--format {json,markdown}] evidence_path
Positional arguments:
evidence_path — Repo-relative runtime evidence JSON path
Options:
--run-spec-path RUN_SPEC_PATH — Repo-relative Airflow run-spec JSON path
--require-all-steps — Require evidence for every required run-spec step
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow doctor`¶

Usage: dpone gitops airflow doctor --pod-template POD_TEMPLATE --image-contract IMAGE_CONTRACT [--image IMAGE] [--require-attestation] [--runner-policy {advisory,pr,release}] [--output OUTPUT] [--format {json,markdown}] bundle_path
Positional arguments:
bundle_path — Repo-relative gitops.bundle JSON path
Options:
--pod-template POD_TEMPLATE — Repo-relative Airflow pod_template_file path
--image-contract IMAGE_CONTRACT — Repo-relative custom dpone image contract JSON
--image IMAGE — Expected custom dpone image
--require-attestation — Require bundle attestation
--runner-policy RUNNER_POLICY — Airflow runner policy profile
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops airflow image-contract`¶

Usage: dpone gitops airflow image-contract --image IMAGE [--image-digest IMAGE_DIGEST] [--dpone-version DPONE_VERSION] [--python-version PYTHON_VERSION] [--airflow-provider-version AIRFLOW_PROVIDER_VERSION] [--tool TOOL] [--user USER] [--workdir WORKDIR] [--entrypoint ENTRYPOINT] [--output-path OUTPUT_PATH] [--output OUTPUT] [--format {json,markdown}]
Options:
--image IMAGE — Custom dpone runner image
--image-digest IMAGE_DIGEST — Optional immutable image digest
--dpone-version DPONE_VERSION — dpone version baked into the image
--python-version PYTHON_VERSION — Python version baked into the image
--airflow-provider-version AIRFLOW_PROVIDER_VERSION — apache-airflow-providers-cncf-kubernetes version
--tool TOOL — Executable expected in the image; repeatable
--user USER — Container user
--workdir WORKDIR — Container working directory
--entrypoint ENTRYPOINT — Container entrypoint path
--output-path OUTPUT_PATH — Repo-relative image contract JSON path
--output OUTPUT — Optional repo-relative report output path
--format FORMAT — Output format

`dpone gitops bundle`¶

Usage: dpone gitops bundle [--changed-files CHANGED_FILES [CHANGED_FILES ...]] [--changed-files-file CHANGED_FILES_FILE] [--from-ref FROM_REF] [--to-ref TO_REF] [--workload-root WORKLOAD_ROOT] [--manifest-glob MANIFEST_GLOB] [--include-global-overrides] [--include-env-overrides ENV] [--include-registry] [--registry REGISTRY] [--support-path SUPPORT_PATH] [--runner {generic,airflow,kubernetes_pod_operator,github_actions,dagster}] [--worktree WORKTREE] [--verify-lock] [--fail-on-empty-impact] [--fail-on-warnings] [--require-lock] [--policy-profile {custom,advisory,pr,release}] [--attest] [--require-attestation] [--output-dir OUTPUT_DIR] [--output OUTPUT] [--format {json,markdown}] [{verify}] [bundle_path]
Positional arguments:
bundle_action — Use 'verify' to check an emitted bundle
bundle_path — Repo-relative bundle.json path for 'verify'
Options:
--changed-files CHANGED_FILES — Repo-relative files changed by Git or CI
--changed-files-file CHANGED_FILES_FILE — Repo-relative newline-delimited changed-files list
--from-ref FROM_REF — Git ref used as the left side of git diff --name-only
--to-ref TO_REF — Git ref used as the right side of git diff --name-only
--workload-root WORKLOAD_ROOT — Workload root that bounds manifest discovery
--manifest-glob MANIFEST_GLOB — Manifest glob evaluated under the workload root
--include-global-overrides — Include overrides/global.yaml
--include-env-overrides ENV — Include overrides/.yaml
--include-registry — Include the workload registry/ directory
--registry REGISTRY — Include an explicit registry path
--support-path SUPPORT_PATH — Include an extra support file or directory
--runner RUNNER — Runner family used for suggested plan commands
--worktree WORKTREE — Repo-relative sparse worktree to verify
--verify-lock — Verify SHA-256 file digests from emitted plan locks
--fail-on-empty-impact — Return a blocker when no manifests are impacted
--fail-on-warnings — Return a blocker when warnings are present
--require-lock — Require lock verification for the bundle policy gate
--policy-profile POLICY_PROFILE — Policy profile defaults for bundle gates
--attest — Embed SHA-256 artifact attestation in bundle.json
--require-attestation — Require bundle attestation when running 'dpone gitops bundle verify'
--output-dir OUTPUT_DIR — Repo-relative directory for bundle artifacts
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT — Output format

`dpone gitops gitlab render-child-pipeline`¶

Usage: dpone gitops gitlab render-child-pipeline --workload-set WORKLOAD_SET [--changed-files CHANGED_FILES [CHANGED_FILES ...]] [--changed-files-file CHANGED_FILES_FILE] [--env ENV] [--output OUTPUT] [--format {yaml}]
Options:
--workload-set WORKLOAD_SET — Repo-relative GitOps workload-set YAML
--changed-files CHANGED_FILES — Repo-relative changed files
--changed-files-file CHANGED_FILES_FILE — Repo-relative newline-delimited changed-files list
--env ENV — Environment scope
--output OUTPUT — Repo-relative child pipeline YAML path
--format FORMAT

`dpone gitops plan`¶

Usage: dpone gitops plan [--workload-root WORKLOAD_ROOT] [--include-global-overrides] [--include-env-overrides ENV] [--include-registry] [--registry REGISTRY] [--support-path SUPPORT_PATH] [--runner {generic,airflow,kubernetes_pod_operator,github_actions,dagster}] [--run-command RUN_COMMAND] [--output OUTPUT] [--format {json,markdown}] path
Positional arguments:
path — Path to a YAML manifest
Options:
--workload-root WORKLOAD_ROOT — Workload root that bounds sparse path validation
--include-global-overrides — Include overrides/global.yaml
--include-env-overrides ENV — Include overrides/.yaml
--include-registry — Include the workload registry/ directory
--registry REGISTRY — Include an explicit registry path
--support-path SUPPORT_PATH — Include an extra support file or directory
--runner RUNNER — Runner family consuming the plan
--run-command RUN_COMMAND — Command the runner should execute after checkout
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT — Output format

`dpone gitops schema list`¶

Usage: dpone gitops schema list [--prefix PREFIX] [--output OUTPUT] [--format {json,markdown}]
Options:
--prefix PREFIX — Optional contract name or kind prefix
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT

`dpone gitops schema show`¶

Usage: dpone gitops schema show [--output OUTPUT] [--format {json,markdown}] kind
Positional arguments:
kind — Contract name or kind, for example dpone.safe-sample-runtime-run.v1
Options:
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT

`dpone gitops schema validate`¶

Usage: dpone gitops schema validate --kind KIND --payload PAYLOAD [--output OUTPUT] [--format {json,markdown}]
Options:
--kind KIND — Contract name or kind
--payload PAYLOAD — JSON payload path
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT

`dpone gitops verify`¶

Usage: dpone gitops verify [--worktree WORKTREE] [--verify-lock] [--output OUTPUT] [--format {json,markdown}] plan
Positional arguments:
plan — Path to a GitOps plan JSON artifact
Options:
--worktree WORKTREE — Repo-relative sparse worktree to verify
--verify-lock — Verify SHA-256 file digests from the plan lock
--output OUTPUT — Optional repo-relative output artifact path
--format FORMAT — Output format

`dpone gitops workloads list`¶

Usage: dpone gitops workloads list --workload-set WORKLOAD_SET [--env ENV] [--output OUTPUT] [--format {json,markdown}]
Options:
--workload-set WORKLOAD_SET — Repo-relative GitOps workload-set YAML
--env ENV — Environment scope
--output OUTPUT — Optional repo-relative output path
--format FORMAT

`dpone gitops workloads explain`¶

Usage: dpone gitops workloads explain --workload-set WORKLOAD_SET [--env ENV] [--output OUTPUT] [--format {json,markdown}] workload_id
Positional arguments:
workload_id
Options:
--workload-set WORKLOAD_SET — Repo-relative GitOps workload-set YAML
--env ENV — Environment scope
--output OUTPUT — Optional repo-relative output path
--format FORMAT

`dpone workload`¶

`dpone workload init`¶

Usage: dpone workload init [--source SOURCE] [--sink SINK] [--strategy STRATEGY] [--wizard] [--layout {batch,catalog}] [--domain DOMAIN] [--dag DAG] [--schedule SCHEDULE] [--owner OWNER] [--timezone TIMEZONE] [--workload-set WORKLOAD_SET] [--repo-root REPO_ROOT] [--apply] [--format {text,json,md}] workload_ref
Positional arguments:
workload_ref — DOMAIN/WORKLOAD_ID reference, for example marketing/wa_reg_auth_app
Options:
--source SOURCE — Source connector type, for example clickhouse
--sink SINK — Sink connector type, for example mssql
--strategy STRATEGY — Load strategy mode
--wizard — Interactive route selection and apply confirmation
--layout LAYOUT — Manifest layout
--domain DOMAIN — Override domain when workload_ref is a bare workload id
--dag DAG — Declared DAG id (default DAG______sync)
--schedule SCHEDULE — Cron schedule for the declared DAG
--owner OWNER — DAG and ownership owner
--timezone TIMEZONE — DAG timezone
--workload-set WORKLOAD_SET — GitOps workload-set root
--repo-root REPO_ROOT — Repository root for scaffold paths
--apply — Write files (default is plan-only)
--format FORMAT

`dpone workload index`¶

Usage: dpone workload index [--root ROOT]
Options:
--root ROOT — Project root (default: current directory)
Output and exit contract:
0: UTF-8 dpone.workload-index.v1 JSON on stdout; stderr is empty.
1: structured JSON with dpone.error.v1 entries on stdout; stderr is empty.
2: argparse usage error on stderr.

`dpone workload impact`¶

Usage: dpone workload impact [--root ROOT] --baseline BASELINE [--current CURRENT]
Options:
--root ROOT — Project root (default: current directory)
--baseline BASELINE — Project-confined prior workload-index JSON/YAML
--current CURRENT — Project-confined candidate workload index; avoids rediscovery races in CI
Output and exit contract:
0: UTF-8 dpone.workload-change-impact.v1 JSON on stdout; stderr is empty.
1: failed discovery or invalid baseline/current JSON on stdout; stderr is empty.
2: argparse usage error on stderr.

`dpone workload promote`¶

Usage: dpone workload promote --candidate PATH --baseline PATH --approved-candidate-sha256 SHA256 --approved-current-fingerprint FINGERPRINT (--expect-baseline-absent | --expected-baseline-sha256 SHA256 --expected-baseline-fingerprint FINGERPRINT) [--root ROOT]
Options:
--root ROOT — Project root (default: current directory)
--candidate CANDIDATE — Project-confined approved candidate index
--baseline BASELINE — Project-confined accepted baseline path
--approved-candidate-sha256 APPROVED_CANDIDATE_SHA256 — Raw candidate digest from approval
--approved-current-fingerprint APPROVED_CURRENT_FINGERPRINT — Candidate semantic fingerprint from approval
--expected-baseline-sha256 EXPECTED_BASELINE_SHA256 — Approved raw digest of the existing baseline
--expect-baseline-absent — Create the first baseline only if it is still absent
--expected-baseline-fingerprint EXPECTED_BASELINE_FINGERPRINT — Approved existing-baseline fingerprint; required with --expected-baseline-sha256
Output and exit contract:
0: UTF-8 dpone.workload-index-promotion.v1 receipt on stdout.
1: invalid workload-index input on stdout; stderr is empty.
2: malformed promotion request as structured JSON on stdout, or argparse usage error on stderr.
4: approval, confinement, lock, or baseline-CAS violation on stdout.

`dpone airflow`¶

`dpone airflow preview`¶

Usage: dpone airflow preview [--format {text,json}] [--select EXPR] [--exclude EXPR] [--state STATE] [--selectors SELECTORS] [--max-selected MAX_SELECTED] pipeline
Positional arguments:
pipeline — Pipeline id, directory, or pipeline.yaml path
Options:
--format FORMAT
--select EXPR — Advanced: filter workloads (see Workload selectors docs)
--exclude EXPR — Advanced: exclude workloads after selection expansion
--state STATE — Advanced: local dpone.selection-state.v1 baseline for state:* selectors
--selectors SELECTORS — Advanced: named selector file (default: selectors.yaml)
--max-selected MAX_SELECTED — Advanced: hard selected workload limit (default: 500)
Output and exit contract:
0: bounded non-runnable preview result on stdout; stderr is empty.
1: validation or Airflow-authoring failure on stdout; stderr is empty.
2: argparse syntax error on stderr.
4: structured security or cache-integrity violation on stdout; stderr is empty.
JSON failures contain dpone.error.v1 entries.

`dpone airflow explain`¶

Usage: dpone airflow explain [--format {text,json}] pipeline
Positional arguments:
pipeline — Pipeline id, directory, or pipeline.yaml path
Options:
--format FORMAT

`dpone airflow build`¶

Usage: dpone airflow build --release-id RELEASE_ID --environment ENVIRONMENT [--trust-tier {production,non_production}] [--runtime-image-ref RUNTIME_IMAGE_REF] --runtime-image-digest RUNTIME_IMAGE_DIGEST --artifact-registry-ref ARTIFACT_REGISTRY_REF [--registry-config-map-name REGISTRY_CONFIG_MAP_NAME] [--registry-config-map-key REGISTRY_CONFIG_MAP_KEY] [--registry-config-sha256 REGISTRY_CONFIG_SHA256] [--trust-policy-config-map-name TRUST_POLICY_CONFIG_MAP_NAME] [--trust-policy-config-map-key TRUST_POLICY_CONFIG_MAP_KEY] [--trust-policy-sha256 TRUST_POLICY_SHA256] [--airflow-bundle-ref AIRFLOW_BUNDLE_REF] [--format {text,json}]
Options:
--release-id RELEASE_ID — Environment-neutral release-set digest
--environment ENVIRONMENT — Environment name, for example dev or prod
--trust-tier TRUST_TIER — Explicit deployment trust tier required by strict v2; never inferred from the environment name
--runtime-image-ref RUNTIME_IMAGE_REF — Exact OCI runtime image ref ending in @sha256:; required by strict v2
--runtime-image-digest RUNTIME_IMAGE_DIGEST — Pinned dpone runtime image digest
--artifact-registry-ref ARTIFACT_REGISTRY_REF — Deployment-owned bounded logical artifact registry reference
--registry-config-map-name REGISTRY_CONFIG_MAP_NAME — Artifact registry ConfigMap name required by strict v2
--registry-config-map-key REGISTRY_CONFIG_MAP_KEY — Artifact registry ConfigMap key; defaults to registry.json when the ConfigMap is selected
--registry-config-sha256 REGISTRY_CONFIG_SHA256 — SHA-256 of the exact artifact registry ConfigMap file bytes required by strict v2
--trust-policy-config-map-name TRUST_POLICY_CONFIG_MAP_NAME — Production artifact trust-policy ConfigMap name
--trust-policy-config-map-key TRUST_POLICY_CONFIG_MAP_KEY — Artifact trust-policy ConfigMap key; defaults to policy.json when the ConfigMap is selected
--trust-policy-sha256 TRUST_POLICY_SHA256 — SHA-256 of the exact artifact trust-policy ConfigMap file bytes
--airflow-bundle-ref AIRFLOW_BUNDLE_REF — Optional Airflow DAG Bundle reference
--format FORMAT

`dpone airflow publish`¶

Usage: dpone airflow publish [--cache-root CACHE_ROOT] --release-id RELEASE_ID --deployment-id DEPLOYMENT_ID --environment ENVIRONMENT --artifact-registry-ref ARTIFACT_REGISTRY_REF --registry-uri REGISTRY_URI (--local-registry-root LOCAL_REGISTRY_ROOT | --identity-mode {workload_identity} | --connection-id CONNECTION_ID) [--connection-type {airflow,env,vault}] [--max-object-bytes MAX_OBJECT_BYTES] [--max-total-bytes MAX_TOTAL_BYTES] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root
--release-id RELEASE_ID — Exact canonical release digest
--deployment-id DEPLOYMENT_ID — Exact canonical deployment digest
--environment ENVIRONMENT — Deployment environment
--artifact-registry-ref ARTIFACT_REGISTRY_REF — Deployment-owned logical registry ref
--registry-uri REGISTRY_URI — Object-storage registry root URI
--local-registry-root LOCAL_REGISTRY_ROOT — Local object-store emulator root for deterministic proof
--identity-mode IDENTITY_MODE — Platform workload identity
--connection-id CONNECTION_ID — Logical dpone credential reference
--connection-type CONNECTION_TYPE — Credential resolver used with --connection-id
--max-object-bytes MAX_OBJECT_BYTES
--max-total-bytes MAX_TOTAL_BYTES
--format FORMAT

`dpone airflow cache-materialize`¶

Usage: dpone airflow cache-materialize [--cache-root CACHE_ROOT] --release-id RELEASE_ID --deployment-id DEPLOYMENT_ID --environment ENVIRONMENT --artifact-registry-ref ARTIFACT_REGISTRY_REF --registry-uri REGISTRY_URI (--local-registry-root LOCAL_REGISTRY_ROOT | --identity-mode {workload_identity}) [--max-object-bytes MAX_OBJECT_BYTES] [--max-total-bytes MAX_TOTAL_BYTES] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root
--release-id RELEASE_ID — Exact canonical release digest
--deployment-id DEPLOYMENT_ID — Exact canonical deployment digest
--environment ENVIRONMENT — Deployment environment
--artifact-registry-ref ARTIFACT_REGISTRY_REF — Deployment-owned logical registry ref
--registry-uri REGISTRY_URI — Object-storage registry root URI
--local-registry-root LOCAL_REGISTRY_ROOT — Local object-store emulator root for deterministic proof
--identity-mode IDENTITY_MODE — Platform workload identity
--max-object-bytes MAX_OBJECT_BYTES
--max-total-bytes MAX_TOTAL_BYTES
--format FORMAT

`dpone airflow cache-sync`¶

Usage: dpone airflow cache-sync [--cache-root CACHE_ROOT] --deployment-dir DEPLOYMENT_DIR --environment ENVIRONMENT --promoted-by PROMOTED_BY --allowed-promoter ALLOWED_PROMOTER (--expected-current-deployment-id EXPECTED_CURRENT_DEPLOYMENT_ID | --expect-current-absent) [--source-commit SOURCE_COMMIT] [--attestation-ref ATTESTATION_REF] [--confirm-promote] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root; defaults to .dpone-cache
--deployment-dir DEPLOYMENT_DIR — Deployment with pinned release-set and artifacts
--environment ENVIRONMENT — Deployment environment to promote
--promoted-by PROMOTED_BY — CI/service identity promoting the deployment
--allowed-promoter ALLOWED_PROMOTER — Platform-approved CI/service identity; repeat for an exact-match promotion allowlist
--expected-current-deployment-id EXPECTED_CURRENT_DEPLOYMENT_ID — CAS guard for updates; promotion fails if current pointer changed
--expect-current-absent — CAS guard for the first promotion; fails if current already exists
--source-commit SOURCE_COMMIT — Optional source commit provenance
--attestation-ref ATTESTATION_REF — Optional promotion attestation reference
--confirm-promote — Required acknowledgement before switching the local current pointer
--format FORMAT — Output text or dpone cache-sync JSON; defaults to text

`dpone airflow cache-retention-plan`¶

Usage: dpone airflow cache-retention-plan [--cache-root CACHE_ROOT] [--environment ENVIRONMENT] [--protect-deployment-id PROTECT_DEPLOYMENT_ID] [--evidence-file EVIDENCE_FILE] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root; defaults to .dpone-cache
--environment ENVIRONMENT — Deployment environment to inspect; defaults to dev
--protect-deployment-id PROTECT_DEPLOYMENT_ID — Deployment id protected by active runs or reproducible evidence; repeatable
--evidence-file EVIDENCE_FILE — Local evidence JSON containing deployment_id references to protect; repeatable
--format FORMAT — Output text or dpone.deployment-cache-retention-plan.v1 JSON; defaults to text

`dpone airflow cache-retention-apply`¶

Usage: dpone airflow cache-retention-apply [--cache-root CACHE_ROOT] [--environment ENVIRONMENT] [--protect-deployment-id PROTECT_DEPLOYMENT_ID] [--evidence-file EVIDENCE_FILE] [--confirm-delete] --promoted-by PROMOTED_BY --allowed-promoter ALLOWED_PROMOTER [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root; defaults to .dpone-cache
--environment ENVIRONMENT — Deployment environment to inspect; defaults to dev
--protect-deployment-id PROTECT_DEPLOYMENT_ID — Deployment id protected by active runs or reproducible evidence; repeatable
--evidence-file EVIDENCE_FILE — Local evidence JSON containing deployment_id references to protect; repeatable
--confirm-delete — Required acknowledgement before deleting unreferenced deployment cache entries
--promoted-by PROMOTED_BY — CI/service identity applying cache retention
--allowed-promoter ALLOWED_PROMOTER — Platform-approved retention identity; repeat for an exact-match allowlist
--format FORMAT — Output text or dpone.deployment-cache-retention-apply.v1 JSON; defaults to text

`dpone airflow cache-recovery-plan`¶

Usage: dpone airflow cache-recovery-plan [--cache-root CACHE_ROOT] [--environment ENVIRONMENT] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root; defaults to .dpone-cache
--environment ENVIRONMENT — Deployment environment to inspect; defaults to dev
--format FORMAT — Output text or dpone.deployment-cache-recovery-plan.v1 JSON; defaults to text

`dpone airflow cache-recovery-apply`¶

Usage: dpone airflow cache-recovery-apply [--cache-root CACHE_ROOT] [--environment ENVIRONMENT] --deployment-id DEPLOYMENT_ID --promoted-by PROMOTED_BY --allowed-promoter ALLOWED_PROMOTER (--expected-current-deployment-id EXPECTED_CURRENT_DEPLOYMENT_ID | --expect-current-absent) [--confirm-repair] [--format {text,json}]
Options:
--cache-root CACHE_ROOT — Local dpone cache root; defaults to .dpone-cache
--environment ENVIRONMENT — Deployment environment to repair; defaults to dev
--deployment-id DEPLOYMENT_ID — Deployment id to promote during recovery
--promoted-by PROMOTED_BY — CI/service identity applying the recovery
--allowed-promoter ALLOWED_PROMOTER — Platform-approved recovery identity; repeat for an exact-match allowlist
--expected-current-deployment-id EXPECTED_CURRENT_DEPLOYMENT_ID — Active deployment id observed in the reviewed recovery plan
--expect-current-absent — Assert that the reviewed recovery plan observed no active current deployment
--confirm-repair — Required acknowledgement before switching the local current pointer
--format FORMAT — Output text or dpone.deployment-cache-recovery-apply.v1 JSON; defaults to text

`dpone airflow runtime-init-fetch`¶

Usage: dpone airflow runtime-init-fetch

`dpone airflow runtime-pack-exec`¶

Usage: dpone airflow runtime-pack-exec

`dpone airflow rerun-plan`¶

Usage: dpone airflow rerun-plan --evidence EVIDENCE --current-index CURRENT_INDEX [--cache-root CACHE_ROOT] [--bundle {original,latest}] [--artifacts {original,latest}] [--critical] [--output OUTPUT] [--format {text,json}]
Options:
--evidence EVIDENCE — Original gitops.airflow_evidence_bundle JSON
--current-index CURRENT_INDEX — Current local airflow-index.json
--cache-root CACHE_ROOT — Local cache root; inferred from --current-index by default
--bundle BUNDLE
--artifacts ARTIFACTS
--critical — Require fully reproducible retained inputs
--output OUTPUT — Optional plan JSON path written atomically
--format FORMAT

`dpone airflow connection-secret-gc-plan`¶

Usage: dpone airflow connection-secret-gc-plan --namespace NAMESPACE [--minimum-age-seconds MINIMUM_AGE_SECONDS] [--page-size PAGE_SIZE] [--kube-auth {auto,in-cluster,kubeconfig}] [--kube-context KUBE_CONTEXT] [--format {text,json}]
Options:
--namespace NAMESPACE — One Kubernetes namespace
--minimum-age-seconds MINIMUM_AGE_SECONDS — Age floor; 300..2592000
--page-size PAGE_SIZE — Metadata page size; 1..1000
--kube-auth KUBE_AUTH — Kubernetes authentication source; defaults to auto
--kube-context KUBE_CONTEXT — Optional kubeconfig context; incompatible with in-cluster
--format FORMAT — Topology-free text or schema-validated JSON; defaults to text

`dpone airflow connection-secret-gc-apply`¶

Usage: dpone airflow connection-secret-gc-apply --namespace NAMESPACE [--minimum-age-seconds MINIMUM_AGE_SECONDS] [--page-size PAGE_SIZE] [--kube-auth {auto,in-cluster,kubeconfig}] [--kube-context KUBE_CONTEXT] [--format {text,json}] [--max-delete-count MAX_DELETE_COUNT] --actor ACTOR --allowed-actor ALLOWED_ACTOR [--confirm-delete]
Options:
--namespace NAMESPACE — One Kubernetes namespace
--minimum-age-seconds MINIMUM_AGE_SECONDS — Age floor; 300..2592000
--page-size PAGE_SIZE — Metadata page size; 1..1000
--kube-auth KUBE_AUTH — Kubernetes authentication source; defaults to auto
--kube-context KUBE_CONTEXT — Optional kubeconfig context; incompatible with in-cluster
--format FORMAT — Topology-free text or schema-validated JSON; defaults to text
--max-delete-count MAX_DELETE_COUNT — Maximum deletes per invocation; 1..1000
--actor ACTOR — Platform audit identity
--allowed-actor ALLOWED_ACTOR — Exact allowed platform identity; repeatable
--confirm-delete — Required deletion acknowledgement

`dpone dag`¶

`dpone dag explain-edge`¶

Usage: dpone dag explain-edge --from UPSTREAM --to DOWNSTREAM [--dag-spec] [--dag-id DAG_ID] [--env ENV] [--base-path BASE_PATH] [--path] [--explain-path] [--path-view {edges,grouped}] [--path-output {compact,full}] [--max-triggers MAX_TRIGGERS] [--format {text,json}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). With --dag-spec this is the GitOps workload-set path (for example dpone_workloads/gitops/gitops.yaml).
Options:
--from UPSTREAM — Upstream task: task_id or file.yaml#selector
--to DOWNSTREAM — Downstream task: task_id or file.yaml#selector
--dag-spec — Explain a GitOps dag-spec edge using declared/curated/inferred layer provenance.
--dag-id DAG_ID — DAG id from the domain catalog dags: block (required with --dag-spec).
--env ENV — GitOps environment label for dag-spec resolution (default: dev).
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--path — If there is no direct edge, try to find and print a shortest path A ~> B.
--explain-path — With --path: also explain every edge along the found path.
--path-view PATH_VIEW — How to present path explanations when --explain-path is enabled.
--path-output PATH_OUTPUT — Level of detail for each edge explanation along the path.
--max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag explain-edge-e2e`¶

Usage: dpone dag explain-edge-e2e --from UPSTREAM --to DOWNSTREAM [--base-path BASE_PATH] [--max-triggers MAX_TRIGGERS] [--path] [--explain-path] [--path-view {edges,grouped}] [--path-output {compact,full}] [--format {text,json}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
Options:
--from UPSTREAM — Upstream task: task_id or file.yaml#selector
--to DOWNSTREAM — Downstream task: task_id or file.yaml#selector
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group attributions.
--path — If there is no direct edge, try to find and print a shortest path A ~> B.
--explain-path — With --path (or when used alone): explain every edge along the found shortest path end-to-end.
--path-view PATH_VIEW — How to present path explanations when --explain-path is enabled.
--path-output PATH_OUTPUT — Level of detail for each end-to-end edge explanation along the path.
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag list-edges`¶

Usage: dpone dag list-edges [--base-path BASE_PATH] [--from UPSTREAM] [--to DOWNSTREAM] [--task TASK] [--group GROUP] [--file FILE] [--selector SELECTOR] [--with-refs] [--with-files] [--with-groups] [--with-reasons] [--max MAX_EDGES] [--max-triggers MAX_TRIGGERS] [--format {text,json}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
Options:
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--from UPSTREAM — Filter: upstream task token (task_id, #selector, file.yaml#selector)
--to DOWNSTREAM — Filter: downstream task token (task_id, #selector, file.yaml#selector)
--task TASK — Filter: include only edges touching this task token (can be repeated)
--group GROUP — Filter: include only edges touching this task_group (can be repeated)
--file FILE — Filter: include only edges touching a YAML file (absolute or relative; can be repeated)
--selector SELECTOR — Filter: include only edges touching this selector (can be repeated)
--with-refs — Include node refs (file.yaml#selector) for copy/paste into explain-edge
--with-files — Include node config_path filenames
--with-groups — Include upstream/downstream task_group columns
--with-reasons — Include reason kinds for each printed edge (slower for large graphs)
--max MAX_EDGES — Max number of edges to print (after filtering)
--max-triggers MAX_TRIGGERS — Max trigger tasks to attribute for group-to-group reasons (when --with-reasons)
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag explain-node`¶

Usage: dpone dag explain-node [--direction {in,out,both}] [--output {compact,full}] [--max-in MAX_IN] [--max-out MAX_OUT] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root task
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
task — Task token (task_id, #selector, file.yaml#selector)
Options:
--direction DIRECTION — Which edges to show.
--output OUTPUT — Compact table or full edge-by-edge explanations.
--max-in MAX_IN — Max incoming edges
--max-out MAX_OUT — Max outgoing edges
--max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag explain-node-e2e`¶

Usage: dpone dag explain-node-e2e [--focus-peer FOCUS_PEER] [--direction {in,out,both}] [--output {compact,full}] [--max-in MAX_IN] [--max-out MAX_OUT] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root task
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
task — Task token (task_id, #selector, file.yaml#selector)
Options:
--focus-peer FOCUS_PEER — Limit end-to-end details to edges between the node and this peer (token).
--direction DIRECTION — Which edges to show.
--output OUTPUT — Compact table or full edge-by-edge explanations.
--max-in MAX_IN — Max incoming edges
--max-out MAX_OUT — Max outgoing edges
--max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag subgraph`¶

Usage: dpone dag subgraph --from UPSTREAM --to DOWNSTREAM [--all-shortest] [--max-edges MAX_EDGES] [--max-triggers MAX_TRIGGERS] [--with-reasons] [--with-evidence] [--base-path BASE_PATH] [--format {text,json,dot,mermaid}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
Options:
--from UPSTREAM — Upstream task: task_id, selector, #selector, file.yaml#selector
--to DOWNSTREAM — Downstream task: task_id, selector, #selector, file.yaml#selector
--all-shortest — Use the union of all shortest paths (can include more nodes/edges than a single path).
--max-edges MAX_EDGES — Safety limit: max edges to include in subgraph.
--max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons (when reasons are enabled).
--with-reasons — Attach reason kinds to edges.
--with-evidence — Include full reason evidence blocks (text/json).
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--format FORMAT — Output format: text/json for inspection, dot/mermaid for visualization.
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag report`¶

Usage: dpone dag report [--base-path BASE_PATH] [--preset {default,ci,debug,debug-lite}] [--format {md,json,both}] [--out-json OUT_JSON] [--out-md OUT_MD] [--max-edges MAX_EDGES] [--md-max-edges MD_MAX_EDGES] [--include-evidence | --no-evidence] [--max-triggers MAX_TRIGGERS] [--registry-require-field REGISTRY_REQUIRE_FIELD] [--profile PROFILE] [--no-lint] [--fail-on {none,lint_errors,anomalies,both}] [--fail-severity {ERROR,WARNING}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
Options:
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--preset PRESET — Report preset. 'ci' uses safe defaults for CI artifacts (e.g., max-edges=500, no evidence). 'debug' includes evidence and disables truncation by default (max-edges=0, md-max-edges=0). 'debug-lite' includes evidence but keeps safe truncation defaults (max-edges=500, md-max-edges=200). Explicit CLI args override preset values.
--format FORMAT — Output format. 'both' emits Markdown + embedded JSON (or writes to --out-* files).
--out-json OUT_JSON — Write JSON report to this file (optional).
--out-md OUT_MD — Write Markdown report to this file (optional).
--max-edges MAX_EDGES — Safety limit: max edges to include in the report (defaults: preset/2000).
--md-max-edges MD_MAX_EDGES — Max edges to print in Markdown output (defaults: preset/200).
--include-evidence — Include full reasons evidence for edges (report can be large).
--no-evidence — Do not include full reasons evidence for edges (overrides preset).
--max-triggers MAX_TRIGGERS — Max trigger tasks to include for group-to-group reasons evidence (defaults: preset/10).
--registry-require-field REGISTRY_REQUIRE_FIELD — Registry required field for dag report lint (can be repeated). Default: host,type. Use 'none' to disable required-field checks.
--profile PROFILE — Validation profile name for manifest validation (overrides per-manifest validation blocks).
--no-lint — Skip lint section (manifest validation / registry lint / dependency checks).
--fail-on FAIL_ON — Exit with code 1 if the generated report contains issues at or above --fail-severity. lint_errors: any lint issue; anomalies: any anomaly; both: either lint_errors or anomalies; none: always exit 0 (default).
--fail-severity FAIL_SEVERITY — Minimum severity threshold for --fail-on. ERROR (default) fails only on ERROR; WARNING fails on WARNING or ERROR.
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone dag explain-deps`¶

Usage: dpone dag explain-deps --for TASK [--index INDEX] [--no-inherited-groups] [--max-upstreams MAX_UPSTREAMS] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root
Positional arguments:
root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
Options:
--for TASK — Downstream task token to explain: task_id, selector, #selector, file.yaml#selector
--index INDEX — Explain only depends_on item with this index (0-based). Can be repeated.
--no-inherited-groups — Do not include inherited TaskGroup group-to-group dependencies affecting the task.
--max-upstreams MAX_UPSTREAMS — Max upstream tasks to print per dependency.
--max-triggers MAX_TRIGGERS — Max trigger tasks to inspect/print for group-to-group dependencies.
--base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
--format FORMAT — Output format
--registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

`dpone docs`¶

`dpone docs update-airflow-public-contract-reference`¶

Usage: dpone docs update-airflow-public-contract-reference [--check] [--baseline BASELINE] [--doc DOC]
Options:
--check — Only check that the generated reference is current
--baseline BASELINE — Reviewed baseline relative to repository root
--doc DOC — Generated reference page relative to repository root

`dpone docs update-dev-metrics`¶

Usage: dpone docs update-dev-metrics [--check] [--target {all,md,quality}] [--docs-dir DOCS_DIR] [--top TOP]
Options:
--check — Only check that docs are up-to-date (do not rewrite). Exit!=0 if differs.
--target TARGET — Which docs to update/check: all (default) | md | quality
--docs-dir DOCS_DIR — Docs dir in the repository (default: docs)
--top TOP — How many largest modules to show (default: 15)

`dpone docs update-cli-reference`¶

Usage: dpone docs update-cli-reference [--check] [--doc DOC]
Options:
--check — Only check that CLI reference is up-to-date.
--doc DOC — Target markdown file (default: docs/cli-reference.md)

`dpone docs update-gitops-schema-reference`¶

Usage: dpone docs update-gitops-schema-reference [--check] [--doc DOC]
Options:
--check — Only check that the schema reference is up-to-date.
--doc DOC — Target markdown file (default: docs/reference/gitops-schema-catalog.md)

`dpone docs update-manifest-schema-reference`¶

Usage: dpone docs update-manifest-schema-reference [--check] [--doc DOC] [--schema-root SCHEMA_ROOT]
Options:
--check — Only check that the reference is up-to-date.
--doc DOC — Target markdown file (default: docs/reference/manifest-schemas.md)
--schema-root SCHEMA_ROOT — Canonical schema directory (default: src/dpone/schema)

`dpone docs update-deprecation-roadmap`¶

Usage: dpone docs update-deprecation-roadmap [--check] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--top-sources TOP_SOURCES]
Options:
--check — Only check that the roadmap doc is up-to-date.
--registry REGISTRY — Compatibility registry yaml file
--doc DOC — Target markdown file
--package PACKAGE — Package root to scan for internal imports
--top-sources TOP_SOURCES — How many canonical source modules to show per blocked entry

`dpone docs update-shim-removal-plan`¶

Usage: dpone docs update-shim-removal-plan [--check] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--batch BATCH]
Options:
--check — Only check that the shim removal plan is up-to-date.
--registry REGISTRY — Compatibility registry path
--doc DOC — Target markdown file
--package PACKAGE — Package directory (default: src/dpone)
--batch BATCH — Removal batch to render (default: cleanup-release-1)

`dpone docs check-airflow-public-contracts`¶

Usage: dpone docs check-airflow-public-contracts [--format {text,json}] [--baseline BASELINE] [--provider-root PROVIDER_ROOT]
Options:
--format FORMAT
--baseline BASELINE — Reviewed baseline relative to repository root
--provider-root PROVIDER_ROOT — Formal provider facade root relative to repository root

`dpone docs check-docs`¶

Usage: dpone docs check-docs [--format {text,json}] [--docs-dir DOCS_DIR] [--no-root-readme]
Options:
--format FORMAT — Output format: text (default) or json
--docs-dir DOCS_DIR — Docs directory relative to repo root (default: docs)
--no-root-readme — Do not include top-level README.md in docs checks

`dpone docs check-generated-references`¶

Usage: dpone docs check-generated-references [--format {text,json}] [--cli-doc CLI_DOC] [--gitops-schema-doc GITOPS_SCHEMA_DOC] [--manifest-schema-doc MANIFEST_SCHEMA_DOC] [--manifest-schema-root MANIFEST_SCHEMA_ROOT]
Options:
--format FORMAT
--cli-doc CLI_DOC — CLI reference markdown file (default: docs/cli-reference.md)
--gitops-schema-doc GITOPS_SCHEMA_DOC — GitOps schema catalog markdown file (default: docs/reference/gitops-schema-catalog.md)
--manifest-schema-doc MANIFEST_SCHEMA_DOC — Manifest schema reference markdown file (default: docs/reference/manifest-schemas.md)
--manifest-schema-root MANIFEST_SCHEMA_ROOT — Canonical manifest schema directory (default: src/dpone/schema)

`dpone docs check-compatibility`¶

Usage: dpone docs check-compatibility [--format {text,json}] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--write-doc]
Options:
--format FORMAT — Output format: text (default) or json
--registry REGISTRY — Compatibility registry path relative to repo root
--doc DOC — Compatibility markdown page to validate/update
--package PACKAGE — Package directory relative to repo root (default: src/dpone)
--write-doc — Update generated compatibility matrix block inside docs/compatibility.md

`dpone docs check-import-rules`¶

Usage: dpone docs check-import-rules [--format {text,json}] [--package PACKAGE]
Options:
--format FORMAT — Output format: text (default) or json
--package PACKAGE — Package directory relative to repo root (default: src/dpone)

`dpone docs check-layer-metrics`¶

Usage: dpone docs check-layer-metrics [--format {text,json}] [--package PACKAGE] [--top TOP] [--exclude-layer EXCLUDE_LAYER] [--baseline BASELINE | --no-baseline] [--write-baseline] [--min-intra-layer-ratio MIN_INTRA_LAYER_RATIO] [--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO] [--max-top-cross-layer-flow MAX_TOP_CROSS_LAYER_FLOW] [--allowed-ratio-regression ALLOWED_RATIO_REGRESSION] [--allowed-flow-regression ALLOWED_FLOW_REGRESSION]
Options:
--format FORMAT — Output format: text (default) or json
--package PACKAGE — Package directory relative to repo root (default: src/dpone)
--top TOP — How many top cross flows to retain in the computed snapshot (default: 15)
--exclude-layer EXCLUDE_LAYER — Layer to exclude from the coarse architecture view (repeatable, default: dpone.compat)
--baseline BASELINE — Baseline JSON path relative to repo root (default: docs/layer_metrics_baseline.json)
--no-baseline — Do not compare against a baseline JSON snapshot
--write-baseline — Write current layer metrics snapshot to --baseline and exit 0
--min-intra-layer-ratio MIN_INTRA_LAYER_RATIO — Fail if current intra-layer ratio is below this threshold (default: 0.55)
--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO — Fail if current cross-layer ratio is above this threshold (default: 0.45)
--max-top-cross-layer-flow MAX_TOP_CROSS_LAYER_FLOW — Optional absolute cap for the largest layer->layer flow
--allowed-ratio-regression ALLOWED_RATIO_REGRESSION — Allowed regression vs baseline for ratio metrics (default: 0.02)
--allowed-flow-regression ALLOWED_FLOW_REGRESSION — Allowed regression vs baseline for largest cross-layer flow (default: 5)

`dpone docs check-architecture-fitness`¶

Usage: dpone docs check-architecture-fitness [--format {text,json}] [--package PACKAGE] [--top TOP] [--target-avg-clustering TARGET_AVG_CLUSTERING] [--max-avg-clustering MAX_AVG_CLUSTERING] [--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO] [--target-module-ce TARGET_MODULE_CE] [--max-module-ce MAX_MODULE_CE] [--max-class-methods MAX_CLASS_METHODS] [--max-class-loc MAX_CLASS_LOC] [--fail-on-class-warnings]
Options:
--format FORMAT
--package PACKAGE
--top TOP
--target-avg-clustering TARGET_AVG_CLUSTERING
--max-avg-clustering MAX_AVG_CLUSTERING
--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO
--target-module-ce TARGET_MODULE_CE
--max-module-ce MAX_MODULE_CE
--max-class-methods MAX_CLASS_METHODS
--max-class-loc MAX_CLASS_LOC
--fail-on-class-warnings — Treat high-responsibility class findings as errors instead of warnings.

`dpone docs check-module-size`¶

Usage: dpone docs check-module-size [--format {text,json}] [--package PACKAGE] [--baseline BASELINE | --no-baseline] [--write-baseline] [--warn-lines WARN_LINES] [--max-lines MAX_LINES] [--warn-sloc WARN_SLOC] [--max-sloc MAX_SLOC]
Options:
--format FORMAT
--package PACKAGE — Python directory to scan (default: src/dpone)
--baseline BASELINE
--no-baseline
--write-baseline
--warn-lines WARN_LINES
--max-lines MAX_LINES
--warn-sloc WARN_SLOC
--max-sloc MAX_SLOC

`dpone docs check-removal-readiness`¶

Usage: dpone docs check-removal-readiness [--format {text,json}] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--batch BATCH] [--write-doc]
Options:
--format FORMAT — Output format
--registry REGISTRY — Compatibility registry path
--doc DOC — Shim removal plan markdown path
--package PACKAGE — Package directory (default: src/dpone)
--batch BATCH — Removal batch to validate (default: cleanup-release-1)
--write-doc — Update docs/shim-removal-plan.md before validation

`dpone dbt`¶

`dpone dbt check`¶

Usage: dpone dbt check --manifest MANIFEST [--profiles PROFILES] [--format {text,json}] [--allow-missing-contracts]
Options:
--manifest MANIFEST — Path to dbt target/manifest.json
--profiles PROFILES — Trusted dpone dbt publish profile registry
--format FORMAT
--allow-missing-contracts — Dev-only contract relaxation

`dpone dbt explain`¶

Usage: dpone dbt explain --manifest MANIFEST [--profiles PROFILES] [--format {text,json}] --model MODEL [--allow-missing-contracts]
Options:
--manifest MANIFEST — Path to dbt target/manifest.json
--profiles PROFILES — Trusted dpone dbt publish profile registry
--format FORMAT
--model MODEL — dbt model name, alias, or unique_id
--allow-missing-contracts — Dev-only contract relaxation

`dpone dbt compile`¶

Usage: dpone dbt compile --manifest MANIFEST [--profiles PROFILES] [--format {text,json}] [--output-dir OUTPUT_DIR] [--allow-missing-contracts]
Options:
--manifest MANIFEST — Path to dbt target/manifest.json
--profiles PROFILES — Trusted dpone dbt publish profile registry
--format FORMAT
--output-dir OUTPUT_DIR — Generated artifact root
--allow-missing-contracts — Dev-only contract relaxation

Kafka manifests¶

Kafka uses the same manifest commands as other backends. Use source.type: kafka for bounded batch topic reads and sink.type: kafka for producing rows into topics. See Kafka batch source/sink for options and examples.

Live replay backend mode¶

dpone resync and dpone resume are safe artifact-only commands by default. Add --live-backend together with --yes to execute through runtime replay backends built by RuntimeReplayBackendFactory.

MSSQL/Postgres/ClickHouse/BigQuery example:

dpone resync \
  --run-id 01JREPLAY000000000000000101 \
  --source-type postgres \
  --sink-type mssql \
  --strategy incremental_merge \
  --partition 2026-06-05 \
  --yes \
  --live-backend \
  --connection-type env \
  --connection-id mssql_dwh \
  --target-schema dbo \
  --target-table orders \
  --staging-schema staging

Kafka example:

dpone resume 01JREPLAY000000000000000102 \
  --from-stage finalize \
  --source-type postgres \
  --sink-type kafka \
  --strategy incremental_merge \
  --yes \
  --live-backend \
  --connection-type params \
  --connection-id '{"bootstrap_servers":"localhost:9092"}' \
  --target-table dwh.orders

Live replay flags:

Flag	Purpose
`--live-backend`	Opt into runtime SQL/Kafka backend execution. Without `--yes`, no live backend is built.
`--connection-id`	Target sink connection id or params JSON. Required with `--live-backend`.
`--connection-type`	Credential provider: `env`, `vault`, `airflow`, or `params`.
`--target-schema`	Target schema/database for DB sinks. Defaults to `public`.
`--target-table`	Target table for DB sinks or Kafka topic for Kafka. Required with `--live-backend`.
`--staging-schema`	Staging schema/database for DB sinks. Defaults to `staging`.
`--mount-point`	Vault mount point when `--connection-type vault` is used.
`--connection-path`	Vault path or provider-specific credential path.

`dpone strategy certification-bundle`¶

Aggregate strategy certification evidence into one JSON/Markdown bundle.

dpone strategy certification-bundle \
  --bundle-id oss_rc_2026_06_05 \
  --output-dir test_artifacts/strategies/certification_bundle \
  --replay-evidence test_artifacts/replay_integration/resync_01_evidence.json \
  --matrix-artifact test_artifacts/integration_matrix/certification_report.json \
  --connector-artifact test_artifacts/connectors/connector_certification.json \
  --benchmark-artifact test_artifacts/benchmarks/benchmark_baseline.json \
  --native-transfer-evidence test_artifacts/native-transfer/postgres-mssql/evidence/01J00000000000000000000000/evidence_index.json \
  --docs-link docs/testing/replay-integration.md \
  --format json

Flag	Purpose
`--bundle-id`	Stable release, certification, or audit id. Required.
`--output-dir`	Directory for `strategy_certification_bundle.json` and `.md`.
`--replay-evidence`	Replay evidence JSON. Can be repeated.
`--matrix-artifact`	Source -> sink matrix or certification report JSON. Can be repeated.
`--connector-artifact`	Connector certification JSON. Can be repeated.
`--benchmark-artifact`	Benchmark baseline/regression JSON. Can be repeated.
`--native-transfer-evidence`	Native transfer evidence index JSON from `dpone strategy native-transfer-evidence`. Can be repeated.
`--docs-link`	Relevant runbook or evidence docs link. Can be repeated.

`dpone ops release-summary`¶

Build the final replay + matrix + connector release go/no-go report.

dpone ops release-summary \
  --output-dir test_artifacts/certification/release-summary \
  --release-id vX.Y.Z \
  --replay-chain-dir test_artifacts/replay-evidence-chain \
  --matrix-suite test_artifacts/source-sink-certification-suite/certification_suite.json \
  --matrix-chain-dir test_artifacts/source-sink-evidence-chain \
  --connector-suite test_artifacts/connector-certification-suite/certification_suite.json \
  --connector-chain-dir test_artifacts/connector-evidence-chain \
  --format json

Required inputs:

--release-id: release, RC, or promotion identifier.
--replay-chain-dir: directory containing evidence_chain_index.json and replay chain entries.
--matrix-suite: source -> sink certification_suite.json.
--matrix-chain-dir: source -> sink evidence chain directory.
--connector-suite: connector certification_suite.json.
--connector-chain-dir: connector evidence chain directory.

Exit code 0 means all chains verify and all suites pass. Exit code 1 means the release remains blocked.

`dpone ops certification-automation-plan`¶

Render the full source -> sink certification automation plan and required artifacts.

dpone ops certification-automation-plan \
  --output-dir test_artifacts/full_certification/automation \
  --profile mock_contract \
  --row-count 10000 \
  --format json

Options:

--output-dir: where certification_automation_plan.json and .md are written.
--profile: mock_contract, mock_local, or vendor_live.
--row-count: mock matrix row count, capped by the service at 100000.
--format: md or json.

Use this before changing .github/workflows/full-certification.yml so command order, required artifacts, docs, and runbooks remain aligned.

`dpone normalize`¶

Preview and infer nested normalization output from local row samples. This is a plan-only/self-service command: it does not connect to source systems and does not write target data.

`dpone normalize preview`¶

dpone normalize preview \
  --sample examples/nested/orders.jsonl \
  --root-table orders \
  --config examples/nested/normalization.yml \
  --format md \
  --output .dpone/normalization-preview.md

Options:

Option	Description
`--sample`	Local JSON, JSONL/NDJSON, CSV, or TSV sample file.
`--root-table`	Root normalized table name.
`--config`	Optional normalization config JSON/YAML file.
`--nested-level`	Override `normalization.nested.nested_level`.
`--limit`	Maximum sample rows to read; default `1000`.
`--format`	`text`, `json`, or `md`; default `text`.
`--output`	Optional output file path.

`dpone normalize infer`¶

dpone normalize infer \
  --sample examples/nested/orders.jsonl \
  --root-table orders \
  --nested-level 3 \
  --format json

Use infer when the output will be stored as GitOps evidence or reviewed in a pull request. See Nested normalization for policies, raw landing, guardrails, hierarchy contracts, and reverse hierarchy checks.

`dpone normalize lint`¶

dpone normalize lint \
  --root-table orders \
  --config examples/nested/normalization.yml \
  --format md \
  --output .dpone/nested-lint.md \
  --fail-on-error

Checks nested configuration for table collisions, missing explosion guardrails, and rollout risks before a manifest is enabled in production.

`dpone normalize certify`¶

dpone normalize certify \
  --row-count 1000 \
  --output-dir test_artifacts/nested/latest

Writes JSON and Markdown certification evidence covering lint, spill-to-disk, reverse readback, child finalizers, snapshot stores, schema-evolution contract, native fast-path execution contract, live harness contract, quarantine and raw landing.

`dpone normalize benchmark`¶

dpone normalize benchmark \
  --row-count 10000 \
  --max-rows 100000 \
  --output-dir test_artifacts/nested/benchmark-latest

Runs a deterministic local benchmark and writes throughput/row-count evidence.

`dpone normalize stress`¶

dpone normalize stress \
  --row-count 100000 \
  --max-rows 100000 \
  --spill-output-format json_each_row \
  --output-dir test_artifacts/nested/stress-latest

Runs skewed nested payload certification with sparse nested objects and child array sizes such as 0, 1, 10 and 1000 rows per parent.

CLI reference¶

dpone doctor¶

dpone doctor¶

dpone init¶

dpone init¶

dpone init project¶

dpone init domain¶

dpone init pipeline¶

dpone plan¶

dpone plan¶

dpone run¶

dpone run¶

dpone test¶

dpone test¶

dpone resync¶

dpone resync¶

dpone resume¶

dpone resume¶

dpone run-report¶

dpone run-report¶

dpone studio¶

dpone studio¶

dpone certify¶

dpone certify¶

dpone certify routes¶

dpone certify self-service¶

dpone certify route-capabilities¶

dpone schema-plan¶

dpone schema-plan¶

dpone recipe¶

dpone recipe list¶

dpone recipe show¶

dpone recipe pin¶

dpone recipe validate¶

dpone check¶

dpone check¶

dpone fix¶

dpone fix¶

dpone cdc-plan¶

dpone cdc-plan¶

dpone backfill¶

dpone backfill plan¶

dpone backfill run¶

dpone backfill resume¶

dpone backfill status¶

dpone backfill retry-failed¶

dpone backfill cancel¶

dpone backfill doctor¶

dpone state¶

dpone state inspect¶

dpone state reset¶

dpone state export¶

dpone state replay-from¶

dpone state rewind¶

dpone state compare¶

dpone normalize¶

dpone normalize preview¶

dpone normalize infer¶

dpone normalize lint¶

dpone normalize certify¶

dpone normalize benchmark¶

dpone normalize stress¶

dpone connectors¶

dpone connectors list¶

dpone connectors certify¶

dpone connectors scaffold¶

dpone ops¶

dpone ops artifact-index¶

dpone ops certification-run¶

dpone ops certification-history¶

dpone ops connector-badges¶

dpone ops contract-check¶

dpone ops quarantine-export¶

dpone ops quarantine-replay¶

dpone ops package-start¶

dpone ops package-commit¶

dpone ops rollback-plan¶

dpone ops rollback-apply¶

dpone ops rollback-execute¶

dpone ops marketplace¶

`dpone doctor`¶

`dpone doctor`¶

`dpone init`¶

`dpone init`¶

`dpone init project`¶

`dpone init domain`¶

`dpone init pipeline`¶

`dpone plan`¶

`dpone plan`¶

`dpone run`¶

`dpone run`¶

`dpone test`¶

`dpone test`¶

`dpone resync`¶

`dpone resync`¶

`dpone resume`¶

`dpone resume`¶

`dpone run-report`¶

`dpone run-report`¶

`dpone studio`¶

`dpone studio`¶

`dpone certify`¶

`dpone certify`¶

`dpone certify routes`¶

`dpone certify self-service`¶

`dpone certify route-capabilities`¶

`dpone schema-plan`¶

`dpone schema-plan`¶

`dpone recipe`¶

`dpone recipe list`¶

`dpone recipe show`¶

`dpone recipe pin`¶

`dpone recipe validate`¶

`dpone check`¶

`dpone check`¶

`dpone fix`¶

`dpone fix`¶

`dpone cdc-plan`¶

`dpone cdc-plan`¶

`dpone backfill`¶

`dpone backfill plan`¶

`dpone backfill run`¶

`dpone backfill resume`¶

`dpone backfill status`¶

`dpone backfill retry-failed`¶

`dpone backfill cancel`¶

`dpone backfill doctor`¶

`dpone state`¶

`dpone state inspect`¶

`dpone state reset`¶

`dpone state export`¶

`dpone state replay-from`¶

`dpone state rewind`¶

`dpone state compare`¶

`dpone normalize`¶

`dpone normalize preview`¶

`dpone normalize infer`¶

`dpone normalize lint`¶

`dpone normalize certify`¶

`dpone normalize benchmark`¶

`dpone normalize stress`¶

`dpone connectors`¶

`dpone connectors list`¶

`dpone connectors certify`¶

`dpone connectors scaffold`¶

`dpone ops`¶

`dpone ops artifact-index`¶

`dpone ops certification-run`¶

`dpone ops certification-history`¶

`dpone ops connector-badges`¶

`dpone ops contract-check`¶

`dpone ops quarantine-export`¶

`dpone ops quarantine-replay`¶

`dpone ops package-start`¶

`dpone ops package-commit`¶

`dpone ops rollback-plan`¶

`dpone ops rollback-apply`¶

`dpone ops rollback-execute`¶

`dpone ops marketplace`¶

`dpone ops evidence-bundle`¶