Skip to main content

rigor-cli

A tool for performing logic against a ledger, so reasoning stays tractable and provable. Every premise, rule application and conclusion is recorded as an append-only ledger entry that can be replayed, audited and checked independently of the agent that produced it.

Status

The ledger domain is not implemented yet. What is checked in today is the agent scaffold rigor-cli was minted from: an agent-first CLI, a mesh identity, the vendored skill kit, and a build/lint/deploy baseline. Nothing in rigor/ models premises, rules, entries, replay, or audit so far — the verbs below are the scaffold's introspection surface, not the tool described above.

What you get

  • An agent-first CLI cited from teken (afi-cli) — the runtime package has no third-party dependencies.
  • A mesh identity — culture.yaml (suffix + backend) and the matching resident prompt file (AGENTS.colleague.md, since this agent runs backend: colleague).
  • The guildmaster skill kit (18 skills) under .claude/skills/, vendored cite-don't-import. See docs/skill-sources.md.
  • A build + deploy baseline — pytest, lint, the agent-first rubric gate, and PyPI Trusted Publishing wired into GitHub Actions.

Quickstart

The distribution is named rigor-cli; the console script it installs is rigor.

uv sync
uv run pytest -n auto                 # run the test suite
uv run rigor whoami                   # identity from culture.yaml
uv run rigor learn                    # self-teaching prompt (add --json)
uv run teken cli doctor . --strict    # the agent-first rubric gate CI runs

CLI

Verb What it does
whoami Report this agent's nick, version, backend, and model from culture.yaml.
learn Print a structured self-teaching prompt.
explain <path> Markdown docs for any noun/verb path.
overview Read-only descriptive snapshot of the agent.
doctor Check the agent-identity invariants (prompt-file-present, backend-consistency).
cli overview Describe the CLI surface itself.

Every command supports --json. Results go to stdout, errors/diagnostics to stderr (never mixed). Exit codes: 0 success, 1 user error, 2 environment error, 3+ reserved.

The CLI's own learn and explain output still describes this repo as a clonable agent template — leftover scaffold prose that the first domain-bearing change replaces.

Development

uv run pytest -n auto                        # tests
uv run black --check rigor tests             # lint (CI runs black, isort,
uv run isort --check-only rigor tests        # flake8, bandit, markdownlint)
uv run flake8 rigor tests
uv run bandit -c pyproject.toml -r rigor

Every PR bumps the version — even docs and CI — and the version-check job blocks merge otherwise. See CLAUDE.md for the full conventions: the CLI's output/error contracts, how to add a verb, the cicd PR lane, the skill kit's cite-don't-import rule, worktree layout, and deploy setup.

License

Apache 2.0 — see LICENSE.

Metadata

Release files for rigor-cli 0.6.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rigor-cli 0.6.2
File Size Uploaded Provenance
rigor_cli-0.6.2.tar.gz 158.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for rigor-cli 0.6.2
File Interpreter ABI Platform
rigor_cli-0.6.2-py3-none-any.whl Python 3 none any Details

Total release size: 180.9 kB

Release files / rigor_cli-0.6.2.tar.gz

Download URL rigor_cli-0.6.2.tar.gz
Size 158.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f746479d1d3e1bdcaab57214f36f99cbe21c7f6cccebd3a300bbfab098b22538
BLAKE2b-256 checksum
How to use checksums
ce9e2a20f3bfa1885deea4b3d194296ea9c44aeade1e16832c3d4cc8a0c6052d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / rigor_cli-0.6.2-py3-none-any.whl

Download URL rigor_cli-0.6.2-py3-none-any.whl
Size 22.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a12a76e9b84ef373f963a10caf7eb2ec8d3badc3e3eacb60bb9cbc88ca9d4f93
BLAKE2b-256 checksum
How to use checksums
d53c141960cd39ef66d95b5944b5c5b2e4eb5a368b8760d90be08b560d228e2a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for rigor-cli 0.6.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page