OM World Contributors

June 14, 2026 · View on GitHub

Public attribution for everyone who has shaped OM World — from a single design suggestion to ongoing Primitive Stewardship.

The roles, expectations, and lifecycle below are defined in GENESIS-BUILDERS.md.

Past contributions are permanent. Active status can change. Names appear here with the contributor's permission.

Genesis Co-builders

Intent Schema

Co-authors

Kawacu Rugiraneza Arnaud Kennedy — @kawacukennedy · @kawacukennedy on X · kubernalabs.vercel.app — Joined 2026-05-17

Shaped four sections of the Intent Schema across 5 rounds of design dialogue (reference thread):

  • executor binding model — established activation-time binding as the recommended default and explained why creation-time binding defeats permissionless solver networks (commit a3bdb5d)
  • attestation.type: multi semantics — proposed and grounded the ALL-with-fallback-chain-by-dimension model over the original "satisfy at least one" framing, with the anti-pattern rule for same-dimension redundancy (commit a3bdb5d)
  • attestation.verifier per-dimension map — moved the schema default from single routing-contract address to per-dimension addresses; surfaced the dispute-resolution argument (challenger should not need an extra RTT through a router inside a 48h window) (commit cad3c57)
  • attestation.verifier.fallback adjudicator field — added the escape hatch for verifier compromise during the dispute window, with the two-layer compromise response pattern (on-chain VerifierRegistry timelocked pause + off-chain security-council signal) (commit b24ef68)

