Home Demo Paper Docs About

Phase 1 · Building · Live Demo Available

OrgForge

Cryptographic governance.

A governance layer for humans and autonomous agents.
Organizations define rules. OrgForge enforces them at execution.

See It Run → Read the Whitepaper
Actor
human · agent · bot
any actor
submitIntent()
declares action
ORGFORGE
Governance Engine
the gate
✓ AUTHORIZED
→ Execute Action
✗ REJECTED
→ Block + Log
Actor
human · agent · bot
any actor
↓
submitIntent()
declares action
↓
ORGFORGE
Governance Engine
the gate
↓
✓ AUTHORIZED
→ Execute Action
↓
✗ REJECTED
→ Block + Log
LIVE DEMO →
agent:trader_1 → PLACE_ORDER ETH-USD $20,000 → REJECTED: ERR_MAX_ORDER_EXCEEDED ($10k limit)
The Problem

Governance that depends on trust is governance that can fail.

Modern organizations are increasingly made of software: APIs, bots, pipelines, schedulers, and now autonomous agents. Once an action can be executed by code, the organization's rules become optional unless they are enforced at the point of execution.

A generation ago, shared computing faced this same problem. Multi-user systems ran on fragile assumptions. Over time, access control became a first-class primitive. We did not just write policies. We built systems that enforced them.

Organizations now need that same shift. Not for access. For authority itself.

We trust that people follow policy.
We trust that approvals are real and not rubber-stamped.
We trust that permissions are configured correctly across a growing number of services.
We trust that automation will not exceed its mandate, even as it accumulates credentials.
We trust that logs will exist when something goes wrong, and that someone will notice.

In practice, governance is a narrative layered on top of execution.
Not a mechanism inside it.

How It Works

Intent → Authorization → Execution.

Every action begins as an intent. OrgForge evaluates it against the organization's constitution. The result is a cryptographic proof. Execution systems accept or reject it.

Submit Intent
Any actor (human, bot, or AI agent) declares what they want to do before doing it.
{ actor: "agent:trader_1", action: "PLACE_ORDER", params: { notional: 8000 }, nonce: "0x4a91…", expires_at: 1712000300 }
Check the OrgSpec
Validators deterministically evaluate the intent against the organization's machine-readable constitution.
max_order_usd: 10000 allowed_markets: [ETH-USD] approval_threshold: 10000 max_trades_per_min: 10
Issue Authorization Proof
A 2-of-3 quorum produces a signed proof bound to the exact intent hash. Unforgeable.
{ decision: "AUTHORIZED", intent_hash: "0x2b0f…", quorum_signatures: […], expires_at: 1712000360 }
Execute or Block
Execution adapters verify the proof before acting. No valid proof. No execution. Replay-protected.
verify(proof) → EXECUTED receipt: ord_000012 ETH: +2.666… USD: -8000
Infrastructure Pattern

Every major protocol is a control gate.

The most important infrastructure in computing follows the same pattern: a verification layer that sits between actors and execution. OrgForge introduces that layer for organizational authority.

Stripe
App
→ Stripe →
Bank Network
Standardized payment authorization
Cloudflare
User
→ Cloudflare →
Origin Server
Security + routing layer
Chainlink
Contract
→ Chainlink →
External Data
Verifiable oracle network
OrgForge
Actor
→ OrgForge →
Execution
Programmable governance enforcement. The missing layer.
The Pattern

Two protocols. The same move. One layer apart.

Bitcoin proved you do not need a bank to authorize a transaction. OrgForge proves you do not need a centralized service to authorize an autonomous agent's action.

Bitcoin had to displace banks that already existed. OrgForge arrives before the centralized version of agent governance has entrenched. That is the strategic window.

Bitcoin  =  transactions ∅ intermediaries  (trusted financial)
OrgForge  =  authorization ∅ intermediaries  (trusted authority)
Bitcoin  →  Money Movement
OrgForge  →  Permission to Act
Use Cases

Any actor. Any action. Any system.

OrgForge does not care what is being executed. It enforces governance wherever actions happen. On-chain, off-chain, or both.

