throughline-ms-copilot 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (25) hide show
  1. throughline_ms_copilot-0.1.0/LICENSE +201 -0
  2. throughline_ms_copilot-0.1.0/MANIFEST.in +4 -0
  3. throughline_ms_copilot-0.1.0/NOTICE +16 -0
  4. throughline_ms_copilot-0.1.0/PKG-INFO +121 -0
  5. throughline_ms_copilot-0.1.0/README.md +94 -0
  6. throughline_ms_copilot-0.1.0/pyproject.toml +55 -0
  7. throughline_ms_copilot-0.1.0/setup.cfg +4 -0
  8. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/__init__.py +15 -0
  9. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/cli.py +199 -0
  10. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/export.py +170 -0
  11. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/inbox.py +184 -0
  12. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/provenance.py +118 -0
  13. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/reply.py +130 -0
  14. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot/tool.py +88 -0
  15. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/PKG-INFO +121 -0
  16. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/SOURCES.txt +23 -0
  17. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/dependency_links.txt +1 -0
  18. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/entry_points.txt +3 -0
  19. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/requires.txt +4 -0
  20. throughline_ms_copilot-0.1.0/src/throughline_ms_copilot.egg-info/top_level.txt +1 -0
  21. throughline_ms_copilot-0.1.0/tests/conftest.py +151 -0
  22. throughline_ms_copilot-0.1.0/tests/test_apply.py +122 -0
  23. throughline_ms_copilot-0.1.0/tests/test_export.py +192 -0
  24. throughline_ms_copilot-0.1.0/tests/test_inbox.py +171 -0
  25. throughline_ms_copilot-0.1.0/tests/test_reply.py +68 -0
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 The throughline-transform authors
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,4 @@
1
+ # setuptools' default sdist file set ships modules matching test*.py but not the
2
+ # shared conftest that defines their fixtures, so the shipped suite would error
3
+ # at collection. Ship it so the suite runs green from the sdist.
4
+ include tests/conftest.py
@@ -0,0 +1,16 @@
1
+ throughline-ms-copilot
2
+ Copyright 2026 Henry J Grech-Cini
3
+ Created by Dr Henry J Grech-Cini (ORCID https://orcid.org/0009-0007-1565-7530).
4
+
5
+ This product includes software developed by Henry J Grech-Cini.
6
+
7
+ Licensed under the Apache License, Version 2.0. See the LICENSE file for the
8
+ full terms.
9
+
10
+ throughline-ms-copilot is a command-line companion for throughline (the `tl`
11
+ CLI). It builds on throughline's published command line; no third-party source
12
+ code was copied. Its export form was first written in throughline-transform
13
+ 0.6.0, by the same author, and moved here.
14
+
15
+ Microsoft 365 Copilot is a product of Microsoft Corporation. This project is
16
+ not affiliated with or endorsed by Microsoft.
@@ -0,0 +1,121 @@
1
+ Metadata-Version: 2.4
2
+ Name: throughline-ms-copilot
3
+ Version: 0.1.0
4
+ Summary: Hand a throughline requirements graph to Microsoft 365 Copilot as a folder it reads whole — one file per register — and apply the change set it sends back through tl apply. Ships the tl-ms-copilot CLI.
5
+ Author-email: Henry J Grech-Cini <henry.grechcini@gmail.com>
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/rhodium-org/throughline-ms-copilot
8
+ Project-URL: Repository, https://github.com/rhodium-org/throughline-ms-copilot
9
+ Project-URL: Issues, https://github.com/rhodium-org/throughline-ms-copilot/issues
10
+ Keywords: requirements,requirements-management,copilot,microsoft-365-copilot,traceability,idd,intent-driven-development,throughline
11
+ Classifier: Development Status :: 3 - Alpha
12
+ Classifier: Environment :: Console
13
+ Classifier: Intended Audience :: Developers
14
+ Classifier: Operating System :: OS Independent
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Programming Language :: Python :: 3.11
17
+ Classifier: Programming Language :: Python :: 3.12
18
+ Classifier: Topic :: Software Development :: Documentation
19
+ Requires-Python: >=3.11
20
+ Description-Content-Type: text/markdown
21
+ License-File: LICENSE
22
+ License-File: NOTICE
23
+ Requires-Dist: throughline>=3.18.0
24
+ Provides-Extra: dev
25
+ Requires-Dist: pytest>=8.0; extra == "dev"
26
+ Dynamic: license-file
27
+
28
+ # throughline-ms-copilot
29
+
30
+ Work on a [throughline](https://github.com/rhodium-org/throughline) requirements
31
+ graph with **Microsoft 365 Copilot**, in an environment where Copilot is the only
32
+ assistant you have: it reads at most fifty files, runs no command and answers
33
+ only in text. `tl-ms-copilot` writes the graph as a folder Copilot reads whole,
34
+ and carries the changes Copilot sends back into the graph as proposals, through
35
+ `tl apply`, all or nothing.
36
+
37
+ ```bash
38
+ pipx install throughline-ms-copilot
39
+ tl-ms-copilot export -C idd ~/OneDrive/graph-exchange # the folder Copilot reads
40
+ # … give Copilot every file in graph-exchange/export/, ask for changes,
41
+ # save each answer into graph-exchange/inbox/ …
42
+ tl-ms-copilot ingest -C idd ~/OneDrive/graph-exchange --dry-run
43
+ tl-ms-copilot ingest -C idd ~/OneDrive/graph-exchange # carried out by tl apply
44
+ tl -C idd check
45
+ ```
46
+
47
+ The graph's content moves only between your computer and GitHub. The package
48
+ runs `tl` in-process and starts no process, so it runs unchanged under Pyodide
49
+ in a browser tab beside the folder you chose — which is how
50
+ [sync.iddn.uk](https://sync.iddn.uk/) offers it on a laptop where nothing can be
51
+ installed.
52
+
53
+ ## The exchange folder
54
+
55
+ ```
56
+ graph-exchange/
57
+ ├── export/ written by `export`, replaced whole each time
58
+ │ ├── manifest.json what the export was true of, and how to answer
59
+ │ ├── INT.json REQ.json TEST.json … one file per register
60
+ │ └── source-<ns>.json the clauses an adopted source lends
61
+ └── inbox/ Copilot's answers, saved by you
62
+ ├── new/REQ.md new items for one register
63
+ ├── updates/REQ.md amend, link, unlink, delete on one register's items
64
+ ├── anything.md a whole change set, any registers
65
+ └── applied/<when>/ where `ingest` moves what it carried out
66
+ ```
67
+
68
+ **Why one file per register.** Copilot's cap counts files, not items. A graph
69
+ holds hundreds of item files but fewer than fifty registers, so one file per
70
+ register is the smallest layout Copilot can read whole. `--wrap md` writes each
71
+ file as Markdown holding one fenced JSON block, for a Copilot that will not read
72
+ `.json` files. `--only UID,…` narrows the export to the items named.
73
+
74
+ **Why changes come back as a change set, not as files.** Copilot's answer is
75
+ length-capped: a rewritten register file cut off half-way would read as the
76
+ deletion of everything after the cut. A change set names only what changes, and
77
+ `tl apply` refuses the whole set if any item it touches changed since the export.
78
+ The manifest carries the form, as `tl apply --describe` states it, and tells
79
+ Copilot to answer in one fenced `json` block.
80
+
81
+ **Why answers are saved by register.** For long work, ask Copilot for one
82
+ register at a time — the new items for REQ, then the changes to REQ's items —
83
+ and save each answer as `inbox/new/REQ.md` or `inbox/updates/REQ.md`. Paste the
84
+ whole answer; the change set is found inside it. `ingest` gathers every file into
85
+ one change set: new items first, each after any new item it links to, then the
86
+ updates, then whole sets. It checks each file holds what its place says, and
87
+ moves what it applied into `inbox/applied/` so nothing is applied twice.
88
+
89
+ **Why there are no ID conflicts.** Copilot never chooses a UID. A new item is
90
+ named by a `label`, and another item in any answer links to it as `$label`;
91
+ `tl` allocates the real UID when the set is carried out, against the graph as it
92
+ then stands.
93
+
94
+ Everything Copilot drafts arrives with origin `ai` and waits as `proposed`: a
95
+ person decides. Decisions — ratifying, withdrawing — are never in a change set.
96
+
97
+ ## Commands
98
+
99
+ | Command | What it does |
100
+ | --- | --- |
101
+ | `export [-C DIR] EXCHANGE [--wrap json\|md] [--only UID,…]` | Writes `EXCHANGE/export/` and creates `EXCHANGE/inbox/new` and `inbox/updates`. |
102
+ | `ingest [-C DIR] EXCHANGE [--dry-run]` | Gathers `EXCHANGE/inbox/` into one change set and has `tl apply` carry it out. |
103
+ | `apply [-C DIR] [REPLY\|-] [--dry-run] [--extract]` | The same for one saved reply. `--extract` prints the change set found and stops. |
104
+
105
+ `export` reads the repository, ref, commit and working-tree state from git;
106
+ `--repository`, `--ref`, `--commit` and `--tree` state them instead, as a host
107
+ with no git — the browser — does.
108
+
109
+ ## Working on it
110
+
111
+ Its requirements live in [`idd/`](idd); see [AGENTS.md](AGENTS.md).
112
+
113
+ ```bash
114
+ python -m venv .venv && . .venv/bin/activate
115
+ pip install -e ".[dev]"
116
+ pytest -q
117
+ tl -C idd check
118
+ ```
119
+
120
+ Apache-2.0. Microsoft 365 Copilot is a product of Microsoft Corporation; this
121
+ project is not affiliated with or endorsed by Microsoft.
@@ -0,0 +1,94 @@
1
+ # throughline-ms-copilot
2
+
3
+ Work on a [throughline](https://github.com/rhodium-org/throughline) requirements
4
+ graph with **Microsoft 365 Copilot**, in an environment where Copilot is the only
5
+ assistant you have: it reads at most fifty files, runs no command and answers
6
+ only in text. `tl-ms-copilot` writes the graph as a folder Copilot reads whole,
7
+ and carries the changes Copilot sends back into the graph as proposals, through
8
+ `tl apply`, all or nothing.
9
+
10
+ ```bash
11
+ pipx install throughline-ms-copilot
12
+ tl-ms-copilot export -C idd ~/OneDrive/graph-exchange # the folder Copilot reads
13
+ # … give Copilot every file in graph-exchange/export/, ask for changes,
14
+ # save each answer into graph-exchange/inbox/ …
15
+ tl-ms-copilot ingest -C idd ~/OneDrive/graph-exchange --dry-run
16
+ tl-ms-copilot ingest -C idd ~/OneDrive/graph-exchange # carried out by tl apply
17
+ tl -C idd check
18
+ ```
19
+
20
+ The graph's content moves only between your computer and GitHub. The package
21
+ runs `tl` in-process and starts no process, so it runs unchanged under Pyodide
22
+ in a browser tab beside the folder you chose — which is how
23
+ [sync.iddn.uk](https://sync.iddn.uk/) offers it on a laptop where nothing can be
24
+ installed.
25
+
26
+ ## The exchange folder
27
+
28
+ ```
29
+ graph-exchange/
30
+ ├── export/ written by `export`, replaced whole each time
31
+ │ ├── manifest.json what the export was true of, and how to answer
32
+ │ ├── INT.json REQ.json TEST.json … one file per register
33
+ │ └── source-<ns>.json the clauses an adopted source lends
34
+ └── inbox/ Copilot's answers, saved by you
35
+ ├── new/REQ.md new items for one register
36
+ ├── updates/REQ.md amend, link, unlink, delete on one register's items
37
+ ├── anything.md a whole change set, any registers
38
+ └── applied/<when>/ where `ingest` moves what it carried out
39
+ ```
40
+
41
+ **Why one file per register.** Copilot's cap counts files, not items. A graph
42
+ holds hundreds of item files but fewer than fifty registers, so one file per
43
+ register is the smallest layout Copilot can read whole. `--wrap md` writes each
44
+ file as Markdown holding one fenced JSON block, for a Copilot that will not read
45
+ `.json` files. `--only UID,…` narrows the export to the items named.
46
+
47
+ **Why changes come back as a change set, not as files.** Copilot's answer is
48
+ length-capped: a rewritten register file cut off half-way would read as the
49
+ deletion of everything after the cut. A change set names only what changes, and
50
+ `tl apply` refuses the whole set if any item it touches changed since the export.
51
+ The manifest carries the form, as `tl apply --describe` states it, and tells
52
+ Copilot to answer in one fenced `json` block.
53
+
54
+ **Why answers are saved by register.** For long work, ask Copilot for one
55
+ register at a time — the new items for REQ, then the changes to REQ's items —
56
+ and save each answer as `inbox/new/REQ.md` or `inbox/updates/REQ.md`. Paste the
57
+ whole answer; the change set is found inside it. `ingest` gathers every file into
58
+ one change set: new items first, each after any new item it links to, then the
59
+ updates, then whole sets. It checks each file holds what its place says, and
60
+ moves what it applied into `inbox/applied/` so nothing is applied twice.
61
+
62
+ **Why there are no ID conflicts.** Copilot never chooses a UID. A new item is
63
+ named by a `label`, and another item in any answer links to it as `$label`;
64
+ `tl` allocates the real UID when the set is carried out, against the graph as it
65
+ then stands.
66
+
67
+ Everything Copilot drafts arrives with origin `ai` and waits as `proposed`: a
68
+ person decides. Decisions — ratifying, withdrawing — are never in a change set.
69
+
70
+ ## Commands
71
+
72
+ | Command | What it does |
73
+ | --- | --- |
74
+ | `export [-C DIR] EXCHANGE [--wrap json\|md] [--only UID,…]` | Writes `EXCHANGE/export/` and creates `EXCHANGE/inbox/new` and `inbox/updates`. |
75
+ | `ingest [-C DIR] EXCHANGE [--dry-run]` | Gathers `EXCHANGE/inbox/` into one change set and has `tl apply` carry it out. |
76
+ | `apply [-C DIR] [REPLY\|-] [--dry-run] [--extract]` | The same for one saved reply. `--extract` prints the change set found and stops. |
77
+
78
+ `export` reads the repository, ref, commit and working-tree state from git;
79
+ `--repository`, `--ref`, `--commit` and `--tree` state them instead, as a host
80
+ with no git — the browser — does.
81
+
82
+ ## Working on it
83
+
84
+ Its requirements live in [`idd/`](idd); see [AGENTS.md](AGENTS.md).
85
+
86
+ ```bash
87
+ python -m venv .venv && . .venv/bin/activate
88
+ pip install -e ".[dev]"
89
+ pytest -q
90
+ tl -C idd check
91
+ ```
92
+
93
+ Apache-2.0. Microsoft 365 Copilot is a product of Microsoft Corporation; this
94
+ project is not affiliated with or endorsed by Microsoft.
@@ -0,0 +1,55 @@
1
+ [build-system]
2
+ requires = ["setuptools>=77"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "throughline-ms-copilot"
7
+ version = "0.1.0"
8
+ description = "Hand a throughline requirements graph to Microsoft 365 Copilot as a folder it reads whole — one file per register — and apply the change set it sends back through tl apply. Ships the tl-ms-copilot CLI."
9
+ readme = "README.md"
10
+ requires-python = ">=3.11"
11
+ license = "Apache-2.0"
12
+ license-files = ["LICENSE", "NOTICE"]
13
+ authors = [{ name = "Henry J Grech-Cini", email = "henry.grechcini@gmail.com" }]
14
+ keywords = [
15
+ "requirements",
16
+ "requirements-management",
17
+ "copilot",
18
+ "microsoft-365-copilot",
19
+ "traceability",
20
+ "idd",
21
+ "intent-driven-development",
22
+ "throughline",
23
+ ]
24
+ classifiers = [
25
+ "Development Status :: 3 - Alpha",
26
+ "Environment :: Console",
27
+ "Intended Audience :: Developers",
28
+ "Operating System :: OS Independent",
29
+ "Programming Language :: Python :: 3",
30
+ "Programming Language :: Python :: 3.11",
31
+ "Programming Language :: Python :: 3.12",
32
+ "Topic :: Software Development :: Documentation",
33
+ ]
34
+ # Every item in the export is `tl dump`'s, fingerprint included (throughline
35
+ # SR-0251); the change-set form is `tl apply --describe`'s and the change is made
36
+ # by `tl apply` (SR-0252). Both arrived in 3.18.0.
37
+ dependencies = ["throughline>=3.18.0"]
38
+
39
+ [project.optional-dependencies]
40
+ dev = ["pytest>=8.0"]
41
+
42
+ [project.urls]
43
+ Homepage = "https://github.com/rhodium-org/throughline-ms-copilot"
44
+ Repository = "https://github.com/rhodium-org/throughline-ms-copilot"
45
+ Issues = "https://github.com/rhodium-org/throughline-ms-copilot/issues"
46
+
47
+ [project.scripts]
48
+ tl-ms-copilot = "throughline_ms_copilot.cli:main"
49
+ throughline-ms-copilot = "throughline_ms_copilot.cli:main"
50
+
51
+ [tool.setuptools.packages.find]
52
+ where = ["src"]
53
+
54
+ [tool.pytest.ini_options]
55
+ testpaths = ["tests"]
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -0,0 +1,15 @@
1
+ # Copyright (c) 2026 Henry J Grech-Cini
2
+ # SPDX-License-Identifier: Apache-2.0
3
+ """throughline-ms-copilot: a throughline graph handed to Microsoft 365 Copilot and back.
4
+
5
+ Copilot in a controlled environment reads at most fifty files, cannot run ``tl``
6
+ and returns only text. This package writes the graph as a folder it reads whole,
7
+ one file per register, and carries the change set it answers with through
8
+ ``tl apply``. Everything of an item is the tool's: the export is ``tl dump``
9
+ unreshaped, and the change is made by ``tl apply``, never here.
10
+ """
11
+
12
+ from .reply import ReplyError
13
+ from .tool import CopilotError
14
+
15
+ __all__ = ["CopilotError", "ReplyError"]