Skip to content
Protocol v1.0

The identity layer your agents have been missing.

Software development has moved from writing code to steering agents. ribo.dev provides the semantic grounding needed to keep agents aligned with your engineering soul.

ribo --identity-check
Checking artifact: "Auth-v2-invariant"
● Intent: Maintain JWT statelessness
● Evaluation: Passing (100%)
! Warning: Agent 42 attempted database-backed sessions
✖ Blocked: Action violates "Invariant:Stateless"
The Core Framework

The Seven Truth Artifact Types

Define your engineering identity through seven structured layers that agents can actually parse and obey.

lightbulb

Intent

The high-level 'Why'. Why does this service exist? What problem is it solving for the user?

brew install go-ribo/taps/ribo
"intent": "Provide a low-latency cache for high-frequency user metadata without compromising consistency."
lock

Invariant

The non-negotiables. Rules that can never be broken by an agent, no matter the context.

NO_EXTERNAL_CALLS = true
handshake

Contract

Formal interface expectations between services or components.

functions

Algorithm

The specific logic patterns preferred for complex processing.

rule

Evaluation

How we measure success. Metrics and observability markers.

speed

Pace

Deployment velocity and stability thresholds for this truth artifact.

monitoring

Monitor

Real-time health definitions and alert paths.

Discoverability

Semantic Identity Search

Agents don't search for "auth.go". They ask: "What is our authentication approach for internal microservices?" ribo.dev maps natural language to your structural identity.

check_circleResolves architecture patterns, not just file paths.
check_circleConnects disparate truth artifacts via intent-clustering.
searchauthentication approach
Matched artifact: InvariantRelevance: 0.98
Auth-Stateless-Policy

"All microservices must use OIDC with short-lived bearer tokens. No local session storage permitted."

Matched artifact: ContractRelevance: 0.84
Identity-Provider-Interface-v2
Standardized Protocol

Native MCP Support

Integrate ribo.dev directly into your Model Context Protocol (MCP) compatible tools. Claude, Cursor, and custom internal agents can now "speak" your engineering identity natively.

  • settings_input_componentZero-config server for Claude Desktop
  • apiReal-time identity verification in IDEs
mcp-config.json
{
  "mcpServers": {
    "ribo-identity": {
      "command": "ribo",
      "args": ["mcp", "stdio"],
      "env": {
        "RIBO_API_KEY": "rb_live_...",
        "RIBO_ORG_ID": "engineering_hq"
      }
    }
  }
}

Identity Beats Specs

Traditional documentation is a fossil. Swagger specs are too narrow. ribo.dev is the "live soul" of your codebase that agents use to make decisions when you aren't looking.

cancelWithout ribo.dev

Agents hallucinate "best practices" based on generic training data, often violating your specific internal architectural constraints and debt-reduction goals.

check_circleWith ribo.dev

Agents are grounded in your truth artifacts. Every PR, every refactor, and every new feature is verified against your engineering identity before it hits the disk.

Ready to ground your agents?

v1.2.4 • MIT Licensed Core

We use cookies to understand how you use ribo.dev and improve your experience.

Learn more in our Cookie Policy