throughline-ratify 0.1.2__tar.gz

throughline_ratify-0.1.2/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 The throughline-ratify authors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

throughline_ratify-0.1.2/NOTICE

@@ -0,0 +1,11 @@
+throughline-ratify
+Copyright 2026 The throughline-ratify authors
+
+This product includes software developed by the throughline-ratify authors.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file for the
+full terms.
+
+throughline-ratify is a full-screen terminal companion for
+throughline (the `tl` CLI) and throughline-compose (`tl-compose`). It builds
+on their public Python APIs; no third-party source code was copied.

throughline_ratify-0.1.2/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: throughline-ratify
+Version: 0.1.2
+Summary: A full-screen, htop-style terminal assistant for reviewing and ratifying throughline requirement items. Compose-aware: grounds items over the composed union so borrowed clauses count. Ships the tl-ratify TUI.
+Author-email: Henry J Grech-Cini <henry.grechcini@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/rhodium-org/throughline-ratify
+Project-URL: Repository, https://github.com/rhodium-org/throughline-ratify
+Project-URL: Issues, https://github.com/rhodium-org/throughline-ratify/issues
+Keywords: requirements,requirements-management,ratification,review,tui,curses,traceability,grounding,idd,intent-driven-development,throughline
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console :: Curses
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX
+Classifier: Operating System :: MacOS
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: throughline-compose>=0.3.1
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Dynamic: license-file
+
+# throughline-ratify
+
+A full-screen, **htop-style** terminal cockpit for working through the
+[throughline](https://github.com/rhodium-org/throughline) requirement items that
+await human ratification — one item at a time, with colour and glyphs carrying the
+semantic weight so your eye lands on the actionable rows first.
+
+It is **compose-aware**: on a
+[`tl-compose`](https://github.com/rhodium-org/throughline-compose) project it grounds
+each item over the *composed union*, so an item whose grounding chain reaches a root
+only through a borrowed source counts as grounded — never orphaned. Writes only ever
+land on your own consumer registers; a composed source stays read-only.
+
+```
+ throughline-ratify │ my-service                               composed │ 2 source(s)
+ queue: ● 3 proposed  ◉ 2 ready  ○ 0 blocked  ⚠ 1 ungrounded  ⚑ 0 ambiguous   (6 shown)
+ ▸ ● SR-0007  Rate-limit the login endpoint    │ ● SR-0007  system_requirement
+   ◉ SR-0008  Store audit events append-only   │   status: proposed
+   ⚠ SR-0011  Redact PII from logs             │
+                                               │   ✓ ready to ratify (proposed → ratified)
+                                               │   grounded: ✓   ambiguous: no
+                                               │   links
+                                               │     derives_from → asvs:V7.1.1  "..."
+ j/k:move  r/↵:ratify  x:reject  a:all  /:filter  R:reload  ?:help  q:quit
+```
+
+## Install
+
+```bash
+pipx install throughline-ratify
+```
+
+This pulls in `throughline-compose` (and, transitively, the `throughline` core), so
+the `tl` and `tl-compose` CLIs come along too.
+
+## Use
+
+From anywhere inside a throughline project (it walks up to find `throughline.toml`):
+
+```bash
+tl-ratify                    # open the cockpit
+tl-ratify -C path/to/project # point at a specific project
+tl-ratify --by alice         # record a specific ratifier on sign-off
+tl-ratify --list             # print the worklist (no TUI) — good for CI/pipelines
+tl-ratify --list --all       # include already-ratified items
+```
+
+### Keys
+
+| Key | Action |
+| --- | --- |
+| `j` / `↓`, `k` / `↑` | move |
+| `g` / `G`, PgUp / PgDn | jump / page |
+| `r` / `Enter` | ratify the selected item (with confirm) |
+| `x` | reject (invalidate) the selected item, cascading suspect to dependents |
+| `a` | toggle showing already-ratified items |
+| `/` | filter by uid or title |
+| `R` | reload the graph from disk |
+| `?` | help |
+| `q` | quit |
+
+### Concerns
+
+Every row is classified by the one thing you most need to know about it:
+
+| Glyph | Concern | Meaning |
+| --- | --- | --- |
+| ● | proposed | AI-proposed, awaiting a human's accountability |
+| ◉ | ready | already approved, one move from ratified |
+| ○ | blocked | pending, but not directly ratifiable from its status |
+| ⚠ | ungrounded | reaches no root — link it upward before sign-off |
+| ⚑ | ambiguous | flagged ambiguous — clarify it first |
+
+## How it works
+
+`tl-ratify` is a thin, safe view over throughline's own Python API:
+
+- **What needs ratifying** — every local item whose status is not the project's
+  `ratified` role and is not a dead status. Ranking, colour and icon come from the
+  concern each item earns.
+- **Ratifying** mirrors `tl-compose ratify`: it runs throughline's grounding gate
+  over the composed union (refusing ambiguous or ungrounded items), sets the
+  `ratified`-role status through the config-driven `set_status` choke point, records
+  who signed off, and writes the item back to its own register.
+- **Rejecting** calls throughline's `invalidate`, moving the item to the
+  `invalidated` role and cascading `suspect` to its trusting dependents.
+
+No status names are hardcoded: the project's `[status.roles]` and `[transitions]`
+govern every move.
+
+## Development
+
+```bash
+python -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"
+pytest -q
+tl -C idd check --strict   # this repo is itself throughline-managed
+```
+
+This project practises what it automates: its own requirements live in
+[`idd/`](idd/) as a throughline graph, and CI gates every change on
+`tl check --strict`.
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

throughline_ratify-0.1.2/README.md

@@ -0,0 +1,106 @@
+# throughline-ratify
+
+A full-screen, **htop-style** terminal cockpit for working through the
+[throughline](https://github.com/rhodium-org/throughline) requirement items that
+await human ratification — one item at a time, with colour and glyphs carrying the
+semantic weight so your eye lands on the actionable rows first.
+
+It is **compose-aware**: on a
+[`tl-compose`](https://github.com/rhodium-org/throughline-compose) project it grounds
+each item over the *composed union*, so an item whose grounding chain reaches a root
+only through a borrowed source counts as grounded — never orphaned. Writes only ever
+land on your own consumer registers; a composed source stays read-only.
+
+```
+ throughline-ratify │ my-service                               composed │ 2 source(s)
+ queue: ● 3 proposed  ◉ 2 ready  ○ 0 blocked  ⚠ 1 ungrounded  ⚑ 0 ambiguous   (6 shown)
+ ▸ ● SR-0007  Rate-limit the login endpoint    │ ● SR-0007  system_requirement
+   ◉ SR-0008  Store audit events append-only   │   status: proposed
+   ⚠ SR-0011  Redact PII from logs             │
+                                               │   ✓ ready to ratify (proposed → ratified)
+                                               │   grounded: ✓   ambiguous: no
+                                               │   links
+                                               │     derives_from → asvs:V7.1.1  "..."
+ j/k:move  r/↵:ratify  x:reject  a:all  /:filter  R:reload  ?:help  q:quit
+```
+
+## Install
+
+```bash
+pipx install throughline-ratify
+```
+
+This pulls in `throughline-compose` (and, transitively, the `throughline` core), so
+the `tl` and `tl-compose` CLIs come along too.
+
+## Use
+
+From anywhere inside a throughline project (it walks up to find `throughline.toml`):
+
+```bash
+tl-ratify                    # open the cockpit
+tl-ratify -C path/to/project # point at a specific project
+tl-ratify --by alice         # record a specific ratifier on sign-off
+tl-ratify --list             # print the worklist (no TUI) — good for CI/pipelines
+tl-ratify --list --all       # include already-ratified items
+```
+
+### Keys
+
+| Key | Action |
+| --- | --- |
+| `j` / `↓`, `k` / `↑` | move |
+| `g` / `G`, PgUp / PgDn | jump / page |
+| `r` / `Enter` | ratify the selected item (with confirm) |
+| `x` | reject (invalidate) the selected item, cascading suspect to dependents |
+| `a` | toggle showing already-ratified items |
+| `/` | filter by uid or title |
+| `R` | reload the graph from disk |
+| `?` | help |
+| `q` | quit |
+
+### Concerns
+
+Every row is classified by the one thing you most need to know about it:
+
+| Glyph | Concern | Meaning |
+| --- | --- | --- |
+| ● | proposed | AI-proposed, awaiting a human's accountability |
+| ◉ | ready | already approved, one move from ratified |
+| ○ | blocked | pending, but not directly ratifiable from its status |
+| ⚠ | ungrounded | reaches no root — link it upward before sign-off |
+| ⚑ | ambiguous | flagged ambiguous — clarify it first |
+
+## How it works
+
+`tl-ratify` is a thin, safe view over throughline's own Python API:
+
+- **What needs ratifying** — every local item whose status is not the project's
+  `ratified` role and is not a dead status. Ranking, colour and icon come from the
+  concern each item earns.
+- **Ratifying** mirrors `tl-compose ratify`: it runs throughline's grounding gate
+  over the composed union (refusing ambiguous or ungrounded items), sets the
+  `ratified`-role status through the config-driven `set_status` choke point, records
+  who signed off, and writes the item back to its own register.
+- **Rejecting** calls throughline's `invalidate`, moving the item to the
+  `invalidated` role and cascading `suspect` to its trusting dependents.
+
+No status names are hardcoded: the project's `[status.roles]` and `[transitions]`
+govern every move.
+
+## Development
+
+```bash
+python -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"
+pytest -q
+tl -C idd check --strict   # this repo is itself throughline-managed
+```
+
+This project practises what it automates: its own requirements live in
+[`idd/`](idd/) as a throughline graph, and CI gates every change on
+`tl check --strict`.
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

throughline_ratify-0.1.2/pyproject.toml

@@ -0,0 +1,59 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "throughline-ratify"
+version = "0.1.2"
+description = "A full-screen, htop-style terminal assistant for reviewing and ratifying throughline requirement items. Compose-aware: grounds items over the composed union so borrowed clauses count. Ships the tl-ratify TUI."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Henry J Grech-Cini", email = "henry.grechcini@gmail.com" }]
+keywords = [
+  "requirements",
+  "requirements-management",
+  "ratification",
+  "review",
+  "tui",
+  "curses",
+  "traceability",
+  "grounding",
+  "idd",
+  "intent-driven-development",
+  "throughline",
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console :: Curses",
+  "Intended Audience :: Developers",
+  "Operating System :: POSIX",
+  "Operating System :: MacOS",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development :: Documentation",
+  "Topic :: Software Development :: Quality Assurance",
+]
+# throughline-compose re-exports the throughline core it composes over, so this
+# single pin gives us both the union engine and the model/grounding APIs.
+dependencies = ["throughline-compose>=0.3.1"]
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0"]
+
+[project.urls]
+Homepage = "https://github.com/rhodium-org/throughline-ratify"
+Repository = "https://github.com/rhodium-org/throughline-ratify"
+Issues = "https://github.com/rhodium-org/throughline-ratify/issues"
+
+[project.scripts]
+tl-ratify = "throughline_ratify.cli:main"
+throughline-ratify = "throughline_ratify.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

throughline_ratify-0.1.2/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

throughline_ratify-0.1.2/src/throughline_ratify/__init__.py

@@ -0,0 +1,14 @@
+# Copyright (c) 2026 Henry J Grech-Cini
+# SPDX-License-Identifier: Apache-2.0
+"""throughline-ratify — a full-screen terminal companion for
+working through the throughline items that await human ratification."""
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError, version as _version
+
+try:
+    __version__ = _version("throughline-ratify")
+except PackageNotFoundError:  # running from a source tree
+    __version__ = "0.0.0+unknown"
+
+__all__ = ["__version__"]

throughline_ratify-0.1.2/src/throughline_ratify/cli.py

@@ -0,0 +1,94 @@
+# Copyright (c) 2026 Henry J Grech-Cini
+# SPDX-License-Identifier: Apache-2.0
+"""``tl-ratify`` — the entry point.
+
+Launches the full-screen ratification cockpit over the throughline project
+enclosing ``--path`` (default: the current directory). ``--list`` prints the same
+worklist to stdout without curses, for pipelines, CI logs and quick glances.
+"""
+from __future__ import annotations
+
+import argparse
+import sys
+from importlib.metadata import PackageNotFoundError, version as _pkg_version
+
+from . import core
+
+
+def _v(name: str) -> str:
+    try:
+        return _pkg_version(name)
+    except PackageNotFoundError:  # pragma: no cover - source tree
+        return "0.0.0+unknown"
+
+
+def _version_string() -> str:
+    return (
+        f"tl-ratify {_v('throughline-ratify')} "
+        f"(throughline-compose {_v('throughline-compose')}, throughline {_v('throughline')})"
+    )
+
+
+def build_parser() -> argparse.ArgumentParser:
+    p = argparse.ArgumentParser(
+        prog="tl-ratify",
+        description="A full-screen assistant for ratifying throughline items (compose-aware).",
+    )
+    p.add_argument("--version", action="version", version=_version_string())
+    p.add_argument("-C", "--path", default=".", help="project root or a path within it (default: .)")
+    p.add_argument("--by", default=None,
+                   help="the ratifier recorded on sign-off (default: the current user)")
+    p.add_argument("--list", action="store_true",
+                   help="print the ratification worklist and exit (no TUI)")
+    p.add_argument("--all", action="store_true",
+                   help="with --list, include already-ratified items")
+    p.add_argument("--sort", choices=core.SORTS, default="concern",
+                   help="worklist ordering: concern (default), roots (shallowest "
+                        "grounding depth first) or leaves (deepest first)")
+    return p
+
+
+def _print_list(session: core.Session, show_all: bool, sort: str) -> int:
+    rows = core.build_queue(session, show_all=show_all, sort=sort)
+    scope = "composed union" if session.composed else "local graph"
+    done, total = core.ratification_progress(session)
+    print(f"{session.project_name} \u2014 {scope}  \u2502  {done}/{total} ratified")
+    if session.composed:
+        for s in session.sources:
+            print(f"  source {s.namespace}: {s.location}")
+    if not rows:
+        print("nothing to ratify \u2014 all clear")
+        return 0
+    header = "item(s) shown" if show_all else "item(s) pending ratification"
+    print(f"{len(rows)} {header} (sort: {sort}):\n")
+    for r in rows:
+        mark = "ratify-ready" if r.ratifiable_now else r.concern
+        print(f"  {r.icon} {r.uid:<14} [{r.status:<10}] {mark:<12} {r.title}")
+    return 0
+
+
+def main(argv: list[str] | None = None) -> int:
+    args = build_parser().parse_args(argv)
+    try:
+        session = core.open_session(args.path)
+    except core.RatifierError as exc:
+        print(f"tl-ratify: {exc}", file=sys.stderr)
+        return 2
+
+    if args.list:
+        return _print_list(session, args.all, args.sort)
+
+    if not sys.stdout.isatty():
+        print("tl-ratify: not a terminal; use --list for non-interactive output",
+              file=sys.stderr)
+        return 2
+
+    from . import tui  # deferred: only import curses when we actually open the UI
+
+    ratifier = args.by or core.default_ratifier()
+    tui.run(session, ratifier)
+    return 0
+
+
+if __name__ == "__main__":  # pragma: no cover
+    raise SystemExit(main())