0d29343941
- Added new deployment script references for Aave quote-push and treasury manager in .env.master.example. - Updated AGENTS.md to include information on GRU reference primacy versus public PMM mesh execution model. - Minor updates to various documentation files to reflect changes in policy and operational guidelines. Made-with: Cursor
6.4 KiB
6.4 KiB
GRU reference primacy and mesh execution model
Purpose: Integrate monetary-policy intent into engineering and operations: reference markets and GRU policy define truth; the public cW* PMM mesh and soak grid are execution and capacity layers, not independent FX discovery or shadow-banking surfaces.
Audience: Protocol architects, GRU governance, RTGS/OMNL operators, cross-chain PMM owners, explorer/token-aggregation maintainers, auditors.
Status: Active — treat as a design constraint alongside GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md and GRU_STANDARDS_PROFILE.md.
1. Non-negotiable rule (tail does not wag dog)
- SDR (IMF XDR) and GRU (reserve / valuation unit in the OMNL model) must trace to institution-grade references: published basket methodology, agreed FX rate sets, XAU triangulation where the GL/FX model requires it, and reserve attestations — see mifos-omnl-central-bank/FX_AND_VALUATION.md, mifos-omnl-central-bank/CURRENCY_AND_UNITS.md.
- On-chain PMM prices, DEX midquotes, and bot activity are implementation signals (slippage, inventory, latency). They are not the oracle of record for GRU or XDR unless explicitly adopted as a secondary feed with governance, staleness bounds, and fallbacks.
- Base money (
c*) remains e-money-shaped: par redeemability, segregated reserves, monitoring hooks — runbooks/MULTI_CHAIN_EXECUTION_ISO20022_EMONEY.md. Capability and mesh layers (cW*, PMM, flash wrappers) must not redefine base liability semantics.
2. Three GRU layers + mesh (integrated stack)
This doc does not replace GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md; it pins the public mesh into that stack:
| GRU layer (c* V2 matrix) | Role | Mesh / public-chain touchpoint |
|---|---|---|
| Base money | Canonical c*; payment standards; liability clarity |
Chain 138 canonical tokens; registry + explorer policy |
| Capability | Bridges, cW*, x402, vault/flash wrappers |
cross-chain-pmm-lps token map, pool-matrix, deployment-status |
| Policy / governance | ReserveGate, ComplianceGate, ISO-20022, accounting | M00 facets, institutional JSON, RTGS runbooks |
Mesh execution: cross-chain-pmm-lps/README.md describes the bot-managed PMM stabilization mesh. Under this model, that mesh implements corridor behavior against policy/reference inputs (peg-bands.json, oracles, throttling), rather than inventing FX reality.
3. Integration map (where this must show up)
| Surface | Required linkage |
|---|---|
| OMNL / Fineract FX | Rate matrix, revaluation, GRU/XDR/XAU units — FX_AND_VALUATION.md |
| RTGS / institutional rails | Settlement messaging, UETR vs on-chain ids — 03-deployment/OMNL_DBIS_CORE_CHAIN138_SMART_VAULT_RTGS_RUNBOOK.md, 03-deployment/DBIS_RTGS_FX_AND_LIQUIDITY_OPERATING_MODEL.md |
| Phase C edge pools | Deploy/fund pools after reference and transport policy are clear — 03-deployment/PHASE_C_CW_AND_EDGE_POOLS_RUNBOOK.md |
| Public protocol truth | deployment-status.json + verifier — 11-references/GRU_V2_PUBLIC_PROTOCOL_DEPLOYMENT_STATUS.md (links this policy doc), scripts/verify/check-gru-v2-public-protocols.sh |
| PMM / DEX status narrative | Distinguish Chain 138 venues vs public cW* mesh — 11-references/PMM_DEX_ROUTING_STATUS.md |
| Liquidity taxonomy | Reserve vs public stabilization vs price discovery — 11-references/LIQUIDITY_POOLS_MASTER_MAP.md |
| Soak grid (6,534 wallets) | Operational throughput and segmentation; not a substitute for reserve policy — 11-references/CHAIN138_GRID_6534_WALLET_FUNDING_PLAN.md |
| Stress and dominance discipline | External market baselines for simulation — gru-m1/GRU_M1_REAL_DATA_DOMINANCE_ADDENDUM.md |
4. Implementation checklist (anti–afterthought)
Use this when adding bots, oracles, new cW* rows, or explorer surfaces:
- Name the reference for each corridor (fixing, triangulation path, basket rule, or attested reserve parity).
- Declare on-chain price role (execution only vs allowed secondary oracle) and staleness / divergence behavior.
- Wire policy gates per GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md (ReserveGate / compliance / ISO-20022 routing as applicable).
- Update machine-readable status (
cross-chain-pmm-lps/config/deployment-status.json, config/gru-transport-active.json) so public truth tables stay aligned. - Keep the peg-bands policy hook:
cross-chain-pmm-lps/config/peg-bands.jsonmust retaingruPolicyIntegration(referencePrimacyDoc,meshExecutionRole) so mesh config stays explicitly subordinate to this document. CI enforces it when the submodule is present (scripts/verify/check-gru-reference-primacy-integration.shviavalidate-config-files.sh). - Document edge vs mesh: edge pools scale access; mesh + reference define acceptable executable bounds — consistent with cross-chain-pmm-lps/docs/02-pool-topology.md and Phase C.