Reality-audited V3 · corrected against live GitHub/VPS/OpenClaw/Odoo/Slack state · no fake autonomy claims

Viewport CompanyOS Master Operating Plan for MLG + MLH.

This page is now corrected against current integration reality. It is a living operating plan, not a done claim: Cloudflare serves the pages, Odoo/Slack has a safe foundation, old OpenClaw roles/crons were read, but GitHub source-of-truth, VPS RuntimeContracts, CompanyOS enforcement, watcher execution, and tenant isolation are still unfinished work.

Cloudflare live pages verified Odoo/Slack validation 15/15 Old OpenClaw read: 24 seats / 25 role folders / 50 crons CompanyOS planned, not enforced GitHub source sync blocked VPS runtime unreconciled: 72 containers / 3 unhealthy

Main Deep Rebuild Plan Slack export Odoo export status.json

Live status

Hermesv0.15.2

VPSvmi3130827

Containers72 (3 unhealthy)

Last audit2026-06-05 · PASS:2 FAIL:10 UNKNOWN:1

Tasks139 total

NOW / NEXT58 / 73

BLOCKED / DONE4 / 1

Datastatus.json

Updated2026-06-09

Live data: Task counts from status.json · NOW:58 NEXT:73 BLOCKED:4 DONE:1 (total 139) · VPS: 72 containers, 3 unhealthy · Cross-link: Deep rebuild plan → · Fetched: 2026-06-09

Content preservation guarantee: this page keeps the full researched source content. UI, navigation, spacing, and mobile behavior are upgraded without shortening sections.

MLG / MLH operating rails — visible reference

Slack + Odoo approval flows

This section is intentionally pinned near the top so humans and agents can immediately see where documents, support, and finance work should go.

Documents

Odoo: Documents / project document folder

Flow: Document needed → Odoo document folder → Slack approval if legal/signature → sign only after approval.

Helpdesk / warranty / legacy issues

Slack: #mlh-warranty-support, #mlh-legacy-issues

Odoo: Helpdesk

Flow: MLH issue → Slack issue thread → Odoo helpdesk ticket → evidence attached → agent suggests next action → approval if legal/financial/customer-facing.

Finance review

Slack: #mlg-finance-review

Odoo: Accounting / Invoicing / Expenses

Flow: Draft invoice/payment/expense → Slack finance review → Odoo record → approval before sending/payment/customer-facing action.

Active execution loop — GitHubOps truth

GSD + RalphLoop is active for GitHub Ops and VPS Runtime

Mode: GitHub issue → branch → artifact → validator → evidence → live status. VPS runtime remains read-only/reconciliation until RuntimeContracts, backups, rollback, and approval gates exist.

Goal

Move real business/runtime work through visible GitHub issues and acceptance criteria.

Setup

Create branch, artifacts, validator, evidence path, and rollback boundary before touching runtime.

Do / Verify / Fix

Run the smallest safe action, verify with tests or live proof, diagnose failures, then repeat.

Evidence

Issue #196 · status JSON · viewport-company-os/workflows/gsd-ralphloop-operating-contract.yaml

Section 0 · Integration reality

0. Current integration reality audit — what is actually integrated

Verdict: We are not yet an AI-operated company. We have working display pages, partial Odoo/Slack foundations, recovered OpenClaw role/cron knowledge, and a live mixed VPS runtime. The missing layer is enforcement: GitHub source-of-truth, RuntimeContracts, CompanyOS registry, tenant isolation, and watcher execution.

GitHub Ops / source of truthPARTIAL / BLOCKED
Local branch ops/openclaw-github-flow-44 is ahead 6 commits; gh CLI missing; GitHub MCP get_file_contents for branch/path returned Not Found; previous push/write blocked. Live worker deploy is Cloudflare-side, not GitHub-synced source of truth.

Cloudflare / migration pagesWORKING FOR LIVE PAGES
Cloudflare API auth with contactviewport@gmail.com succeeds; account Workers scripts listed; viewport.llc zone found; /migration, /migration/plan, /migration/task are live HTTP 200 after deploy.

VPS / Docker runtimeLIVE BUT UNRECONCILED
Read-only Docker check: 72 total containers, 65 running, 3 unhealthy: saathi-app-1, origin-backend, platformx-nextcloud. Dokploy, Coolify, NPM/nginx, Traefik coexist.

OpenClaw agentsLEGACY KNOWLEDGE READ; NOT CENTRALIZED COMPANYOS
Old backup verified 24 configured seats, 25 workspace docs, 50 legacy crons; fresh OpenClaw has 1 cron. Roles exist as source material, not operating agents under current GitHub/Odoo/Slack loop.

