Slack is the top approval and control layer for all Viewport entities. Every agent action that touches legal, financial, customer-facing, or destructive operations requires a Slack approval before execution. This page is generated from GitHub truth and live status.json.
These Slack channels are hardwired approval gates. No agent or human may complete a gated action without a thread approval in the correct channel.
MLH warranty and support issues. Requires an Odoo Helpdesk ticket with attached evidence before any customer-facing, legal, or financial action.
Legacy MLH issue room. Same evidence-first and approval-gate policy. All findings must be logged in Odoo before action.
Finance approval room for MLG invoices, payments, and expense records. No send, no payment, no customer-facing action before channel approval.
| Area | Slack channel / action | Odoo module | Flow |
|---|---|---|---|
| Documents | Approval thread/channel when legal or signature is needed | Documents / document folder | Document needed → Odoo document folder → Slack approval if legal/signature → sign only after approval |
| Helpdesk | mlh-warranty-support mlh-legacy-issues | Helpdesk | MLH issue → Slack issue thread → Odoo helpdesk ticket → evidence attached → agent suggests next action → approval if legal/financial/customer-facing |
| Finance | mlg-finance-review | Accounting / Invoicing / Expenses | Draft invoice/payment/expense → Slack finance review → Odoo record → approval before sending/payment/customer-facing action |
Step-by-step protocol for any gated operation. Five gates, in order — no skipping, no reordering.
Before anything is posted for approval, the action must be documented in the correct Odoo module — Helpdesk ticket, document folder, or finance record — with full evidence attached. The Slack post references the Odoo record ID and links the evidence. No record, no thread approval, no execution.
Agent or human identifies a gated action — legal, financial, customer-facing, destructive, DNS/billing, or any approval-class action.
Document in the correct Odoo module (Helpdesk ticket, document folder, or finance record) with full evidence attached.
Record-first ruleReference the Odoo record ID, describe the action, attach evidence link.
No action until a human (Sam or designated approver) replies with approval in the thread.
Hard stop · human gateComplete the action, then post the result back to the thread and update the Odoo record.
These gate classes apply to every agent and human operator regardless of channel.
Honest enforcement status — what is real today versus operating intent.
Slack channel/process mapping is visible, but full production Slack app enforcement still requires verified signing, idempotency, retries, rate limits, approval packets, and write policies. The channels and flows documented here reflect the operating intent — enforcement is being built incrementally.