The Agent Layer

Aria

A named agent for every vertical. Aria is the agent layer of the shared platform — CORTEX's personas, each with a job, a voice, and boundaries. The first is Fit's Aria: lead-to-cash, end to end.

Request access Meet Fit's Aria

Substrate chain

Pulse · Mesh · Synapse · Cortex · Aria · Forge

Six named systems on one runtime. Open any dock — the chain stays the same.

Loading scene

01 / 03 · Act I · The silent inbox

Fracture

An inbox nobody answers fast enough.

Every vertical buys the same stack: a CRM nobody updates, a booking flow that leaks intent at every step.

See Aria Request Access

02 / 03 · Act II · Named agents

Aria

Meet CORTEX

03 / 03 · Finale · Request

Enter

Schedule a briefing See the platform

Full cinema

01Fracture · Act I · The silent inboxWebGL

Drag to explore — or scroll

Swipe to explore

Continue into the platform.

How it Works Request Access

Lead to cash

Fit's Aria, end to end

First response
Every lead gets a reply while intent is still hot — the persona owns the lane instead of leaving the inbox silent.
Intent is hot
Book the visit
Free-session booking and confirmation run under the same identity and consent scopes as the staff console.
Visit booked
Recover the no-show
No-show and win-back follow-up stay reviewable drafts until policy says otherwise — humans keep the sensitive gates.
Win-back path
Keep the desk free
Front-desk busywork moves to a named agent with a job and an audit trail, so staff stay with members on the floor.
Audit-ready

Personas

Named jobs on the agent OS

Personas run on CORTEX

Aria is not a separate AI product. Every persona is a configured CORTEX agent — mission, tools, memory, and autonomy level included — so the workforce inherits the OS's reasoning, governance, and audit for free.

Meet CORTEX

They perceive through MCV Pulse

Personas do not work from stale exports. MCV Pulse streams the signals their jobs depend on — a lead's intent, a member drifting, a narrative forming — straight into the persona responsible for acting on them.

Meet MCV Pulse

Signal flow — schematic

First persona: Fit's Aria

In the fitness vertical, Aria already has her job description: answer every lead, book the visit, chase the no-show, win back the lapsed member, and keep the front desk free for humans. Aria answers. The club converts. You see everything.

See the Fit vertical

Persona Sigil render — Persona sigil — Aria render

The Agent Layer

Capabilities

A persona with a job, not a bot with a script

Every vertical gets a named agent persona with a defined mission — not a generic assistant. The persona owns its lane: what it handles, what it drafts, what it escalates.

Lead-to-cash, out of the box

Fit's Aria is the first persona: first response on every lead while intent is hot, free-session booking, no-show and win-back follow-up, front-desk automation. Aria turns intent into booked visits.

A voice you would put your brand on

Each persona speaks in a voice tuned to its vertical and your brand — warm but precise. Every message is reviewable, every draft approvable, until you say otherwise.

Boundaries enforced by the platform

A persona's reach is set by MCV One identity scopes and CORTEX autonomy levels — alert-only, draft-only, or limited action. Aria stays inside its job because the platform holds the line, not the prompt.

Agent templates

Named personas per vertical

Fit vertical: Fit.MembershipRetentionAgent; watches billing/contract signals, drafts save actions
Fit vertical: Fit.FranchiseOpsAgent; monitors cross-club variance and facility health
Fit vertical: Fit.LocationCoachAgent; local insights and coaching recommendations
Rest vertical: Rest.DistrictManagerAgent; portfolio consistency and divergence alerts
Rest vertical: Rest.BrandProtectionAgent; viral risk and brand-level narrative protection

All pre-wired to correct Pulse tools, vertical taxonomies, and MCV One identity scopes. The persona owns its lane: what it handles, what it drafts, what it escalates. Aria stays inside its job because the platform holds the line, not the prompt.

Named personas · Bounded by job · Runs on CORTEX

The agent layer

Problem

Software you operate, instead of a worker you delegate to

Every vertical buys the same stack: a CRM nobody updates, an inbox nobody answers fast enough, a booking flow that leaks intent at every step. The tools are fine. The problem is that they are tools — they wait for a human with time, attention, and follow-through, and those are exactly the things a growing operation runs out of first. What operators actually ask for is not another tool. It is a worker: someone who answers every lead, books the visit, chases the no-show — and does it the same way at every location, every hour, without being managed.

Solution

The agent layer: personas with jobs

Aria is the agent layer of the shared platform — CORTEX's named personas, one per vertical, each with a job, a voice, and boundaries. A persona is not a prompt or a chatbot skin. It is a configured CORTEX agent: a mission, a tool list, durable memory, an identity scope, event subscriptions, and explicit limits on what it may do — wearing a name and a voice your customers will come to know. The first persona is Fit's Aria: lead-to-cash for fitness. First response on every lead, free-session booking, no-show and win-back follow-up, front-desk automation. Aria turns intent into booked visits.

Why a persona, not a feature

Features are things your staff must remember to use. A persona is someone your customers meet. Naming the agent — giving it an identity, a voice, and a defined job — is what makes delegation legible: your team knows exactly what Aria owns, your customers know who answered them, and your audit trail knows who acted. One agent, one job, one name — then repeat per vertical.

The first persona is proof of the pattern

Fit's Aria exists because fitness has the sharpest version of the universal problem: leads arrive at all hours, intent decays in minutes, and front desks are already underwater. The same chassis — CORTEX runtime, Pulse perception, One scoping, Atlas memory — carries the next vertical's persona without rebuilding the workforce. Documented pilot engagement in fitness and hospitality is where the pattern is being proven.

Success-aligned by design