Reference implementation: Kuberna IVerifierRouter Solidity interface — canonical maintained gist by @kawacukennedy as a reference shape for implementations to adopt or adapt. Licensed Apache-2.0 (matching OM World's code license).

Genesis Reviewer for the intent-schema v0.2 freeze (target 2026-07-04) and the v0.2 freeze wave (2026-08-01).

Agent Mandate

Co-authors will be listed here as primitive design dialogue matures.

Note on agent-passport-system (citation, not co-authorship). The Agent Mandate §Identity model and §Scope narrowing sections draw on the published design of agent-passport-system and IETF draft-pidlisnyi-aps, cited inline at the point of use in docs/agent-mandate.md. At the maintainer's explicit request (2026-05-30, 2026-05-31, 2026-06-11), this is recorded as a citation, not a co-author listing — the exchange was the maintainer answering design questions about their own published implementation, which the inline citation captures accurately. No co-author role, design veto, or standing review commitment is carried.

Execution Proof

Co-authors will be listed here as primitive design dialogue matures.

Tool Registry

Co-authors will be listed here as primitive design dialogue matures.

Genesis Reviewers

Substantive design improvements that landed in the spec. Reviewers are listed once the change ships and the contributor consents to public attribution.

Agent Mandate

@Nolpak14 — Joined 2026-05-18

Multi-round design feedback (reference thread) grounded in production agorio code paths, shaping four sections of the Agent Mandate spec:

  • Three-axis decomposition for cross-protocol composition — the framing of Discovery / Session-state-model / Authorization-carrier as orthogonal axes in §Composition with commerce protocols, preventing the silent leak that happens when any two are collapsed into one Mandate field
  • tools_declared[*].carrier field for explicit carrier binding — a minimal v0.2 addition that lets verifiers reject mandate/carrier mismatches instead of silently adopting bearer semantics, closing the sub-credential expiry split-brain (AP2 mandate.expiresAt vs tools_declared[*].expiry)
  • executor.delegates: address[] for multi-LLM sub-agent attribution — pre-authorizes a set of sub-agent addresses under one parent identity, so EU AI Act attribution (which LLM authorized what) survives without forcing one slashable bond per sub-agent
  • Asymmetric framing of UCP vs ACP in §Composition — UCP is the canonical vocabulary; ACP and AP2 are adapted into it. Stated explicitly so implementers don't assume parity and silently break on ACP-specific behaviors (lifecycle transitions, mid-session payment_handler swap)

Reference implementation: Nolpak14/agorio — quad-protocol toolkit (UCP / ACP / MCP / AP2) cited in §Composition with commerce protocols as a reference single-agent runtime that composes cleanly under an OM World mandate.

Genesis Reviewer for the agent-mandate v0.2 freeze (target 2026-08-01); pre-publication review window ~2026-07-15.

Execution Proof

Tyche Institute — maintainer of the EATF research project · contact dev@tyche.institute — Joined 2026-05-19

Multi-round design feedback (reference thread) shaping two sections of the Execution Proof spec:

  • §Threat model — runtime honesty as an explicit out-of-scope property — added §Threat model at the top of the spec, stating verbatim what the envelope claims and what it deliberately does not, with the composition story (TEE underneath optional, optimistic challenge above, envelope unchanged in either direction). The term "runtime honesty" itself is adopted from Tyche; it sharpens the boundary that prior drafts treated implicitly.
  • §Related work — key-rooted + key-history-mirror as a complementary axis — added EATF to §Related work as a key-rooted reference instance, complementary to the JCS/JWS stack already in the cluster. The cross-spec convergence is now framed around four converging primitives (JCS canonicalization + key-rooted signatures + RFC 3161 timestamping + runtime-honesty out-of-scope) rather than just JCS+JWS+Ed25519.

Posture: Tyche's listing is for technical review of substrate / canonicalization / freshness / revocation decisions. It is explicitly not an endorsement of OM World governance, business model, or any future commercial state. Tyche reserves the right to withdraw attribution if a token, ICO, or commercial offering is introduced prior to v0.2 publication, or if the no-token policy in GENESIS-BUILDERS.md is rescinded.

License of contribution: CC-BY-4.0 (per the prose scope in LICENSE).

Genesis Reviewer for the execution-proof v0.2 freeze (target 2026-08-01); pre-publication review window ~2026-07-25. Schedule conditional on no collision with Tyche's own public-release prep under github.com/tyche-institute — to be confirmed ~2026-07-15.

@Trusteedxyz — Joined 2026-05-17

Multi-round design feedback (reference thread) that shaped six sections of the Execution Proof spec:

  • JCS (RFC 8785) as the canonical-form requirement — moved intent-schema §Canonicalization out of TBD and grounded execution-proof §Canonicalization in a deterministic, multi-language-supported standard (commit d380a69)
  • RFC 3161 timestamp sidecar pattern — added §Long-term verifiability so proofs remain verifiable across signing-key rotation and compromise events without invalidating the original signature (d380a69)
  • Two-state key revocation (rotated vs compromised) — added §Key revocation states with the verifier rule that revocation state is consulted at proof-validation time rather than proof-creation time (d380a69)
  • "Envelope is the unit; slicing is undefined behavior" — pinned in §Envelope as a documented non-goal to prevent the predictable forwarding-of-sub-receipts failure mode ([commit pending])
  • Relayer attestation must commit to exact JCS-canonicalized bytes — encoded as a rule in the new §On-chain verification section, closing the dispute-path reconstruction gap on the relayer-attested path
  • JCS + JWS + Ed25519 ecosystem-convergence note — surfaced in the new §Related work so verifier code can be shared across the cluster

Reference implementation: Trusteedxyz/Trust-Receipt-Verifier — JWS Compact + JCS + Ed25519 trust-receipt stack for agentic commerce.

Genesis Reviewer for the execution-proof v0.2 freeze (target 2026-08-01).

attestplane project — maintained by @merchloubna70-dot — Joined 2026-05-21

Multi-comment design feedback (reference thread), backed by five concrete artifacts published on the attestplane side, shaping three elements of the Execution Proof spec:

  • §On-chain verification — verifier-independence rule — the trust root MUST be the deterministic open-source verifier + versioned schemas + exported evidence bytes; hosted indices, APIs, or convenience services are an acceptable convenience layer for discovery and retrieval, but verification correctness MUST NOT depend on trusting them (commit 61979b1)
  • §Deletion evidence (commit-then-redact) — a new top-level section: minimize PII before ingest → commitments in the chain → raw/deletable material in a controller-owned sidecar → on verified deletion, destroy the sidecar and append a signed deletion-evidence event, preserving the envelope's append-only property (61979b1)
  • §Related work — compliance-and-audit-substrate corner of the convergence cluster — attestplane added as the AIA-12-aligned-profile reference instance, carrying the alpha-stage qualifier and the "evidence-substrate primitives, not a legal compliance conclusion" caveat as defended framing (61979b1)

Posture: attestplane's listing is a spec-level convergence only — technical review of audit-substrate / verifier-independence / retention-deletion decisions. It is explicitly not an endorsement of OM World governance, business model, or any future commercial state, and carries no joint marketing, hosted-service endorsement, or economic axis. Opt-out at any time per GENESIS-BUILDERS.md.

License of contribution: CC-BY-4.0 (per the prose scope in LICENSE).

Genesis Reviewer for the execution-proof v0.2 freeze (target 2026-08-01); pre-publication review window ~2026-07-25.

ark-forge/proof-spec (Compliance Receipts v0.1, maintained by @desiorac) — Joined 2026-05-23 · institutional attribution confirmed 2026-05-25

Multi-comment design feedback (reference thread) shaping five elements of the Execution Proof spec:

  • §Canonicalization — absent-optional-fields rule — explicit rule that missing optional fields (e.g. context_hash, attestation) are excluded from the JCS input rather than serialized as null, preventing divergent hashes from identical step data when implementations disagree on null-vs-omit
  • §Canonicalization — context_hash binary-presence rule — context_hash is either absent (tool output fully determined by inputs — pure function / stateless transform) or present-with-a-real-hash (output depends on external state); "" and empty-hash encodings are explicitly invalid
  • §Step record — plan_hash pre-commitment clarification — explicit that the mandate's plan_hash is the pre-committed value from the intent record (set before execution begins), not a hash computed by the agent at proof time; binds the chain to what was authorized rather than what the agent claims it did
  • §Related work — Compliance Receipts v0.1 composability — previous_receipt_hash in CR v0.1 is structurally equivalent to prev_hash in OM World's Step record; chained proof mode composes with the CR v0.1 pipeline format without additional fields
  • §Open questions — two v0.2 boundary markers added at the reviewer's request: (i) config-injected stateless tools (env vars / feature flags / per-tenant settings) — current lean is explicitly out-of-scope at step level for v0.2, with a composability test vector to surface implementation disagreements; (ii) parallel step execution — linear prev_hash is sequential-only; flagged as v0.3+ fork point for Merkle-root composition over parallel step-hash sets

Reference: ark-forge/proof-spec — Compliance Receipts v0.1 open spec for verifiable agent-to-agent execution proofs.

Posture: spec-level convergence only — not an endorsement of OM World governance, business model, or any future commercial state. Institutional attribution chosen as the durable referent (the spec project, not whoever happened to maintain it at review time).

License of contribution: CC-BY-4.0 (per the prose scope in LICENSE).

Genesis Reviewer for the execution-proof v0.2 freeze (target 2026-08-01); pre-publication review window ~2026-07-25. A draft PR on ark-forge/proof-spec (#2) is open with the field mapping, the canonical step_hash formula, the absent-optional-fields + context_hash binary-presence rules, and three JSON examples exercising the stateless/stateful/anti-pattern edge case. To be updated with a config-injected stateless-tool test vector per the 2026-05-25 review pass.

Primitive Stewards

Stewards take long-term maintenance ownership of a primitive's spec section, typically after v1.0 freeze.

(none yet — earliest possible Steward appointment is post-v0.2)

Genesis Co-builder Emeritus

Past Co-builders who have stepped back from active status. Their attributed contributions remain in the lists above.

(none yet)

How attribution works

  • Listing here requires the contributor's permission. If you have shaped the spec but are not listed, you may not have been asked yet — open an issue tagged genesis-builders and we will reach out.
  • Listings are concrete: they cite the specific spec sections or commits the contribution shaped, not a general "thanks to X."
  • Past contributions are permanent. We do not rewrite attribution if active status later changes (see GENESIS-BUILDERS.md §Lifecycle).
  • Listings link to the contributor's GitHub profile by default; alternate handles (X, personal site) are added on request.