Replace shipped pipeline examples with research and task starters
This commit is contained in:
+5
-5
@@ -159,7 +159,7 @@ pipelines edit # fuzzy pipeline selection
|
||||
pipelines edit "bug fix" # ask the harness what to change
|
||||
pipelines edit "bug fix" "Add a review step"
|
||||
pipelines new "release notes" "Summarize changes and notify my phone"
|
||||
pipelines new "Add a feature" --template feedback-loop
|
||||
pipelines new "Add a feature" --template task
|
||||
```
|
||||
|
||||
`new` opens the configured harness (Pi or OpenCode; host by default, or
|
||||
@@ -222,10 +222,10 @@ is not ownership (the kernel lock is). This is a local-filesystem lock, not a
|
||||
distributed lease; hard-link database aliases and filesystems without reliable
|
||||
advisory locking are unsupported.
|
||||
|
||||
Use `:templates` for the four manual-only examples, read in order: one stage,
|
||||
two stages, a feedback loop and a human decision (`examples/README.md`). A
|
||||
brand-new database already holds them as ordinary pipelines; the server seeds
|
||||
them once and never again, so removing them or upgrading never brings them back.
|
||||
Use `:templates` for the two general-purpose starters, research and task
|
||||
(`examples/README.md`). A brand-new database already holds them as ordinary
|
||||
pipelines; the server seeds them once and never again, so removing them or
|
||||
upgrading never brings them back.
|
||||
**Submit template** (`s` or Enter) asks for a
|
||||
name without opening an editor. Enter saves a retained draft, then a separate
|
||||
confirmation publishes it as a new pipeline. Esc before naming creates nothing;
|
||||
|
||||
@@ -29,15 +29,15 @@ sandbox for model tools.
|
||||
|
||||
1. Pick a disposable project without secrets or valuable uncommitted changes.
|
||||
A remote browser selects a directory on the **server**, not its own computer.
|
||||
2. A fresh database already holds the four example pipelines
|
||||
(`examples/README.md`). Run the read-only **Example 1: one stage** first.
|
||||
3. Ask it to review one short file. Watch the graph and inspect the retained
|
||||
report and the stage's **Audit → Session** evidence.
|
||||
4. Try **Example 2: two stages** on a few local files. Check the result against
|
||||
the sources yourself; a successful stage is not proof of factual accuracy.
|
||||
5. Only then try an editing example (**feedback loop**, **human decision**).
|
||||
Inspect actual changes and test evidence, not just the model's summary. Keep
|
||||
version control/backups.
|
||||
2. A fresh database already holds the two starter pipelines
|
||||
(`examples/README.md`). Run **research** first with a small, well-defined
|
||||
question and authoritative sources.
|
||||
3. Watch the graph and inspect the retained report and the stage's
|
||||
**Audit → Session** evidence. Check the result against the sources yourself;
|
||||
a successful stage is not proof of factual accuracy.
|
||||
4. Only then try **task** on a disposable repository. Inspect actual changes,
|
||||
review findings, rendered checks when applicable and test evidence, not just
|
||||
the model's summary. Keep version control/backups.
|
||||
|
||||
Editing a draft does not publish it. Publication creates an immutable version;
|
||||
runs retain the version they used. Export/import bundles contain **definitions
|
||||
|
||||
+3
-3
@@ -379,9 +379,9 @@ File-attachment bytes are stored by ntfy, not permanently archived in SQLite;
|
||||
run metadata stores the delivered filename/URL, and workspace files may later
|
||||
change. Download attachments before your ntfy retention expires.
|
||||
|
||||
Bundled examples need no schedule setup. **Example 4: human decision** shows
|
||||
`notify` hooks (`plan` on failure, `decide` on `waiting`, `act` on success and
|
||||
failure); they only deliver once the system phone connection is configured. Add a
|
||||
Bundled starters need no schedule setup. **Research and report** shows a
|
||||
`notify` hook on research failure; it only delivers once the system phone
|
||||
connection is configured. Add a
|
||||
`notify` block to the stages of your own workflow the same way. Adding a schedule activates it on publication,
|
||||
so review it explicitly rather than copying a scheduled niche example.
|
||||
|
||||
|
||||
@@ -106,7 +106,7 @@ Its complete model/web/phone execution was **not tested**. It used dated web
|
||||
evidence → verify/enrich → Markdown report → native ntfy attachment through the
|
||||
system connection; the LiveChart schedule was fetched during that investigation.
|
||||
Removing its bundled starter does not remove its published history. Current
|
||||
snapshot fixtures use the generic `examples/human-decision.md` example.
|
||||
snapshot fixtures use the generic `examples/task.md` example.
|
||||
|
||||
`PIPELINES_UX_SNAPSHOT_DIR=<directory> go test ./internal/tui -run
|
||||
TestUIUXReviewSnapshots -count=1` regenerates the existing snapshots without server
|
||||
|
||||
Reference in New Issue
Block a user