For a tweet-driven Sui wallet, the enclave must re-fetch the mention. Backend metadata is not a source of truth.

Dugong: do not trust the tweet the backend sends

Something important happens on Sui. The screen still reads PostgreSQL — and the gap is the real design problem.

The screen does not read the chain

An agent should pay for a call without me clicking checkout. 402 → settle on Sui → retry with proof.

An agent that can pay for the call

Claude writes the diff. I almost merged a cache-before-auth bug. Ownership is still the job.

The agent writes the diff. I still own it.

Tweet → webhook → processor. Redis and Apalis keep mention handling off the hot path.

Dugong queues: mentions off the request path

I was building agent memory that had to stay private. Walrus holds the bytes; the chain is the lock; Postgres answers search.

Memory for agents, with the chain as the lock

A recoverable Git forge: Sui holds refs and identity, Walrus holds durable bundles, local cache is rebuildable.

Octopus: Git that can come back from Walrus

Store the meme on Walrus. Keep the rules in Move. Serve the feed from an API — or everyone notices the lag.

Where Rememe keeps the meme, and where it keeps the feed

Postgres is the product surface the UI queries — and it can lie if you let it.

Postgres read models that do not lie

Move holds the lock — who may read, pay, own.

Move as the permission layer, not the database

Delegate tokens, credential helper, and WWW-Authenticate retry so Git over HTTP does not feel bolted on.

Octopus auth: Git that retries like a grown-up

Inherited Solr, left with Elasticsearch hybrid ranking — after a boost-file fix broke an unrelated category overnight.

Moving Cazoodle off Solr

Redis + Apalis for work that must not live on the request path.

Redis and Apalis: queues that survive the click

TEE/Nautilus for signing — keys stay in the boundary.

TEE and Nautilus: where the key is allowed to live

macOS overlay for Codex CLI / Claude Code — show a theme while the agent runs, hide when it is done.

Ahalo: a blessing overlay while the agent works

Airflow said success while Apple News still had yesterday's package. Retries with honesty fixed more than any new service.

Ingest, retry, then hand it to Apple News

CLI + indexer + Walrus/SEAL so paid agent skills are fetchable.

Walcraft: marketplace plumbing over clever contracts

When the indexer lags, the product feels wrong even if the chain is right.

Indexer lag is a product bug

Local HTTPS proxy swaps real secrets for format-identical fakes before AI tools see them, then restores them on the way back.

DotMask: fake secrets that still look real

How Ahalo uses agent hook adapters, a shared signal file, and a Swift AppKit overlay so Codex and Claude Code stay stock TUIs while a theme appears only while the agent is busy.

Ahalo deeper: busy/idle hooks without wrapping the TUI

MemWal SDK stays small: write, checkpoint, retrieve.

TypeScript SDK boundaries for agent memory

Search memories without scanning Walrus

On a small team, review is where architecture ships.

Code review is architecture with a diff

Airflow green while Apple News is stale is a lie.

Airflow: prefer honest failure to fake success

Design notes on DotMask’s local HTTPS MITM: format-preserving fakes, declining WebSocket upgrades, decompressing bodies, and the rewrite tradeoffs that come with in-place masking.

DotMask MITM choices: fakes, WebSockets, compression, false positives

Solr → Elasticsearch: parity fixtures and kill switches.

Search migration notes from the Solr years

Sui Objects as wallets, not just tokens

SEAL and paid content without magic URLs

AI drafts fast. Boundaries still need a human merge.

Reviewing AI-generated Move and Rust

Building the Rememe feed API

How Octopus splits identity and refs on Sui, durable Git bundles on Walrus, and a rebuildable local bare-repo cache — plus restore atomicity and the failure modes that matter.

Octopus durability: Sui manifests, Walrus bundles, disposable cache

Lag budgets and a written source of truth per field.

Consistency between chain and Postgres

TDD, Sentry/UXCam, MDM habits from React Native.

Mobile observability habits I still use

402 → settle → retry: replay, latency, logs.

Sharp edges in Sui Agent Payment

Walk the Dugong path tweet  worker  Nautilus refetch → signed payload → sponsored PTB, and name what each hop must not be trusted for.

Dugong trust hops: tweet to Enoki without trusting the middle

Hi — I'm ducnmm. I write about backends, storage, and on-chain systems 😎