13d0d7130e
- config/gru-governance-supervision-profile.json + gru-standards-profile cross-refs - GRU_STORAGE_GOVERNANCE_AND_SUPERVISION_STANDARD.md; GRU matrix/profile doc updates - naming-conventions: 03 bridges/cross-chain, 04 registry JSON fields; README table complete - validate-config-files: governance profile checks (existing jq rules) - reports/identity-completion: templates + README for DID/governance completion path - mlfo-gitea-avatar.svg; refreshed transaction-package-HYBX-BATCH-001.zip - gitignore: .codex, tmp/, regenerated output audit trees/zips, token-lists/logos PNGs Submodules remain dirty locally (commit inside each submodule separately). Made-with: Cursor
57 lines
3.7 KiB
Markdown
57 lines
3.7 KiB
Markdown
# 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
|
|
|
|
- **Config:** [`config/gru-standards-profile.json`](../../config/gru-standards-profile.json)
|
|
|
|
## 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 mirrored `cW*`**
|
|
- the payment profile for **x402**
|
|
- the required base-token standards for `c* V2`
|
|
- the transport / wrapper standards for `cW*`
|
|
- the required storage, governance, and supervision metadata for `c*`, `cW*`, and tokenized assets
|
|
- 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:
|
|
|
|
1. A `138 -> chain` mapping exists in [`config/token-mapping-multichain.json`](../../config/token-mapping-multichain.json).
|
|
2. The destination `cW*` deployment is non-zero in [`cross-chain-pmm-lps/config/deployment-status.json`](../../cross-chain-pmm-lps/config/deployment-status.json).
|
|
3. `bridgeAvailable` is `true` in that deployment status entry.
|
|
4. The chain is explicitly enabled in [`config/gru-transport-active.json`](../../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.json`](../../config/gru-iso4217-currency-manifest.json)
|
|
Tracks which currencies exist and their current lifecycle state.
|
|
- [`config/gru-transport-active.json`](../../config/gru-transport-active.json)
|
|
Activates the currently enabled canonical tokens, compatible destination chains, and public pools.
|
|
- [`config/gru-governance-supervision-profile.json`](../../config/gru-governance-supervision-profile.json)
|
|
Captures deterministic storage namespaces, jurisdiction-review rules, supervision metadata, and upgrade notice periods.
|
|
- [GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md](GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md)
|
|
Explains the same standards in narrative form and maps them to contracts/facets.
|
|
- [GRU_STORAGE_GOVERNANCE_AND_SUPERVISION_STANDARD.md](GRU_STORAGE_GOVERNANCE_AND_SUPERVISION_STANDARD.md)
|
|
Defines the required metadata, jurisdiction-review flow, and storage namespace rules for governed assets.
|
|
- [CHAIN138_X402_TOKEN_SUPPORT.md](CHAIN138_X402_TOKEN_SUPPORT.md)
|
|
Records the current x402-ready token state on Chain 138.
|
|
- [GRU_FX_CURRENCY_ONBOARDING_CHECKLIST.md](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, deterministic storage namespaces, jurisdiction/supervision metadata, 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.
|
|
- **Governance scope:** proposal tagging by jurisdiction, jurisdictional authority approval when required, and minimum upgrade notice periods that survive across asset families.
|