We are a team of 5: 2 admins, 2 treasury operators, and 1 risk reviewer. We want to earn onchain yield on 1,000,000 USDC through Aave and Morpho on Arbitrum One. Use the official Chainwall CLI and its chainwall-operations skill to prepare an account, approved lending actions, spending limits, and approval rules. Build and test the setup before asking us to approve deployment or funding. Use the official skill Invoke $chainwall-operations if installed. Otherwise read skills/chainwall-operations/SKILL.md at https://github.com/okcontract/chainwall-cli-arbitrum/blob/main/skills/chainwall-operations/SKILL.md and follow it with its references and assets. If installing it, copy the complete skill folder, not just SKILL.md. Read references/setup.md, authoring.md, execution.md, and operations.md for this task. GitHub: https://github.com/okcontract/chainwall-cli-arbitrum GitHub: https://github.com/okcontract/chainwall Use matching local checkouts at ../chainwall-cli-arbitrum and ../chainwall-public when available. Record the reviewed commits and CLI version. Use the CLI repository's README.md and MANUAL.md, current command help, schemas, artifacts, and deployed contract behavior as the implementation references. https://docs.chainwall.org/docs provides additional context. Do not invent subcommands, addresses, ABIs, policy features, or ready-made protocol integrations. Start with chainwall --version, chainwall --help, chainwall config show, and chainwall doctor --json. Reuse existing configuration in an explicit project profile. Verify the RPC is Arbitrum One (42161), the official OKFactory, and any existing Registry, Interact, and account bindings. Check which facets are installed; an ABI in the CLI does not prove the deployed instance supports it. Ask only for missing addresses, access, or decisions that block the next step; continue local preparation with clearly marked placeholders. Use a native OKAccount unless an existing Safe needs to be retained. For a Safe, follow the skill's guarded import workflow and inspect owners, threshold, guard, modules, and every execution path. Registering an address alone does not protect it. Identify the address serving as signer, approval actor, gas payer, managed account, and Registry; some roles may share an address. Prepare and test now. Use named Foundry keystores or supported hardware wallets; we handle secrets in our own terminals. Never request, read, print, or store them in chat, source files, logs, or command arguments. Before any mainnet broadcast, present the exact transactions for approval. Deployment, acceptance of the exact factory terms, funding, and role transfers each need explicit authorization. The CLI is preview software and its README says it is unaudited and not considered safe for production use; prepare a fork rehearsal and identify what remains before live use. Our treasury and team - Alice and Ben are the two admins. Changes to approved contracts, scripts, policies, budgets, group membership, capabilities, and upgrades require both admins and a 48-hour waiting period. Map these requirements to the actual Registry governance categories and scopes, including changes to the delay itself. - Cara and Diego are treasury operators. Either can propose and execute an approved lending operation, with approval from at least one of them AND Erin, our risk reviewer. Use separate groups and criteria; an admin signature cannot substitute for Erin's approval. Erin has no execution or configuration powers by default. Distinguish these business roles from Registry roles and capabilities. - Our example treasury holds 1,000,000 native USDC on Arbitrum One, not bridged USDC.e. Target 200,000 USDC kept liquid, 400,000 supplied to Aave V3, and 400,000 deposited into one reviewed Morpho USDC vault or market. These are planning allocations, not authorization to move funds. Verify current deployments, availability, liquidity, fees, and withdrawal conditions from official protocol sources. Identify the exact Morpho integration and its risks before choosing its ABI; do not assume Morpho markets and ERC-4626 vaults share an interface. - Start with lending only. Exclude borrowing, leverage, bridging, swaps, and arbitrary transfers. Keep receipt tokens, shares, supplied positions, and withdrawal proceeds owned by the managed account. Use exact required allowances to approved spenders and clear residual allowances where supported. Implement the lending rules Prepare narrow interactions for supplying and withdrawing USDC on Aave and depositing and withdrawing through the selected Morpho integration. Fix the asset, contracts, market parameters, account, and recipient. Bind every interaction to its intended policy and account so choosing a weaker policy cannot bypass the checks. Check return values, actual asset/share changes, and minimum received amounts where needed. Cap new lending at 100,000 USDC per operation and 250,000 USDC in total per day across both protocols and both operators. Use the maintained policy-meter pattern for the cumulative limit; specify its units, window boundaries, shared counter, and reset behavior. A per-operation ceiling alone is insufficient. Prevent new deposits from taking idle USDC below 200,000. Withdrawals back to the same account must remain possible without consuming the deposit budget. Label the target allocations separately from enforced limits. If a rule needs new code, show the gap and prepare the smallest reviewed implementation rather than claiming configuration already enforces it. Compile and analyze the Lambdascript and policy programs with verified ABIs and catalog entries. Reuse the skill's templates where applicable, render every placeholder, and retain source, compiler settings, artifacts, and analysis. Chainwall supplies the account and execution rules; this treasury does not need us to issue ERC-4626 shares. Treat a future customer-facing vault and its accounting as a separate integration. Prove the treasury setup On a pinned Arbitrum fork, rehearse setup and a 10,000 USDC deposit/withdrawal round trip for each integration. Check balances, shares or position accounting, allowances, approvals, and gas. Test missing Erin approval, an unauthorized operator, a different recipient or spender, a weaker policy, the wrong account, the per-operation ceiling, cumulative deposits split across both operators and protocols, the day boundary, the liquid reserve, and an external call failure that must roll back the entire transaction and meter update. Test delayed changes, cancellation, and recovery when a required signer is unavailable. Show which withdrawals can still fail because the lending protocol lacks liquidity or is paused. Deliver a reviewable setup 1. Produce a table of people, accounts, exact permissions, approval thresholds, limits, and delays. For each rule, cite the enforcing contract or script and mark it as supported configuration, new code, or an unresolved gap. 2. Prepare reproducible CLI commands, configuration, interaction and policy sources, compiled artifacts, schema-validated operation files, and fork test results. Get exact command shapes from --help and --schema. Use IDs returned by the selected instance. Verify token decimals and encode amounts, uint256 words, and timestamps as exact integer strings in JSON without floating-point conversion. Keep private configuration and signing material out of Git. 3. Distinguish calldata previews from simulations: --dry-run usually only previews. Use explicit policy and operation simulation with the actual executor and required approvals, record the block and decoded result, and repeat against live installed state before an authorized execution. Do not claim an unpublished policy was simulated onchain. Interact operation approvals and Registry timelock approvals are separate workflows; a queued Registry write must apply before dependent steps. 4. Present the deployment or migration sequence, exact factory terms for human review, estimated fees, and remaining decisions. Verify governance, recovery, and ownerBootstrapFinalized before funding or transferring protocol authority. Explain the availability cost of requiring both admins or the sole reviewer and propose a governed replacement process. 5. After separately authorized broadcasts, preserve transaction hashes, receipts, returned operation/action IDs, and applied or pending state. Verify actual balances and permissions with fresh reads. Recover interrupted transactions before retrying. Leave a runbook for routine actions, signer replacement, pauses, cancellations, and failed transactions. State the remaining risks precisely. Chainwall checks configured execution paths; it cannot guarantee yield, liquidity, solvency, or the safety of approved contracts, oracles, upgrades, or keys. Simulations describe one chain state and do not guarantee later execution.