{
  "$schema": "https://docs.mobazha.org/visual-evidence.schema.json",
  "schema_version": "1.1",
  "reviewed": "2026-07-06",
  "visuals": [
    {
      "id": "mobazha-product-atlas",
      "src": "/images/docs/project/mobazha-product-atlas.svg",
      "sha256": "b0adee81eb14228fadc3d9169c797ae48d959468cb1d0624387d6cac00add54c",
      "mobile_src": "/images/docs/project/mobazha-product-atlas-mobile.svg",
      "mobile_sha256": "ed550f42de13888a9098a949f92703059376dff315832b8d84511bacd68df9c1",
      "kind": "conceptual",
      "width": 760,
      "height": 460,
      "mobile_width": 360,
      "mobile_height": 720,
      "alt": "Conceptual Mobazha product map showing storefronts, community channels, and Agent integrations connected to an operator-selected backend, with payment, delivery, discovery, and hosted services as explicit dependencies.",
      "caption": "One commerce core can support several operating and distribution paths without moving business-state authority into the presentation channel.",
      "claim": "Explains the product and authority model; it does not assert that every pictured channel, integration, or external service is available in every distribution.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "product-atlas-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "identity-storefront-model",
      "src": "/images/docs/project/identity-storefront-model.svg",
      "sha256": "ba28eef9f58d55f80205f6f697b6f116a8f292be60aa87edfa7624124653f9dd",
      "mobile_src": "/images/docs/project/identity-storefront-model-mobile.svg",
      "mobile_sha256": "f1f499dd4f8608e44b08fb04737e3ebc3654c6d291c16f954817958bcbab532f",
      "kind": "conceptual",
      "width": 760,
      "height": 500,
      "mobile_width": 360,
      "mobile_height": 760,
      "alt": "Conceptual model separating an access account or credential, the store and Node business-state boundary, storefront views that share store state, and the channels that present those views.",
      "caption": "Accounts authorize access, stores own business state, storefronts shape presentation, and channels provide entry context.",
      "claim": "Explains product and authority boundaries; it does not assert that every distribution enables multiple stores, named storefronts, every channel, or future identity models.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "identity-storefront-model-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "transaction-spine",
      "src": "/images/docs/project/transaction-spine.svg",
      "sha256": "448c48082fa809c22ffcc16ca1abfea2842886dbdb20fcf4721100ee5b1ea77d",
      "mobile_src": "/images/docs/project/transaction-spine-mobile.svg",
      "mobile_sha256": "5ee3aa4aa173c2b8fb5ae4f606fe8c54f07182e4f6eceab0f9e7dcb478d09bd7",
      "kind": "conceptual",
      "width": 760,
      "height": 500,
      "mobile_width": 360,
      "mobile_height": 760,
      "alt": "Conceptual transaction spine showing a normal path from reviewed terms through order creation, payment verification, fulfillment, and completion, with separate bands for order authority, payment evidence, and policy-gated recovery.",
      "caption": "One trade connects order, payment, and protection state without collapsing them into one misleading status.",
      "claim": "Explains durable authority and recovery boundaries; it does not assert that every distribution, order, payment rail, or protection model exposes every pictured action.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "transaction-spine-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "community-commerce-network",
      "src": "/images/docs/project/community-commerce-network.svg",
      "sha256": "d83e1826fafaf27e1c5d390816f39f87ea0ffbdd5cef1d82c675404500efddfd",
      "mobile_src": "/images/docs/project/community-commerce-network-mobile.svg",
      "mobile_sha256": "c80d73c32601f4533864e4a18818de8c2fa596f6f0b4cb6e36bf0421f6096684",
      "kind": "conceptual",
      "width": 760,
      "height": 520,
      "mobile_width": 360,
      "mobile_height": 780,
      "alt": "Conceptual distributed discovery model showing community, Web, direct-link, and Agent channels entering an operator-owned market projection, with participating stores remaining separate transaction authorities.",
      "caption": "Markets organize audience, consent, access, and curation; a selected offer still hands off to one seller-owned transaction.",
      "claim": "Explains durable discovery and transaction boundaries; it does not assert that every market shape, channel, access mode, domain flow, or curation feature is available in every distribution.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "community-commerce-network-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "agent-commerce-boundary",
      "src": "/images/docs/project/agent-commerce-boundary.svg",
      "sha256": "e0db66ef2305b8b88849c263cfa1c7b7670202c87ce8d0b5ca4dc0e5bd9471a7",
      "mobile_src": "/images/docs/project/agent-commerce-boundary-mobile.svg",
      "mobile_sha256": "a15207ce3572657c8e9d0af4366dc89010f40b5ca788d997bfc32e8cd011c1bf",
      "kind": "conceptual",
      "width": 760,
      "height": 520,
      "mobile_width": 360,
      "mobile_height": 780,
      "alt": "Conceptual Agent-commerce execution path from a user goal through persona and scope, a Skill, current Tool discovery, request-bound approval, Core validation, and an audited result.",
      "caption": "Reasoning proposes an action; typed identity, scope, capability, approval, and Core state gates decide whether it executes.",
      "claim": "Explains current authority primitives and a safe composition model; it does not assert that every Skill, Tool, workflow, approval policy, model, or autonomous mode is available.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "agent-commerce-boundary-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "offer-to-fulfillment",
      "src": "/images/docs/project/offer-to-fulfillment.svg",
      "sha256": "507cd4856700f982c65068076ba9db5e830c7a351190e91318a0073fe5209528",
      "mobile_src": "/images/docs/project/offer-to-fulfillment-mobile.svg",
      "mobile_sha256": "f7cc389b9e4620a3d7105518d322baa28053eeb69ac256d5a0d8e1a8cb1ba61b",
      "kind": "conceptual",
      "width": 760,
      "height": 520,
      "mobile_width": 360,
      "mobile_height": 780,
      "alt": "Conceptual commerce flow from supply facts through a seller-owned listing revision, merchandising projection, accepted quote and order, and fulfillment evidence, with external providers and Core authority kept separate.",
      "caption": "One seller-owned promise can use several merchandising, supply, and fulfillment models without allowing later changes to rewrite an accepted order.",
      "claim": "Explains durable offer and fulfillment boundaries; it does not assert that every product shape, discount, collection rule, supply provider, or delivery path is available in every distribution.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "offer-to-fulfillment-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "surfaces-and-integrations",
      "src": "/images/docs/project/surfaces-and-integrations.svg",
      "sha256": "aa8b65bf62d385f4c06382c37dbf8cec07d44cb886c975ab8ca88e591840dd94",
      "mobile_src": "/images/docs/project/surfaces-and-integrations-mobile.svg",
      "mobile_sha256": "3d61795f1ef455f36eed00ae8376160138c9f4a60809abf592670140bb86df98",
      "kind": "conceptual",
      "width": 760,
      "height": 540,
      "mobile_width": 360,
      "mobile_height": 800,
      "alt": "Conceptual model showing Web, mobile, desktop, community, embedded, browser, and Agent shells resolving server context before using HTTP, WebSocket, webhook, MCP, or chat contracts to reach capability-gated Core commerce state.",
      "caption": "Many experience shells and interaction contracts can share one server-resolved context and one Core-owned commerce authority.",
      "claim": "Explains durable surface and transport boundaries; it does not assert that every client shell, domain route, channel, event, chat service, Tool, or integration is available in every distribution.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "surfaces-and-integrations-v1",
      "applies_to": "Mobazha v0.3 release-candidate product model",
      "reviewed": "2026-07-06"
    },
    {
      "id": "buyer-order-lifecycle",
      "src": "/images/docs/buy/order-lifecycle.svg",
      "sha256": "ae6227f538038f4be74d93a3402810cb7220802eb98850c6ae610c7ebcdc3e93",
      "mobile_src": "/images/docs/buy/order-lifecycle-mobile.svg",
      "mobile_sha256": "712799d325a9e67bcec89e5021cb25777bde7e960f886c01d64a95dd0f7f6567",
      "kind": "conceptual",
      "width": 760,
      "height": 420,
      "mobile_width": 360,
      "mobile_height": 560,
      "alt": "Conceptual buyer journey from reviewing one seller quote through payment, fulfillment, and completion, with recovery actions dependent on active order state.",
      "caption": "One seller-owned order, from reviewed quote to observable completion.",
      "claim": "Explains the documentation authority and milestone model; it does not assert that every deployment exposes every transition.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "buyer-order-path-light-v2",
      "applies_to": "Mobazha v0.3 release-candidate guidance",
      "reviewed": "2026-07-06"
    },
    {
      "id": "seller-operating-loop",
      "src": "/images/docs/sell/store-operating-loop.svg",
      "sha256": "821c17af3a6aab26ef274d08e5de9f32e0feb08e13c4f38fda195f2f2b55f2b8",
      "mobile_src": "/images/docs/sell/store-operating-loop-mobile.svg",
      "mobile_sha256": "26f1cf6ab939bfcc90e4bb61b9b4126a40dbeaa37a8401a781813f463c138777",
      "kind": "conceptual",
      "width": 760,
      "height": 420,
      "mobile_width": 360,
      "mobile_height": 560,
      "alt": "Conceptual seller operating loop covering store identity and policy, listings, payment readiness, a test purchase, and ongoing order operations.",
      "caption": "A store is ready only when the complete buyer journey has been tested.",
      "claim": "Explains the operator responsibility sequence; it is not evidence that a specific store has completed these checks.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "store-readiness-loop-light-v2",
      "applies_to": "Mobazha v0.3 release-candidate guidance",
      "reviewed": "2026-07-06"
    },
    {
      "id": "self-host-trust-boundary",
      "src": "/images/docs/self-host/operator-trust-boundary.svg",
      "sha256": "9d5d1114d2d192696b77f458663d56d3e4af3f3ba7afac0d81678ed63952451b",
      "mobile_src": "/images/docs/self-host/operator-trust-boundary-mobile.svg",
      "mobile_sha256": "72cc8ec3ce49620736bf7dfd223c389f7cd318fdf578d1ad358ea8e1e924437d",
      "kind": "conceptual",
      "width": 760,
      "height": 420,
      "mobile_width": 360,
      "mobile_height": 560,
      "alt": "Conceptual self-hosting boundary showing clients entering through an operator-controlled network boundary to a Mobazha Node and local data, with payment systems and optional hosted services remaining separate dependencies.",
      "caption": "Self-hosting moves operational control to the Node operator; external dependencies remain explicit.",
      "claim": "Explains responsibility boundaries and does not prescribe one mandatory network topology.",
      "privacy_review": "synthetic-only",
      "source": "https://github.com/mobazha/mobazha-docs",
      "source_revision": "self-host-boundary-light-v2",
      "applies_to": "Mobazha v0.3 release-candidate guidance",
      "reviewed": "2026-07-06"
    }
  ]
}