zendt 0.1.0__tar.gz

zendt-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 SPLOR/SEPLAG/MG
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

zendt-0.1.0/PKG-INFO

@@ -0,0 +1,200 @@
+Metadata-Version: 2.4
+Name: zendt
+Version: 0.1.0
+Summary: CLI for applying business rules built in the GoRules tool model to data tables.
+License-Expression: MIT
+License-File: LICENSE
+Author: Laura Dilly
+Author-email: laura.dgm06@gmail.com
+Requires-Python: >=3.13,<4.0
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Dist: openpyxl (>=3.1.5,<4.0.0)
+Requires-Dist: pandas (>=3.0.5,<4.0.0)
+Requires-Dist: prompt-toolkit (>=3.0.0,<4)
+Requires-Dist: python-dotenv (>=1.2.2,<2)
+Requires-Dist: pyyaml (>=6.0.0,<7.0.0)
+Requires-Dist: requests (>=2.34.2,<3)
+Requires-Dist: typer (>=0.15.0)
+Requires-Dist: zen-engine (>=2.0.2,<3.0.0)
+Description-Content-Type: text/markdown
+
+# zendt [Zen Engine for Data Tables]
+
+![Coverage](coverage.svg)
+
+
+Apply [GoRules](https://gorules.io/) business rules to a table from the terminal. Rules are JSON graphs in the [JDM standard](https://docs.gorules.io/developers/jdm/standard). Tables are CSV, gzip-compressed CSV, Excel (`.xlsx`), or JSON.
+
+```bash
+pip install zendt
+zendt apply student_discount -s ./rules -i customers.csv -o customers-out.csv
+```
+
+The command keeps every input column and appends the columns each rule creates. Each rule sees the original rows, not columns produced by an earlier rule in the same command.
+
+Python 3.13 or newer is required.
+
+## Commands
+
+```bash
+zendt list -s ./rules
+zendt list -s source_one -f discount
+zendt apply student_discount age_discount -s ./rules -i customers.csv -o customers-out.csv
+zendt apply student_discount -s https://github.com/user/rules/tree/main/rules -a GH_TOKEN -v 1.2.1 -i customers.csv
+zendt flow financedata -i customers.csv -o customers-out.csv --printhead
+zendt config --create
+zendt config --edit
+```
+
+| Command | What it does |
+| --- | --- |
+| `list` | Print the rule names in a source. Does not run them. |
+| `apply` | Run one or more rules on a table. |
+| `flow` | Run a named pipeline from `zendt.json`. |
+| `config --create` | Write `zendt.json` by answering prompts. |
+| `config --edit` | Edit that file by answering prompts. |
+
+
+### Flags
+
+| Flag | Short | Use |
+| --- | --- | --- |
+| `--source` | `-s` | GitHub URL, local file or directory, or a source id from the config. `list` and `apply`. |
+| `--find` | `-f` | On `list`, keep names that contain this text. |
+| `--version` | `-v` | Git tag, branch, or other ref. `list` and `apply`. |
+| `--authentication` | `-a` | Name of the environment variable that holds a GitHub token. Not the token. |
+| `--input` | `-i` | Input file. Omitted means stdin. |
+| `--output` | `-o` | Output file. Omitted writes CSV to stdout only when stdout is a pipe or a redirect. |
+| `--printhead` | `-ph` | Print the first five result rows. On `apply` and `flow` this is not help; use `--help`. |
+| `--create` | `-c` | Create `zendt.json`. |
+| `--edit` | `-e` | Edit `zendt.json`. |
+
+## A local folder of rules
+
+```bash
+zendt list -s ./rules
+zendt apply student_discount -s ./rules -i customers.csv -o customers-out.csv
+```
+
+`student_discount` is the file `rules/student_discount.json`. Nested files are listed by their stem as well. A decision node inside a graph calls another file by its path relative to the folder, without `.json` (`discounts/student_discount`).
+
+`list` prints one name per line. A file named `zendt.json` inside the rules folder is skipped.
+
+## GitHub
+
+```bash
+export GH_TOKEN=github_pat_...
+zendt apply student_discount \
+  -s https://github.com/user/rules/tree/main/rules \
+  -a GH_TOKEN \
+  -v 1.2.1 \
+  -i customers.csv \
+  -o customers-out.csv
+```
+
+The URL must be GitHub: a repository, a `tree` URL of the rules folder, a `blob` URL of one JSON file, or a `raw.githubusercontent.com` URL. Other hosts are rejected.
+
+`-v` is the git ref sent to GitHub. If you omit it, the ref in the URL is used, or `HEAD` when the URL has none. zendt does not look up the latest tag. `-a` is the name of the environment variable that stores the token for a private repository. You can also put the token in a `.env` file in the current directory. Values already set in the environment are left as they are.
+
+
+## Configuration and flows
+
+When you omit `--source`, zendt looks for `zendt.json` in the current directory, then the `config` (or `CONFIG`) environment variable, which stores the path to a config file (json or yaml), then `sources` (or `SOURCES`) env variable. `sources` is one source object or a JSON array of sources. Flows, if any, go in env variable `flows` (or `FLOWS`).
+
+```json
+{
+  "sources": [
+    {
+      "id": "source_one",
+      "source": "https://github.com/user/rules_repo",
+      "authentication": "GH_TOKEN",
+      "version": "1.2.1"
+    },
+    {
+      "id": "source_two",
+      "source": "rules"
+    }
+  ],
+  "flows": [
+    {
+      "id": "financedata",
+      "description": "finance team flow for discount purposes",
+      "input": "data-raw/finance.csv.gz",
+      "rules": ["student_discount", "source_two/age_discount"],
+      "output": "data/finance.csv"
+    }
+  ]
+}
+```
+
+```bash
+zendt list
+zendt list -s source_one
+zendt apply source_one/student_discount -i customers.csv -o customers-out.csv
+zendt flow financedata
+zendt flow financedata -i other.csv -o other-out.csv
+```
+
+`id` cannot contain `/`. `authentication` is an environment-variable name. `version` is a git ref. `description` is for self organization; the command does not print it.
+
+`zendt flow financedata` uses every source in the file, with each source's own token variable and ref. It does not take `-s`, `-v`, or `-a`. The flow can store an input and an output which are overriden by `-i` and `-o` flags if provided for that run.
+
+The same file stem may exist in two sources. The short name works only when it is unique. Otherwise the command refuses and tells you to use `source_id/name`. `list` prints those qualified names. Two files with the same stem inside one source are an error, even in different subfolders.
+
+JSON and YAML files may hold other project keys. zendt reads `sources` and `flows` only. Those keys may also sit under `zendt_config`. Point `config` env variable at that file.
+
+`zendt config --create` and `zendt config --edit` always edit `zendt.json` in the current directory in a interactive way through the terminal. Use that to guide you through creation or editing of the config file. 
+
+## Input and output
+
+Accepted suffixes: `.csv`, `.csv.gz`, `.json`, `.xlsx`.
+
+CSV delimiters are detected from the header and limited to comma and semicolon. The same delimiter is used when the result is written as CSV. JSON input is one object (one row) or an array of objects. `.xlsx` uses openpyxl.
+
+```bash
+cat customers.csv | zendt apply student_discount -s ./rules > customers-out.csv
+```
+
+A terminal with no `--input` fails instead of waiting for typed rows. An empty pipe fails with `Stdin is empty.` On a terminal, omitting `--output` writes nothing; pass `--printhead` to see the first five rows, or pass `--output` / redirect stdout to get the table. In a pipe, `--printhead` prints the preview on stderr so the CSV on stdout stays intact.
+
+zendt does not validate columns. Enforce the shape in the pipeline (before running zendt rules application) or with an input schema inside the JDM graph.
+
+## How rules are applied
+
+Named rules run in order, each on the original table. New fields are appended. Fields the rule returns that already exist on the input stay as they were. If two rules in one command create the same new column, the command stops. A row the engine rejects stops the command and names the rule and the 1-based row number.
+
+Decision nodes load the called graph from the same source. The key is the file's path relative to the source, without `.json`. Only those graphs are downloaded and compiled.
+
+Below 10,000 rows the command evaluates in the current process, in batches of 20,000. At 10,000 rows or more it uses up to eight processes, and never more than the machine's cores. The full table is still loaded in the parent process.
+
+## Errors
+
+| Exit | When |
+| --- | --- |
+| 0 | The command finished. |
+| 1 | Config, source, authentication, input, missing rule, ambiguous name, invalid graph, or engine failure. The reason is on stderr. |
+| 2 | Usage error: unknown flag, missing argument, or `zendt` with no command. |
+
+Common cases: no config and no `--source`; `--version` on a local folder; a rule name that is not in the source; a name that exists in two sources; GitHub 401 or 403; a file that is not a JDM object (`nodes` and `edges`).
+
+## Documentation
+
+The `docs/` directory is the full reference (commands, configuration, rule names, input and output, evaluation, errors). It is a [Zensical](https://zensical.org/) site. From a checkout:
+
+```bash
+zensical serve
+```
+
+## Development
+
+This repository uses Poetry. The dev group includes pytest.
+
+```bash
+poetry install
+poetry run pytest
+```
+
+The tests live in `tests/` and cover the CLI, config editor, catalog, GitHub listing, input and output, and rule evaluation.
+

zendt-0.1.0/README.md

@@ -0,0 +1,177 @@
+# zendt [Zen Engine for Data Tables]
+
+![Coverage](coverage.svg)
+
+
+Apply [GoRules](https://gorules.io/) business rules to a table from the terminal. Rules are JSON graphs in the [JDM standard](https://docs.gorules.io/developers/jdm/standard). Tables are CSV, gzip-compressed CSV, Excel (`.xlsx`), or JSON.
+
+```bash
+pip install zendt
+zendt apply student_discount -s ./rules -i customers.csv -o customers-out.csv
+```
+
+The command keeps every input column and appends the columns each rule creates. Each rule sees the original rows, not columns produced by an earlier rule in the same command.
+
+Python 3.13 or newer is required.
+
+## Commands
+
+```bash
+zendt list -s ./rules
+zendt list -s source_one -f discount
+zendt apply student_discount age_discount -s ./rules -i customers.csv -o customers-out.csv
+zendt apply student_discount -s https://github.com/user/rules/tree/main/rules -a GH_TOKEN -v 1.2.1 -i customers.csv
+zendt flow financedata -i customers.csv -o customers-out.csv --printhead
+zendt config --create
+zendt config --edit
+```
+
+| Command | What it does |
+| --- | --- |
+| `list` | Print the rule names in a source. Does not run them. |
+| `apply` | Run one or more rules on a table. |
+| `flow` | Run a named pipeline from `zendt.json`. |
+| `config --create` | Write `zendt.json` by answering prompts. |
+| `config --edit` | Edit that file by answering prompts. |
+
+
+### Flags
+
+| Flag | Short | Use |
+| --- | --- | --- |
+| `--source` | `-s` | GitHub URL, local file or directory, or a source id from the config. `list` and `apply`. |
+| `--find` | `-f` | On `list`, keep names that contain this text. |
+| `--version` | `-v` | Git tag, branch, or other ref. `list` and `apply`. |
+| `--authentication` | `-a` | Name of the environment variable that holds a GitHub token. Not the token. |
+| `--input` | `-i` | Input file. Omitted means stdin. |
+| `--output` | `-o` | Output file. Omitted writes CSV to stdout only when stdout is a pipe or a redirect. |
+| `--printhead` | `-ph` | Print the first five result rows. On `apply` and `flow` this is not help; use `--help`. |
+| `--create` | `-c` | Create `zendt.json`. |
+| `--edit` | `-e` | Edit `zendt.json`. |
+
+## A local folder of rules
+
+```bash
+zendt list -s ./rules
+zendt apply student_discount -s ./rules -i customers.csv -o customers-out.csv
+```
+
+`student_discount` is the file `rules/student_discount.json`. Nested files are listed by their stem as well. A decision node inside a graph calls another file by its path relative to the folder, without `.json` (`discounts/student_discount`).
+
+`list` prints one name per line. A file named `zendt.json` inside the rules folder is skipped.
+
+## GitHub
+
+```bash
+export GH_TOKEN=github_pat_...
+zendt apply student_discount \
+  -s https://github.com/user/rules/tree/main/rules \
+  -a GH_TOKEN \
+  -v 1.2.1 \
+  -i customers.csv \
+  -o customers-out.csv
+```
+
+The URL must be GitHub: a repository, a `tree` URL of the rules folder, a `blob` URL of one JSON file, or a `raw.githubusercontent.com` URL. Other hosts are rejected.
+
+`-v` is the git ref sent to GitHub. If you omit it, the ref in the URL is used, or `HEAD` when the URL has none. zendt does not look up the latest tag. `-a` is the name of the environment variable that stores the token for a private repository. You can also put the token in a `.env` file in the current directory. Values already set in the environment are left as they are.
+
+
+## Configuration and flows
+
+When you omit `--source`, zendt looks for `zendt.json` in the current directory, then the `config` (or `CONFIG`) environment variable, which stores the path to a config file (json or yaml), then `sources` (or `SOURCES`) env variable. `sources` is one source object or a JSON array of sources. Flows, if any, go in env variable `flows` (or `FLOWS`).
+
+```json
+{
+  "sources": [
+    {
+      "id": "source_one",
+      "source": "https://github.com/user/rules_repo",
+      "authentication": "GH_TOKEN",
+      "version": "1.2.1"
+    },
+    {
+      "id": "source_two",
+      "source": "rules"
+    }
+  ],
+  "flows": [
+    {
+      "id": "financedata",
+      "description": "finance team flow for discount purposes",
+      "input": "data-raw/finance.csv.gz",
+      "rules": ["student_discount", "source_two/age_discount"],
+      "output": "data/finance.csv"
+    }
+  ]
+}
+```
+
+```bash
+zendt list
+zendt list -s source_one
+zendt apply source_one/student_discount -i customers.csv -o customers-out.csv
+zendt flow financedata
+zendt flow financedata -i other.csv -o other-out.csv
+```
+
+`id` cannot contain `/`. `authentication` is an environment-variable name. `version` is a git ref. `description` is for self organization; the command does not print it.
+
+`zendt flow financedata` uses every source in the file, with each source's own token variable and ref. It does not take `-s`, `-v`, or `-a`. The flow can store an input and an output which are overriden by `-i` and `-o` flags if provided for that run.
+
+The same file stem may exist in two sources. The short name works only when it is unique. Otherwise the command refuses and tells you to use `source_id/name`. `list` prints those qualified names. Two files with the same stem inside one source are an error, even in different subfolders.
+
+JSON and YAML files may hold other project keys. zendt reads `sources` and `flows` only. Those keys may also sit under `zendt_config`. Point `config` env variable at that file.
+
+`zendt config --create` and `zendt config --edit` always edit `zendt.json` in the current directory in a interactive way through the terminal. Use that to guide you through creation or editing of the config file. 
+
+## Input and output
+
+Accepted suffixes: `.csv`, `.csv.gz`, `.json`, `.xlsx`.
+
+CSV delimiters are detected from the header and limited to comma and semicolon. The same delimiter is used when the result is written as CSV. JSON input is one object (one row) or an array of objects. `.xlsx` uses openpyxl.
+
+```bash
+cat customers.csv | zendt apply student_discount -s ./rules > customers-out.csv
+```
+
+A terminal with no `--input` fails instead of waiting for typed rows. An empty pipe fails with `Stdin is empty.` On a terminal, omitting `--output` writes nothing; pass `--printhead` to see the first five rows, or pass `--output` / redirect stdout to get the table. In a pipe, `--printhead` prints the preview on stderr so the CSV on stdout stays intact.
+
+zendt does not validate columns. Enforce the shape in the pipeline (before running zendt rules application) or with an input schema inside the JDM graph.
+
+## How rules are applied
+
+Named rules run in order, each on the original table. New fields are appended. Fields the rule returns that already exist on the input stay as they were. If two rules in one command create the same new column, the command stops. A row the engine rejects stops the command and names the rule and the 1-based row number.
+
+Decision nodes load the called graph from the same source. The key is the file's path relative to the source, without `.json`. Only those graphs are downloaded and compiled.
+
+Below 10,000 rows the command evaluates in the current process, in batches of 20,000. At 10,000 rows or more it uses up to eight processes, and never more than the machine's cores. The full table is still loaded in the parent process.
+
+## Errors
+
+| Exit | When |
+| --- | --- |
+| 0 | The command finished. |
+| 1 | Config, source, authentication, input, missing rule, ambiguous name, invalid graph, or engine failure. The reason is on stderr. |
+| 2 | Usage error: unknown flag, missing argument, or `zendt` with no command. |
+
+Common cases: no config and no `--source`; `--version` on a local folder; a rule name that is not in the source; a name that exists in two sources; GitHub 401 or 403; a file that is not a JDM object (`nodes` and `edges`).
+
+## Documentation
+
+The `docs/` directory is the full reference (commands, configuration, rule names, input and output, evaluation, errors). It is a [Zensical](https://zensical.org/) site. From a checkout:
+
+```bash
+zensical serve
+```
+
+## Development
+
+This repository uses Poetry. The dev group includes pytest.
+
+```bash
+poetry install
+poetry run pytest
+```
+
+The tests live in `tests/` and cover the CLI, config editor, catalog, GitHub listing, input and output, and rule evaluation.

zendt-0.1.0/pyproject.toml

@@ -0,0 +1,76 @@
+[project]
+name = "zendt"
+version = "0.1.0"
+license = "MIT"
+description = "CLI for applying business rules built in the GoRules tool model to data tables."
+authors = [
+    {name = "Laura Dilly", email = "laura.dgm06@gmail.com"},
+    {name = "Gabriel Dornas", email = "gabrielbdornas@gmail.com"}
+]
+readme = "README.md"
+requires-python = ">=3.13,<4.0"
+dependencies = [
+    "requests>=2.34.2,<3",
+    "python-dotenv>=1.2.2,<2",
+    "prompt-toolkit>=3.0.0,<4",
+    "typer>=0.15.0",
+    "zen-engine (>=2.0.2,<3.0.0)",
+    "pandas (>=3.0.5,<4.0.0)",
+    "openpyxl (>=3.1.5,<4.0.0)",
+    "pyyaml (>=6.0.0,<7.0.0)",
+]
+
+[dependency-groups]
+dev = [
+    "pytest (>=9.1.1,<10.0.0)",
+    "genbadge[coverage] (>=1.1.3,<2.0.0)",
+    "pytest-cov (>=7.1.0,<8.0.0)",
+    "ruff (>=0.16.9,<0.17.0)",
+    "zensical (>=0.0.67,<0.0.68)",
+    "taskipy (>=1.14.1,<2.0.0)",
+    "commitizen (>=4.19.0,<5.0.0)",
+    "python-dotenv (>=1.2.4,<2.0.0)"
+]
+
+[project.scripts]
+zendt = "zendt.cli:app"
+
+[build-system]
+requires = ["poetry-core>=2.0.0"]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry]
+packages = [{include = "zendt", from = "src"}]
+
+[tool.ruff]
+line-length = 79
+
+[tool.ruff.lint]
+preview = true
+select = ['I', 'F', 'E', 'W', 'PL', 'PT']
+
+[tool.ruff.format]
+preview = true
+quote-style = 'single'
+
+
+[tool.commitizen]
+name = 'cz_conventional_commits'
+tag_format = '$version'
+version_scheme = 'pep440'
+version_provider = 'pep621'
+update_changelog_on_bump = true
+major_version_zero = true
+
+
+[tool.taskipy.tasks]
+list = { cmd = 'task --list', help = 'Lists all tasks.' }
+lint = { cmd = 'ruff check', help = 'Checks for good coding practices in Python.' }
+pre_format = { cmd = 'ruff check --fix', help = 'Makes some best practice corrections.' }
+format = { cmd = 'ruff format', help = 'Formats code according to code style conventions.' }
+test = { cmd = 'pytest -vv --cov=zendt --cov-report=term-missing --cov-report=xml', help = 'Runs unit tests with coverage.' }
+test_debug = { cmd = 'pytest -s -x -vv', help = 'Runs unit tests in debug mode.' }
+coverage_badge = { cmd = 'genbadge coverage -i coverage.xml -o coverage.svg --local', help = 'Generates the README coverage badge.' }
+check = { cmd = 'task lint && task test', help = 'Runs lint and tests.' }
+bump = { cmd = 'cz bump', help = 'Bumps project version.' }
+publish = { cmd = 'task bump && dotenv run poetry publish --build -n && git push origin main --tags', help = 'Bumps version and publish the package on Pypi.' }

zendt-0.1.0/src/zendt/__init__.py

@@ -0,0 +1,3 @@
+from zendt.main import apply, flow, rules_list
+
+__all__ = ['apply', 'flow', 'rules_list']

zendt-0.1.0/src/zendt/__main__.py

@@ -0,0 +1,4 @@
+from zendt.cli import app
+
+if __name__ == '__main__':
+    app()

zendt-0.1.0/src/zendt/cli.py

@@ -0,0 +1,167 @@
+import sys
+from typing import Annotated
+
+import pandas as pd
+import typer
+
+from zendt.config.create import create_config
+from zendt.config.edit import edit_config
+from zendt.engine.output import write_output
+from zendt.errors import ZendtError
+from zendt.main import apply, flow, rules_list
+
+app = typer.Typer(
+    name='zendt',
+    help='Apply JDM (GoRules) rules to data from the terminal.',
+    no_args_is_help=True,
+)
+
+SourceOption = typer.Option(
+    None,
+    '--source',
+    '-s',
+    help='GitHub URL, local path, or id of a configured source.',
+)
+
+FindOption = typer.Option(
+    None,
+    '--find',
+    '-f',
+    help='Search for rules whose name contains the specified word.',
+)
+
+VersionOption = typer.Option(
+    None,
+    '--version',
+    '-v',
+    help='Rule version to apply for git repositories.',
+)
+
+AuthOption = typer.Option(
+    None,
+    '--authentication',
+    '-a',
+    help=(
+        'Name of the environment variable that holds the token '
+        '(private repositories).'
+    ),
+)
+
+InputOption = typer.Option(
+    None,
+    '--input',
+    '-i',
+    help='Input file to process.',
+)
+
+OutputOption = typer.Option(
+    None,
+    '--output',
+    '-o',
+    help='Output file to save.',
+)
+
+PrintHeadOption = typer.Option(
+    False,
+    '--printhead',
+    '-ph',
+    help='Print a preview of the result on screen.',
+)
+
+CreateConfigOption = typer.Option(
+    False,
+    '--create',
+    '-c',
+    help='Create a zendt.json configuration file.',
+)
+
+EditConfigOption = typer.Option(
+    False,
+    '--edit',
+    '-e',
+    help='Edit the zendt.json configuration file.',
+)
+
+
+def echo_head(frame: pd.DataFrame) -> None:
+    """Preview on the terminal.
+
+    Keep it off stdout when that stream carries the csv.
+    """
+    typer.echo(frame.head(), err=not sys.stdout.isatty())
+
+
+@app.command('config')
+def config(
+    create: bool = CreateConfigOption,
+    edit: bool = EditConfigOption,
+) -> None:
+    """Manage the zendt.json configuration file."""
+    if create:
+        create_config()
+    elif edit:
+        edit_config()
+
+
+@app.command('list')
+def list_rules_command(
+    source: str = SourceOption,
+    find: str = FindOption,
+    version: str = VersionOption,
+    authentication: str = AuthOption,
+) -> None:
+    """List the JDM rules found in SOURCE."""
+    try:
+        names = rules_list(source, find, version, authentication)
+    except ZendtError as exc:
+        typer.echo(str(exc), err=True)
+        raise typer.Exit(code=exc.exit_code) from exc
+
+    typer.echo('Rules found in provided sources:')
+    for name in names:
+        typer.echo(name)
+
+
+@app.command('apply')
+def apply_command(
+    rules: Annotated[
+        list[str], typer.Argument(help='Names of the rules to apply.')
+    ],
+    source: str = SourceOption,
+    authentication: str = AuthOption,
+    version: str = VersionOption,
+    input: str = InputOption,
+    output: str = OutputOption,
+    printhead: bool = PrintHeadOption,
+) -> None:
+    """Apply the JDM rules passed as arguments."""
+    try:
+        result = apply(rules, source, authentication, version, input)
+        write_output(result, output)
+        if printhead:
+            echo_head(result)
+    except ZendtError as exc:
+        typer.echo(str(exc), err=True)
+        raise typer.Exit(code=exc.exit_code) from exc
+
+
+@app.command('flow')
+def flow_command(
+    flow_id: Annotated[str, typer.Argument(help='Configured flow ID.')],
+    input: str = InputOption,
+    output: str = OutputOption,
+    printhead: bool = PrintHeadOption,
+) -> None:
+    """Apply a pre-configured flow."""
+    try:
+        result = flow(flow_id, input)
+    except ZendtError as exc:
+        typer.echo(str(exc), err=True)
+        raise typer.Exit(code=exc.exit_code) from exc
+
+    destination = output
+    if destination is None:
+        destination = result.attrs.get('output')
+    write_output(result, destination)
+    if printhead:
+        echo_head(result)