Skip to content

Penelope v0.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 22:21
· 280 commits to main since this release

Penelope now provides recoverable task execution alongside deterministic saga
orchestration. Applications can declare recovery permissions, persist valid
checkpoints and reconcile ambiguous effects through runtime-independent APIs.
The existing saga engine remains independently useful, with its v1 history
representations and execution guarantees preserved.

Added

  • Recoverable task definitions with explicit restart-from-input,
    restart-from-checkpoint, reconcile-before-restart and never-restart policies.
  • Checkpoint-aware execution with immutable input and result records, committed
    recovery boundaries and application-authorized checkpoint migration.
  • Task supervision with generation fencing, typed fault observations, bounded
    recovery attempts, deadlines, restart delays and execution/resource budgets.
  • Independently versioned task history and deterministic reconstruction without
    rerunning computation or repeating external effects during replay.
  • Backend-neutral synchronous journal and runtime contracts, plus a bridge to
    existing saga effect execution.
  • Optional StateChronicle verification evidence bound to the exact task scope,
    generation and checkpoint identity.
  • An allocation-free no_std task core, optional portable Serde support,
    distinct identity/time newtypes and caller-owned bounded execution buffers.
  • Recoverable computation examples and deployment contracts covering journal
    durability, runtime enforcement, checkpoint schemas and external-effect evidence.
  • Recovery validation through process termination against filesystem and
    transactional SQLite test journals, concurrent supervisor stress, property
    testing and sanitizer-instrumented fuzz targets.

Security

  • Task scope, definition, generation, sequence and monotonic time are checked
    before execution history advances; stale or cross-scope results fail closed.
  • Input commits precede execution, and checkpoints/results commit before
    acknowledgement. Ambiguous persistence outcomes require reconstruction.
  • Live generations retain capacity for a fault or completion; rejected resource
    proposals fence execution before recovery proceeds.
  • Corrupt checkpoints, incompatible schemas and unknown effects cannot become
    unsupported claims of completion or authorize blind retries.
  • Runtime isolation, CPU enforcement, storage authenticity and the correctness
    of computation and physical side effects remain explicit application contracts.

Changed

  • The facade exposes both saga orchestration and recoverable task execution
    while preserving existing linear/graph decisions, retries, compensation and
    reconciliation semantics.
  • Task definition fingerprints bind recovery permissions and resource budgets
    to execution scope, and strict task wire decoding rejects malformed records.
  • The workspace supports Rust 1.85 and uses Rust 1.99 for development, with
    hosted adapters separated from the portable task core.
  • Release verification checks all seven library packages; tag releases use the
    matching dated changelog entry as their GitHub release notes.