REVIEW — Which account context does an M5Agent serve?

[satonakaoshimoto]

Account context: Bank of Me through Bank of Government / Governance

An M5Agent must act for a named human or lawful entity in a defined account context. The account context describes who the agent serves and the relationship in which it acts:

Code	Account context	Questions for agent design
000-IAM	Identity & Access Management	What identity, recovery, and authentication facts may the agent rely on?
001-M5BOM	Bank of Me	What may a personal agent do for one human, and what always requires fresh approval?
002-M5BOU	Bank of Us	How are shared consent, quorum, dissent, exit, and collective authority represented?
003-M5BOB	Bank of Business	Which officer, employee, contractor, or service-provider roles may delegate which business capabilities?
004-M5BOI	Bank of Institutions	How do institutional policy, regulated functions, segregation of duties, and supervision constrain agents?
005-M5BOG	Bank of Government / Governance	How are public authority, due process, records, accessibility, appeal, and official-source verification preserved?

These are not the M1–M5 asset/economic states. An account context does not grant an agent legal authority or make an action valid.

Help us review

• Which capabilities belong in each account context?
• What must never flow from one context into another?
• How should shared accounts represent quorum, conflict, and revocation?
• Which actions need fresh human, officer, board, institutional, or governmental approval?
• What receipts should prove who authorized an action and in which context?
• How should a person safely move from a personal context to an organization role without leaking private data?

Start with the M5-agent hub · Read the M5 Economic Architecture

Do not post real account, credential, wallet, member, employee, constituent, or institutional data. This is architecture review, not account activation or an offer of regulated services.