Built for a full-time overland-and-sea traveler who needed one system to remember where they've been, plan where they're going, and keep finances in view — without flying, without SaaS lock-in, without forgetting.
About
Scott is a retired tech founder who traded the headquarters desk for a passport stamped on every continent but Antarctica. He travels full-time with his partner — overland and by sea only, no flying — collecting temples, local food, and a photo archive that outgrew every off-the-shelf assistant.
Generic chatbots could answer questions; none could remember that Tuesday in Kyoto, reconcile a cruise PDF against a Schengen day count, or say whether last month's cloud bill spiked. So he built Wave4u on OpenClaw: a coordinator agent, a council of specialists, and a spec pipeline that ships changes the way a real engineering org would — plan, critique, build, verify.
Wave4u is personal infrastructure, not a product launch. This page exists to show how it works for anyone curious about serious personal-agent systems.
Capabilities
A travel-vault/ single source of truth: bookings, segments,
corridors, Schengen spine, cruise-PDF ingest. World Journal, Year View,
Travel Log, and a read-only Cloudflare Pages mirror. Overland and sea
routing only.
EXIF ingest, geocoding, favorites, hotel/blog tags, and natural-language search across a local SQLite media index. Photos stay on your own drives; only the index lives in the database.
Portfolio snapshots (crypto + equities), spend monitoring, billing ground-truth. Local-only; no money movement. Finance v2 adds live valuation and alerts.
All three share the same memory layers and the same multi-agent pipeline — so a cruise payment reminder and a geocoded harbor photo reference the same truth.
How it's programmed
Wave4u runs like a small engineering org. Four agents, each with a single responsibility — and a hard invariant that keeps the system auditable.
The separation-of-duties invariant is the whole point: the coordinator never moves specs, never self-certifies tests, and never writes production Python. Each gate has exactly one owner. That is why the system stays auditable instead of drifting into one agent marking its own homework.
The pipeline
Every change is a spec that moves through physical directories under
specs/ as it matures. A spec is only ever in one stage at a time.
Memory
Wave4u remembers in tiers — from a structured database, to curated markdown, to a knowledge graph and an evergreen wiki.
| Layer | Store | What it holds |
|---|---|---|
| Structured | SQLite | ~188K rows — media index, travel notes, full-text search |
| Curated files | memory/ markdown | Decisions, daily logs, a hand-curated index |
| Knowledge graph | graphify BFS | LLM-free "what connects to what" in under a second |
| Wiki | wiki/ | Evergreen synthesis — how things work, not what happened |
Technology
OpenClaw ecosystem
The open-source personal-agent harness — persistent memory, skills, heartbeats, comms integrations. openclaw.ai. Wave4u is a deployment, not the framework.
A sibling open-source project — spec-driven workflows, a publishing agent workforce, and public articles on multi-agent ops. studyskills.ai.
A future read-only Cloudflare Pages slice built on synthetic test data — not the live vault. Mentioned here for lineage only; no outbound link until that demo ships.
An Access-gated, read-only snapshot of the live travel source of truth, used by the operator when the home machine is offline. Internal only — no public link.
Wave4u is personal infrastructure today. The OpenClaw framework and these architecture patterns are designed to be reusable and self-hostable; future phases may explore broader ecosystem sharing while preserving the self-hosted core.
Wave4u is by SJK Enterprise. OpenClaw is by its own contributors. No endorsement implied either direction — just honest lineage.
Design system
Cool, technical, night-ops — Vercel dark meets Grafana. A deep-slate palette, Inter for UI, Fira Code for mono, and emoji-native iconography.
Typography: Inter for all UI, Fira Code for mono blocks. Motion stays subtle — 0.15–0.2s ease transitions. Mobile-first; the nav collapses to a menu below 768px.