px is the Prometheux command-line tool. It lets you keep an entire Prometheux environment — the lineage (concepts, datasources, ontology schema, apps) and the context layer (knowledge notes) — as a directory of files that you author locally, review in a pull request, and apply to a Prometheux platform over REST. Beyond authoring, px covers the full platform surface — snapshots, policies, templates, apps, ad-hoc queries, semantic search, and compute — so it is a scriptable alternative to the MCP connection for everything you’d otherwise do in chat. It is a thin, files-first layer over the prometheux_chain Python SDK: px owns the file format, the offline validator, and the plan/diff engine; every platform call underneath goes through the SDK.

Install px

uv, pipx, or pip — plus one-liners for macOS/Linux and Windows.

Quickstart

Scaffold → author → validate → plan → apply in five commands.

Author a workspace

The file model: manifests, concept kinds, datasources.

Add the agent skill

Give Claude Code / Cursor full knowledge of px — no repo to clone.

​
Why lineage as code

Everything a Prometheux ontology is — concepts, their bindings, the ontology schema, apps, and the notes your AI assistant reads — becomes plain files in one git repo. That gives you:
  • Version control & review — diff a change, review it in a PR, roll back with git.
  • Reproducibility — recreate an ontology on another account or environment from the files.
  • Automation — apply from CI on every merge (see CI/CD).
  • Agent authoring — a coding agent writes the files and runs px for you (see the agent skill).

​
Mental model

1

Write logic, derive the graph

You never hand-write lineage edges. A concept’s Vadalog head/body predicates are the edges — if concept risk references predicate customer in its body, that reference is the edge. px plan reconstructs the whole graph from your rules.
2

A concept is a struct; its body is a projection

Each concept is a body file (the logic) plus, for most kinds, a sibling .meta.yaml envelope (binds, output predicate, fields). See concept kinds.
3

The database is the state

There is no external state file to lock or corrupt. px plan pulls current server state and diffs your local files against it, Terraform-style — then px apply reconciles them.
4

Safe by default

A concept is never deleted just because its file vanished. Pruning is explicit (px apply --prune). Secrets are referenced as ${ENV_VAR} and never written to files.

​
The workflow

init and validate are fully offline — no platform connection, no SDK. Every other command (login, pull, list, plan, apply, run, show, query, search, status, snapshot, policy, template, datasource, app, context, playbook, compute, delete) reaches the platform — see the command reference.

​
How it fits with the rest of Prometheux

px and the SDK share one brand and one binding layer: the CLI orchestrates the same px.* SDK calls the MCP tools use, so behaviour is identical across the CLI, CI, and interactive use.

​
Requirements

  • Python ≥ 3.9 (the px console script ships in the prometheux package).
  • A Prometheux platform URL + API token for the online commands (see Installation → Authenticate).
The CLI is open-source (Apache-2.0) — the repository is prometheuxresearch/prometheux-cli. All platform IP stays server-side; the client only speaks the REST surface any client already uses.