7ac74f432b
- Institutional / JVMTM / reserve-provenance / GRU transport + standards JSON - Validation and verify scripts (Blockscout labels, x402, GRU preflight, P1 local path) - Wormhole wiring in AGENTS, MCP_SETUP, MASTER_INDEX, 04-configuration README - Meta docs, integration gaps, live verification log, architecture updates - CI validate-config workflow updates Operator/LAN items, submodule working trees, and public token-aggregation edge routes remain follow-up (see TODOS_CONSOLIDATED P1). Made-with: Cursor
2.9 KiB
2.9 KiB
GRU Standards Profile
Purpose: Define the machine-readable standards profile for canonical c* V2, mirrored cW*, x402 capability, GRU governance/policy enforcement, and the broader ISO-4217-plus asset scope.
File
What it standardizes
This profile is the shared standards contract between docs, configs, operators, and future contract work. It records:
- the canonical methodology: Chain 138 keeps canonical
c*; compatible public chains carry mirroredcW* - the payment profile for x402
- the required base-token standards for
c* V2 - the transport / wrapper standards for
cW* - the GRU M00 governance and policy standards
- the broader asset scope: ISO-4217 fiat currencies, approved commodities, and future monetary units
Compatibility boundary
The profile does not mean every public chain or every currency is live today.
A destination chain is only considered compatible for GRU Transport when all of the following are true:
- A
138 -> chainmapping exists inconfig/token-mapping-multichain.json. - The destination
cW*deployment is non-zero incross-chain-pmm-lps/config/deployment-status.json. bridgeAvailableistruein that deployment status entry.- The chain is explicitly enabled in
config/gru-transport-active.json.
That keeps the standards profile broad while keeping the active transport overlay conservative and operationally precise.
Relationship to other files
config/gru-iso4217-currency-manifest.jsonTracks which currencies exist and their current lifecycle state.config/gru-transport-active.jsonActivates the currently enabled canonical tokens, compatible destination chains, and public pools.- GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md Explains the same standards in narrative form and maps them to contracts/facets.
- CHAIN138_X402_TOKEN_SUPPORT.md Records the current x402-ready token state on Chain 138.
- GRU_FX_CURRENCY_ONBOARDING_CHECKLIST.md Uses this standards profile as part of the acceptance gate for new currencies.
Current intent
- Standards scope: x402, EIP-712, ERC-2612, ERC-3009, ERC-5267, AccessControl, Pausable, ISO-20022-aligned policy routing, and GRU M00 governance/policy facets.
- Asset scope: all currencies added to the GRU manifest, not just the currently active USD lanes.
- Transport scope: every public chain that is structurally compatible according to mapping, deployment, and bridge metadata.