BOB - Sovereign Compliance Agent for UiPath

A UiPath Robot submits a document. BOB reasons under the Bel Esprit D'Accord Trust Deed, calls Claude Sonnet 4.6 through AWS Bedrock, returns EVIDENCE or SILENCE, then seals the verdict into a SHA-256 WORM audit chain.

UiPath Studio Maestro Case AWS Bedrock Claude Sonnet 4.6 NATS WORM Seal

Source Repo Submission Summary

Submission Summary

BOB solves the audit gap in enterprise AI automation. When an AI agent approves, blocks, or escalates a document-driven workflow, the enterprise needs proof: what was asked, what policy governed the answer, what verdict was returned, and whether anyone tampered with it afterward. BOB makes that proof the default.

End-to-End Flow

1. UiPath

Studio workflow sends document context to BOB through HTTP or ABZU's Phoenix API.

2. Trust Deed

BOB evaluates under a six-article governing charter, not a loose prompt.

3. Bedrock

Claude Sonnet 4.6 reasons over the packet and returns strict JSON.

4. Verdict

EVIDENCE auto-executes. SILENCE routes to a human review queue.

What It Does

Compliance Verdicts

EVIDENCE means the Robot can proceed. SILENCE means the case is blocked and escalated.

Tamper Evidence

Every verdict is sealed with SHA-256 using verdict, score, query, and timestamp. Change the output and the seal breaks.

Human Control

Unknown vendors, weak evidence, malformed data, and scores below threshold force human review by construction.

Architecture

UiPath Studio -> Main.xaml -> POST localhost:7474/validate
                                  |
                                  v
                    BOB validate-server.mjs
                    - Claude Sonnet 4.6 via AWS Bedrock
                    - Trust Deed v1.0, six articles
                    - strict JSON verdict format
                    - threshold: score >= 0.42
                    - SHA-256 WORM seal
                                  |
                                  v
                    NATS snapkitty.bifrost.sealed
                    - Discord #chain verdict feed
                    - Telegram alert path
                    - ABZU Phoenix API bridge

Optional ABZU path:

UiPath -> POST /api/validate on Phoenix :4000
       -> NATS snapkitty.agents.operator
       -> BOB
       -> NATS snapkitty.bifrost.sealed
       -> Phoenix PubSub verdict:{request_id}
       -> UiPath receives sealed JSON

Formal Theorems

THEOREM: Verdict Completeness

For every submitted document packet d,
BOB(d) returns exactly one verdict:

  EVIDENCE
  SILENCE

There is no third state.

THEOREM: WORM Integrity

seal(v,s,q,t) = SHA256(v | s | q | t)

If verdict, score, query, or timestamp
is changed after emission, the seal no
longer verifies.

THEOREM: Trust Deed Soundness

If Trust Deed policy blocks action a,
model output cannot authorize a.

The charter constrains the model.
The model does not rewrite the charter.

THEOREM: Human-in-Loop Guarantee

BOB(d) = SILENCE
  implies
d enters the human review queue.

Unsupported automation cannot silently
continue.

What Was Built In One Day

BOB Validate Server

Node.js service on port 7474 with HTTP and NATS channels, Bedrock Claude Sonnet 4.6 calls, Trust Deed v1.0, and sealed JSON verdicts.

ABZU Bridge

Phoenix API on port 4000 routes UiPath validation requests through NATS and falls back to direct BOB HTTP if NATS is offline.

Event Mesh

NATS subjects connect BOB, ABZU, Discord, and Telegram so every verdict can be watched in real time.

Coding Agent Build

Built with Claude Code as the coding agent for the UiPath for Coding Agents bonus track, with Codex consolidating the final submission.

Repositories

Primary source:
https://github.com/SNAPKITTYWEST/bob-orchestrator

Public submission page:
https://snapkittywest.github.io/bob-hackathon-demo/

Related bridge:
https://github.com/SNAPKITTYWEST/abzu-sovereign-ide