loopsmith-cli 0.1.3__tar.gz → 0.2.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.
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/PKG-INFO +25 -2
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/README.md +24 -1
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/pyproject.toml +1 -1
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli/__init__.py +1 -1
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli.egg-info/PKG-INFO +25 -2
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/setup.cfg +0 -0
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli/__main__.py +0 -0
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli.egg-info/SOURCES.txt +0 -0
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli.egg-info/dependency_links.txt +0 -0
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli.egg-info/entry_points.txt +0 -0
- {loopsmith_cli-0.1.3 → loopsmith_cli-0.2.0}/src/loopsmith_cli.egg-info/top_level.txt +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: loopsmith-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.2.0
|
|
4
4
|
Summary: Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`.
|
|
5
5
|
Author-email: bitphill <bitphill@tuta.com>
|
|
6
6
|
License-Expression: MIT
|
|
@@ -21,7 +21,7 @@ Requires-Python: >=3.8
|
|
|
21
21
|
Description-Content-Type: text/markdown
|
|
22
22
|
|
|
23
23
|
<div align="center">
|
|
24
|
-
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.
|
|
24
|
+
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
|
|
25
25
|
<h1>loopsmith</h1>
|
|
26
26
|
<p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
|
|
27
27
|
</div>
|
|
@@ -40,6 +40,29 @@ loopsmith doctor
|
|
|
40
40
|
> `import`. It installs a `loopsmith` command. To drive loops from Python, use
|
|
41
41
|
> `subprocess` — its exit codes are its API.
|
|
42
42
|
|
|
43
|
+
## TL;DR:
|
|
44
|
+
|
|
45
|
+
You have a job you redo every week and are fussy about — a competitor roundup, a
|
|
46
|
+
lead list, a landing page, a research brief. Write down **what you want** and
|
|
47
|
+
**how anyone would tell it's good**, in one plain text file. loopsmith puts an AI
|
|
48
|
+
to work on it, checks the result, sends it back when it falls short, and stops
|
|
49
|
+
when it passes. It can run on a schedule for weeks without you.
|
|
50
|
+
|
|
51
|
+
The rule that makes it safe to walk away: **the AI never gets to say "done".** A
|
|
52
|
+
deterministic checker reads the actual files and decides — and it can revoke, so
|
|
53
|
+
a goal that stops being true stops being satisfied.
|
|
54
|
+
|
|
55
|
+
**Not a developer?** Marketing, sales, research, ops — if you can edit a text
|
|
56
|
+
file, you can run a loop.
|
|
57
|
+
|
|
58
|
+
### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
|
|
59
|
+
|
|
60
|
+
A plain-English guide: one install line, thirteen ready-made loops to copy, the
|
|
61
|
+
six settings you actually edit, and how to leave it running on a schedule.
|
|
62
|
+
|
|
63
|
+
There is also a generated [code wiki](https://bitphill.github.io/loopsmith/wiki/#overview) mapping the crates,
|
|
64
|
+
the execution engine, the gate, and the provider layer.
|
|
65
|
+
|
|
43
66
|
## What it is
|
|
44
67
|
|
|
45
68
|
You describe a purpose in a config — goals, how each is checked, what counts as
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
<div align="center">
|
|
2
|
-
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.
|
|
2
|
+
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
|
|
3
3
|
<h1>loopsmith</h1>
|
|
4
4
|
<p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
|
|
5
5
|
</div>
|
|
@@ -18,6 +18,29 @@ loopsmith doctor
|
|
|
18
18
|
> `import`. It installs a `loopsmith` command. To drive loops from Python, use
|
|
19
19
|
> `subprocess` — its exit codes are its API.
|
|
20
20
|
|
|
21
|
+
## TL;DR:
|
|
22
|
+
|
|
23
|
+
You have a job you redo every week and are fussy about — a competitor roundup, a
|
|
24
|
+
lead list, a landing page, a research brief. Write down **what you want** and
|
|
25
|
+
**how anyone would tell it's good**, in one plain text file. loopsmith puts an AI
|
|
26
|
+
to work on it, checks the result, sends it back when it falls short, and stops
|
|
27
|
+
when it passes. It can run on a schedule for weeks without you.
|
|
28
|
+
|
|
29
|
+
The rule that makes it safe to walk away: **the AI never gets to say "done".** A
|
|
30
|
+
deterministic checker reads the actual files and decides — and it can revoke, so
|
|
31
|
+
a goal that stops being true stops being satisfied.
|
|
32
|
+
|
|
33
|
+
**Not a developer?** Marketing, sales, research, ops — if you can edit a text
|
|
34
|
+
file, you can run a loop.
|
|
35
|
+
|
|
36
|
+
### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
|
|
37
|
+
|
|
38
|
+
A plain-English guide: one install line, thirteen ready-made loops to copy, the
|
|
39
|
+
six settings you actually edit, and how to leave it running on a schedule.
|
|
40
|
+
|
|
41
|
+
There is also a generated [code wiki](https://bitphill.github.io/loopsmith/wiki/#overview) mapping the crates,
|
|
42
|
+
the execution engine, the gate, and the provider layer.
|
|
43
|
+
|
|
21
44
|
## What it is
|
|
22
45
|
|
|
23
46
|
You describe a purpose in a config — goals, how each is checked, what counts as
|
|
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
|
|
|
6
6
|
# `loopsmith` on PyPI was already registered by an unrelated project, so the
|
|
7
7
|
# distribution is `loopsmith-cli`. The installed command is `loopsmith`.
|
|
8
8
|
name = "loopsmith-cli"
|
|
9
|
-
version = "0.
|
|
9
|
+
version = "0.2.0"
|
|
10
10
|
description = "Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`."
|
|
11
11
|
readme = "README.md"
|
|
12
12
|
license = "MIT"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: loopsmith-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.2.0
|
|
4
4
|
Summary: Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`.
|
|
5
5
|
Author-email: bitphill <bitphill@tuta.com>
|
|
6
6
|
License-Expression: MIT
|
|
@@ -21,7 +21,7 @@ Requires-Python: >=3.8
|
|
|
21
21
|
Description-Content-Type: text/markdown
|
|
22
22
|
|
|
23
23
|
<div align="center">
|
|
24
|
-
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.
|
|
24
|
+
<img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
|
|
25
25
|
<h1>loopsmith</h1>
|
|
26
26
|
<p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
|
|
27
27
|
</div>
|
|
@@ -40,6 +40,29 @@ loopsmith doctor
|
|
|
40
40
|
> `import`. It installs a `loopsmith` command. To drive loops from Python, use
|
|
41
41
|
> `subprocess` — its exit codes are its API.
|
|
42
42
|
|
|
43
|
+
## TL;DR:
|
|
44
|
+
|
|
45
|
+
You have a job you redo every week and are fussy about — a competitor roundup, a
|
|
46
|
+
lead list, a landing page, a research brief. Write down **what you want** and
|
|
47
|
+
**how anyone would tell it's good**, in one plain text file. loopsmith puts an AI
|
|
48
|
+
to work on it, checks the result, sends it back when it falls short, and stops
|
|
49
|
+
when it passes. It can run on a schedule for weeks without you.
|
|
50
|
+
|
|
51
|
+
The rule that makes it safe to walk away: **the AI never gets to say "done".** A
|
|
52
|
+
deterministic checker reads the actual files and decides — and it can revoke, so
|
|
53
|
+
a goal that stops being true stops being satisfied.
|
|
54
|
+
|
|
55
|
+
**Not a developer?** Marketing, sales, research, ops — if you can edit a text
|
|
56
|
+
file, you can run a loop.
|
|
57
|
+
|
|
58
|
+
### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
|
|
59
|
+
|
|
60
|
+
A plain-English guide: one install line, thirteen ready-made loops to copy, the
|
|
61
|
+
six settings you actually edit, and how to leave it running on a schedule.
|
|
62
|
+
|
|
63
|
+
There is also a generated [code wiki](https://bitphill.github.io/loopsmith/wiki/#overview) mapping the crates,
|
|
64
|
+
the execution engine, the gate, and the provider layer.
|
|
65
|
+
|
|
43
66
|
## What it is
|
|
44
67
|
|
|
45
68
|
You describe a purpose in a config — goals, how each is checked, what counts as
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|