AIMOS / Mphoka Coworker System

One front door.
Many governed capabilities.

A personal AI operating layer for Mphoka's brands, business, family and career. Telegram is the interface. Notion is the business ledger. The coordinator routes work without replacing the legacy agents that already do useful jobs.

DEPLOYED FOUNDATIONHetzner VPS · governed Telegram coordinator · shared memory · approval gates

How a request moves

01 · AskNatural English or Dutch through Telegram, text or voice note.
02 · ResolveDetect intent, brand, department, task and required sources.
03 · RouteChoose the smallest specialist role or approved legacy capability.
04 · DeliverReturn the answer, draft, plan, metric readout or proposed action.
05 · ApproveRequire confirmation before external mutations or publishing.

The coordinator and its teams

Personal Assistant · the front door

Maintains continuity, protects sleep/family boundaries, understands the active brand, and coordinates the right coworker. Business Mentor, Business Coach, Career Coach and Life Coach are governed workflows behind this one conversational entry point, not four competing bots.

Marketing & content

Marketing Lead, Social Strategist, Social Copywriter, Email Copywriter and Content Producer.

Commerce & products

Ecommerce research, Product Strategist, Product Builder, Offer/Funnel, Conversion Copy, QA and Launch.

Research & performance

Niche, product and affiliate research plus Performance Analyst. Metrics requests return metrics unless analysis is requested.

Brand lanes

M2R, PHP, DD, DTH, ED, IS, HD and POP use separate brand context and account mappings.

Where truth lives

LayerWhat it ownsWhat it must not do
NotionLive business context, Brand DNA, Content Factory, Publishing Queue, social logs and approved feedback.It is not silently overwritten by guesses or duplicate databases.
GitHubRuntime code, role registry, brand Markdown, curated agent knowledge and durable operating rules.It never stores credentials or the raw private brain file.
SQLite + stateExact conversation turns, outputs, checkpoints, Telegram ownership and proposal hashes.It is not a second business source of truth.
Legacy Empire OSExisting scripts, workers and Mandalorian-named agents used through allowlisted capability wrappers.It is not rewritten, duplicated or granted unrestricted execution.

Execution paths

Read / advise

Coordinator reads scoped memory and sources, then returns a plan, decision, draft or raw metrics.

No external mutation

Legacy capability

Capability Broker calls existing IG-11/Meta pullers, Shopify tools and other registered wrappers.

Allowlisted

POP publishing

07:00 proposal → Telegram approval → Notion queue → Claude in Chrome checks 08:00, 13:00 and 18:00.

Approval + browser evidence

Outlook

Personal and 9-to-5 email/calendar integration remains a separate next phase.

Not wired yet

Safety by design

One approval chain

Proposed copy is previewed, approved, hash-bound and written idempotently.

Fail closed

Missing brand mapping, visual asset, login, CAPTCHA or publication evidence becomes Blocked.

Coexistence

Legacy workers remain available without becoming a second conversational front door.

Human authority

Mphoka remains the final authority for external actions, publishing and irreversible changes.