686d02755f
- new pi-durable.md: architecture (session/entry/document/task/submission), effect-sandwich semantics, structured concurrency, storage backends, maturity/adoption, taxonomy placement, implications for hermes-vm - empirical tests on @earendil-works/pi-durable 1.3.0 (Node 22.22.2): kill -9 mid-phase (memo vs plain), kill -9 mid-tool (safe vs unsafe), SQLite schema; noted cold-open waitForTask race and the main-vs-1.3.0 version gap (sleepUntil/onWake/restartLimit/sleeping not published) - taxonomy: durable harness library added as a new primitive family - sources + next-steps updated
20 lines
1.6 KiB
Markdown
20 lines
1.6 KiB
Markdown
# Next Steps — Durable Agent Runtime
|
|
|
|
> Part of [[durable-agent-runtime/index|Durable Agent Runtime]]
|
|
|
|
## Open questions
|
|
|
|
- [ ] Which repos get the `.agents/setup`-style contract first (clan-private, law retrieval, idx-cli)?
|
|
- [ ] Should the dev-server + ports-file pattern be a shared script library in clan-private or per-repo?
|
|
- [ ] Is hypeman worth an evaluation build on hermes-vm (per-task VM with standby) vs NixOS containers?
|
|
- [ ] pi-durable: prototype one long-running service on Node/SQLite, or borrow only its semantics? (see [[durable-agent-runtime/pi-durable|pi-durable]])
|
|
- [ ] pi-durable open questions: no Postgres/KV adapter; multi-client transport is app-owned; default Node env has no sandbox; no published recovery/latency benchmarks; `sleeping`/`onWake`/`restartLimit` not yet in a published release
|
|
- [ ] Does the Forgejo webhook → kanban wake need a new service, or does an existing cron/webhook path cover it?
|
|
- [ ] Code Mode pattern for our Effect TS stack now tracked in [[harness-engineering/index|Harness Engineering]]
|
|
|
|
## Decisions made (2026-08-07)
|
|
|
|
- Research topic: **durable-agent-runtime** — covers durable objects, stateful machines, and harness engineering (sandboxed or not). On 2026-08-11 harness engineering was split out into its own topic under the agent-infra umbrella.
|
|
- Do NOT build a distributed durable-object layer (celld) or actor platform (rivet) on a single box.
|
|
- Do NOT build an E2B-style per-thread VM fleet; use NixOS-native isolation when needed.
|
|
- DO build environment contracts: per-repo setup hooks, AGENTS.md per repo, dev-server skills, event wake.
|