gimmie.
Case study Open console Waiting for runtime evidence Checking
Gimmie AI · Autonomous operations

A governed control surface for work performed across OpenClaw, Hermes, and the Gimmie bridge.

RuntimesOpenClaw + Hermes GovernanceHuman approval ProofCanonical receipts
The operating brief

Make autonomous work inspectable before making it scalable.

Gimmie Agent Operations brings scheduled work, human approvals, provider delivery, and proof into one governed console. It separates a model's claim from evidence a human can inspect.

RoleProduct system designScopeAgent operationsInterfaceWeb console
System model
01ObserveRuns · artifacts · cost · freshness
02DecideValidate · approve · reject · retry
03ActOpenClaw · Hermes · Gimmie bridge
Design principles
  • Evidence over claimsA completed run needs retrievable proof.
  • Control before autonomyApprovals and stop controls stay visible.
  • One operating languageEvery runtime reports through canonical receipts.
Engineering case study · September 2026

From scattered agent activity to inspectable operations.

Product and engineering work spans the console design, VM integration, run receipts, runtime diagnosis, and repeatable releases. The console brings OpenClaw schedules, Hermes reports, and the Gimmie task queue into a shared view.

01Execution layerOpenClaw and Hermes on the VM → mounted execution records and artifacts.
02Evidence layerGimmie bridge + PostgreSQL → normalized outcomes, validation, and delivery receipts.
03Operator layerAuthenticated web console → inspect runs, review evidence, and control scheduled work.

Verified improvements: restored brain reachability, connected the CMS using its existing credential, preserved execution metadata, and corrected misleading completion and integration-health states.

Release discipline: automated checks, reviewed production hashes, a scoped deployment package, timestamped backups, and a documented rollback.

Operational capabilities shown here are distinct from business outcomes. Revenue, lead conversion, and time savings are not claimed without measured evidence.

Total Agents
—
—
30-day runs
—
—
Verified success
—
—
Attention required
—
per task
No evidence
—
needs a receipt or validation
Operational review

Attention required

—
AgentRunOutcomeEvidenceAge
Throughput

Task volume today

Hourly distribution across the fleet
Completed
Health

Fleet status

Activity

Top agents by runs

observed · 30 days
Services

External status

Green only on live evidence. Env keys alone read as configured.
Loading…
Unified activity

Latest work across all runtimes