II.Operating Model · concept map

AVAS OS Operating Model

How the AVAS AI OS fits together: business roles, Hermes runtime profiles, boards, modes, skills, and Brain authority — one layered map.

STATIC · CONCEPT · READ-ONLY

STATICCONCEPT

How to read this

Six distinct concepts, often confused. Each answers a different question.

Business Agent

who / what business role owns the work

Runtime Profile

how Hermes safely runs the work

Board

where the work lives

Mode

what permission level is allowed

Skill

a reusable procedure

AVAS Brain

the authority / memory source

Status legendLivePlannedNeeds SOUL.mdManual onlyApproval required

Executive Layer

Phil / CEO

Final approval, business direction, pricing authority, client commitments, production approval, and memory promotion authority.

Final approvalActions end here

Core Intelligence Layer

AVAS AI OS

Company operating intelligence layer across Brain, runtime, lanes, and governance.

Live

AVAS Brain

Official knowledge base and the single source of truth. Authority over every other layer.

Live

Brain Library →

Agent Registry

Approved agents, roles, routing, and responsibility map. Documentation-only governance.

Live

Agent Workers →

Mission Control

Agent Hub — task routing visibility, workflow surfaces, board control. Displays, never decides.

Live

Mission Control →

Business Agents · Operating Lanes

Business roles — who owns and routes work. Most are documented/planned, not live runtime profiles yet.

Atlas

Company-wide routing, intake, and governance — the front door.

Live

▸ details

Runtime profile: default / root Hermes (live)

Board: Default

Mode: inspect → safe implementation w/ approval

Source: AVAS Company Roster · Agent-Routing-Rules

Open Hermes profile →

COO / Operations

Operations, service flow, delivery, handoffs, and daily execution.

Planned

▸ details

Runtime profile: coo-ops (planned)

Board: Hermes Runtime now · AVAS IT later

Mode: read-only first

Source: Profile Rollout Roadmap (Phase 2)

CFO / Accounting

Pricing, margin, MRR, billing, and financial modeling.

PlannedApproval required

▸ details

Runtime profile: cfo-billing (planned)

Board: Hermes Runtime now · Accounting/CFO later

Mode: read-only financial review

Never moves money or alters invoices — Phil approval required

Source: Profile Rollout Roadmap · invoice-sender-tracking-workflow

CISO / Security

Security, risk, compliance posture, and cyber escalation.

Planned

▸ details

Runtime profile: ciso (planned)

Board: Hermes Runtime now · AVAS IT later

Mode: read-only posture review + immediate escalation

Source: Profile Rollout Roadmap (Phase 2)

Technical / AVAS IT

Infrastructure, implementation, support, M365, RMM, backups, troubleshooting.

PlannedApproval required

▸ details

Runtime profile: technical-infra (planned)

Board: Hermes Runtime now · AVAS IT later

Mode: read first; live changes require approval

Source: Profile Rollout Roadmap · AVAS-IT-Roster · ninjaone-patch-review-sop

Quote Builder / Docs / SOWs

Proposals, quote drafts, SOWs, pricing packs, client-ready docs.

PlannedApproval required

▸ details

Runtime profile: docs-quotes-sow (planned)

Board: AVAS Brain now · AVAS Pro / Sales Pipeline later

Mode: draft-only / plan-only

Halo check before quotes · Phil approval before client-facing output

Skills: avas-proposal-builder · avas-pricing-builder

AVAS Pro / Dealer Ops

AV/project workflows, dealer support, AV system proposals.

Planned

▸ details

Runtime profile: routes via docs-quotes-sow + technical-infra (Kanban task type first)

Board: Default now · AVAS Pro later

Mode: draft / plan

Skills: avas-pro-control-blueprint · dealer-support-scope-review

Social Media / Marketing

Content, campaigns, positioning, client-safe language.

PlannedApproval required

▸ details

Runtime profile: marketing (planned)

Board: AVAS Brain now · Social Media later

Mode: draft-only — never publishes/sends

Anonymize client examples unless Phil approves

Source: Profile Rollout Roadmap (Phase 3)

Sales / Pipeline

Lead follow-up, CRM workflow, pipeline tracking, next actions.

Planned

▸ details

Runtime profile: orchestrator / docs-quotes-sow (planned)

Board: Default now · Sales Pipeline later

Mode: draft / plan

Source: crm-pipeline-lifecycle-workflow

Client Success / Support

Client communication, support coordination, service quality.

Planned

▸ details

Runtime profile: coo-ops (planned)

Board: Default / Hermes Runtime now · Support later

Mode: read-only first · approval for SLA changes

Source: ticket-escalation-sop

Memory / Brain Librarian

Brain structure, promotion queue, governance, memory candidate handling.

LiveNeeds SOUL.md

▸ details

Runtime profile: reviewer (live, SOUL.md not yet differentiated)

Board: AVAS Brain

Mode: brain-candidate-only / inspect-only

No direct Brain mutation without Phil approval

Source: Agent-Roster · promotion-lifecycle-rules

Promotion Queue →

Ops Portal Manager

Ops Portal roadmap, Lovable-exit workflow, portal requirements and QA.