// AI AGENTS
Autonomous Agent Safety
AI agents can trade, deploy code, call APIs, and move money. OrgForge enforces hard limits before any of it executes.
AI agent: PLACE_ORDER $50k OrgForge: REJECTED → ERR_MAX_ORDER_EXCEEDED (limit: $10,000)
// DEVOPS
Deployment Pipelines
Production deployments require authorization. No signed proof. No deploy. Regardless of who holds the keys.
deploy: production actor: ci_bot → requires: engineer approval → AUTHORIZED (human:alice) → Deploying…
// ENTERPRISE
Corporate Authorization
Payment approvals, vendor disbursements, and infrastructure changes. All governed by a single machine-readable policy.
vendor_payment: $120k policy: CFO approval > $100k → REJECTED: ERR_APPROVAL_REQUIRED approver: cfo@org
// DAO TREASURY
DAO & Protocol Governance
Replace fragile multisigs and manual voting flows with deterministic enforcement of treasury rules and proposal execution.
Transfer $500k to partner → requires: 3 approvals → status: 2/3 received → PENDING_APPROVAL
// DEFI
Smart Contract Governance
On-chain execution gated by an OrgSpec stored on-chain. Every governance change is versioned and auditable.
contract.execute(call) → verify(auth_proof) → proof valid + fresh → EXECUTED on-chain
// COMPLIANCE
Audit-Ready by Default
Every intent, every proof, every receipt is logged with a cryptographic hash. Compliance becomes a property of the system, not a process.
intent_hash: 0x2b0f… receipt_hash: 0x9c1a… orgspec_version: v4 decision: AUTHORIZED ✓
Architecture

Layer 3 is where real power lives.

Most governance tools address identity or voting. OrgForge targets the layer that actually matters: who is allowed to act, and what enforces that at the moment of execution.

LAYER 01
Identity
Who is part of the organization?
ENS / DID / SSO
Role assignment
Membership registries
LAYER 02
Governance
How are decisions made?
Snapshot / Tally
Voting systems
Aragon / Compound
LAYER 03: ORGFORGE
Execution Authority
Who is allowed to act, enforced at the point of execution?
OrgSpec (machine constitution)
Authorization proofs
Execution adapters
Roadmap

Service → Network → Protocol.

The strongest protocols in computing started narrow and expanded to become infrastructure. OrgForge follows the same trajectory. Prove the primitive. Decentralize the network. Open the ecosystem.

PHASE 0 · COMPLETE ✓
Authorization Engine
Deterministic authorization primitive. 2-of-3 validator quorum. 25/25 test assertions passing. The kernel proved.
PHASE 1 NOW
Governance Firewall
Policy enforcement proxy for AI agent tool calls. Intent evaluation against OrgSpec. Authorization gate before execution. The primitive.
PHASE 2 · 6mo
Policy Engine
OrgForge becomes the source of truth for organizational policy. Developers build against the API. On-chain registry goes live.
PHASE 3 · 12mo
Org Operating System
Full organizational lifecycle. Proposals, votes, budgets, payments, audit logs. All coordinated through OrgForge.
PHASE 4 · 24mo
AI Coordination Layer
The governance layer for autonomous systems. Agents negotiate under constraints. Organizations run on OrgForge.
Research

Published. Patented. Documented.

The OrgForge whitepaper introduces deterministic authorization as a cryptographic primitive. Published on Zenodo with DOI, arXiv submission pending endorsement (cs.CR), and covered by U.S. provisional patent applications.

Read the Whitepaper → View on GitHub
DOI  ·  10.5281/zenodo.18968718
ORCID  ·  0009-0008-1254-1652
Patent  ·  U.S. Provisional Applications Filed · Patent Pending
Get Involved

The governance layer
organizations need.

Phase 0 is complete. Phase 1 is underway. If you are building systems where governance matters, we want to talk. AI agents. DAOs. Automated finance.

See the Live Demo → Read the Whitepaper
25/25
TEST ASSERTIONS PASSING
2-of-3
VALIDATOR QUORUM
5
PIPELINE STAGES
FAIL‑CLOSED
BY DESIGN