throughline-compose 0.1.0__tar.gz

throughline_compose-0.1.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 Time Back Solutions Limited
+
+   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_compose-0.1.0/NOTICE

@@ -0,0 +1,12 @@
+throughline-compose
+Copyright 2026 Time Back Solutions Limited
+
+This product includes software developed by Time Back Solutions Limited.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file for the
+full terms.
+
+throughline-compose builds on throughline (https://pypi.org/project/throughline/),
+which it consumes as an unmodified library. It adds source composition — namespace
+declaration, pinning, fetching, and union merging — over that library and reuses
+throughline's validator without forking it.

throughline_compose-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: throughline-compose
+Version: 0.1.0
+Summary: Compose one requirements graph from many reusable throughline sources: importer-assigned namespaces, source-native UIDs, and a union checked by throughline's own validator. Ships the tl-compose CLI, a strict superset of tl.
+Author: Time Back Solutions Limited
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/rhodium-org/throughline-compose
+Project-URL: Repository, https://github.com/rhodium-org/throughline-compose
+Project-URL: Issues, https://github.com/rhodium-org/throughline-compose/issues
+Keywords: requirements,requirements-management,traceability,composition,git-native,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 :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: throughline>=0.5.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Dynamic: license-file
+
+# throughline-compose
+
+**Compose one requirements graph from many reusable
+[throughline](https://github.com/rhodium-org/throughline) sources** — a house style
+guide, a platform standard, a regulatory baseline — alongside the requirements you
+write yourself, and work the combined graph as one.
+
+This repository is itself a throughline project: its own design is captured as a
+grounded IDD spine of
+<!-- tl:count type == 'user_requirement' -->
+3
+<!-- tl:end --> user requirements and
+<!-- tl:count type == 'system_requirement' -->
+7
+<!-- tl:end --> system requirements under [`vision/`](vision), [`goals/`](goals),
+[`user-requirements/`](user-requirements),
+[`system-requirements/`](system-requirements), and [`non-goals/`](non-goals), and
+published to [`docs/spec.md`](docs/spec.md). The graph is gated by `tl-compose check
+--strict` and the document by `tl-compose docs --check`; these two counts are
+rendered from the live spine by the `tl:count` directive, so they cannot drift.
+
+> **Status: alpha.** The composition engine is built. `tl-compose check` composes the
+> declared `[[sources]]` into a union graph and validates it, and `tl-compose docs`
+> renders the published document over that same union, resolving borrowed
+> (`namespace:UID`) targets ([SR-0007](system-requirements/SR-0007.yml)). Each source
+> resolves from either a local `path` or a pinned git `url` + `ref` into a per-user
+> cache ([SR-0006](system-requirements/SR-0006.yml)). Still pending: the
+> `tl-compose source add/update/pin` subcommands for managing source declarations from
+> the CLI (today you edit the `[[sources]]` tables by hand).
+
+## The idea
+
+A team should be able to adopt standard requirement sets *by reference*, not by
+copy-paste, and receive upstream revisions without ever forking. Two identity rules
+make that safe:
+
+- **Imported items keep their source-native UID** ([SR-0002](system-requirements/SR-0002.yml)).
+  Composition never renumbers or copies. Canonical identity is the pair
+  `(source-namespace, UID)`, so the same `SR-0001` may legitimately exist in two
+  sources without collision — the immutable-UID rule is never violated.
+- **The composer controls the namespaces** ([SR-0001](system-requirements/SR-0001.yml)).
+  The consumer's own `throughline.toml` binds each source to a short name it chooses
+  (`import X as Y`). A qualified reference like `gds:SR-0001` denotes a borrowed item;
+  a bare UID is always local. Renaming a namespace is a local-only change with a
+  bounded blast radius.
+
+## Declaring sources
+
+A consumer names the sources it composes in an array of `[[sources]]` tables in its
+own `throughline.toml`. Each entry binds a `namespace` to one source, located either
+by a pinned git `url` or by a local `path` ([SR-0006](system-requirements/SR-0006.yml)):
+
+```toml
+# Adopt a published standard by reference, pinned to an edition.
+[[sources]]
+namespace = "asvs"
+url = "https://github.com/rhodium-org/standard-asvs"
+ref = "v4.0.3"                       # a git tag (normal form), branch, or commit SHA
+
+# Develop a source and its consumer side by side.
+[[sources]]
+namespace = "house-style"
+path = "../house-style"              # a directory relative to this project
+```
+
+- **`url` + `ref` is the durable, shareable form.** The `ref` pins the exact edition
+  — normally a release tag, but any git ref (branch or commit SHA) works. `tl-compose`
+  fetches the source from its origin on first use into a per-user cache that lives
+  *outside* any project tree (`$TL_COMPOSE_CACHE`, else `$XDG_CACHE_HOME`, else
+  `~/.cache/throughline-compose/sources/`), keyed by `(url, ref)`. Resolution is
+  idempotent and offline thereafter: a source already cached at the pinned ref is
+  reused, never refetched. Nothing is vendored into your repo, so your own item scan
+  never ingests a borrowed graph.
+- **`path` is for local development.** A directory, relative to the consumer, for
+  working on a source alongside the project that consumes it.
+- **The two are mutually exclusive, and a `url` must carry a `ref`.** Declaring both
+  `path` and `url`, or a `url` with no `ref`, is rejected at check time — a dependency
+  can never silently track a moving default. (A `ref` alongside a `path` is likewise
+  rejected: a ref only pins a `url`.)
+
+Moving to a new upstream edition is a one-line change to the `ref`; the borrowed graph
+is never edited. See [`rhodium-org/idd-example`](https://github.com/rhodium-org/idd-example)
+for a complete worked consumer that adopts `standard-asvs` this way.
+
+## One tool, one set of guarantees
+
+In a composed project you drive everything through **`tl-compose`**, never `tl`
+directly ([UR-0002](user-requirements/UR-0002.yml)). The architecture keeps that
+honest:
+
+- **`tl-compose` is a strict superset of `tl`** ([SR-0003](system-requirements/SR-0003.yml)).
+  Local-graph commands are forwarded to the throughline library unchanged; the
+  union-aware `check` and `docs` are overridden to compose, validate, and render the
+  combined graph. (The `source` subcommands for editing declarations are the remaining
+  superset surface — see the status note above.) The core command set is obtained
+  programmatically, so the two surfaces cannot drift apart.
+- **Composition reuses throughline unchanged** ([SR-0004](system-requirements/SR-0004.yml)).
+  It merges the sources into one in-memory `Project` and runs throughline's existing
+  `validate`, `Index`, and `fingerprint` over that union — no second validation
+  engine. A composed graph is exactly as sound as a native one.
+- **Bare `tl check` fails fast on unresolved cross-source refs**
+  ([SR-0005](system-requirements/SR-0005.yml)). If you run core `tl` in a composed
+  repo by habit, a namespace-qualified reference it cannot resolve makes it stop and
+  point you at `tl-compose` — never a false clean result. Free external references (a
+  URL, a linked standard) stay opaque, as intended.
+
+Composition deliberately lives here, not in the throughline core
+([NG-0001](non-goals/NG-0001.yml)) — the core stays a single-purpose, offline tool
+over one graph, consumed here as a library.
+
+## Working here
+
+```sh
+pip install .            # pulls throughline transitively; installs tl and tl-compose
+tl-compose context       # agent brief, generated from throughline.toml
+tl-compose check --strict # gate the whole graph
+tl-compose docs --check  # gate published-document freshness
+tl-compose docs          # regenerate docs/spec.md from the graph
+```

throughline_compose-0.1.0/README.md

@@ -0,0 +1,119 @@
+# throughline-compose
+
+**Compose one requirements graph from many reusable
+[throughline](https://github.com/rhodium-org/throughline) sources** — a house style
+guide, a platform standard, a regulatory baseline — alongside the requirements you
+write yourself, and work the combined graph as one.
+
+This repository is itself a throughline project: its own design is captured as a
+grounded IDD spine of
+<!-- tl:count type == 'user_requirement' -->
+3
+<!-- tl:end --> user requirements and
+<!-- tl:count type == 'system_requirement' -->
+7
+<!-- tl:end --> system requirements under [`vision/`](vision), [`goals/`](goals),
+[`user-requirements/`](user-requirements),
+[`system-requirements/`](system-requirements), and [`non-goals/`](non-goals), and
+published to [`docs/spec.md`](docs/spec.md). The graph is gated by `tl-compose check
+--strict` and the document by `tl-compose docs --check`; these two counts are
+rendered from the live spine by the `tl:count` directive, so they cannot drift.
+
+> **Status: alpha.** The composition engine is built. `tl-compose check` composes the
+> declared `[[sources]]` into a union graph and validates it, and `tl-compose docs`
+> renders the published document over that same union, resolving borrowed
+> (`namespace:UID`) targets ([SR-0007](system-requirements/SR-0007.yml)). Each source
+> resolves from either a local `path` or a pinned git `url` + `ref` into a per-user
+> cache ([SR-0006](system-requirements/SR-0006.yml)). Still pending: the
+> `tl-compose source add/update/pin` subcommands for managing source declarations from
+> the CLI (today you edit the `[[sources]]` tables by hand).
+
+## The idea
+
+A team should be able to adopt standard requirement sets *by reference*, not by
+copy-paste, and receive upstream revisions without ever forking. Two identity rules
+make that safe:
+
+- **Imported items keep their source-native UID** ([SR-0002](system-requirements/SR-0002.yml)).
+  Composition never renumbers or copies. Canonical identity is the pair
+  `(source-namespace, UID)`, so the same `SR-0001` may legitimately exist in two
+  sources without collision — the immutable-UID rule is never violated.
+- **The composer controls the namespaces** ([SR-0001](system-requirements/SR-0001.yml)).
+  The consumer's own `throughline.toml` binds each source to a short name it chooses
+  (`import X as Y`). A qualified reference like `gds:SR-0001` denotes a borrowed item;
+  a bare UID is always local. Renaming a namespace is a local-only change with a
+  bounded blast radius.
+
+## Declaring sources
+
+A consumer names the sources it composes in an array of `[[sources]]` tables in its
+own `throughline.toml`. Each entry binds a `namespace` to one source, located either
+by a pinned git `url` or by a local `path` ([SR-0006](system-requirements/SR-0006.yml)):
+
+```toml
+# Adopt a published standard by reference, pinned to an edition.
+[[sources]]
+namespace = "asvs"
+url = "https://github.com/rhodium-org/standard-asvs"
+ref = "v4.0.3"                       # a git tag (normal form), branch, or commit SHA
+
+# Develop a source and its consumer side by side.
+[[sources]]
+namespace = "house-style"
+path = "../house-style"              # a directory relative to this project
+```
+
+- **`url` + `ref` is the durable, shareable form.** The `ref` pins the exact edition
+  — normally a release tag, but any git ref (branch or commit SHA) works. `tl-compose`
+  fetches the source from its origin on first use into a per-user cache that lives
+  *outside* any project tree (`$TL_COMPOSE_CACHE`, else `$XDG_CACHE_HOME`, else
+  `~/.cache/throughline-compose/sources/`), keyed by `(url, ref)`. Resolution is
+  idempotent and offline thereafter: a source already cached at the pinned ref is
+  reused, never refetched. Nothing is vendored into your repo, so your own item scan
+  never ingests a borrowed graph.
+- **`path` is for local development.** A directory, relative to the consumer, for
+  working on a source alongside the project that consumes it.
+- **The two are mutually exclusive, and a `url` must carry a `ref`.** Declaring both
+  `path` and `url`, or a `url` with no `ref`, is rejected at check time — a dependency
+  can never silently track a moving default. (A `ref` alongside a `path` is likewise
+  rejected: a ref only pins a `url`.)
+
+Moving to a new upstream edition is a one-line change to the `ref`; the borrowed graph
+is never edited. See [`rhodium-org/idd-example`](https://github.com/rhodium-org/idd-example)
+for a complete worked consumer that adopts `standard-asvs` this way.
+
+## One tool, one set of guarantees
+
+In a composed project you drive everything through **`tl-compose`**, never `tl`
+directly ([UR-0002](user-requirements/UR-0002.yml)). The architecture keeps that
+honest:
+
+- **`tl-compose` is a strict superset of `tl`** ([SR-0003](system-requirements/SR-0003.yml)).
+  Local-graph commands are forwarded to the throughline library unchanged; the
+  union-aware `check` and `docs` are overridden to compose, validate, and render the
+  combined graph. (The `source` subcommands for editing declarations are the remaining
+  superset surface — see the status note above.) The core command set is obtained
+  programmatically, so the two surfaces cannot drift apart.
+- **Composition reuses throughline unchanged** ([SR-0004](system-requirements/SR-0004.yml)).
+  It merges the sources into one in-memory `Project` and runs throughline's existing
+  `validate`, `Index`, and `fingerprint` over that union — no second validation
+  engine. A composed graph is exactly as sound as a native one.
+- **Bare `tl check` fails fast on unresolved cross-source refs**
+  ([SR-0005](system-requirements/SR-0005.yml)). If you run core `tl` in a composed
+  repo by habit, a namespace-qualified reference it cannot resolve makes it stop and
+  point you at `tl-compose` — never a false clean result. Free external references (a
+  URL, a linked standard) stay opaque, as intended.
+
+Composition deliberately lives here, not in the throughline core
+([NG-0001](non-goals/NG-0001.yml)) — the core stays a single-purpose, offline tool
+over one graph, consumed here as a library.
+
+## Working here
+
+```sh
+pip install .            # pulls throughline transitively; installs tl and tl-compose
+tl-compose context       # agent brief, generated from throughline.toml
+tl-compose check --strict # gate the whole graph
+tl-compose docs --check  # gate published-document freshness
+tl-compose docs          # regenerate docs/spec.md from the graph
+```

throughline_compose-0.1.0/pyproject.toml

@@ -0,0 +1,52 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "throughline-compose"
+version = "0.1.0"
+description = "Compose one requirements graph from many reusable throughline sources: importer-assigned namespaces, source-native UIDs, and a union checked by throughline's own validator. Ships the tl-compose CLI, a strict superset of tl."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Time Back Solutions Limited" }]
+keywords = [
+  "requirements",
+  "requirements-management",
+  "traceability",
+  "composition",
+  "git-native",
+  "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 :: Software Development :: Quality Assurance",
+]
+dependencies = ["throughline>=0.5.0"]  # is_external / is_namespace_qualified public since 0.4.0 (SR-0004); tl:count badge needs 0.5.0 (SR-0109)
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0"]
+
+[project.urls]
+Homepage = "https://github.com/rhodium-org/throughline-compose"
+Repository = "https://github.com/rhodium-org/throughline-compose"
+Issues = "https://github.com/rhodium-org/throughline-compose/issues"
+
+[project.scripts]
+tl-compose = "throughline_compose.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

throughline_compose-0.1.0/setup.cfg

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

throughline_compose-0.1.0/src/throughline_compose/__init__.py

@@ -0,0 +1,15 @@
+# Copyright (c) 2026 Time Back Solutions Limited
+# SPDX-License-Identifier: Apache-2.0
+"""throughline-compose — compose one requirements graph from many reusable sources.
+
+Builds on ``throughline`` as an unmodified library (SR-0004): it prepares a union
+``Project`` from the declared sources and runs throughline's own ``validate``,
+``Index``, and ``fingerprint`` over it. The ``tl-compose`` CLI is a strict superset
+of ``tl`` (SR-0003) — it forwards local commands to throughline unchanged and
+overrides only the union-aware ones.
+"""
+from __future__ import annotations
+
+__version__ = "0.0.1"
+
+__all__ = ["__version__"]