CompanyOS / GSD/Ralph loopDESIGN + TEST FILES EXIST; NOT ENFORCED END-TO-END
viewport-company-os/tests/gsd-ralph-loop.yaml exists; task board has agent/role/watchers tasks; no CI/issue/PR/runtime enforcement proven.

Odoo + Slack MLG/MLHPARTIAL OPERATIONAL FOUNDATION
validate_odoo_slack_integration.py passes 15/15; Odoo safe draft/control records and Slack bot/channel checks exist. Still not a full production app/control room with all commands, workflows, approvals, and tenant operations automated.

MLG/MLH tenant/associate operating modelTEMPLATE PLANNED, PARTIAL FOUNDATION ONLY
Odoo/Slack matrices, task board, and plan include tenant template; repo/runtime isolation and per-tenant GitHub/Odoo/Slack/agent registry not proven complete.

Postiz/social automationIDENTIFIED / NOT INTEGRATED
Task board now includes Postiz/social automation tasks; no verified Postiz repo-to-runtime/control-flow integration completed.

OpenRouter/councilAPI PRESENT NOW; PLAN CLAIMS NEED TIMESTAMPED STATUS
Current OpenRouter key present and /models returned HTTP 200. Prior model council runs were partial/unstable; not enough to claim all council review done.

Section 1 · Honesty gate

1. Honest self-audit of the prior plan

Verdict: the first page was directionally right but not enough. It was 5/10 as an orientation page and 2/10 as an executable CompanyOS spec. This V2 must be judged against execution artifacts, not words.

What was wrong

Phases were slogans, not work packets.
Departments and agent seats were shallow.
GitHub Ops was philosophy, not issue/PR/workflow rules.
Odoo app mapping lacked models, write policies, and approval classes.
Slack was channels/commands only, not a production app spec.
VPS was not tied to concrete RuntimeContracts.
Evidence claims lacked source → finding → implication traceability.

What V2 adds

Concrete research artifacts.
Department-by-department roles and KPIs.
Agent role/seat/readiness/lease model.
Executable GitHub task packet and runtime contract direction.
Odoo/Slack approval and write-policy mapping.
Evidence vault ingestion and privacy gates.
Anti-patterns to ban.

What is still unproven

Live VPS container classification rows need a separate snapshot.
Odoo model field inventory must be exported directly from Odoo.
Slack app production endpoints need build/verification.
Raw Mac secret-like files must remain excluded unless Sam explicitly approves a secure private handling process.

Section 2 · Sources

2. Research evidence ledger

95,420files inventoried · 9.39GB observed

17,342safe text files extracted/indexed

17,188binary/large hashed/cataloged

60,727vendor/generated hashed/cataloged

163secret-like hashed/cataloged only

0read errors

Deep-read bundleevidence/modern-lao-deep-read-20260602/manifest.jsonl, text-index.jsonl, summary.json, skipped-sensitive-or-generated.jsonl.

Scale read95,420 files inventoried; 9.39GB observed; 17,342 safe text files extracted/indexed; 17,188 binary/large hashed/cataloged; 60,727 vendor/generated hashed/cataloged; 163 secret-like hashed/cataloged only; 0 read errors.

New specialist artifactsevidence/migration-plan-self-audit-20260603.md; evidence/odoo/mlg-mlh-odoo-slack-operating-model-20260603.md; evidence/modern-lao-deep-read-20260602/evidence-ingestion-website-client-investor-plan.md; evidence/github-vps-companyos-control-plane-executable-plan-20260603.md; evidence/department-segment-agent-operating-template-20260603.md; evidence/global-research-synthesis-migration-plan-20260603.md.

High-signal rootsMLH-COMMS-VAULT, MLH-FB-extracted, MLH-Research, MLH - Clients Chats, mlh-clients-portal, mlh-clients-portal-clean, modernlaohomes-site, MLG Website, _repo-staging/modern-lao-investor-site, docs/contracts, handoffs, plans.

Global referencesOdoo implementation/app docs; Slack signing/events/interactivity/workflows docs; OWASP agent/LLM risk guidance; NIST AI RMF/Privacy Framework; AWS/Azure tenant-isolation guidance.

Target architecture

Trillion-scale company architecture — target structure, not a done claim

Ambition: Viewport is being designed as an AI-operated global company that can serve every country and every industry — an all-country/all-industry operating architecture — through reusable tenant/company operating systems. This is not yet fully built. The live reality audit above shows the missing rails: GitHub source-of-truth, RuntimeContracts, CompanyOS enforcement, tenant isolation, and watcher execution.

