A record of becoming.

An AME is an ERC-721 identity, not an executable runtime. Its token ID provides a stable reference while the owner, assigned agent wallet and metadata describe its current state.

A transfer changes the owner and clears the previous wallet assignment. Core receipt history remains associated with the identity. Lending positions and repayment obligations remain bound to their contract-defined accounts; an NFT transfer does not transfer a borrower’s obligations or authorize a new operator.

Contracts define ownership and permitted writes. Wallet authorization determines who can act. Events expose the records from which the frontend builds readable views.

CONTRACTS

Enforce ownership, issuance and market-specific rules.

AUTHORIZATION

Checks the signer’s permissions in the relevant contract; connecting a wallet grants no financial authority.

EVENTS

Provide ordered, chain-specific evidence of accepted contract interactions.

FRONTEND

Reads, indexes and presents state; prepares eligible actions without custody of user keys.

An assertion needs a source.

An interaction begins with an identifiable origin: a wallet action, a contract event or an external result. Verification must be appropriate to that origin. A confirmed repayment event can establish a contract transition; an external task outcome requires a verifier and an explicit trust model.

1. ORIGINIdentify the actor, network and action.
2. VERIFICATIONCheck source evidence and the verifier’s authority.
3. ISSUANCEAccept only contract-authorized receipt writers.
4. ASSOCIATIONAttach the attestation to the correct identity.
5. INTEGRITYRetain transaction order, issuer and referenced data.

Authorized actors append attestations. In the core receipt contract, the current NFT owner or assigned agent wallet can issue a receipt. That permission does not make a self-issued claim independently verified.

Receipts are attestations, not proof of execution.

Onchain inclusion establishes who recorded an attestation and when. It does not establish the truth of every asserted outcome or the permanent availability of externally referenced content. Financial engine events and core identity receipts are distinct sources, each with its own authority and trust assumptions.

Evidence in. Interpretation out.

Identity continuity makes activity attributable over time. Repayment history, verified outcomes, liquidation events and the provenance of each record can become inputs to a defined evaluation model.

A credible model must distinguish accepted evidence from unverified claims, retain provenance and account for negative outcomes. Token balance, wallet size and NFT ownership alone are not measures of credit quality. Historical account control must be verified before attributing wallet activity to an identity.

The existing testnet lending engine has a narrow informational repayment score. It does not adjust borrowing limits, collateral requirements or interest rates. General task weighting and reputation-driven credit policies remain separate, unimplemented models.

History informs risk.
Markets define access.

Liquidity providers supply assets to a market. An authorized borrower interacts under that market’s collateral, oracle, liquidation and repayment rules. Available liquidity limits borrowing and withdrawals; reputation does not create capital or guarantee a loan.

Wallet ownership, token balances, allowances and account authorization are checked for the relevant action. Collateral value, debt and risk limits depend on the actual market and verified oracle inputs. Financial events extend the borrower’s history; linking that history to an NFT requires verified attribution.

MORPHO

Robinhood Chain Mainnet market reads cover USDG / USDe and USDG / syrupUSDG. Mainnet transaction signing remains disabled.

IDENTITY

Current identity minting uses Robinhood Chain Testnet (46630). Mainnet market reads use chain 4663 independently.

ACCESS

Verified $AME balances identify holders. The lending application retains its holder gate; premium and lending entitlements require separately approved access rules. Product access is separate from market solvency and borrower eligibility.

RISK

A future reputation policy may inform eligibility; collateral, oracle validity, liquidity and market-specific safeguards still constrain any credit decision.

One identity.
A continuing record.

1. 01IDENTITY CREATED→
2. 02WALLET ASSOCIATED→
3. 03ACTIVITY VERIFIED→
4. 04RECEIPT RECORDED→
5. 05HISTORY EXPANDED→
6. 06REPUTATION EVALUATED→
7. 07CREDIT INTERACTION

Identity creation and wallet assignment establish the reference and its permitted actors. Accepted attestations and financial events expand the readable history. Verification depends on the source; reputation evaluation and reputation-conditioned credit are model-dependent stages, not automatic consequences of minting an NFT.

Identity is the origin.
History is the signal.
Reputation is the interpretation.
Credit is the consequence of an eligible market interaction.

Tasks V1 adds wallet-authorized, user-assisted activity to agent history. Signed submissions are graded against confirmed chain evidence. Wallet control, contract research and transaction analysis earn at most 60 Task XP per ownership epoch after durable recording is enabled.

Task XP is independent from repayment-based financial reputation. It grants no lending permission and changes no rates or credit limits. The current evidence tools award no XP while production persistence remains disabled. Records are offchain attestations, not onchain receipts or autonomous execution claims.