Personas are priced the way the platform is priced: success-aligned economics — performance fees or revenue share on attributed lift, so Aria earns when you do. Pilot engagements define the attribution framework and success metrics together: speed-to-first-response, booking conversion, win-back recovery — measured as targets you agree on, not numbers we assert.

How it works

Anatomy of a persona

Name the job
Start from the vertical's persona template — mission, tools, and playbooks pre-tuned — or define your own.
Give it a voice
Tune tone and phrasing to your brand; the persona speaks as your operation, warm but precise.
Set the boundaries
Identity scopes from MCV One decide what it can see; CORTEX autonomy levels decide what it can do — alert-only, draft-only, or limited action.
Put it to work
The persona perceives through MCV Pulse, acts through Fabric-connected tools, and logs everything to MCV Atlas — every message, every booking, every escalation.
Supervise, then trust
Review drafts and approvals in the CORTEX console; widen autonomy only as the evidence earns it.

FAQ

Frequently asked questions

What is Aria?

Aria is the agent layer of the MCV platform — CORTEX's named personas, one per vertical, each with a defined job, a tuned voice, and enforced boundaries. The first persona is Fit's Aria, handling lead-to-cash for fitness: first response, booking, win-back, and front-desk automation.

Is Aria a chatbot?

No. A chatbot answers messages; an Aria persona holds a job. Each persona is a configured CORTEX agent with tools, memory, event subscriptions, and autonomy limits — it acts proactively on live signals, drafts for approval where required, and escalates with evidence. Conversation is one surface, not the product.

Can we name our own persona?

Yes. Persona name, voice, and tone are configurable per deployment — Aria is the first persona in the fitness vertical, not a mandatory brand. What stays constant is the structure: every persona runs on CORTEX, perceives through MCV Pulse, and operates inside MCV One identity scopes.

What can an Aria persona actually do?

Fit's Aria shows the shape: first response on every lead while intent is hot, free-session booking, no-show and win-back follow-up, and front-desk automation across voice and messaging. Each persona acts through tools connected by Fabric, within the autonomy level — alert, draft, or limited action — that you set.

How does a persona stay on-brand and in-bounds?

Three layers. Voice is tuned to your brand and reviewed before autonomy widens. Scope is enforced by MCV One identity and consent at the platform layer, not by prompt instructions. And every action is gated by CORTEX policy — severity decides whether the persona acts, drafts, or waits for a human.

Which verticals have Aria personas today?

Fitness is first — Fit's Aria is live in the vertical's lead-to-cash story — with hospitality following; the platform has documented pilot engagement in fitness and hospitality. Each new vertical gets its own named persona on the same CORTEX chassis, rather than a rebuilt agent stack.

How is Aria different from MCV Forge?

They complement, never overlap. Aria's personas act — a named persona holds the job, with a mission, a voice, and enforced boundaries. Forge adapts the how: the dynamic workflows, training paths, and playbooks the work runs on, simulated, deployed, measured, and reforged in continuous loops.

Your next hire does not need a desk. Give your vertical a named agent with a real job — and keep the authority that makes delegation safe. Request access and meet the persona your operation has been missing.

The substrate family

Aria is one of six named systems.

Pulse senses · Mesh connects · Synapse fires · Cortex thinks · Aria acts · Forge transforms

Aria acts — the agent layer of the platform: CORTEX's named personas, one per vertical, each with a job, a voice, and enforced boundaries.

Meet CORTEX Meet MCV Forge

Operator plane · product teaser

The substrate behind the marketing surface

Every department, approval gate, and service signal across the network lands in one operator shell — the same governed record the agents act on.

Open Console Request Access

Control Room

VerticalsOpsIdentityGates

Network portfolio · live operations · service health

PROD

Verticals

Ops

Live

Identity

Gates

Green

Live streamTeaser

Network graph · healthy

Triangle identity · session live

Payments loop · live

Deploy queue · idle

Next step

Schedule a briefing for your network

Corporate buyers, multi-unit operators, and investors start with a briefing — then a vertical path that fits the portfolio. Pilot one workflow, expand on evidence.

Schedule a briefing Explore verticals

Enter Aria

Schedule a briefing Open Console

Fracture

An inbox nobody answers fast enough.

Every vertical buys the same stack: a CRM nobody updates, a booking flow that leaks intent at every step.

Aria

Enter

Capabilities

A persona with a job, not a bot with a script

Every vertical gets a named agent persona with a defined mission — not a generic assistant. The persona owns its lane: what it handles, what it drafts, what it escalates.

Lead-to-cash, out of the box

Fit's Aria is the first persona: first response on every lead while intent is hot, free-session booking, no-show and win-back follow-up, front-desk automation. Aria turns intent into booked visits.

A voice you would put your brand on

Each persona speaks in a voice tuned to its vertical and your brand — warm but precise. Every message is reviewable, every draft approvable, until you say otherwise.

Aria

Fracture

First response

Book the visit

Recover the no-show

Keep the desk free

Personas run on CORTEX

They perceive through MCV Pulse

First persona: Fit's Aria

Capabilities

A persona with a job, not a bot with a script

Lead-to-cash, out of the box

A voice you would put your brand on

Boundaries enforced by the platform

Name the job

Give it a voice

Set the boundaries

Put it to work

Supervise, then trust

The substrate behind the marketing surface

Schedule a briefing for your network

Aria

Fracture

First response

Book the visit

Recover the no-show

Keep the desk free

Personas run on CORTEX

They perceive through MCV Pulse

First persona: Fit's Aria

Capabilities

A persona with a job, not a bot with a script

Lead-to-cash, out of the box

A voice you would put your brand on

Boundaries enforced by the platform

Name the job

Give it a voice

Set the boundaries

Put it to work

Supervise, then trust

The substrate behind the marketing surface

Schedule a briefing for your network