Core company stack

Viewport LLC / parent governancePlatformX / multi-tenant AI business OSCompanyOS / rules + roles + workflowsHermes operator shellOpenClaw legacy role libraryGitHub source-of-truthVPS/cloud runtimeOdoo business recordSlack command room

Global replication model

Each company, tenant, client, associate, or partner gets an isolated package: GitHub repo/labels/issues, Slack channels, Odoo company/context/apps, runtime namespace, domain map, knowledgebase, approval matrix, agent roster, watchers, reports, onboarding, rollback, and offboarding.

Industries to support

Real estate & constructionFinance & accountingLegal & complianceHealthcare & wellnessEducation & trainingRetail & commerceManufacturing & supply chainHospitality & tourismMedia & entertainmentAgriculture & foodEnergy & utilitiesTransport & logisticsGovernment/civic servicesNonprofits & communityTechnology/SaaSAI/model/tool R&D

Departments every serious tenant can receive

Executive commandGitHub PMO / source-of-truthTenant operationsEngineering / productRuntime / SRE / DNSAI automation / agent factorySecurity / privacy / complianceResearch / intelligenceEvidence / data / knowledgeSales / CRMMarketing / content / Postiz/socialCustomer success / helpdeskProject delivery / operationsDocuments / contracts / legal/signFinance / accounting / procurementHR / training / agent readinessQuality / verification / auditR&D for cheaper AI compute/energy/hardware

Reusable service catalog

Tenant/company setupWebsite/client portal/investor portalOdoo ERP/CRM/helpdesk/documents/accounting workflowsSlack/WhatsApp/Telegram command roomsGitHub task/PR/evidence operating systemRuntime/DNS/SSL/container operationsPostiz/social/content workflowEvidence vault/knowledgebaseAgent/watcher operationsApprovals/legal/finance gatesReporting/analytics/KPIsSecurity/privacy/complianceTraining/role onboardingAutomation connectors/MCP/toolsModel/provider/cost optimization

MLG / MLH as first proof tenant

Modern Lao Group / Modern Lao Homes is the first full reference implementation: GitHub ops, Slack approvals/audit/support channels, Odoo CRM/project/helpdesk/documents/finance foundations, public/private portal separation, Postiz/social workflow, and Modern Manager-style agent coordination.

AI R&D mandate

Viewport must research cheaper, lower-energy, lower-hardware AI operation: model routing, open/free models, local inference, workflow caching, agent specialization, evaluation, and provider fallback so high-class AI operations can become globally accessible rather than expensive enterprise-only tooling.

Reality boundary

Already in place: live migration pages, Cloudflare deploy path, partial Odoo/Slack foundation, old OpenClaw agent/cron readout, VPS Docker visibility, task board. Not yet complete: remote GitHub source sync, RuntimeContracts for every service, enforced CompanyOS registry, production watcher system, full tenant isolation proof, full Odoo/Slack command-room automation, and global replication playbooks.

Section 3 · Operating doctrine

3. Operating doctrine

Control plane

GitHub = control plane

Issues, task packets, branches, PRs, checks, evidence paths, runtime contracts, skills, approval records, rollback plans.

Command room

Slack = command room

Slash commands, buttons, modals, approvals, threads, audit posts, escalation, agent status, operating rhythm.

Business record

Odoo = business record

Contacts, CRM, projects, helpdesk, documents, knowledge, invoices, expenses, purchases, inventory, sign, activities, reporting.

Runtime

VPS = runtime

Runtime is replaceable. Nothing on VPS is trusted as source of truth unless mapped to GitHub and backed by RuntimeContract.

Seats

Agents = seats, not magic

Every role has a seat, lease, readiness level, tools, approval class, verifier, evidence output, and handoff rules.

Guardrail

Sam = approval guardrail

Finance, legal, customer-facing, DNS, destructive runtime, billing, payroll, and security-sensitive work require explicit gates.

Section 4 · 37 phases · uniform close gate

4. Phase plan with execution gates

All 37 phases (00–36) below, grouped into seven stages for readability — numbering and full text preserved. Every phase carries the same close gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close. The source plan defines gates, not per-phase completion status — live state comes from the reality audit above and status.json; the only phase explicitly promoted to immediate blocker is the Runtime Source-of-Truth phase (04A).

