{
  "schema_version": "initiative-changes.v1",
  "registry_version": "2026.06.10-8752c9d",
  "initiative_id": "arbitrum-ecosystem-readiness",
  "change_count": 7,
  "changes": [
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-agentic-commerce-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "Arbitrum can serve as a low-cost execution surface for agentic commerce demos that combine payment, identity, wallet, and automation components.",
      "affected_roles": [
        "agent_builders",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "agentic_commerce_teams",
        "marketplace_builders",
        "payment_flow_builders",
        "wallet_onboarding_teams"
      ],
      "affected_protocols": [
        "arbitrum-one",
        "x402",
        "erc-8004",
        "privy",
        "safe",
        "gelato",
        "biconomy"
      ],
      "affected_chains": [
        "arbitrum-one",
        "arbitrum-sepolia"
      ],
      "affected_intents": [
        "build-agentic-commerce-with-x402",
        "gasless-onboarding"
      ],
      "possible_consequences": [
        "Agents should separate the execution chain choice from payment protocol and agent identity/discovery choices.",
        "x402 should be treated as a payment layer, while ERC-8004 should be treated as agent identity/discovery/reputation/validation infrastructure.",
        "Builders should not imply ERC-8004 is a chain or that 8004scan is chain ID 8004."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-composable-defi-dapps",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "Arbitrum stack plans should account for composable DeFi and dApp dependencies such as Aave, Morpho, Uniswap, and other liquidity venues when the user flow needs them.",
      "affected_roles": [
        "defi_builders",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "lending_app_builders",
        "swap_app_builders",
        "portfolio_app_builders",
        "agentic_defi_builders"
      ],
      "affected_protocols": [
        "arbitrum-one",
        "uniswap"
      ],
      "affected_chains": [
        "arbitrum-one"
      ],
      "affected_intents": [
        "swap-tokens-in-my-app"
      ],
      "possible_consequences": [
        "Agents should ask whether the project needs lending, borrowing, vaults, swaps, pricing, liquidation data, or portfolio state before choosing dApps.",
        "Aave and Morpho should be added as first-class registry records before Composewith makes detailed readiness claims about them.",
        "Until coverage is added, agents should cite official Aave/Morpho sources directly and label them as registry coverage gaps."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:aave-arbitrum-market",
        "official:morpho-docs",
        "official:arbitrum-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-infra-data-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "indexer_surface",
      "status": "reviewed",
      "summary": "Arbitrum apps often need an explicit infra/data layer for indexing, price feeds, automation, wallets, and account abstraction rather than only a chain choice.",
      "affected_roles": [
        "app_builders",
        "data_engineers",
        "wallet_teams",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "indexing_teams",
        "oracle_users",
        "account_abstraction_builders",
        "marketplace_builders",
        "defi_builders"
      ],
      "affected_protocols": [
        "the-graph",
        "goldsky",
        "chainlink",
        "pyth",
        "safe",
        "privy",
        "gelato",
        "biconomy"
      ],
      "affected_chains": [
        "arbitrum-one",
        "arbitrum-sepolia"
      ],
      "affected_intents": [
        "real-time-price-feeds",
        "gasless-onboarding",
        "build-agentic-commerce-with-x402"
      ],
      "possible_consequences": [
        "Agents should include indexer/oracle/wallet/automation requirements in Arbitrum stack plans when the user flow depends on them.",
        "Builders should cite official support for the specific chain and data source they use.",
        "A low-cost L2 recommendation is incomplete if the demo cannot read the data or trigger the actions it claims to support."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-docs",
        "official:arbitrum-chain-info"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-orbit-appchain-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "protocol_architecture",
      "status": "reviewed",
      "summary": "Orbit is the Arbitrum appchain path for custom L2/L3 chains, but most hackathon teams should justify it against a simpler Arbitrum One deployment.",
      "affected_roles": [
        "appchain_teams",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "appchain_builders",
        "gaming_teams",
        "custom_gas_token_teams",
        "high_throughput_app_teams"
      ],
      "affected_protocols": [
        "arbitrum-orbit"
      ],
      "affected_chains": [
        "orbit",
        "arbitrum-one"
      ],
      "affected_intents": [
        "launch-an-appchain"
      ],
      "possible_consequences": [
        "Agents should ask about operations capacity, data availability assumptions, custom gas token needs, and bridge/RPC/sequencer plans before recommending Orbit.",
        "For a 48-hour MVP, Orbit should usually be a demo architecture or explicit appchain track choice, not an accidental default.",
        "Builders need a fallback plan that starts on Arbitrum One if chain operations are outside the timebox."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-orbit-docs",
        "official:arbitrum-orbit-sdk"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-privacy-app-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "Arbitrum privacy app recommendations should focus on credible user-flow privacy boundaries rather than broad anonymity claims.",
      "affected_roles": [
        "privacy_builders",
        "wallet_teams",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "privacy_wallet_builders",
        "private_voting_builders",
        "private_app_builders",
        "demo_teams"
      ],
      "affected_protocols": [
        "arbitrum-one",
        "fluidkey",
        "semaphore",
        "railgun"
      ],
      "affected_chains": [
        "arbitrum-one",
        "arbitrum-sepolia"
      ],
      "affected_intents": [
        "build-privacy-first-ethereum-wallet",
        "build-private-onchain-voting",
        "build-private-smart-contract-app"
      ],
      "possible_consequences": [
        "Agents should check whether a privacy protocol/dApp actually supports the intended Arbitrum chain before recommending it as an implementation dependency.",
        "For hackathon demos, mocked or offchain privacy flows should be labeled clearly if production integration is not complete.",
        "README and pitch copy should include do-not-claim guidance for anonymity, unlinkability, and production security."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-shared-l2-build-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "protocol_architecture",
      "status": "reviewed",
      "summary": "Arbitrum One is the default shared L2 surface for most hackathon MVPs that need low-cost EVM execution without appchain operations.",
      "affected_roles": [
        "hackathon_builders",
        "app_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "solidity_app_teams",
        "defi_builders",
        "wallet_builders",
        "agentic_app_builders"
      ],
      "affected_protocols": [
        "arbitrum-one"
      ],
      "affected_chains": [
        "arbitrum-one",
        "arbitrum-sepolia"
      ],
      "affected_intents": [
        "deploy-on-a-low-cost-l2",
        "gasless-onboarding",
        "swap-tokens-in-my-app"
      ],
      "possible_consequences": [
        "Agents should usually choose Arbitrum One before recommending Orbit for a small MVP.",
        "Builders can preserve standard EVM tooling while targeting lower-cost execution than Ethereum mainnet.",
        "Bridge, sequencer, and chain-specific support assumptions should still be stated in README and pitch materials."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-docs",
        "official:arbitrum-chain-info"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "arbitrum-stylus-build-surface",
      "initiative_id": "arbitrum-ecosystem-readiness",
      "type": "evm_capability",
      "status": "reviewed",
      "summary": "Stylus is a credible Arbitrum build surface for Rust, C, and C++ contracts, but it should be selected for a reason rather than by default.",
      "affected_roles": [
        "smart_contract_developers",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "rust_contract_teams",
        "performance_sensitive_app_teams",
        "game_builders",
        "agentic_execution_builders"
      ],
      "affected_protocols": [
        "arbitrum-stylus"
      ],
      "affected_chains": [
        "arbitrum-one",
        "arbitrum-sepolia"
      ],
      "affected_intents": [
        "write-smart-contracts-in-rust"
      ],
      "possible_consequences": [
        "Agents should recommend Stylus when the project benefits from non-Solidity languages, performance-sensitive logic, or reusable Rust/C/C++ code.",
        "For simple ERC-20-style contracts or teams without Rust/C/C++ experience, standard EVM deployment is the safer hackathon path.",
        "README claims should distinguish Stylus experimentation from audited production readiness."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:arbitrum-stylus-docs"
      ],
      "last_verified_at": "2026-06-09"
    }
  ]
}