Skip to content

History / Project status

Revisions

  • audit: give M24 criterion 1 one verdict (#94) The M24 row said the steady-state memory condition was not settled and that no result was recorded in docs/perf.md; the gaps list said the same. But docs/perf.md has recorded both runs at ADR 0140's default since e7f87e0f, before this page was revised: the 10-minute run passed every condition and the 60-minute one passed all ten checks, +9.4 % VmRSS over the hour with the heap leveling off. Both pages now state the same partial verdict. The run was on the test machine confined to two CPUs, standing in for the 2-vCPU test VPS; the brief defines criterion 1 on the test VPS, which has not run it, and no workflow runs scripts/acceptance-m24.sh load. The memory measurement is recorded, not missing. No counts or other rows change.

    @maintainers maintainers committed Nov 15, 2026
  • status: make cluster verification prospective (#95) The known-gaps bullet said a release is verified on a three-node cluster since v0.4.0, while the same page records the cluster track (M16–M19) as design only with no cluster crate and no such environment provisioned. No tagged release has a cluster to verify, so state the policy as future work and name the absent environment as the reason the M32 cluster targets are unmeasured.

    @maintainers maintainers committed Nov 15, 2026
  • status, compliance audit: v0.5.0 released Project status opens the 0.6.0-dev line and lists v0.5.0 as the latest release with its engine and contents. The audit's snapshot moves to the tag (fcc5bf5a) and says what the commits between the audited tree and the tag changed.

    @maintainers maintainers committed Nov 15, 2026
  • status: M24 criterion 1 passes at the default concurrency

    @maintainers maintainers committed Nov 15, 2026
  • status: blobs always on (M26 B20)

    @maintainers maintainers committed Nov 14, 2026
  • status: M25 and M26 on main

    @maintainers maintainers committed Nov 14, 2026
  • status: M24 on main, M20 accepted, M20 and M21 proven

    @maintainers maintainers committed Nov 14, 2026
  • status: main has the isolation series, M23 and the audit fixes

    @maintainers maintainers committed Nov 14, 2026
  • status: v0.5.0 progress and the decisions of 2026-11-13 Record the state of M20-M26 on main and the isolation branch, the maintainers' decisions (M21's deviation ratified, the M24-M26 designs accepted, M20 experimental until its proofs run), the WASI 0.3 gate check, and correct the M0 tag claim (#56) and the compliance audit's reproduction commands (#46).

    @maintainers maintainers committed Nov 13, 2026
  • status: record the decided gaps and the manual workflows CI and nightly start only from workflow_dispatch. Release archives carry the license notices. The restore demo is not a destroyed VPS. The 1 000 turns/s target is across actors. Untagged SQL writes are refused. Fork crypto follows the grant's in-forks mode.

    @maintainers maintainers committed Nov 11, 2026
  • Project status: v0.4.1 is the latest release The patch release shipped with its advisory; main is the 0.5.0-dev line. The M20/M21 rows name the isolation branch, its experimental/opt-in status and what still has to be proved before the ADRs move: a real KVM boot and the Ubuntu 24.04/AppArmor (R1) pair.

    @maintainers maintainers committed Nov 8, 2026
  • Publish project documentation

    @maintainers maintainers committed Nov 3, 2026