00–03Foundation & control 04–08Runtime truth & evidence 09–11Tenant, departments & agents 12–16Odoo & Slack rails 17–26Business workflows 27–30Enforcement & visibility 31–36Pilot, writes & replication

PHASES 00–03

Foundation & control plane

GitHub source sync blocked

Command reset, research ledger, GitHub Ops rules, agent leases.

00Command reset

Command reset: freeze random fixes, use this page as living master draft, create master GitHub issue and evidence index links.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

01Research ledger lock

Research ledger lock: commit the deep-read manifest, text index, self-audit, specialist artifacts, and source-to-finding matrix.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

02GitHub Ops foundation

GitHub Ops foundation: expand issue templates, PR template, labels, task-packet schema, branch rules, no-secret checks, evidence checks.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

03Agent lease system

Agent lease system: one active executor per task, heartbeat, expiry, backup takeover, reviewer/verifier separation, handoff format.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 04–08

Runtime truth & evidence

Immediate blocker — see Phase 04A

Runtime inventory, RuntimeContracts, domain/auth map, evidence vault.

04Runtime inventory snapshot

Runtime inventory snapshot: collect read-only Docker/Dokploy/Coolify/Traefik/ports/domains/volumes/secrets-names/backups/healthchecks.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

05RuntimeContract queue

RuntimeContract queue: create contracts for migration worker, Slack/Odoo bot, Modern Lao sites, client portals, investor vault, auth gates, proxies.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

06Domain and auth map

Domain and auth map: classify public, client, investor, admin, API, Odoo, Slack connector, and tenant domains; define Cloudflare/DNS approval gates.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

07Evidence vault schema

Evidence vault schema: canonical evidence IDs, source path/hash, owner, client/case/project link, privacy class, publication class, Odoo target.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

08Evidence ingestion MVP

Evidence ingestion MVP: ingest manifests/CSV ledgers first; no raw secrets; no public publishing; create client/case/document candidates.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 09–11

Tenant, departments & agents

Planned

MLG/MLH tenant model, 17-department factory, agent role library.

09MLG/MLH tenant model

MLG/MLH tenant model: define tenant metadata, channels, Odoo company/context, GitHub labels, runtime namespace, evidence vault rules.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

10Department factory implementation

Department factory implementation: instantiate 17 departments with charters, roles, tools, KPIs, Slack/Odoo/GitHub inputs and outputs.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

11Agent role library

Agent role library: define lead/worker/reviewer/verifier/router/operator/watcher/evidence-auditor skills and readiness levels.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 12–16

Odoo & Slack rails

Foundation partial — validation 15/15 passed

Odoo export + write policy, Slack production app, channels, approval packets.

12Odoo live model export

Odoo live model export: export installed modules, models, fields, stages, permissions, record counts, current safe records, and risky-zero records.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

13Odoo write policy matrix

Odoo write policy matrix: every app/model/action gets L0 read, L1 draft, L2 approval packet, L3 execute-after-approval, or HOLD.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

14Slack production app spec

Slack production app spec: slash commands, interactivity, events, modals, signature verification, idempotency, retries, rate limits, audit logs.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

15Slack channel architecture

Slack channel architecture: create or verify command, approvals, audit, sales, project, docs/sign, finance, procurement, support, marketing, incident channels.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

16Approval packet standard

Approval packet standard: Odoo record, Slack thread, GitHub issue, evidence IDs, risk class, decision buttons, expiry, reviewer, final action.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 17–26

Business workflows

Planned

Lead intake through comms-vault publication — the MLG/MLH business loops.

17Lead intake workflow

Lead intake workflow: website/client/WhatsApp/Facebook/manual lead → CRM draft → Slack thread → agent recommendation → approved next activity.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

18MLH warranty/legacy workflow

MLH warranty/legacy workflow: evidence → helpdesk ticket draft → missing-evidence check → legal/customer/finance gate → approved response.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

19Project delivery workflow

Project delivery workflow: approved CRM/quote → project template → tasks/stages/site visits/material requests/QA/punch list/handover.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

20Documents/sign workflow

Documents/sign workflow: folder/tag/access model, contract template registry, draft signature packet, legal/Sam approval before Sign request.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

21Finance/accounting workflow

Finance/accounting workflow: chart/taxes/bank/payment terms review; draft invoices/expenses/vendor bills; posting/payment/refund held.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

22Procurement/inventory workflow

Procurement/inventory workflow: vendor registry, material request, RFQ/PO draft, receipt evidence; PO/vendor bill approval gates.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

23HR/planning/timesheets workflow

HR/planning/timesheets workflow: roster, crew planning, skills, timesheets, capacity; payroll/paid users held behind approval.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

