Go

By replacing a second time.Format call with a simple string slice (amzDate[:8]), we eliminated redundant heap allocations and CPU overhead when generating timestamps for AWS SigV4 requests.

The momofs FUSE mount traded its hand-rolled bazil.org/fuse adapter for the go-fuse/v2 high-level fs API, mapped all 22 node callbacks to go-fuse interfaces, and deprecated consistency=cached.

time.Format allocates a fresh string on every S3 GET/HEAD response. Swapping to time.AppendFormat drops that heap escape to zero — measured 32 B/op saved per request on the hottest read path.

The FUSE transport (momo -imp fs): bazil.org/fuse binding, per-handle buffered writes, /dev/fuse-gated e2e, and a clean unmount lifecycle.

Base-vs-branch benchmark comparison gates every PR — plus the runner-noise saga (S3PutSpool, LocalWrite, allowlist, apostrophe) that made it honest.

The R4 POSIX core: inodes as content-addressed manifests, files as blobs, atomic rename, hardlinks, permission enforcement — a filesystem on momo.

Ack only what survived: fsync/group-commit durability barrier, survivor quorum, and read-your-writes — the write-side of the P0 stack.

When a local replica is corrupted or missing, degraded read fetches from healthy survivors transparently, while a background rebuild loop restores cluster redundancy.

Replicas must not ride in the same rack: CRUSH weights become rack/zone/DC-aware so a single domain failure can’t lose the data.

Prometheus metrics export with a per-node metrics_host/metrics_port bind — observability that scales past the ‘just scrape node 0’ era.