Skip to main content

​
Commerce V1 Overview

Current OACP authority docs start at OACP Authority Overview. This Commerce V1 page is retained for historical/contextual payment-control pilot material and must not be used to imply that Grantex owns the AgenticOrg seller/buyer runtime, Shopify connector runtime, or provider rail execution. Grantex Commerce V1 is the trust, protocol, policy, and canonical-artifact authority for agentic commerce. AgenticOrg runs buyer and seller agents. Merchant systems remain operational sources of record. Provider and fintech rails own mandate and payment execution. Grantex keeps OACP artifacts, source/freshness rules, refusal semantics, consent posture, and audit evidence safe without becoming a toll booth for every non-binding agent interaction. This page also references the separate Grantex Commerce payment-control pilot. That pilot is not OACP runtime artifact launch proof. OACP runtime proof is limited to AgenticOrg seller onboarding, read-only Shopify evidence, Grantex internal artifact issuance, AgenticOrg cache consumption, buyer-safe answers, bridge metadata, and provider-owned capability metadata. Public discovery, checkout, payment, order, mandate, refund, return, shipment, live-provider execution, certification, conformance, standardization, and public OACP publication are not enabled by the OACP runtime artifact path.

​
Current Posture

​
Start Here

​
Architecture

The important boundary is that the agent does not execute payments or become the merchant system of record. AgenticOrg may initiate approved connector sync jobs and may verify provider-owned mandate capability where approved. Grantex owns artifact authority, policy enforcement, refusal semantics, and evidence requirements. For the full consolidated product requirements, use docs/guides/commerce-v1-agentic-commerce-prd.md as the source of truth.

​
End-To-End Flow Summary

  1. Seller starts in AgenticOrg Seller Commerce Agent, creates an onboarding packet, connects systems through approved connector custody, and requests Grantex authority review.
  2. Buyer completes one-time setup in their preferred channel: account/session linking, safe preferences, and understanding that current OACP runtime answers are non-binding.
  3. Buyer asks an AgenticOrg-powered agent to discover or compare.
  4. AgenticOrg uses cached OACP artifacts when TTL, revocation, and risk rules allow; otherwise it asks Grantex to refresh or verify.
  5. Commitment-bound actions require boundary, envelope, reconciliation, eligibility, and dry-run checks before any future handoff.
  6. AgenticOrg explains sourced facts, warns about stale or unknown data, and refuses unsupported claims.
The Commerce Passport is scoped runtime material. It may be used during approved smoke runs, but it must never appear in committed docs, PR bodies, logs, raw payload dumps, or chat.

​
Readiness Gate Ladder

Each gate is separate. The approved Shopify live pilot does not imply broad merchant self-service, provider certification, or production Plural settlement. The runtime live-readiness gate still requires machine-readable approval evidence; feature flags alone are not sufficient to start live commerce.

​
Allowed And Blocked

  • docs/guides/commerce-v1-agentic-commerce-implementation-prd.md
  • docs/guides/commerce-v1-developer-guide.mdx
  • docs/guides/commerce-v1-merchant-operator-guide.mdx
  • docs/guides/commerce-v1-operations.mdx
  • docs/guides/commerce-v1-repeatable-option-a-smoke-workflow.md
  • docs/api/grantex-commerce-v1.openapi.yaml
Internal Option A smoke evidence and production-discovery readiness records are operator-internal artifacts kept in docs/internal/commerce-v1/ and are available to authorized reviewers on request via sanjeev@orchestrum.in or mishra.sanjeev@gmail.com.

​
Ownership

Grantex is owned by Orchestrum Technologies LLP. Inventor and owner: Sanjeev Kumar. Ownership contact: sanjeev@orchestrum.in or mishra.sanjeev@gmail.com.
Last modified on August 29, 2026