arcrun — AI workflow execution engine (clean history)
Self-hosted 開源:WASM 零件 + recipe + cypher-executor,跑在你自己的 Cloudflare。 此為重建的乾淨歷史起點(移除曾誤 commit 的 GCP SA 金鑰,舊歷史保留在 richblack/arcrun 與本地 backup 分支)。含: - acr init --self-hosted installer(建 KV/R2 + codeload 拉預編譯 wasm + wrangler deploy + seed recipe) - recipe push 把關(資料外流提醒 + 打通檢查) - 19 個正當零件預編譯 wasm(claude_api/km_writer/kbdb_upsert_block 排除:違反 DECISIONS §1) - CLI / cypher-executor / registry / 完整 SDD Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
# cron-watcher
|
||||
|
||||
## 解決什麼問題
|
||||
定期巡 KBDB(或任何資料源),找到「未處理」的紀錄,每筆觸發一個處理 workflow。
|
||||
**最常見的 pattern**:mira 就是這樣把河道貼文自動跑 wiki_synthesis。
|
||||
|
||||
## 怎麼觸發
|
||||
不用手動觸發 — 部署後自動每 5 分鐘跑。
|
||||
|
||||
cron 解析在 `acr push` 時自動偵測首節點是 `cron` 零件,存進 `WEBHOOKS:cron-idx:` 索引,
|
||||
`scheduled()` handler 每分鐘 tick 對齊。
|
||||
|
||||
## 改成你自己的
|
||||
- `watch_cron.cron_expr` 改頻率(標準 5 欄 cron 語法)
|
||||
- `list_unprocessed` 改你的 KBDB query(type / source / tag 等)
|
||||
- `filter_new.condition` 改你的「未處理」定義
|
||||
- `trigger_processor.workflow_name` 改你的處理 workflow
|
||||
|
||||
## 為什麼用 trigger_workflow 不用 http_request
|
||||
|
||||
CF Workers 有 self-fetch 防護:cypher-executor 自打 `cypher.arcrun.dev/*` 或自己的
|
||||
`arcrun-cypher-executor.*.workers.dev` 都被攔(CF 1042)。
|
||||
|
||||
`trigger_workflow` 是 cypher-executor 內建的 orchestration 零件,直接 in-process
|
||||
call `executeWebhookGraph`,**不走外部 HTTP**,徹底繞掉 self-fetch。
|
||||
|
||||
## 學到什麼
|
||||
- cron + FOREACH + trigger_workflow 三件套
|
||||
- `{{api_key}}` 從 trigger context 自動帶(cron 觸發時 cypher-executor 自動塞進去)
|
||||
- `對每個 X >> Y` 中文關係詞(也接受 `FOREACH X`)
|
||||
- filter 零件用 `condition.op: eq` 配 `tags_json: "[]"` 偵測「無 tag」
|
||||
@@ -0,0 +1 @@
|
||||
["cron", "watcher", "kbdb", "foreach", "trigger_workflow", "common-pattern"]
|
||||
@@ -0,0 +1,38 @@
|
||||
name: cron_watcher_example
|
||||
description: 每 5 分鐘掃 KBDB 未處理的 note → 對每筆觸發子 workflow
|
||||
|
||||
flow:
|
||||
- "watch_cron >> ON_SUCCESS >> list_unprocessed"
|
||||
- "list_unprocessed >> ON_SUCCESS >> filter_new"
|
||||
- "filter_new >> 對每個 item >> trigger_processor"
|
||||
|
||||
config:
|
||||
watch_cron:
|
||||
component: cron
|
||||
cron_expr: "*/5 * * * *"
|
||||
description: "每 5 分鐘掃一次"
|
||||
|
||||
list_unprocessed:
|
||||
component: kbdb_get
|
||||
api_key: "{{api_key}}"
|
||||
type: "note"
|
||||
source: "user-input"
|
||||
limit: 20
|
||||
|
||||
filter_new:
|
||||
component: filter
|
||||
items: "{{list_unprocessed.blocks}}"
|
||||
condition:
|
||||
key: "tags_json"
|
||||
op: "eq"
|
||||
value: "[]"
|
||||
|
||||
# trigger_workflow 是內建 orchestration 零件,in-process call 另一個 workflow
|
||||
# **千萬不要用 http_request 自打 cypher-executor 自己的 webhook** — 會撞 CF self-fetch 死鎖
|
||||
trigger_processor:
|
||||
component: trigger_workflow
|
||||
workflow_name: "your_processor_workflow" # ← 改成你的處理 workflow 名
|
||||
api_key: "{{api_key}}"
|
||||
input:
|
||||
api_key: "{{api_key}}"
|
||||
block_id: "{{item.id}}"
|
||||
Reference in New Issue
Block a user