Skip to content

0.7.23: Reactive Topology Closure and Cohort Throughput

Choose a tag to compare

View all tags
@llblab llblab released this 24 Aug 16:26
· 5 commits to main since this release
v0.7.23
de498bf

DEOS 0.7.23 closes reactive topology ownership and adds bounded Crossing cohort throughput.

Highlights

  • Declarative Trigger topology: Crossing phase/revision and cadence now live in canonical Actor state; lifecycle changes share one transactional transition compiler with exact no-op, rollback, family-matrix, fresh-genesis, and refundable User-bond semantics.
  • Lifecycle and ingress Weight: Generated lifecycle owners cover Crossing topology branches, while host-composed Oracle publication owns its complete synchronous broad/Crossing consequence exactly once.
  • Branch-exact Crossing: Read-only work plans, staged probes, transaction-time revalidation, exact counters, and retained-threshold radix charging admit and consume only the reachable multidimensional owner.
  • Cohort throughput: Homogeneous tail and non-tail cohorts process up to four candidates with aggregate FIFO authority, stable compaction, physical-tail refill, grouped split destinations, exact locator repair, and scalar fallback.
  • Materialization and capacity: Wakeups, Crossing, and broad fanout share deterministic rotated grants, protected minima, repairable faults, and a positive Actor execution floor. Reference limits remain 9,000 User / 10,000 total memberships per feed.
  • Assurance: Pure and randomized models, corruption/fault matrices, exact-root rollback, queue pressure, mixed-family fairness, and 10,000-Actor convergence extend release evidence.
  • API and client: Actor eligibility API v4 projects semantic Trigger state, placement, faults, capacity, and bond policy; metadata, descriptors, ABI, vectors, and client authoring evidence were regenerated.
  • Packaging and release: Rust 1.94.1, independent embedding/no-default/TryRuntime contracts, strict-OKF bilingual Wiki, generated Weight/capacity/delta evidence, and the no-migration fresh-genesis boundary are synchronized.

Artifact identity

  • Commit: de498bf5a2822e48b1a08fc3f1951d2790c160ce
  • Tree: 88af295a9ec21d024b678d273500d23d0cd908d0
  • Compact runtime Wasm SHA-256: 4b04e98b598cb0e72516e12382b742858ba720631f769b60be433d7e1acd989a

This is a fresh-genesis 0.x release. It makes no 0.7.22 migration or live-network upgrade claim.

Assets 4
Loading