throughline-transform 0.2.0__tar.gz

throughline_transform-0.2.0/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_transform-0.2.0/MANIFEST.in

@@ -0,0 +1,4 @@
+# setuptools' default sdist file set ships modules matching test*.py but not the
+# shared conftest that defines their fixtures, so the shipped suite would error
+# at collection. Ship it so the suite runs green from the sdist.
+include tests/conftest.py

throughline_transform-0.2.0/NOTICE

@@ -0,0 +1,12 @@
+throughline-transform
+Copyright 2026 Henry J Grech-Cini
+Created by Dr Henry J Grech-Cini (ORCID https://orcid.org/0009-0007-1565-7530).
+
+This product includes software developed by Henry J Grech-Cini.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file for the
+full terms.
+
+throughline-transform 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_transform-0.2.0/PKG-INFO

@@ -0,0 +1,121 @@
+Metadata-Version: 2.4
+Name: throughline-transform
+Version: 0.2.0
+Summary: Turn a throughline requirements graph on disk, committed or not, into the forms its readers open: Markdown, a folder of Obsidian notes, CSV, an Excel workbook, a Word document, or a print-ready HTML document. Ships the tl-transform CLI.
+Author-email: Henry J Grech-Cini <henry.grechcini@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/rhodium-org/throughline-transform
+Project-URL: Repository, https://github.com/rhodium-org/throughline-transform
+Project-URL: Issues, https://github.com/rhodium-org/throughline-transform/issues
+Keywords: requirements,requirements-management,export,obsidian,docx,xlsx,markdown,traceability,idd,intent-driven-development,throughline
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Office/Business
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: throughline-compose>=0.16.1
+Requires-Dist: throughline>=2.2.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Dynamic: license-file
+
+# throughline-transform
+
+A [throughline](https://github.com/rhodium-org/throughline) requirements graph on
+disk — committed or not — in the forms its readers open. One command, one file:
+
+```bash
+pipx install throughline-transform      # pulls tl and tl-compose along too
+
+tl-transform md      -C idd             # Markdown, written by the tool itself
+tl-transform notes   -C idd             # a folder of notes for Obsidian (zip)
+tl-transform notes   -C idd --folder    # …or the folder itself, ready to open as a vault
+tl-transform csv     -C idd             # one row per item, a links file, a file per cited source (zip)
+tl-transform xlsx    -C idd             # the same as a read-only workbook that still sorts and filters
+tl-transform docx    -C idd             # a Word document: title page, contents, a heading per item
+tl-transform html    -C idd             # a print-ready page — print it to PDF from any browser
+```
+
+It is the command-line half of the
+[throughline editor](https://github.com/rhodium-org/throughline-editor)'s export:
+the same six forms, laid out the same way, from the graph as it stands on your
+disk. The editor needs the graph on GitHub. This does not — it reads the working
+tree, and the output says whether that tree was clean, carried uncommitted
+changes, or was not under version control at all.
+
+## What it does not do
+
+**It never renders an item's words.** The Markdown is asked of `tl docs` over a
+document of directives; the structure is read from `tl dump`. What this package
+adds is the containers — a workbook, a Word document, a folder of notes, a
+print-ready page — and the front matter and link syntax a note tool reads. If a
+requirement here rendered prose, it would drift from what `tl docs --check`
+gates, and a document that quietly differs from the published specification is
+worse than none. That is [`NG-0001`](idd/non-goals/NG-0001.yml).
+
+**It ships no PDF writer** ([`NG-0002`](idd/non-goals/NG-0002.yml)). Every
+browser prints to PDF with a renderer that is already on the machine.
+
+**It depends on nothing but the family.** `throughline` and
+`throughline-compose`, and the standard library's `zipfile` for the two Office
+formats, which are written from their own specifications.
+
+## Which tool answers
+
+A graph whose `throughline.toml` declares `[[sources]]` is read through
+`tl-compose`; any other through `tl`. That is not cosmetic: over a composed graph
+the core command exits cleanly and writes a borrowed clause as its synthetic uid
+alone, dropping the reference number a conformance document exists to carry.
+The tool is found beside this package's interpreter first and on the path
+second, and is run as a command — its command line is the surface it publishes.
+
+## The outputs
+
+| Format | What you get |
+|---|---|
+| `md` | The tool's own document: a summary, a catalogue of every item in full, the mirrored clauses of adopted sources. `--body table` or `both` for a one-line-per-item table, `--matrix` for one traceability matrix per grounding link type, `--markers` to keep the region markers so `tl docs` can refill the file later. |
+| `notes` | One Markdown note per item in a folder per register, YAML front matter as properties (type, status, attributes, the title as an alias, a tag each for type and status), every identifier a `[[wikilink]]`. Cited clauses under `sources/<namespace>/`, the colon in their name replaced by a space. Open the folder as an Obsidian vault: the graph view is the intent graph, and a note's backlinks are what rests on it. |
+| `csv` | A zip of one file of items (or one per register with `--split per-register`), `links.csv` with one row per link naming the sheet at each end, one file per cited source, and the provenance. |
+| `xlsx` | The same as sheets, read-only by recommendation with the structure locked and no password. Sorting and filtering stay allowed; a spreadsheet nobody can sort is one nobody can review. |
+| `docx` | A title page with the provenance, a contents field Word fills in, a section per register, a heading per item with its type and status beneath, its words as a quotation, its rationale, its attributes in small print, and one appendix per cited source. |
+| `html` | The same document as one self-contained page with print typography, A4 page rules and a contents list of links. Print it to PDF; the browser numbers the pages. |
+| `blocks` | The document's structure as JSON — the same list of headings, quotations, paragraphs, attribute lines, tables and appendices the Word and HTML outputs are built from — for a front end that lays out its own pages. The editor's PDF is laid out from it. |
+
+Every output carries the repository, ref, commit, working-tree state and tool
+version it was taken from, because an output outlives the tree that made it and
+the first question anyone asks of one is what it was true of. A caller that
+knows them without git — the editor holds them from its clone — states them with
+`--repository`, `--ref`, `--commit` and `--tree clean|dirty|untracked`, and git
+is then not consulted.
+
+## One implementation, two surfaces
+
+The [throughline editor](https://github.com/rhodium-org/throughline-editor)
+runs this package as a wheel under Pyodide beside `tl` and `tl-compose`, so an
+export from a browser tab and an export from a terminal are the same bytes for
+the same graph at the same commit. Pyodide has no processes, so there the tool
+calls the console entry point `tl` or `tl-compose` declares in its package
+metadata — the same function the command runs — instead of spawning it.
+
+## Self-hosting
+
+This repository's own requirements live under [`idd/`](idd) and compose
+throughline's graph as a pinned source, so a requirement here can cite the
+clause of the tool it reads (`satisfies: tl:SR-0111`) and have the citation
+resolved rather than asserted.
+
+```bash
+tl-compose -C idd check --strict     # the grounding gate
+tl-compose -C idd docs --check       # idd/docs/spec.md must match the graph
+tl-transform html -C idd             # and the tool over its own graph
+```
+
+Apache-2.0. Created by Dr Henry J Grech-Cini; see [`PROVENANCE.md`](PROVENANCE.md).

throughline_transform-0.2.0/README.md

@@ -0,0 +1,92 @@
+# throughline-transform
+
+A [throughline](https://github.com/rhodium-org/throughline) requirements graph on
+disk — committed or not — in the forms its readers open. One command, one file:
+
+```bash
+pipx install throughline-transform      # pulls tl and tl-compose along too
+
+tl-transform md      -C idd             # Markdown, written by the tool itself
+tl-transform notes   -C idd             # a folder of notes for Obsidian (zip)
+tl-transform notes   -C idd --folder    # …or the folder itself, ready to open as a vault
+tl-transform csv     -C idd             # one row per item, a links file, a file per cited source (zip)
+tl-transform xlsx    -C idd             # the same as a read-only workbook that still sorts and filters
+tl-transform docx    -C idd             # a Word document: title page, contents, a heading per item
+tl-transform html    -C idd             # a print-ready page — print it to PDF from any browser
+```
+
+It is the command-line half of the
+[throughline editor](https://github.com/rhodium-org/throughline-editor)'s export:
+the same six forms, laid out the same way, from the graph as it stands on your
+disk. The editor needs the graph on GitHub. This does not — it reads the working
+tree, and the output says whether that tree was clean, carried uncommitted
+changes, or was not under version control at all.
+
+## What it does not do
+
+**It never renders an item's words.** The Markdown is asked of `tl docs` over a
+document of directives; the structure is read from `tl dump`. What this package
+adds is the containers — a workbook, a Word document, a folder of notes, a
+print-ready page — and the front matter and link syntax a note tool reads. If a
+requirement here rendered prose, it would drift from what `tl docs --check`
+gates, and a document that quietly differs from the published specification is
+worse than none. That is [`NG-0001`](idd/non-goals/NG-0001.yml).
+
+**It ships no PDF writer** ([`NG-0002`](idd/non-goals/NG-0002.yml)). Every
+browser prints to PDF with a renderer that is already on the machine.
+
+**It depends on nothing but the family.** `throughline` and
+`throughline-compose`, and the standard library's `zipfile` for the two Office
+formats, which are written from their own specifications.
+
+## Which tool answers
+
+A graph whose `throughline.toml` declares `[[sources]]` is read through
+`tl-compose`; any other through `tl`. That is not cosmetic: over a composed graph
+the core command exits cleanly and writes a borrowed clause as its synthetic uid
+alone, dropping the reference number a conformance document exists to carry.
+The tool is found beside this package's interpreter first and on the path
+second, and is run as a command — its command line is the surface it publishes.
+
+## The outputs
+
+| Format | What you get |
+|---|---|
+| `md` | The tool's own document: a summary, a catalogue of every item in full, the mirrored clauses of adopted sources. `--body table` or `both` for a one-line-per-item table, `--matrix` for one traceability matrix per grounding link type, `--markers` to keep the region markers so `tl docs` can refill the file later. |
+| `notes` | One Markdown note per item in a folder per register, YAML front matter as properties (type, status, attributes, the title as an alias, a tag each for type and status), every identifier a `[[wikilink]]`. Cited clauses under `sources/<namespace>/`, the colon in their name replaced by a space. Open the folder as an Obsidian vault: the graph view is the intent graph, and a note's backlinks are what rests on it. |
+| `csv` | A zip of one file of items (or one per register with `--split per-register`), `links.csv` with one row per link naming the sheet at each end, one file per cited source, and the provenance. |
+| `xlsx` | The same as sheets, read-only by recommendation with the structure locked and no password. Sorting and filtering stay allowed; a spreadsheet nobody can sort is one nobody can review. |
+| `docx` | A title page with the provenance, a contents field Word fills in, a section per register, a heading per item with its type and status beneath, its words as a quotation, its rationale, its attributes in small print, and one appendix per cited source. |
+| `html` | The same document as one self-contained page with print typography, A4 page rules and a contents list of links. Print it to PDF; the browser numbers the pages. |
+| `blocks` | The document's structure as JSON — the same list of headings, quotations, paragraphs, attribute lines, tables and appendices the Word and HTML outputs are built from — for a front end that lays out its own pages. The editor's PDF is laid out from it. |
+
+Every output carries the repository, ref, commit, working-tree state and tool
+version it was taken from, because an output outlives the tree that made it and
+the first question anyone asks of one is what it was true of. A caller that
+knows them without git — the editor holds them from its clone — states them with
+`--repository`, `--ref`, `--commit` and `--tree clean|dirty|untracked`, and git
+is then not consulted.
+
+## One implementation, two surfaces
+
+The [throughline editor](https://github.com/rhodium-org/throughline-editor)
+runs this package as a wheel under Pyodide beside `tl` and `tl-compose`, so an
+export from a browser tab and an export from a terminal are the same bytes for
+the same graph at the same commit. Pyodide has no processes, so there the tool
+calls the console entry point `tl` or `tl-compose` declares in its package
+metadata — the same function the command runs — instead of spawning it.
+
+## Self-hosting
+
+This repository's own requirements live under [`idd/`](idd) and compose
+throughline's graph as a pinned source, so a requirement here can cite the
+clause of the tool it reads (`satisfies: tl:SR-0111`) and have the citation
+resolved rather than asserted.
+
+```bash
+tl-compose -C idd check --strict     # the grounding gate
+tl-compose -C idd docs --check       # idd/docs/spec.md must match the graph
+tl-transform html -C idd             # and the tool over its own graph
+```
+
+Apache-2.0. Created by Dr Henry J Grech-Cini; see [`PROVENANCE.md`](PROVENANCE.md).

throughline_transform-0.2.0/pyproject.toml

@@ -0,0 +1,62 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "throughline-transform"
+version = "0.2.0"
+description = "Turn a throughline requirements graph on disk, committed or not, into the forms its readers open: Markdown, a folder of Obsidian notes, CSV, an Excel workbook, a Word document, or a print-ready HTML document. Ships the tl-transform CLI."
+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",
+  "export",
+  "obsidian",
+  "docx",
+  "xlsx",
+  "markdown",
+  "traceability",
+  "idd",
+  "intent-driven-development",
+  "throughline",
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development :: Documentation",
+  "Topic :: Office/Business",
+]
+# The prose of every output is the tool's own: this package asks `tl docs` for the
+# Markdown and `tl dump` for the structure, and writes nothing of an item itself
+# (SR-0002). `tl:catalog` and `tl:sourced` as they are rendered from 2.2.0 and
+# 0.16.1 are the shapes this package reads (SR-0003); it was written against those
+# releases and the floors say so. compose 0.16.1 requires throughline 2.2.0, so the
+# two floors are one fact stated at both ends.
+dependencies = ["throughline-compose>=0.16.1", "throughline>=2.2.0"]
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0"]
+
+[project.urls]
+Homepage = "https://github.com/rhodium-org/throughline-transform"
+Repository = "https://github.com/rhodium-org/throughline-transform"
+Issues = "https://github.com/rhodium-org/throughline-transform/issues"
+
+[project.scripts]
+tl-transform = "throughline_transform.cli:main"
+throughline-transform = "throughline_transform.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

throughline_transform-0.2.0/setup.cfg

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

throughline_transform-0.2.0/src/throughline_transform/__init__.py

@@ -0,0 +1,13 @@
+# Copyright (c) 2026 Henry J Grech-Cini
+# SPDX-License-Identifier: Apache-2.0
+"""throughline-transform: a throughline graph on disk, in the forms its readers open.
+
+Everything here reads what the tool writes. The Markdown comes from ``tl docs``
+over a document of directives; the structure comes from ``tl dump``. What this
+package adds is the containers — a workbook, a Word document, a folder of notes,
+a print-ready page — and never a second rendering of an item's words.
+"""
+
+from .project import TransformError
+
+__all__ = ["TransformError"]