Business Operations / Community / Digital Assets
Leads the human adoption layer: community, business operations, wallet-aware workflows, digital-asset operations and the trainer network.
- M5-CV proof ID
- FC-0002
- Default disclosure
- Capability only
- Human root
- IAM proof required
- M5✦AI status
- Founding cohort · demonstrate
- GitHub binding
- To be completed
- Identity
- Member-controlled
Core M5 AI Agent Operations
Freedom Office, M5Brain, agent, approved model/runtime and member-controlled context.
Permissions, memory, READ / DRAFT / ACT authority, human approvals and revocation.
Use agent workflows inside a real specialty without silently surrendering responsibility.
Capture evidence, provenance, approved contributions and capability results into the Passport.
M5✦AI means the human can operate, supervise and govern an AI agent — not that the AI replaces the human. Domain credentials sit on top of this common AI Agent Operations capability.
Domain capability intake
Imported capabilities remain declared or source-verified until an M5 demonstration, accepted contribution or other evidence raises their proof state.
M5Agent specialty stack
What this human + M5Agent can unlock
- •Freedom Office train-the-trainer
- •Connect business to Bank of Me
- •GL + invoicing activation
- •Digital-asset operations
- •Trainer network
- •Member onboarding system
- •Operations SOP library
- •Business-wallet migration playbook
- •M5 trainer cohorts
- •Business wallet activation cohorts
- •Community operations program
- •Digital-asset classes
- •Operations leader
- •Community / CX leader
- •Wallet operations lead
- •Training & enablement leader
Evidence already available
Public professional profile
ZenLedger / professional evidence
Trainer rubric and demonstrations still required
Foundation contribution
Own the trainer quality system: turn technical/business workflows into teachable SOPs, trainer rubrics, cohort operating standards and feedback loops; certify trainers only after demonstrated evidence.
IAM ↔ GitHub proof chain
The static demo does not perform GitHub OAuth, issue credentials or enforce identity access. In production, the identity layer and GitHub binding are verified server-side and the credential can be active, suspended, revoked or renewed.
Identity is withheld by default. The capability view is the default; identity is disclosed only when the member chooses — for an interview, contract, partnership, background check or other defined purpose.