24Marketing/public content workflow

Marketing/public content workflow: claims evidence, website copy, social/email/WhatsApp drafts; customer/investor-facing publication gate.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

25Website/portal QA

Website/portal QA: public MLH, client portals, investor vault, auth gates, mobile/tablet/desktop, no public/private leakage.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

26Comms vault publication

Comms vault publication: investor/auth-gated summaries only; raw evidence privacy classification; missing media and dispute indexes.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 27–30

Enforcement, watchers & visibility

Planned

GSD/Ralph CI, watcher MVP, Dashboard V2, skills/training.

27GSD/Ralph loop CI

GSD/Ralph loop CI: Goal→Setup→Do→Verify→Diagnose→Fix→Repeat→Evidence encoded into GitHub checks and Slack status.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

28Watcher/reporting MVP

Watcher/reporting MVP: GitHub stale work, runtime health, DNS/SSL, Odoo/Slack health, evidence drift, agent silence, backup status.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

29Dashboard V2

Dashboard V2: show phases, issues, PRs, runtime contracts, Odoo/Slack health, evidence coverage, approvals, blockers, next decisions.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

30Skills/training creation

Skills/training creation: Odoo app map, Slack control flows, Mac evidence ingestion, client portal QA, comms vault, runtime contracts, tenant template.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

PHASES 31–36

Pilot, approved writes & replication

Planned / gated

Low-risk pilot, L3 writes after proof, tenant template, replication, rhythm, continuous improvement.

31MLG/MLH pilot execution

MLG/MLH pilot execution: run low-risk read/draft workflows end-to-end with no customer-facing or finance/legal execution.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

32Approval-controlled writes

Approval-controlled writes: enable specific L3 writes only after phase proof, rollback, verifier, and Sam approval.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

33Tenant template extraction

Tenant template extraction: repo layout, Slack channel map, Odoo app matrix, runtime contracts, agent roster, approval policy, onboarding checklist.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

34Replication pilot

Replication pilot: onboard one safe associate/client using minimal template, prove isolation, reporting, rollback, and handoff.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

35Operating rhythm

Operating rhythm: daily Slack digest, weekly GitHub/Odoo report, monthly tenant audit, quarterly skills/agent readiness review.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

36Continuous improvement

Continuous improvement: plan can change 10–20 times; every change must cite evidence, impact, phase/gate deltas, and reviewer verdict.

Gate: GitHub issue/task packet, evidence path, verifier, Slack summary, approval class, and rollback/abort rule must be present before close.

Section 5 · 17 departments

5. Department and segment design

Every tenant starts with a department package. Each department gets Slack channels, Odoo apps/models, GitHub queues, agent roles, approval gates, KPIs, and evidence outputs.

Executive Control Office

Sam/owner decisions, approvals, priorities, escalation, audit.

GitHub Control Plane / PMO

task packets, PRs, workflows, evidence, issue hygiene.

Tenant Operations

tenant onboarding, templates, channel/app/runtime namespace.

Research / Market / Regulatory

global/local research, legal/regulatory scan, citations.

Product / Website / Portal

public sites, client portals, investor surfaces, forms, QA.

Engineering / AI Automation

connectors, APIs, bot backends, agent tools, tests.

Runtime / DevOps / SRE / DNS

VPS, containers, deploys, health, SSL, backups.

Security / Compliance / Privacy

secrets, auth, privacy classes, agent permissions, reviews.

Evidence / Data / Knowledge / Analytics

vaults, indexes, dashboards, SOPs, KPIs.

Sales / CRM / Proposal Desk

leads, qualification, quotes, proposals, follow-up.

Construction / Design / Project Delivery

site visits, design, tasks, materials, QA.

Customer Success / Helpdesk / Warranty

support tickets, legacy issues, customer updates.

Documents / Contracts / Legal / Sign

folders, contracts, legal review, signing gates.

Finance / Accounting / Cost Control / Procurement

invoices, expenses, POs, vendors, cost reports.

Marketing / Brand / Content / Investor Relations

claims, content, campaigns, investor updates.

HR / Training / Agent Readiness

roles, skill training, readiness, performance audit.

Open Source / Model / Tool Lab

models, MCP tools, cost/compute R&D, tool acquisition.

Section 6 · Seats, leases, readiness

6. Agent operating model

Standard role pattern

Department LeadWorkerReviewerVerifierApproval RouterApproved OperatorWatcherEvidence Auditor

Readiness levels

