Back to corpus
technical notebacklog referencescore 22

Handoff: Mesh / V1.1 Event-Sourced Rail / KARL Reward Engine

**From:** the agent running the "Life of Leisure, mesh from phone" goal (mac1, main session) **To:** the SEA (skill-entity-architecture) agent **Date:** 2026-05-14 **Why you're getting this:** you've been working on SEA / the mac3-worker-config track. This session drifted from a phone-app build into a corpus-wide KARL reward-engine repair. The work is real and committed, but one piece (`karl train`) is blocked on a rate-limited machine, and you may be able to unblock it. Full context below so you can pick up cleanl

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**From:** the agent running the "Life of Leisure, mesh from phone" goal (mac1, main session) **To:** the SEA (skill-entity-architecture) agent **Date:** 2026-05-14 **Why you're getting this:** you've been working on SEA / the mac3-worker-config track. This session drifted from a phone-app build into a corpus-wide KARL reward-engine repair. The work is real and committed, but one piece (`karl train`) is blocked on a rate-limited machine, and you may be able to unblock it. Full context below so you can pick up cleanly. The active `/goal` is the **"Life of Leisure, mesh from phone"** build: run all 5 Macs (mac1-5) + K11 from an iPhone, hands-off, via two pieces: - **aura-gateway** — FastAPI service on `mac1:8095`, launchd label `com.openclaw.aura-gateway`, file at `[home-path]`. The control plane: inject prompts cross-machine over SSH+tmux, spawn sessions, autopilot loops, wake-on-LAN, and a **flow runtime**. - **Pebble** — iOS app at `Desktop/Pebble/`, bundle `com.diomande.pebble`. The phone surface. Conversations list + chat + a FlowsSection driving the gateway's flow runtime. The leisure metric: "Tier-C taps per active hour, under 5 = leisure." The point is to walk away from the laptop. **The honest summary:** KARL was never a deliberate destination. The V1.1 architecture verdict (Path C + Path F from the divergent doc) said completed flows become KARL trajectory cards. Phase 2 wired that. "Backfill the scores" was a natural next-step — and once inside KARL, the backfill kept hitting pre-existing bugs that had nothing to do with flows. Every record in the corpus was scoring a flat 0.5. Fixing that was the right call (root-cause over symptom) but it drifted us well off the leisure/mesh goal.

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.