OpenChainGraph Suite · wave 29 · compliance_mandate

ViDA Platform & Registration

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Classify a digital platform as a ViDA deemed supplier under Art. 46a — short-term accommodation or road transport (art-162) → route the supply to the correct ViDA Single VAT Registration scheme: Union OSS, Non-Union OSS, IOSS, or Domestic VAT (art-163) → scored ViDA readiness diagnostic with 2028/2030/2035 obligation timeline (art-164). EU 2025/516, platform rule mandatory 2028-07-01. Zero network, zero PII.

OpenChainGraph · 3 Steps compliance mandate ViDA EU 2025/516 Art. 46a · OSS/SVR W3C VC §13.11 Hash-Anchored §4 chain_depth:3 · Zero PII
Chain Topology — ViDA Platform & Registration (art-162→163→164)
art-162 Deemed Supplier Classifier art-163 OSS Registration Router art-164 Readiness Diagnostic ⊥
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1ROOT · D0node
Deemed supplier verdict feeds OSS registration router
MCP Call · classify_vida_platform_deemed_supplier
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "classify_vida_platform_deemed_supplier",
    "arguments": {
      "platform": {
        "sector": "short_term_accommodation",
        "duration_nights": 3,
        "supplier_has_valid_vat_id": false,
        "intra_eu_supply": true
      }
    }
  },
  "id": 1
}
↓
2MIDDLE · D1node
OSS scheme recommendation feeds readiness diagnostic
MCP Call · route_vida_oss_registration
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "route_vida_oss_registration",
    "arguments": {
      "supply": {
        "supply_type": "deemed_supplier",
        "seller_establishment": "DE",
        "destination_member_state": "FR"
      }
    }
  },
  "id": 2
}
↓
3TERMINAL · D2node
Exports scored ViDA readiness position with phased obligation timeline — final stage
MCP Call · run_vida_readiness_diagnostic
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_vida_readiness_diagnostic",
    "arguments": {
      "entity": {
        "einvoice_ready": true,
        "drr_ready": true,
        "platform_not_applicable": true,
        "oss_scheme_configured": true
      }
    }
  },
  "id": 3
}
Export Artifacts
Download the §4 chain definition artifact or the §13.11 W3C VC view. Each of art-162, art-163, and art-164 individually support Policy Mandate JSON and W3C VC export.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: Deemed-supplier rules now reach our platform sellers. Which VAT registration scheme should they use for their cross-border sales?
Run the AINumbers MCP tool `run_chain` with {"chain":"vida-platform-and-registration"} and read `art-163-vida-oss-registration-router.recommended_scheme`.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/vida-platform-and-registration.html