R0 proposedR1 read-onlyR2 draft-onlyR3 approved writeR4 deploy operatorR5 privileged emergency only

Rule

No agent gets broad power because it sounds smart. Every agent must have scope, tools, skills, task packet, lease, reviewer, verifier, evidence output, and approval policy.

Section 7 · Business record

7. Odoo operating model

Read/draft now

Contacts, CRM drafts, Helpdesk drafts, Project notes, Documents placeholders, Knowledge SOPs, Activities.

Approval before execution

Quotes, invoice posting, payment/refund, vendor PO, expense approval, contract signature, customer-facing messages.

HOLD until designed

Tax/bank finalization, payroll, production accounting, automated WhatsApp/social/email sends, Studio structural changes.

App families to map

ContactsCRMSalesProjectHelpdeskDocumentsKnowledgeSignAccountingInvoicingExpensesPurchaseInventoryPlanningTimesheetsEmployeesCalendarAppointmentsWebsiteMarketingSocialWhatsAppDashboardsStudio

Section 8 · Command room

8. Slack control room model

Slack must be the operating cockpit, not a notification dump.

Surfaces

Slash commands
Interactive buttons
Modals/forms
Events API
App Home
Workflow steps
Audit posts

Channels

#mlg-command-center#mlg-odoo-approvals#mlg-odoo-audit#mlg-agent-control#mlg-sales-crm#mlg-projects-delivery#mlg-documents-sign#mlg-finance-review#mlh-warranty-support#mlh-legacy-issues

Production requirements

Request signing verification
Idempotency keys
Retry handling
Rate limits
Fail-closed policy
Odoo/GitHub audit link

Section 9 · Executable model

9. GitHub + VPS executable model

Task packettenant, department, goal, source evidence, owner role, executor lease, risk, approvals, files/routes, tests, evidence path, rollback, verifier.

PR gatelinked issue, task packet, validation output, no-secret scan, runtime contract if runtime touched, approval class, dashboard update.

RuntimeContractservice, domain/path, container, deploy method, source repo, healthcheck, ports, volumes, secrets names only, backup, rollback, owner, status.

Service statusesKEEP MIGRATE ARCHIVE DELETE-LATER UNKNOWN DO-NOT-TOUCH

WatchersGitHub stale tasks, CI, runtime health, DNS/SSL, Odoo/Slack health, backup, cost/security, evidence drift, agent silence.

Section 10 · Replication

10. Multi-tenant replication template

MLG + MLH is the first complete tenant. Future clients/associates/partners receive the same package:

Tenant metadata and isolation class.
GitHub repo/folder, labels, issue templates, task packet queue.
Slack channel map, commands, approval policy.
Odoo app/model matrix, write policy, record taxonomy.
Runtime namespace/contracts and healthchecks.
Evidence vault schema and privacy classes.
Agent roster, skills, readiness levels, leases.
Dashboards, reports, operating rhythm, KPIs.
Finance/legal/customer-facing/destructive approval gates.
Onboarding, rollback, offboarding, archive procedures.

Section 11 · Dedicated manager agent

11. Modern Manager — dedicated Modern Lao manager bot/agent

Correction: Modern Manager is not optional. Modern Lao work needs one dedicated manager bot/agent identity across Hermes, OpenClaw, Slack, WhatsApp, Telegram, Odoo, GitHub, and VPS/runtime — with strict Modern-only scope and Sam escalation.

Mission

Own Modern Lao daily execution: receive work, classify tenant/client/risk, open GitHub task packets, coordinate agents, draft Odoo/Slack actions, request approvals, verify completion, and report blockers.

Where it lives

HermesOpenClawSlackWhatsAppTelegramOdooGitHubVPS

Hard boundary

Modern Manager handles Modern Lao work only. Other tenants get their own manager agent from the tenant template.

Daily loop

Read Slack/Odoo/GitHub queuesCheck WhatsApp/Telegram intakeClassify riskOpen/update task packetsAssign agentsCreate approval packetsVerify evidencePost daily digest

Blocked without approval

Customer-facing sendInvoice posting/payment/refundContract/sign requestPO/vendor billDNS/runtime destructiveSecrets/user permissionsPublic investor/legal claims

Implementation artifact: evidence/agents/modern-manager-agent-design-20260603.md.

Section 12 · 616-line matrix

12. Odoo full feature automation matrix

Every Odoo function must be mapped to Modern Lao business use, agent skills, allowed functions, blocked functions, Slack approval path, GitHub evidence path, and training. Agents must become Odoo experts before write permissions.

