Ontology / M5Brain / Sovereign AI Wiring
Wires the member-controlled context layer underneath the personal, business, cooperative and startup agents.
- M5-CV proof ID
- FC-0004
- 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
- •Ontology basics
- •Personal vs business graph
- •Authority / permissions
- •Local runtime architecture
- •M5Brain reference environment
- •Ontology templates
- •Graph relationships
- •Deployment adapters
- •M5Brain activation lab
- •Ontology workshop
- •Sovereign AI technical clinic
- •Builder track
- •Ontology architect
- •Knowledge graph specialist
- •AI systems architect
- •Sovereign AI implementation lead
Evidence already available
Defined first-100 activation role
Reference implementation evidence
Accepted deployment procedures become proof
Foundation contribution
Activate and harden the M5Brain/M5POD/local AI layer, define portable ontology patterns and contribute OS/runtime/graph reference implementations to the Foundation repository.
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.