HN Showcase
Back to browse
GitHub Repository

Covenant Layer is an open model for outcome-based coordination between users, agents, brokers, providers, verifiers, and settlement services. This repository contains the working protocol draft, network architecture, security model, diagrams, and demo outline.

68 starsRust

Agents shouldn't operate software–they should coordinate commitments

by csehammad·Mar 13, 2026·3 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidBold BetBig Brain

Shifts agents from tool operators to commitment coordinators with evidence settlement.

Strengths
  • •Separates probabilistic reasoning from deterministic execution cleanly.
  • •Provider accountability with evidence submission reduces failure modes.
Weaknesses
  • •Protocol spec only—no working implementation or demo shown.
  • •Requires provider ecosystem adoption to function at all.
Category
AI/ML
Target Audience

AI agent framework developers

Similar To

LangGraph · AutoGen · CrewAI

Post Description

I've been working on Covenant Layer — an open protocol and framework for shifting AI agent systems from tool orchestration to outcome coordination.

The core idea: agents shouldn't operate software step by step. They should publish objectives, compare competing provider offers, accept the best one under policy, and let providers fulfill outcomes with evidence and settlement.

Why this matters: we're still building agents as "software operators" — better interns that click through UIs and call APIs. That forces probabilistic models to produce deterministic side effects. The failure modes (wrong clicks, prompt injection, "probably right" becoming "committed") keep piling up.

https://github.com/csehammad/covenant-layer

Covenant Layer moves the edge from procedures to commitments. The agent handles intent, comparison, approval. The provider handles execution, evidence, accountability.

What's in the repo: - Protocol spec - Rust + Solidity implementation (onboarding, conformance, registry) - E2E demo: JFK→CDG flight booking with 3 competing providers on Base Sepolia - Architecture diagrams and security rationale

Early draft. Would love feedback on the model, weak assumptions, or missing pieces.

Similar Projects