Files
pipelines/examples/README.md
T

4.9 KiB

Showcase definitions

These are pipeline definitions, not execution evidence. The server supports sequential execution with OpenCode Go / DeepSeek V4.1 Flash, optional scoped agent tools, next-stage output-map propagation, bounded loops, and persisted TUI run history. Use :run on an explicit version and :runs to inspect actual evidence. The bug fix workflow has been run end to end for outcome-arrow alignment; the other showcases have not. Browser capture and general-purpose shell access are not enabled by the current narrow tool policy. Unavailable operations must return an error rather than fabricated evidence. Config validation alone does not prove provider/model availability.

Pipeline name Definition Showcase
bug fix bug-fix.md Reproduction evidence, focused implementation, executed checks, review/revision loop, final report
new feature new-feature.md UI/API conditional fork, sequential full-stack work, targeted retry routes
dashboard screenshots dashboard-screenshots.md Local app readiness, fixture/capture matrix, screenshot inspection/retakes, artifact gallery and owned-process cleanup
dependency upgrade dependency-upgrade.md Baseline comparison, lockfile/API migration, regression loop, approval and rollback notes
incident diagnosis incident-diagnosis.md Read-only evidence collection loop, confidence and inconclusive failure outcome
nested forks nested-forks.md Forward-only acyclic graph: brief/detailed fork, walkthrough/reference nested fork, shared delivery
scheduled summary scheduled-summary.md Text-only example scheduled every 15 minutes on weekdays in the server's local timezone
scheduled web research scheduled-web-research.md Websearch/webfetch-only research stage followed by tool-free summarization; requires an OpenCode search provider
anime digest anime-digest.md Current-season anime via webfetch → Markdown digest with per-stage ntfy notifications; daily 19:00
notification test notification-test.md Manual-only system notification test; normal prompt succeeds, standalone FAIL deliberately fails; both notify with Markdown
anime today anime-today.md Today's dated episode schedule → verify/enrich → Markdown with links/images → native ntfy delivery through the system connection; manual only

See ntfy setup before submitting anime digest. Its destination and credentials must be configured on the server; no ntfy instance is created by submitting the pipeline.

Submitting a scheduled example activates its schedule immediately. Each is provided as a file only, not automatically submitted. Remove the top-level settings when submitting a new version to disable scheduled execution.

nested forks is a text-only routing/rendering showcase with seven stages and three possible successful paths. All stage-to-stage edges point forward in the declaration order; none can form a cycle. Try a brief request, a detailed how-to, or a detailed reference request to select different routes. Forks remain exclusive, not parallel; the mandatory failure routes are separate from the two content forks.

The original bug fix v2 had three stages and a review loop, but no explicit reproduction evidence, independent verification, or delivery report. The improved definition retains planner/implementer/reviewer while adding verifier and report. Failed verification and requested review changes return to implementer; missing evidence and exhausted revision budgets lead to failure, not a false success.

A fork means selecting one outcome, never parallel execution. In new feature, planner chooses UI/full-stack or API-only. Full-stack work passes from UI to API sequentially, then converges at verifier. The output blocks document handoff fields, not enforced schemas. There are no declared input blocks: the entry stage reads the user's prompt, and each next stage receives the preceding stage's output automatically. Carry necessary earlier fields in those outputs. Prompt-specific revision/evidence budgets remain instructions, not enforced map schemas. The runner independently enforces 30 total steps, five visits per stage, and a 30-minute deadline; retries=0 is separate from graph-level revision loops.

Submit each Markdown source using its pipeline name through the existing WebSocket submit operation. An update creates an immutable version; re-submitting the latest identical source returns no changes. Do not submit this README as a definition.

The sources now use deepseek-v4.1-flash (not the earlier flask typo). Corrected definitions should be submitted as new versions, not edits to historical records.