Introduction

Jixu means continue in Chinese. It gives one Agent a durable Thread so work can survive a process exit, an interrupted provider request, or a deliberate pause without inventing another source of truth.

The public promise

Define one immutable Agent, bind it to Stores and Drivers through a Harness, and continue its work through one durable Thread.

one Agent → one Harness → one durable Thread

The ordered Event log is the sole authority for that Thread. State is derived, Checkpoints are disposable, and external work follows one explicit path:

Event → Reducer → Effect → Driver → Event

This makes recovery explainable. Jixu knows which work was requested, which outcome became durable, and which uncertain boundary requires a person instead of a blind retry.

Choose a path

Designed for long-lived work

Jixu is intentionally small. It does not hide execution behind an opaque runtime. The important boundaries are named and inspectable:

• Inputs and external requests become durable before execution proceeds.
• Reducers are pure and perform no I/O.
• Replay reconstructs State without calling a live Driver.
• Unknown persisted data fails closed.
• Secrets never enter Events, State, Checkpoints, errors, or Signals.
• One Harness never routes work between Agents.

Continue with the Quick start, or begin with the Core model.