Durable runtime for continuous agents.
Pulse keeps agent identity, sessions, turns, approvals, workspace changes, and recovery state durable on one host. Pulse 0.3 Alpha includes the provider-neutral Pulse Harness Kernel v0.1. Pi is the first compatibility adapter; it is no longer the architecture's only load-bearing interface.
This is an engineering Research Alpha. It publishes installable code, provider-free deterministic contracts, and a reproducible release procedure. It does not claim consciousness, autonomous life, real-provider validation, or longitudinal behavioural change.
- Durable Harness sessions with scoped identity, ordered events, replay cursors, transcripts, approvals, and explicit uncertain recovery.
- A Pulse-owned model/tool loop with bounded payloads and provider evidence.
- A structured workspace adapter with path fencing, deterministic diffs, and restorable checkpoints.
- A generic Harness factory and a Pi compatibility adapter.
pulse-harness create|wake|status, the/v1/harnessAPI and SSE stream, and a Harness panel in the local Workbench.- The existing single-host
PulseWorld: durable scheduling, causal recovery, Engram continuity, and local observation.
See Capabilities for the complete engineering surface.
Required toolchain: Python 3.12.13 and uv 0.11.1.
uv sync --locked --extra observatory
uv run pulse-harness create \
--db .pulse/harness.db \
--workspace .pulse/harness-workspace \
--session first-session
uv run pulse-harness status \
--db .pulse/harness.db \
--workspace .pulse/harness-workspace \
--session first-sessionThese commands use the real durable Harness store and structured workspace
adapter. They do not call a model provider. The result therefore reports
live_gate: BLOCKED, verified: false, and provider_unconfigured; no
mock answer is substituted.
To open the local Monitor/Workbench without credentials:
uv run pulse --mock --profile safe \
--db .pulse/runtime.db \
--harness-db .pulse/harness.db \
--port 8100Open http://127.0.0.1:8100. The --mock flag is an explicit legacy runtime
test harness, not a live-provider result. The independent Harness Kernel stays
provider-unconfigured and honest. The safe Profile is read-only over HTTP,
so it is suitable for observation; state-changing Workbench calls remain
blocked.
A configured Pi executable can be selected through the same generic factory:
uv run pulse --pi-executable /absolute/path/to/pi \
--pi-provider YOUR_PROVIDER \
--pi-model YOUR_MODELThe repository does not include or reproduce Pi/provider artifacts, credentials,
costs, or live-session evidence. This release therefore marks
LIVE_GATE_UNVERIFIED and CODEX_PARITY_INCOMPLETE.
The Web toolchain is pinned to Node.js 24.15.0 and npm 11.12.1.
cd web
npm ci
npm test
npm run buildEnglish and Simplified Chinese use physically separate locale catalogs. The interface renders one locale at a time; Harness, Engram, Pi, Provider, SSE and other product or protocol names may remain untranslated where translation would reduce precision.
one host
└── PulseWorld
├── runtime lease, scheduler, and causal ledger
└── Engram 1..N
└── durable Harness session
├── provider-neutral Kernel
├── structured workspace adapter
└── adapter: Pi (included) or another compatible factory
uv sync --locked --extra observatory --group dev
uv run pytest -q
uv build
bash scripts/release_check.shThe default suite removes provider keys and makes no paid request. Checks that need an external system remain separate and operator-authorized.
- E0: an implementation path exists.
- E1: deterministic provider-free contracts pass.
- E2: an authorized real provider or selected external system is observed.
- E3: a clean checkout can be installed, built, and reproduced.
- E4: long-running counterfactual evidence shows persistent behavioural change.
Pulse 0.3 Alpha claims E0/E1 engineering coverage and an E3 release procedure. It publishes no E2 evidence archive and makes no E4 claim. Browser, UI, local TCP/SQLite, mock-runtime, and operating-system regressions remain E1.
- Research Alpha; single host and single operator.
- The included registry currently ships one production compatibility adapter: Pi. The factory protocol is generic, but adapter parity is incomplete.
- Provider-free flows prove storage, replay, control, workspace, API, SSE, and UI contracts; they do not prove a live model provider.
- No complete operating-system, filesystem, network, credential, PTY, or MCP sandbox is claimed.
- No claim of consciousness, autonomous life, stable interest formation, or longitudinal causality.