Automation levelsL0 read observe/export/summarize; L1 draft create drafts/placeholders; L2 approval packet prepare decision with evidence; L3 approved execute execute after explicit approval; HOLD blocked until design/legal/finance approval.

Core app coverageFinance, Accounting, Invoicing, Expenses, Sales, CRM, Website, Inventory, Purchase, Project, Helpdesk, Documents, Sign, Knowledge, HR, Marketing, Social, WhatsApp, Discuss, Calendar, Appointments, Dashboards, Studio, AI, Field Service, Planning, Timesheets.

Required agent skillsOdoo functional navigation, model/record lifecycle, permissions, audit trail, accounting safety, project/helpdesk stages, document tags, contract/sign rules, CRM pipeline, inventory/purchase process, website publishing gates, import/dedupe, rollback/export.

Global guardsNo posted invoice/payment/refund/bank/tax/payroll/signature/customer send/public claim without approval. No model/schema/Studio changes without GitHub issue, backup/export, reviewer, and rollback.

Evidence artifactevidence/odoo/mlg-mlh-odoo-feature-automation-agent-skill-matrix-20260603.md — 616-line app/function matrix.

Section 13 · 760-line matrix

13. Slack full automation/control-room matrix

Slack must use every relevant automation surface as the Modern Lao control room, but never as the system of record. Slack commands trigger workflows; Odoo/GitHub hold truth; approvals are logged.

Automation surfaces

Slash commands
Global shortcuts
Message actions
Modals
Interactive buttons
Events API
Workflow Builder/custom steps
App Home
Canvases/lists where useful
Audit logs and digests

Technical guards

Signing-secret verification
Raw-body HMAC
Timestamp replay protection
3-second ack
Retry/idempotency keys
Rate limits
Fail closed
Scope minimization

Controls

Odoo draft/approval/execute
GitHub issue/PR/task packet
VPS read-only health/runtime gates
Hermes/OpenClaw agent dispatch
WhatsApp/Telegram intake routing
Sam escalation

Implementation artifact: evidence/slack/mlg-mlh-slack-control-room-automation-matrix-20260603.md — 760-line control-room matrix.

Section 14 · External review

14. LLM Council Review — OpenRouter/free models

Status: Current OpenRouter API access is verified, but previous council review was partial and unstable. Do not treat council feedback as complete until each provider/model run has a timestamped status, raw output, failure mode, and task mapping.

Completed reviewers

openrouter/free — audit completed, verdict medium.
z-ai/glm-4.5-air:free — audit completed, verdict weak/executable detail missing.

Attempted / unstable / blocked

nvidia/nemotron-3-super-120b-a12b:free — smoke passed, audit run unstable.
openai/gpt-oss-20b:free — smoke passed, audit had invalid tool-call output.
qwen/qwen3-coder:free, meta-llama/llama-3.3-70b-instruct:free, google/gemma-4-31b-it:free — upstream rate-limited/blocked.

Council verdict: The reviewers agreed this plan has the right ambition and structure, but is still not final-executable enough. It needs harder timelines, owners, dependencies, risk register, rollback playbooks, tests, compliance mapping, monitoring, and tenant isolation controls before it becomes the locked operating contract.

12Repeated gaps

No formal timeline, milestone duration, capacity model, or critical path.
No full resource allocation per department, agent seat, and human approval owner.
No budget/cost model for Odoo, Slack, VPS, AI usage, observability, and tenant support.
No formal risk register with likelihood, impact, owner, mitigation, and rollback trigger.
No dependency graph between phases and systems.
Rollback/abort procedures are named but not operationally specified.
No detailed integration test matrix across Hermes, OpenClaw, Slack, WhatsApp, Telegram, Odoo, GitHub, and VPS.
No concrete GDPR/privacy/security/compliance mapping for evidence vault and customer records.
No SLA/SLO/RTO/RPO definitions for tenants and internal ops.
GitHub control-plane branch protections, required checks, issue schemas, and reviewer rules need exact implementation.
Monitoring/observability needs exact metrics, dashboards, alert routing, and incident process.
Tenant isolation needs enforceable repo/runtime/network/secrets/IAM controls.

8Immediate GitHub issues recommended by council

Create master phase dependency graph with critical path and owner map.
Create Odoo/Slack/GitHub/VPS integration test matrix and acceptance suite.
Create runtime rollback playbooks for each deployable service.
Create tenant isolation contract covering repositories, containers, secrets, knowledge, and channels.
Create risk register and compliance matrix for client evidence and financial/legal records.
Create budget/capacity model for MLG/MLH first tenant and replicated client tenants.
Create Modern Manager skill curriculum and certification gates for Odoo + Slack functions.
Create observability dashboard spec with metrics, alerts, and escalation routes.

