{"id":51035431,"url":"https://github.com/byte5ai/omadia-proof","last_synced_at":"2026-06-22T05:30:30.761Z","repository":{"id":365088371,"uuid":"1270355873","full_name":"byte5ai/omadia-proof","owner":"byte5ai","description":"Make any binding action provable across trust boundaries — without anyone touching a key, a wallet, or a chain.","archived":false,"fork":false,"pushed_at":"2026-06-15T19:48:05.000Z","size":82,"stargazers_count":0,"open_issues_count":15,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-06-15T21:22:19.560Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/byte5ai.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":"AGENTS.md","dco":null,"cla":null}},"created_at":"2026-06-15T16:24:11.000Z","updated_at":"2026-06-15T20:15:15.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/byte5ai/omadia-proof","commit_stats":null,"previous_names":["byte5ai/omadia-proof"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/byte5ai/omadia-proof","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/byte5ai%2Fomadia-proof","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/byte5ai%2Fomadia-proof/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/byte5ai%2Fomadia-proof/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/byte5ai%2Fomadia-proof/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/byte5ai","download_url":"https://codeload.github.com/byte5ai/omadia-proof/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/byte5ai%2Fomadia-proof/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34636427,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-22T02:00:06.391Z","response_time":106,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-06-22T05:30:29.502Z","updated_at":"2026-06-22T05:30:30.756Z","avatar_url":"https://github.com/byte5ai.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cdiv align=\"center\"\u003e\n\n# omadia-proof\n\n### Make any binding action provable across trust boundaries — without anyone touching a key, a wallet, or a chain.\n\nomadia Proof embeds **[ANP](https://github.com/byte5ai/anp)** — the Agent\nNotarization \u0026amp; Negotiation Protocol — into the\n**[omadia](https://github.com/byte5ai/omadia)** agentic OS. Every binding\naction — a decision, an agreement, a witnessed fact — becomes a signed,\nschema-valid, hash-chained, on-chain-*anchored* receipt. The content stays\noff-chain; only a hash + status reach the ledger. DIDs, keys, signature suites,\nanchoring, escrow — all of it is capsuled, so a manager or employee without an\nIT background experiences just one thing: *\"this is now recorded, verifiable,\nand tamper-proof.\"*\n\n[![License: MIT](https://img.shields.io/badge/License-MIT-black.svg)](LICENSE)\n[![Status: design](https://img.shields.io/badge/status-design-orange.svg)](#status--roadmap)\n[![Implements: ANP v0.3-draft](https://img.shields.io/badge/implements-ANP%20v0.3--draft-6f42c1.svg)](https://github.com/byte5ai/anp)\n[![Plugin for: omadia](https://img.shields.io/badge/plugin%20for-omadia-2496ED.svg)](https://github.com/byte5ai/omadia)\n[![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)\n\n[**Website**](https://omadia.ai) · [**Plan**](plan.md) · [**Fact base**](research.md) · [**Issues**](https://github.com/byte5ai/omadia-proof/issues) · [**ANP spec**](https://github.com/byte5ai/anp/blob/main/SPEC.md) · [**Contributing**](CONTRIBUTING.md)\n\n\u003c/div\u003e\n\n---\n\n\u003e **Status — design / pre-implementation.** This repository currently holds the\n\u003e reviewed implementation [plan](plan.md) and the verified [fact base](research.md)\n\u003e (the plan's load-bearing assumptions checked against the real ANP spec and\n\u003e omadia code). Package code lands per the phase plan below — **nothing here is\n\u003e runnable yet.**\n\n## The whole user surface is four words\n\nThe user never thinks in protocols or pillars. They think in one question —\n*\"do I want this to be undeniable later?\"* — and if yes, they tap a button.\nProof translates that into the right ANP pillar:\n\n| What the user wants | They see | What Proof does underneath |\n|---|---|---|\n| Record that we said / decided this | **Record** | Memorandum (self- or co-signed) |\n| Confirm that something is / was so | **Witness** | Attestation (`observed` / `relayed`) |\n| Make an arrangement binding | **Agree** | Contract: offer / accept (+ optional escrow) |\n| Have a disagreement settled | **Resolve** | Optimistic dispute: assert / dispute / rule / enforce |\n\nNo crypto vocabulary ever reaches the UI — no *hash*, *DID*, *wallet*, *anchor*.\nThe technical receipt is one click away under *View details*, never pushed.\n\n## Why it exists\n\nomadia already gives every run an audit *receipt* — but that receipt lives in\nyour own database, which proves to *you* what *your* system did. A Proof receipt\nis different: it proves to a **mistrustful counterparty or regulator** what was\nagreed or witnessed **across** a trust boundary — externally anchored,\nunalterable by either side. Proof is the bridge from the internal log to the\nexternal, shared fact.\n\nANP normally assumes every actor runs keys and wallets — the exact friction that\nsinks DLT adoption with humans. omadia already has the agent that absorbs it:\nProof turns *\"the human must operate a wallet\"* into *\"the human taps Confirm,\nthe custodial layer signs.\"* It secures all four topologies —\n**Human→Nobody, Human→Human, Agent→Human, Agent→Agent** — with agent-to-agent\nas the strategic centre.\n\n## Architecture\n\nProof is **not a monolith**. It is a small layer of capability providers plus UI\nextensions, shipped as a signed plugin bundle and installed into omadia, with a\nsingle kernel-side hook for the escalation gate.\n\n```\n  omadia UI  ──  Record · Witness · Agree · Resolve cards, confirm dialogs, proof inbox\n       │   proofRef (opaque) + human-readable summary — never raw crypto (Privacy Shield)\n       ▼\n  Orchestrator hooks  ──  native tools: proof.record / attest / agree / resolve\n       │                  + escalation gate: mandate threshold ⇒ human approve   ← one kernel PR\n       ▼\n  Proof capability layer  (signed plugin bundle)\n    proof.objects    ANP object build · JCS canonicalization · schema · hash chain   (pure logic)\n    proof.identity   custodial DID/key per user + agent · mandates · SD-JWT disclosure (the crypto capsule)\n    proof.signer     PQC-capable suite (ML-DSA / SLH-DSA), detached signatures\n    proof.anchor     the DLT seam — IOTA Rebased profile (swappable); a mock for CI\n    proof.store      off-chain object store + data availability; void-on-unavailability\n```\n\nThe full design — risks, cut lines, data model, API surface — is in\n[`plan.md`](plan.md).\n\n## Relationship to the family\n\n- **[omadia](https://github.com/byte5ai/omadia)** — Proof is an omadia plugin\n  bundle. It lives 100% in this repo except one small kernel-side hook (the\n  pre-dispatch escalation gate), needed only once agent-to-agent lands.\n- **[ANP](https://github.com/byte5ai/anp)** — omadia is the **first** ANP\n  implementation, so Proof effectively formalizes the per-object JSON schemas the\n  spec only references today. **Every schema Proof defines or changes MUST ship\n  as a PR back to `byte5ai/anp` in the same unit of work** — the RFC is\n  canonical, not the code ([plan §1.4](plan.md)).\n\n## Status \u0026amp; roadmap\n\nWork is tracked as [issues](https://github.com/byte5ai/omadia-proof/issues)\nacross seven milestones:\n\n| Milestone | Delivers |\n|---|---|\n| **Stage A — Architecture freeze** | blocking ADRs (naming, store, DID method, custody, schema matrix, privacy dataflow) before any code |\n| **Phase 0 — Foundation** | `proof.objects`, mock anchor, plugin scaffold + CI; byte-identical canonicalization |\n| **Phase 1 — Record, solo** | Human→Nobody self-record, custodial identity, proof inbox — the adoption opener |\n| **Phase 2 — Real anchoring + Witness** | IOTA-Rebased anchoring, attestation, data availability / verify-link |\n| **Phase 3 — Two parties** | Human↔Human co-signing, `agree` (offer / accept) |\n| **Phase 4 — Agent-to-Agent** | agent DIDs, mandates, the kernel escalation gate — the strategic centre |\n| **Phase 5 — Resolve + escrow** | optimistic dispute, small-claims profile, settlement |\n\n## Honest limitations\n\nStated up front, per the plan's own framing:\n\n- **Not a legal form.** Proof is a *technical*, tamper-proof receipt. Notarial /\n  eIDAS-qualified form is a separate, later integration — Proof never claims\n  legal force.\n- **Custodial keys.** The \"no wallet\" magic means keys are held custodially in\n  omadia's vault. A deliberate custody trade-off (mandate caps bound the blast\n  radius); the upgrade path to HSM / own keys is a single-package swap.\n- **Escrow inherits the chain's native crypto.** Binding signatures are\n  post-quantum-capable; escrow custody is only as quantum-safe as the chain.\n\n## Documents\n\n| File | What |\n|---|---|\n| [`plan.md`](plan.md) | The implementation plan (Codex-reviewed) — architecture, API surface, risks, phases |\n| [`research.md`](research.md) | Verified fact base — the plan's assumptions checked against the real ANP spec + omadia code |\n| [`AGENTS.md`](AGENTS.md) · [`CONTRIBUTING.md`](CONTRIBUTING.md) | Engineering standards, worktree + PR workflow, schema-backflow rule |\n\n## License\n\n[MIT](LICENSE) — Copyright (c) 2026 byte5 GmbH\n\n## Contributing\n\nSee [`CONTRIBUTING.md`](CONTRIBUTING.md) for the dev setup, the worktree + PR\nworkflow, and the mandatory ANP schema-backflow rule: every change that defines\nor alters an ANP object schema must open a matching PR against\n[`byte5ai/anp`](https://github.com/byte5ai/anp).\n\n## Maintainership\n\nomadia Proof is maintained by [byte5 GmbH](https://byte5.de) under the GitHub\norganisation [`byte5ai`](https://github.com/byte5ai).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbyte5ai%2Fomadia-proof","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbyte5ai%2Fomadia-proof","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbyte5ai%2Fomadia-proof/lists"}