Workflow

From config rendering to remote scoring in four stages.

1

Render

Analysts author Jinja-enriched YAML configs. `hcc-cli render` materializes them into manifests with deterministic hashes for change tracking.

2

Extract

JDBC streams data warehouse results—for example Snowflake—directly into Parquet files stored under run-specific directories.

3

Score

Payloads are uploaded to the remote Node scoring service. The service runs inside container infrastructure and streams risk scores back for each run.

4

Publish

Output Parquet files or score results can be written back to Snowflake, delivered to downstream analytics tooling, or archived with manifest metadata for audit.

CLI Commands

`hcc-cli render`

Render manifests with dry-run support and JSON/YAML output formats.

`hcc-cli score`

Materialize runs, upload payloads, and optionally trigger remote scoring.

`hcc-cli emit-dag`

Generate Airflow or Prefect scaffolds to operationalize manifests.

`hcc-cli validate`

Planned command for schema linting and connectivity diagnostics.

Power User Controls