2 posts tagged with "schema"

Type 2 agents -- Reggie and Henry -- run on remote VMs under OpenClaw, and OpenClaw publishes a new minor release roughly every three days. Each release tends to add, rename, or restructure config keys. If you tried to keep a hand-rolled admin page in sync with that, you would lose. The Type 2 Agent CONFIG page in RABS solves it the only way that scales: it does not know about specific settings at all. Each time it loads, it asks each VM "what is your config schema right now?", walks the answer, and renders a row for every settable variable -- titles, descriptions, types, validation hints, and current values, all the way down. When OpenClaw 2026.4.30 adds a new field next week, the page just shows it. No code change, no deploy. That's the design intent and tonight we made it actually work end-to-end.

The scheduling brain of RABS just had its biggest renovation since the project began. The metaphor names everyone learned -- workshed, loom, ribbon -- have done their job and are now retired. In their place sits core_engine: a born-clean Postgres schema with 19 tables, a dedicated instance API at /api/v1/engine, a fully-wired program creation wizard, and a working philosophy for how the past becomes truth. Twelve backend route files were rewritten to point at the new schema. Seventy-three real billing rates replaced the POC junk rows. The wizard now handles NF2F lines, participant photos, participant fees, click-to-edit time slots, and full draft management. None of this is theoretical anymore.