Skip to content
    Axel Cuevas
    • Home
    • Blog
    • Projects
    • About
    • Resume
    🇺🇸
    Let's talk
    ← All projects02 / 11
    Case 02 · Rivero · 2026

    Orchy — Permission-Gated AI Orchestrator

    An agent that runs backend operations from Slack, and can only touch what it was allowed to.

    StatusInternal · in production
    RoleRivero
    Timeline2026
    CategoryAgents · Orchestration
    StackPythonOpenClawHermesMCPSlack BoltGoogle Workspace API
    LinksWatch demoGitHub
    Demo
    // orchy/cover.pngBrief01/05
    // orchy/cover.png
    [00] Brief

    Orchy is Rivero's internal AI orchestrator, built on OpenClaw and Hermes primitives. Every capability is exposed through MCP integrations behind strict security scopes, so the agent executes real backend operations from Slack, such as Google Workspace provisioning or warehouse lookups, without ever acting outside its grant. A self-learning loop turns resolved threads into reusable procedures: it now closes about 40% of low-complexity engineering tickets on its own, while the permission layer prevents unpermissioned LLM hallucinations from reaching production systems.

    // orchy/cover.png
    [01] Problem

    Routine requests, Google Workspace accounts, warehouse lookups, small fixes, all landed on engineering as Slack threads. An LLM with production access is only acceptable if it cannot act outside what it was granted.

    // orchy/scopes.png
    [02] Build

    Built on OpenClaw and Hermes primitives, every capability is an MCP integration behind an explicit security scope. Orchy reads the thread, checks the grant, executes the backend operation and reports back in Slack; resolved threads feed a self-learning loop that turns them into reusable procedures.

    PythonOpenClawHermesMCPSlack BoltGoogle Workspace APIPostgreSQL
    // orchy/learning.png
    [03] Result

    About 40% of low-complexity engineering tickets now close without a human. The permission layer keeps unpermitted hallucinations from ever reaching production systems.

    40%
    of low-complexity tickets closed on its own
    100%
    of capabilities behind a scope
    0
    actions outside a grant
    Next case

    Rivero Track — Warehouse Platform

    All projects
    03Rivero · 2025 — 26

    Rivero Track — Warehouse Platform

    Receiving, cycle counts, reporting and the semantic layer under one monorepo.

    ← Previous: RIV-Scan — Pallet DimensionerSelected work
    Contact

    Have a system that needs building?

    axeljcuevast@gmail.com
    Santo Domingo · · open to select freelance
    © 2026 Axel CuevasGitHub · LinkedIn · X · Instagram · CVBuilt with Next.js · three.js · GSAP