Artifacts: evidence/llm-council/openrouter_free-migration-plan-audit-20260603.md, evidence/llm-council/z-ai_glm-4.5-air_free-migration-plan-audit-20260603.md, evidence/llm-council/free-model-council-attempts-20260603.md.

Section 15 · Immediate blocker · Phase 04A

15. Runtime Source-of-Truth Phase — make agents stop touching old settings

Status: promoted to immediate blocker after the legal.modernlaohomes.com routing incident. The plan is no longer just a migration narrative; it is the operating checklist that must turn every live domain into a verifiable contract before Codex/Hermes/other agents are allowed to mutate production.

Why this phase exists

Agents are currently blocked because live truth is split across Cloudflare DNS, Dokploy Traefik dynamic files, old Docker containers, nginx configs inside containers, local Mac staging repos, and GitHub. The legal portal proved the risk: the domain was live only after mapping Cloudflare plus Dokploy Traefik to modernlao-site, while Dokploy DB did not show a clean application row for that exact portal.

Required contract row for every service

Domain / route
Cloudflare zone + DNS record ID
Dokploy app/compose/service name
Actual Docker container name
Repo + branch + build path
Runtime path / mounted volume
Traefik/nginx source file
Owner + approval class
Rollback file/snapshot
Verification command + expected result

Immediate MLH rows to inventory

modernlaohomes.com / www.modernlaohomes.com → public site
clients.modernlaohomes.com → private client portal
legal.modernlaohomes.com → legal consultation portal, currently routed to modernlao-site
sign.modernlaohomes.com → signing/docuseal route
investor.modernlao.com → investor/vault surface
modernlao.odoo.com → Odoo SaaS source

Execution rule

No agent gets to say “done” on a domain/app until the contract row exists, the live route is verified from public DNS, and the rollback file is named. If the row says Dokploy but the serving path is old Docker/nginx, the row must say that honestly and mark the cleanup target.

Next concrete artifact

Create evidence/runtime/domain-service-map-20260603.md with the first MLH domain rows.
Create GitHub issue: [Phase-04A] Runtime source-of-truth inventory for MLH/Dokploy/old Docker split.
Convert every future Codex task from “go fix domain” into “read the contract row, then operate only inside the declared app/container/path”.

Section 16 · Banned behavior

16. Anti-patterns banned

Phase-label theaterERP big bangSlack as databaseMagic agentsTenant-blind tasksEvidence dumpingRuntime mutation without contractFake-complete claimsCustomer sends without approvalFinance/legal automation without gate

Section 17 · Do next

17. Immediate execution backlog

FIRST: Build the Runtime Source-of-Truth map so agents stop using old nginx/Docker assumptions.
Create/upgrade master GitHub issue and task packet for this V2 plan.
Create Modern Manager MVP task packet, Slack identity, Hermes/OpenClaw routing, WhatsApp/Telegram intake policy, and Odoo/GitHub audit links.
Convert Odoo feature matrix into app-by-app skills and L0/L1/L2/L3/HOLD permission gates.
Convert Slack automation matrix into production bot scopes, commands, shortcuts, modals, events, and approval packet implementation tasks.
Commit all six research artifacts and this page.
Expand GitHub issue/PR/workflow gates to enforce evidence/task packets/runtime contracts.
Collect live VPS runtime snapshot and create RuntimeContract stubs.
Export live Odoo model/app/stage/permission matrix.
Convert Slack/Odoo operating model into production connector spec.
Create department/agent roster files from department template.
Create evidence-vault ingestion MVP against manifests/CSV ledgers only.
Update dashboard to show phase/task/runtime/Odoo/Slack/evidence status.
Only then begin approved L1/L2 draft workflows.

Updated 2026-06-05. Reality-audited V3: corrected against current GitHub/VPS/OpenClaw/Odoo/Slack state. Local artifacts exist, but GitHub remote source sync is still blocked until write/auth is repaired.

Master Operating Plan V2 / Reality-audited V3 · updated 2026-06-05 · rebuilt 2026-06-10 in the unified migration design system. Every page is public-readable, evidence-linked, and designed for both Sam and future agents. If content appears missing, compare against Git history and restore before changing style. Source: reports/migration-redesign/src/plan.html.

Viewport · migration · unified shell v1 (2026-06-10) · Data: /migration/status.json · Source: viewport-corp/viewport-os