stemmata 0.0.1__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.
- stemmata-0.0.1/LICENSE +201 -0
- stemmata-0.0.1/PKG-INFO +200 -0
- stemmata-0.0.1/README.md +173 -0
- stemmata-0.0.1/pyproject.toml +46 -0
- stemmata-0.0.1/setup.cfg +4 -0
- stemmata-0.0.1/src/stemmata/__init__.py +6 -0
- stemmata-0.0.1/src/stemmata/__main__.py +3 -0
- stemmata-0.0.1/src/stemmata/bundle.py +200 -0
- stemmata-0.0.1/src/stemmata/cache.py +238 -0
- stemmata-0.0.1/src/stemmata/cli.py +329 -0
- stemmata-0.0.1/src/stemmata/deps_check.py +153 -0
- stemmata-0.0.1/src/stemmata/envelope.py +50 -0
- stemmata-0.0.1/src/stemmata/errors.py +209 -0
- stemmata-0.0.1/src/stemmata/interp.py +251 -0
- stemmata-0.0.1/src/stemmata/manifest.py +273 -0
- stemmata-0.0.1/src/stemmata/merge.py +103 -0
- stemmata-0.0.1/src/stemmata/npmrc.py +154 -0
- stemmata-0.0.1/src/stemmata/prompt_doc.py +246 -0
- stemmata-0.0.1/src/stemmata/publish.py +304 -0
- stemmata-0.0.1/src/stemmata/registry.py +217 -0
- stemmata-0.0.1/src/stemmata/resolver.py +418 -0
- stemmata-0.0.1/src/stemmata/schema_check.py +169 -0
- stemmata-0.0.1/src/stemmata/yaml_loader.py +194 -0
- stemmata-0.0.1/src/stemmata.egg-info/PKG-INFO +200 -0
- stemmata-0.0.1/src/stemmata.egg-info/SOURCES.txt +39 -0
- stemmata-0.0.1/src/stemmata.egg-info/dependency_links.txt +1 -0
- stemmata-0.0.1/src/stemmata.egg-info/entry_points.txt +2 -0
- stemmata-0.0.1/src/stemmata.egg-info/requires.txt +4 -0
- stemmata-0.0.1/src/stemmata.egg-info/top_level.txt +1 -0
- stemmata-0.0.1/tests/test_bundle.py +114 -0
- stemmata-0.0.1/tests/test_cache.py +99 -0
- stemmata-0.0.1/tests/test_cli_integration.py +424 -0
- stemmata-0.0.1/tests/test_deps_check.py +154 -0
- stemmata-0.0.1/tests/test_interp.py +175 -0
- stemmata-0.0.1/tests/test_manifest.py +201 -0
- stemmata-0.0.1/tests/test_merge.py +129 -0
- stemmata-0.0.1/tests/test_npmrc.py +102 -0
- stemmata-0.0.1/tests/test_prompt_doc.py +159 -0
- stemmata-0.0.1/tests/test_publish.py +217 -0
- stemmata-0.0.1/tests/test_resolver.py +285 -0
- stemmata-0.0.1/tests/test_yaml_loader.py +50 -0
stemmata-0.0.1/LICENSE
ADDED
|
@@ -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 [yyyy] [name of copyright owner]
|
|
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.
|
stemmata-0.0.1/PKG-INFO
ADDED
|
@@ -0,0 +1,200 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: stemmata
|
|
3
|
+
Version: 0.0.1
|
|
4
|
+
Summary: Hierarchical prompt resolver CLI
|
|
5
|
+
Author: Pedro Javier Martos Velasco
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/pjmartos/genealogy
|
|
8
|
+
Project-URL: Repository, https://github.com/pjmartos/genealogy
|
|
9
|
+
Project-URL: Issues, https://github.com/pjmartos/genealogy/issues
|
|
10
|
+
Keywords: prompt,yaml,inheritance,composition,llm,cli
|
|
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.12
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
18
|
+
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|
|
19
|
+
Classifier: Topic :: Text Processing :: Markup
|
|
20
|
+
Requires-Python: >=3.12
|
|
21
|
+
Description-Content-Type: text/markdown
|
|
22
|
+
License-File: LICENSE
|
|
23
|
+
Requires-Dist: PyYAML>=6.0
|
|
24
|
+
Provides-Extra: publish
|
|
25
|
+
Requires-Dist: jsonschema>=4.18; extra == "publish"
|
|
26
|
+
Dynamic: license-file
|
|
27
|
+
|
|
28
|
+
# stemmata
|
|
29
|
+
|
|
30
|
+
[](https://pypi.org/project/stemmata/)
|
|
31
|
+
[](https://www.python.org/downloads/)
|
|
32
|
+
[](LICENSE)
|
|
33
|
+
|
|
34
|
+
Prompt reuse across repositories is a mess. You copy a YAML prompt into a new project, tweak it, and within a week the original and the copy have diverged. Multiply that by a dozen services and you're maintaining the same boilerplate in twenty places.
|
|
35
|
+
|
|
36
|
+
`stemmata` fixes this with hierarchical composition: prompts declare ancestors (by relative path or by registry coordinate), and the CLI resolves the full inheritance chain into a single, deterministic YAML document. Ancestor prompts are distributed as npm packages through any private registry you already run.
|
|
37
|
+
|
|
38
|
+
## Table of Contents
|
|
39
|
+
|
|
40
|
+
- [Features](#features)
|
|
41
|
+
- [Installation](#installation)
|
|
42
|
+
- [Quick Start](#quick-start)
|
|
43
|
+
- [CLI Reference](#cli-reference)
|
|
44
|
+
- [Prompt Format](#prompt-format)
|
|
45
|
+
- [Merge Semantics](#merge-semantics)
|
|
46
|
+
- [Exit Codes](#exit-codes)
|
|
47
|
+
- [Configuration](#configuration)
|
|
48
|
+
- [Testing](#testing)
|
|
49
|
+
|
|
50
|
+
## Features
|
|
51
|
+
|
|
52
|
+
- **Hierarchical composition**: prompts declare `ancestors` as paths or `(package, version, prompt)` coordinates; the full transitive closure is resolved eagerly via breadth-first search.
|
|
53
|
+
- **Deterministic merging**: nearest-wins for scalars and lists, deep-merge for maps, with breadth-first search distance plus reference occurring-ordering (for breaking ties) so the output is reproducible.
|
|
54
|
+
- **Placeholder interpolation**: `${path}` references resolve against the merged namespace, with structural, textual, and list-splat forms.
|
|
55
|
+
- **npm registry transport**: speaks the standard npm REST API; credentials read from `~/.npmrc`.
|
|
56
|
+
|
|
57
|
+
## Installation
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
pip install stemmata
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Requires **Python 3.12+** (for `tarfile.data_filter`). Sole third-party dependency is `PyYAML`.
|
|
64
|
+
|
|
65
|
+
## Quick Start
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
# You have a local prompt that inherits from a base — resolve it:
|
|
69
|
+
stemmata resolve ./prompts/onboarding.yaml
|
|
70
|
+
|
|
71
|
+
# Or resolve a prompt published to your registry by coordinate:
|
|
72
|
+
stemmata resolve '@acme/prompts-core@1.2.3#onboarding'
|
|
73
|
+
|
|
74
|
+
# Need machine-readable output for a script or pipeline:
|
|
75
|
+
stemmata --output json resolve ./prompts/onboarding.yaml
|
|
76
|
+
|
|
77
|
+
# Wipe the local cache (by default stored under ~/.cache/stemmata):
|
|
78
|
+
stemmata cache clear
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## CLI Reference
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
stemmata [GLOBAL FLAGS] <subcommand> [ARGS]
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Global flags
|
|
88
|
+
|
|
89
|
+
| Flag | Default | Description |
|
|
90
|
+
|-----------------------------|----------------|-------------------------------------------------------------------|
|
|
91
|
+
| `--output {yaml,json,text}` | per-subcommand | Output format (`yaml` for `resolve`, `json` for everything else). |
|
|
92
|
+
| `--verbose` | off | Timestamped diagnostics on stderr. |
|
|
93
|
+
| `--offline` | off | Forbid network access; exit `22` if a fetch would be needed. |
|
|
94
|
+
| `--refresh` | off | Re-fetch artifacts even if cached. |
|
|
95
|
+
| `--version` | — | Print version and exit. |
|
|
96
|
+
|
|
97
|
+
### `resolve <target>`
|
|
98
|
+
|
|
99
|
+
Resolves a single prompt. Target is either a local path (`./prompts/onboarding.yaml`) or a registry coordinate (`@<scope>/<name>@<version>#<prompt-id>`).
|
|
100
|
+
|
|
101
|
+
Resource limits: `--max-prompts` (default 1000), `--max-depth` (default 50), `--http-timeout` (default 30s), `--timeout` (default 5m).
|
|
102
|
+
|
|
103
|
+
On success, stdout carries the resolved YAML (or a JSON envelope with `{root, content, ancestors[]}`). On failure, stdout carries a JSON error envelope regardless of `--output`, and stderr gets a one-line human-readable summary.
|
|
104
|
+
|
|
105
|
+
### `publish [path]`
|
|
106
|
+
|
|
107
|
+
Builds and uploads the package at `path` (default `.`) to the registry routed by `~/.npmrc`. Before any bytes leave the machine, every prompt listed in `package.json` is checked for: (1) ancestor cycles, (2) intra-document type conflicts, (3) placeholder resolvability against the fully resolved namespace, (4) `dependencies` consistency with the cross-package references found in the prompts, (5) manifest closure under relative-path references — every local `ancestors` entry must resolve to a path that is itself declared in `prompts`, since only manifest-listed files are bundled, and (6) `$schema` validation against the prompt's content contract. All errors discovered in the pass are aggregated into a single envelope; the headline exit code is the most severe one (cycle > schema > reference > merge > placeholder).
|
|
108
|
+
|
|
109
|
+
Flags: `--dry-run` (build the tarball but skip upload), `--strict-schema` (treat unfetchable / unvalidated `$schema` as an error rather than a warning), `--tarball <path>` (write the built tarball to `path`). The tarball is deterministic: identical inputs produce byte-identical output.
|
|
110
|
+
|
|
111
|
+
`$schema` enforcement requires `pip install stemmata[publish]` (adds `jsonschema`). Without it, `publish` warns and skips schema validation in default mode, or errors in `--strict-schema` mode.
|
|
112
|
+
|
|
113
|
+
### `cache clear`
|
|
114
|
+
|
|
115
|
+
Evicts every cached entry.
|
|
116
|
+
|
|
117
|
+
## Prompt Format
|
|
118
|
+
|
|
119
|
+
A prompt is a structured mapping (only YAML is supported as of now) with reserved envelope keys plus arbitrary content:
|
|
120
|
+
|
|
121
|
+
```yaml
|
|
122
|
+
ancestors:
|
|
123
|
+
- ../base.yaml # relative path (within package)
|
|
124
|
+
- package: "@acme/common" # cross-package coordinate
|
|
125
|
+
version: "1.0.4"
|
|
126
|
+
prompt: "defaults"
|
|
127
|
+
$schema: "https://schemas.example/foo.v1.json" # optional, enforced at publish time if present
|
|
128
|
+
|
|
129
|
+
database:
|
|
130
|
+
host: "db.internal"
|
|
131
|
+
port: 5432
|
|
132
|
+
body: |
|
|
133
|
+
Region is ${vars.region}; DB is ${database.host}:${database.port}.
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
`ancestors` and `$schema` are stripped from the namespace; every other key is addressable via dotted path.
|
|
137
|
+
|
|
138
|
+
### Package manifest (`package.json`)
|
|
139
|
+
|
|
140
|
+
```json
|
|
141
|
+
{
|
|
142
|
+
"name": "@acme/prompts-core",
|
|
143
|
+
"version": "1.2.3",
|
|
144
|
+
"license": "UNLICENSED",
|
|
145
|
+
"dependencies": { "@acme/common": "1.0.4" },
|
|
146
|
+
"prompts": [
|
|
147
|
+
{ "id": "base", "path": "base.yaml", "contentType": "yaml" },
|
|
148
|
+
{ "id": "onboarding", "path": "extra/onboarding.yaml", "contentType": "yaml" }
|
|
149
|
+
]
|
|
150
|
+
}
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
`name` must be `@<scope>/<n>`. `version` is strict SemVer, no ranges. `prompts` is non-empty; `id` defaults to basename without extension and must match `[a-z0-9][a-z0-9_-]*`.
|
|
154
|
+
|
|
155
|
+
## Merge Semantics
|
|
156
|
+
|
|
157
|
+
Reachable prompts are layered by breadth-first search distance from the root (distance 0 = root, wins everything). Ties at the same distance break by enqueue order.
|
|
158
|
+
|
|
159
|
+
**Maps** are deep-merged, with the nearer value winning at each leaf:
|
|
160
|
+
|
|
161
|
+
```yaml
|
|
162
|
+
# ancestor (distance 1) # root (distance 0)
|
|
163
|
+
database: database:
|
|
164
|
+
host: "base.internal" host: "override.internal"
|
|
165
|
+
port: 5432 ssl: true
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
Resolved: `database.host` = `"override.internal"` (nearer wins), `database.port` = `5432` (survives from ancestor), `database.ssl` = `true` (only root provides it).
|
|
169
|
+
|
|
170
|
+
**Lists** replace wholesale — no element-level merge. **`null`** at a nearer layer shadows the entire subtree beneath it.
|
|
171
|
+
|
|
172
|
+
For the full interpolation reference (structural vs. textual placeholders, list splat, non-splat `${=...}` form, escaping, version conflict resolution), see [`docs/interpolation.md`](docs/interpolation.md).
|
|
173
|
+
|
|
174
|
+
## Exit Codes
|
|
175
|
+
|
|
176
|
+
| Code | Meaning |
|
|
177
|
+
|------|-------------------------------------|
|
|
178
|
+
| `0` | Success |
|
|
179
|
+
| `1` | Generic / unexpected failure |
|
|
180
|
+
| `2` | Usage error |
|
|
181
|
+
| `10` | Schema validation error |
|
|
182
|
+
| `11` | Unknown ancestor or prompt id |
|
|
183
|
+
| `12` | Cycle detected |
|
|
184
|
+
| `14` | Unresolvable placeholder |
|
|
185
|
+
| `15` | Merge / interpolation type mismatch |
|
|
186
|
+
| `20` | Network / registry error |
|
|
187
|
+
| `21` | Cache error |
|
|
188
|
+
| `22` | Offline-mode violation |
|
|
189
|
+
|
|
190
|
+
On failure, stdout always carries a JSON error envelope with `{status, exit_code, command, error: {code, category, message, ...}}` regardless of `--output`. Stderr gets a single-line human summary.
|
|
191
|
+
|
|
192
|
+
## Configuration
|
|
193
|
+
|
|
194
|
+
Registry routing and credentials come from `~/.npmrc` for both fetch and publish.
|
|
195
|
+
|
|
196
|
+
## Testing
|
|
197
|
+
|
|
198
|
+
```
|
|
199
|
+
PYTHONPATH=src python -m pytest tests/ -q
|
|
200
|
+
```
|
stemmata-0.0.1/README.md
ADDED
|
@@ -0,0 +1,173 @@
|
|
|
1
|
+
# stemmata
|
|
2
|
+
|
|
3
|
+
[](https://pypi.org/project/stemmata/)
|
|
4
|
+
[](https://www.python.org/downloads/)
|
|
5
|
+
[](LICENSE)
|
|
6
|
+
|
|
7
|
+
Prompt reuse across repositories is a mess. You copy a YAML prompt into a new project, tweak it, and within a week the original and the copy have diverged. Multiply that by a dozen services and you're maintaining the same boilerplate in twenty places.
|
|
8
|
+
|
|
9
|
+
`stemmata` fixes this with hierarchical composition: prompts declare ancestors (by relative path or by registry coordinate), and the CLI resolves the full inheritance chain into a single, deterministic YAML document. Ancestor prompts are distributed as npm packages through any private registry you already run.
|
|
10
|
+
|
|
11
|
+
## Table of Contents
|
|
12
|
+
|
|
13
|
+
- [Features](#features)
|
|
14
|
+
- [Installation](#installation)
|
|
15
|
+
- [Quick Start](#quick-start)
|
|
16
|
+
- [CLI Reference](#cli-reference)
|
|
17
|
+
- [Prompt Format](#prompt-format)
|
|
18
|
+
- [Merge Semantics](#merge-semantics)
|
|
19
|
+
- [Exit Codes](#exit-codes)
|
|
20
|
+
- [Configuration](#configuration)
|
|
21
|
+
- [Testing](#testing)
|
|
22
|
+
|
|
23
|
+
## Features
|
|
24
|
+
|
|
25
|
+
- **Hierarchical composition**: prompts declare `ancestors` as paths or `(package, version, prompt)` coordinates; the full transitive closure is resolved eagerly via breadth-first search.
|
|
26
|
+
- **Deterministic merging**: nearest-wins for scalars and lists, deep-merge for maps, with breadth-first search distance plus reference occurring-ordering (for breaking ties) so the output is reproducible.
|
|
27
|
+
- **Placeholder interpolation**: `${path}` references resolve against the merged namespace, with structural, textual, and list-splat forms.
|
|
28
|
+
- **npm registry transport**: speaks the standard npm REST API; credentials read from `~/.npmrc`.
|
|
29
|
+
|
|
30
|
+
## Installation
|
|
31
|
+
|
|
32
|
+
```
|
|
33
|
+
pip install stemmata
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Requires **Python 3.12+** (for `tarfile.data_filter`). Sole third-party dependency is `PyYAML`.
|
|
37
|
+
|
|
38
|
+
## Quick Start
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
# You have a local prompt that inherits from a base — resolve it:
|
|
42
|
+
stemmata resolve ./prompts/onboarding.yaml
|
|
43
|
+
|
|
44
|
+
# Or resolve a prompt published to your registry by coordinate:
|
|
45
|
+
stemmata resolve '@acme/prompts-core@1.2.3#onboarding'
|
|
46
|
+
|
|
47
|
+
# Need machine-readable output for a script or pipeline:
|
|
48
|
+
stemmata --output json resolve ./prompts/onboarding.yaml
|
|
49
|
+
|
|
50
|
+
# Wipe the local cache (by default stored under ~/.cache/stemmata):
|
|
51
|
+
stemmata cache clear
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
## CLI Reference
|
|
55
|
+
|
|
56
|
+
```
|
|
57
|
+
stemmata [GLOBAL FLAGS] <subcommand> [ARGS]
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### Global flags
|
|
61
|
+
|
|
62
|
+
| Flag | Default | Description |
|
|
63
|
+
|-----------------------------|----------------|-------------------------------------------------------------------|
|
|
64
|
+
| `--output {yaml,json,text}` | per-subcommand | Output format (`yaml` for `resolve`, `json` for everything else). |
|
|
65
|
+
| `--verbose` | off | Timestamped diagnostics on stderr. |
|
|
66
|
+
| `--offline` | off | Forbid network access; exit `22` if a fetch would be needed. |
|
|
67
|
+
| `--refresh` | off | Re-fetch artifacts even if cached. |
|
|
68
|
+
| `--version` | — | Print version and exit. |
|
|
69
|
+
|
|
70
|
+
### `resolve <target>`
|
|
71
|
+
|
|
72
|
+
Resolves a single prompt. Target is either a local path (`./prompts/onboarding.yaml`) or a registry coordinate (`@<scope>/<name>@<version>#<prompt-id>`).
|
|
73
|
+
|
|
74
|
+
Resource limits: `--max-prompts` (default 1000), `--max-depth` (default 50), `--http-timeout` (default 30s), `--timeout` (default 5m).
|
|
75
|
+
|
|
76
|
+
On success, stdout carries the resolved YAML (or a JSON envelope with `{root, content, ancestors[]}`). On failure, stdout carries a JSON error envelope regardless of `--output`, and stderr gets a one-line human-readable summary.
|
|
77
|
+
|
|
78
|
+
### `publish [path]`
|
|
79
|
+
|
|
80
|
+
Builds and uploads the package at `path` (default `.`) to the registry routed by `~/.npmrc`. Before any bytes leave the machine, every prompt listed in `package.json` is checked for: (1) ancestor cycles, (2) intra-document type conflicts, (3) placeholder resolvability against the fully resolved namespace, (4) `dependencies` consistency with the cross-package references found in the prompts, (5) manifest closure under relative-path references — every local `ancestors` entry must resolve to a path that is itself declared in `prompts`, since only manifest-listed files are bundled, and (6) `$schema` validation against the prompt's content contract. All errors discovered in the pass are aggregated into a single envelope; the headline exit code is the most severe one (cycle > schema > reference > merge > placeholder).
|
|
81
|
+
|
|
82
|
+
Flags: `--dry-run` (build the tarball but skip upload), `--strict-schema` (treat unfetchable / unvalidated `$schema` as an error rather than a warning), `--tarball <path>` (write the built tarball to `path`). The tarball is deterministic: identical inputs produce byte-identical output.
|
|
83
|
+
|
|
84
|
+
`$schema` enforcement requires `pip install stemmata[publish]` (adds `jsonschema`). Without it, `publish` warns and skips schema validation in default mode, or errors in `--strict-schema` mode.
|
|
85
|
+
|
|
86
|
+
### `cache clear`
|
|
87
|
+
|
|
88
|
+
Evicts every cached entry.
|
|
89
|
+
|
|
90
|
+
## Prompt Format
|
|
91
|
+
|
|
92
|
+
A prompt is a structured mapping (only YAML is supported as of now) with reserved envelope keys plus arbitrary content:
|
|
93
|
+
|
|
94
|
+
```yaml
|
|
95
|
+
ancestors:
|
|
96
|
+
- ../base.yaml # relative path (within package)
|
|
97
|
+
- package: "@acme/common" # cross-package coordinate
|
|
98
|
+
version: "1.0.4"
|
|
99
|
+
prompt: "defaults"
|
|
100
|
+
$schema: "https://schemas.example/foo.v1.json" # optional, enforced at publish time if present
|
|
101
|
+
|
|
102
|
+
database:
|
|
103
|
+
host: "db.internal"
|
|
104
|
+
port: 5432
|
|
105
|
+
body: |
|
|
106
|
+
Region is ${vars.region}; DB is ${database.host}:${database.port}.
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
`ancestors` and `$schema` are stripped from the namespace; every other key is addressable via dotted path.
|
|
110
|
+
|
|
111
|
+
### Package manifest (`package.json`)
|
|
112
|
+
|
|
113
|
+
```json
|
|
114
|
+
{
|
|
115
|
+
"name": "@acme/prompts-core",
|
|
116
|
+
"version": "1.2.3",
|
|
117
|
+
"license": "UNLICENSED",
|
|
118
|
+
"dependencies": { "@acme/common": "1.0.4" },
|
|
119
|
+
"prompts": [
|
|
120
|
+
{ "id": "base", "path": "base.yaml", "contentType": "yaml" },
|
|
121
|
+
{ "id": "onboarding", "path": "extra/onboarding.yaml", "contentType": "yaml" }
|
|
122
|
+
]
|
|
123
|
+
}
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
`name` must be `@<scope>/<n>`. `version` is strict SemVer, no ranges. `prompts` is non-empty; `id` defaults to basename without extension and must match `[a-z0-9][a-z0-9_-]*`.
|
|
127
|
+
|
|
128
|
+
## Merge Semantics
|
|
129
|
+
|
|
130
|
+
Reachable prompts are layered by breadth-first search distance from the root (distance 0 = root, wins everything). Ties at the same distance break by enqueue order.
|
|
131
|
+
|
|
132
|
+
**Maps** are deep-merged, with the nearer value winning at each leaf:
|
|
133
|
+
|
|
134
|
+
```yaml
|
|
135
|
+
# ancestor (distance 1) # root (distance 0)
|
|
136
|
+
database: database:
|
|
137
|
+
host: "base.internal" host: "override.internal"
|
|
138
|
+
port: 5432 ssl: true
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Resolved: `database.host` = `"override.internal"` (nearer wins), `database.port` = `5432` (survives from ancestor), `database.ssl` = `true` (only root provides it).
|
|
142
|
+
|
|
143
|
+
**Lists** replace wholesale — no element-level merge. **`null`** at a nearer layer shadows the entire subtree beneath it.
|
|
144
|
+
|
|
145
|
+
For the full interpolation reference (structural vs. textual placeholders, list splat, non-splat `${=...}` form, escaping, version conflict resolution), see [`docs/interpolation.md`](docs/interpolation.md).
|
|
146
|
+
|
|
147
|
+
## Exit Codes
|
|
148
|
+
|
|
149
|
+
| Code | Meaning |
|
|
150
|
+
|------|-------------------------------------|
|
|
151
|
+
| `0` | Success |
|
|
152
|
+
| `1` | Generic / unexpected failure |
|
|
153
|
+
| `2` | Usage error |
|
|
154
|
+
| `10` | Schema validation error |
|
|
155
|
+
| `11` | Unknown ancestor or prompt id |
|
|
156
|
+
| `12` | Cycle detected |
|
|
157
|
+
| `14` | Unresolvable placeholder |
|
|
158
|
+
| `15` | Merge / interpolation type mismatch |
|
|
159
|
+
| `20` | Network / registry error |
|
|
160
|
+
| `21` | Cache error |
|
|
161
|
+
| `22` | Offline-mode violation |
|
|
162
|
+
|
|
163
|
+
On failure, stdout always carries a JSON error envelope with `{status, exit_code, command, error: {code, category, message, ...}}` regardless of `--output`. Stderr gets a single-line human summary.
|
|
164
|
+
|
|
165
|
+
## Configuration
|
|
166
|
+
|
|
167
|
+
Registry routing and credentials come from `~/.npmrc` for both fetch and publish.
|
|
168
|
+
|
|
169
|
+
## Testing
|
|
170
|
+
|
|
171
|
+
```
|
|
172
|
+
PYTHONPATH=src python -m pytest tests/ -q
|
|
173
|
+
```
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["setuptools>=77"]
|
|
3
|
+
build-backend = "setuptools.build_meta"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "stemmata"
|
|
7
|
+
version = "0.0.1"
|
|
8
|
+
description = "Hierarchical prompt resolver CLI"
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
requires-python = ">=3.12"
|
|
11
|
+
license = "Apache-2.0"
|
|
12
|
+
license-files = ["LICENSE"]
|
|
13
|
+
authors = [
|
|
14
|
+
{ name = "Pedro Javier Martos Velasco" }
|
|
15
|
+
]
|
|
16
|
+
keywords = ["prompt", "yaml", "inheritance", "composition", "llm", "cli"]
|
|
17
|
+
classifiers = [
|
|
18
|
+
"Development Status :: 3 - Alpha",
|
|
19
|
+
"Environment :: Console",
|
|
20
|
+
"Intended Audience :: Developers",
|
|
21
|
+
"Operating System :: OS Independent",
|
|
22
|
+
"Programming Language :: Python :: 3",
|
|
23
|
+
"Programming Language :: Python :: 3.12",
|
|
24
|
+
"Programming Language :: Python :: 3.13",
|
|
25
|
+
"Topic :: Software Development :: Libraries :: Python Modules",
|
|
26
|
+
"Topic :: Text Processing :: Markup",
|
|
27
|
+
]
|
|
28
|
+
dependencies = ["PyYAML>=6.0"]
|
|
29
|
+
|
|
30
|
+
[project.optional-dependencies]
|
|
31
|
+
publish = ["jsonschema>=4.18"]
|
|
32
|
+
|
|
33
|
+
[project.urls]
|
|
34
|
+
Homepage = "https://github.com/pjmartos/genealogy"
|
|
35
|
+
Repository = "https://github.com/pjmartos/genealogy"
|
|
36
|
+
Issues = "https://github.com/pjmartos/genealogy/issues"
|
|
37
|
+
|
|
38
|
+
[project.scripts]
|
|
39
|
+
stemmata = "stemmata.cli:main"
|
|
40
|
+
|
|
41
|
+
[tool.setuptools.packages.find]
|
|
42
|
+
where = ["src"]
|
|
43
|
+
|
|
44
|
+
[tool.pytest.ini_options]
|
|
45
|
+
testpaths = ["tests"]
|
|
46
|
+
pythonpath = ["src"]
|
stemmata-0.0.1/setup.cfg
ADDED