A neutral provenance ledger that normalizes agent, principal, purpose, limits, merchants, validity, approvals, rail evidence, and settlement into signed, queryable mandate records.
Genesis score7.23/10
Make MandateLog real.0/500
500 more votes and MandateLog is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
69KActive agents reported by one protocol
$50MReported protocol volume
0Neutral cross-rail peers found
The case
Payment rails can enforce agent mandates internally, but each expresses identity, purpose, limits, merchants, time, approval, authorization, and settlement differently. MandateLog preserves the exact mandate and rail evidence behind a payment in a neutral record. It does not replace the rail, hold funds by default, create authority that the principal lacked, guarantee the merchant or purpose was legitimate, or call signature integrity proof of legal, accounting, tax, sanctions, or policy compliance.
Who pays — and why
Finance-platform, payment, marketplace, card, treasury, procurement, audit, and AI-governance teams that need attributable agent-spend evidence across more than one rail.
What it unlocks
A normalized mandate for principal, organization, human authority, agent identity and version, purpose, rail, account, merchant scope, category, currency, amount, cadence, geography, validity, and revocation
Source-preserving adapters that keep native mandate objects, issuance evidence, policy versions, identity bindings, signatures, verification keys, unknown fields, and transformations
Signed provenance queries and exports with key rotation, revocation, correction, access history, retention, deletion rules, and explicit integrity limitations
How Genesis scored it
7.23across seven criteria
8
Productive tension
A durable record is valuable only if it preserves revocation, correction, and source limits rather than claiming immutability of truth.
8
Temporal window
Government and private initiatives plus measured protocol activity make the window current.
5
Convergence
Two cross-references and no inbound connections show limited repetition.
Why it scored well
Live agent identity and payment-control initiatives, a precise cross-rail evidence gap, and a reusable normalization layer create strong timing and tension.
What's holding it back
The category depends on rail cooperation, identity and authority are legally contextual, internal rail logs may be sufficient, and incumbent copying cost is unproven.
Signals detected4 sources crossed
Signalprimary and corroborating research carried in Genesis
Signalmarket research carried in Genesis
Signalprotocol research carried in Genesis
SignalGenesis competitive search
Direction briefmandatelog.md
mandatelog.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.