LiveApproval required

▸ details

Runtime profile: ops-portal-lovable-exit-agent (live, differentiated)

Board: Ops Portal

Mode: Phil-triggered only · hard stops on prod/Supabase/deploy

Source: lovable-exit-runbook · ops-portal-agent-workspace

Open control profile →

Runtime Profiles · how work runs

Hermes execution profiles. Existing profiles live on disk under /root/.hermes/profiles.

default (root Hermes)

Main runtime — intake, Brain, VPS ops, agent coordination. The root identity.

Live

▸ details

SOUL.md: /root/.hermes/SOUL.md (root identity)

Differentiated: yes (this is the root)

Safe to assign: yes, under approval gates

Open profile →

planner

Prepares the safe daily work batch and fans out Kanban tasks.

LiveNeeds SOUL.md

▸ details

SOUL.md: /root/.hermes/profiles/planner/SOUL.md

Differentiated: NO — currently identical to root Hermes

Gap: missing explicit kanban_complete / kanban_block protocol (protocol violation history)

Action: needs SOUL.md review before safe assignment

Open profile →

reviewer

Validates planner output before anything proceeds; blocks bad batches.

LiveNeeds SOUL.md

▸ details

SOUL.md: /root/.hermes/profiles/reviewer/SOUL.md

Differentiated: NO — currently identical to root Hermes

Action: needs SOUL.md review before safe assignment

Open profile →

ops-portal-lovable-exit-agent

Controller profile for the gated Lovable-exit migration workflow.

LiveManual only

▸ details

SOUL.md: /root/.hermes/profiles/ops-portal-lovable-exit-agent/SOUL.md

Differentiated: YES — unique scoped SOUL.md

Mode: Phil-triggered only · hard stops on prod/Supabase/billing

Safe to assign: yes, within its gated workflow

Open profile →

Planned profilesnot created yet

orchestrator

Silent Kanban router; decomposes and assigns tasks. Phase 1.

Planned

docs-quotes-sow

Drafts proposals, SOWs, quotes, runbooks, Brain docs. Phase 1.

Planned

coo-ops

Halo triage, SLA risk, ops summaries. Phase 2.

Planned

technical-infra

RMM / M365 / backup remediation. Phase 2.

Planned

ciso

Security posture review and escalation. Phase 2.

Planned

compliance

Compliance prep; human review before delivery. Phase 2/3.

Planned

cfo-billing

Read-only MRR snapshots, billing gap detection. Phase 2/3.

Planned

marketing

Draft content; never publishes. Phase 3.

Planned

portal-product

Specs, Lovable prompts, GitHub issue text. Phase 4.

Planned

portal-dev

Scoped patches after approval. Phase 4.

Planned

portal-qa

AGENTS.md / mobile / schema / regression review. Phase 4.

Planned

Boards · where work lives

Default

General Hermes work, inbox, unclassified routing.

Live

Open board →

Implementation

Agent Hub v2 + Ops Portal code build tasks.

Live

Open board →

Hermes Runtime

Hermes OS maintenance: services, cron, VPS config.

Live

Open board →

AVAS Brain

Brain promotions, governance, knowledge work.

Live

Open board →

Ops Portal

Ops Portal specific work and Lovable-exit migration.

Live

Open board →

Boards are where work lives. Business Agents own/route work. Runtime Profiles execute work. Modes control what a run is allowed to do.

Modes · permission levels

Modes are permission levels, not agents.

Plan only

Produce plans and batches. No implementation, no writes.

Inspect only

Read and report. No state change of any kind.

Safe implementation

Scoped changes after approval. No commit by default.

Implementation + commit

Approved local commits with file-scoped diffs. No push/merge.

Live runtime action

Service/job/runtime actions. Highest gate — Phil approval.

Brain candidate only

Draft to inbox/promotion queue. Never mutates canonical Brain.

Example mappings

How a single task threads through all six concepts.

Quote Builder task

Business Agent: Quote Builder / Docs / SOWs
Board: AVAS Brain now · AVAS Pro or Sales Pipeline later
Runtime Profile: future docs-quotes-sow
Mode: draft-only / plan-only
Gate: Phil approval before client-facing output

CFO billing task

Business Agent: CFO / Accounting
Board: Hermes Runtime now · Accounting/CFO later
Runtime Profile: future cfo-billing
Mode: read-only financial review
Gate: Phil approval before money/billing changes

Agent Hub UI task

Business Agent: Atlas / Portal Product / Technical (by scope)
Board: Implementation
Runtime Profile: current default · future portal-dev
Mode: inspect-only first · safe implementation after approval
Gate: Phil approval before commit/merge

AVAS Brain memory graph task

Business Agent: Memory / Brain Librarian
Board: AVAS Brain
Runtime Profile: reviewer now · future avas-brain-reviewer / docs-quotes-sow if approved
Mode: brain-candidate-only / inspect-only
Gate: No direct Brain mutation without Phil approval

AVAS Brain remains authority. This page is a read-only concept map. It creates no profiles, no boards, and mutates nothing. Status reflects the 2026-06-18 agent/profile audit. See the live Operating Lane Map →