CLASSIFICATION REVIEW — Account context, money, assets, wrappers, and security state

[satonakaoshimoto]

Keep account, asset, financial state, and external law separate

An agent needs multiple classifications, but no single internal label should silently overwrite the others.

WHO IS ACTING
IAM / Bank of Me, Us, Business, Institution, or Government/Governance

WHAT IS INVOLVED
M1 Money + Utility / M2 Commodities / M3 Titled or Unique RWA

WHAT FINANCIAL OR REGULATORY PROFILE APPLIES
M4 Financial Wrapper / M5 Jurisdictional Security-State Profile
+ external authoritative legal and regulatory state

WHAT MAY HAPPEN NOW
credentials + delegation + restrictions + jurisdiction + approvals
→ M5Canon

M1–M5 internal states do not create currency, legal tender, a security, commodity, deposit, regulated status, property right, transfer authority, or governmental recognition. External statutes, regulations, courts, agencies, registries, contracts, and responsible professionals remain authoritative.

Help us review

• Which machine-readable fields prevent account context from being confused with asset class?
• How should an agent distinguish a payment instruction, token, underlying right, title record, financial wrapper, and security-state profile?
• What issuer, unit, redeemability, custody, transferability, restriction, and jurisdiction disclosures are required?
• How should changing legal classifications be versioned and sourced?
• When must an agent refuse to classify and refer the matter to qualified legal, accounting, tax, or regulatory review?
• What tests prevent marketing language or UI labels from implying official status?

Start with the M5-agent hub · Read the economic architecture · Read ICSN-0014