MA
Sales OS

Demo seed — Metro Auto facts, not a live rooftop. Messages never send. Intelligence lists factory names; official EPA/NHTSA claims attach from Rig1.

Learn Academy

How to use Manifesto Auto OS on this rooftop. Metro Auto is the hosted demo; a real store is provisioned separately.

Included

What we offer

Products and desks on this rooftop. The Course (LearnHouse) is a separate product.

Sales OS

Pipeline board, leads, inventory SoT, approvals HITL, scoreboard

Use whenWorking the floor, managing SLA, moving inventory, approving drafts

Open Sales OS

AgentOS

In-app control room: monitor, agents, chat drafts, workflows, cron, tokens, APIs

Use whenRunning agents, scheduling jobs, reviewing HITL queue counts, checking tokens

Open AgentOS

Automotive Intelligence

Factory directory of brands, nameplates, generations, and grain rules

Use whenBriefing walkarounds, comparing official specs, or exploring model history

Open Automotive Intelligence

Listing Studio + PhotoDesk

Grounded listing copy and this-VIN photo cleanup (HITL drafts only)

Use whenCreating market listings or preparing accurate photos from lot stills

Open Listing Studio + PhotoDesk

Learn Academy

In-app solutions guide and rooftop journal of OS playbooks

Use whenLearning how the Manifesto Auto OS surfaces work together on this rooftop

Open Learn Academy

How to use it

Hosted demo vs a provisioned rooftop

Metro Auto (metro-auto) is the hosted production demo for HITL-safe walks — not a live paying rooftop and not live dealer inventory. A real store is provisioned separately with TENANT_SLUG and TENANT_NAME, the master admin attached, autoSend and autoPublish locked false, and quiet-hours enforce off until that rooftop takes night leads. White-label overlay is a layer, not a SKU. Dealer-site traffic posts to /api/webhooks/lead with x-crm-tenant set to the provisioned slug.

Using the Sales OS pipeline (stages + SLA)

Core stages follow: New Lead → Contacted → Test Drive Scheduled → Deal Pending → Sold / Delivered → Lost. Click any card on the pipeline board to open the lead detail view, attach matching inventory from SoT, add tasks, or draft first responses. Apply top filters for Due soon, At risk, and breached items while checking the dedicated scoreboard daily for compliance. Always process approvals through the HITL queue and update vehicle records as units progress.

HITL in this OS (Approvals)

Click Approvals from the Sales OS sidebar or via links in the AgentOS Monitor to load the queue. For every draft, review against inventory SoT and directory facts, edit copy or photos as needed, then approve or reject with detailed notes. Export the queue CSV regularly to track review volume and SLA adherence. Configure quiet hours in settings to auto-hold first-response drafts outside business windows.

Listing Studio + PhotoDesk in this OS

Navigate to /listings via sidebar and filter or select specific vehicles by stock. Activate Listing Studio to auto-generate copy pulled live from the unit record then refine before queuing. Run PhotoDesk jobs on the exact VIN's lot stills for scene detection and integrity checks that block invalid edits. Review all outputs as drafts in the Approvals queue prior to any publish action.

Intelligence grain in this OS

Click Directory in the sidebar to browse the official brand to nameplate to generation catalog. Filter by rooftop country settings then cross-reference specific inventory units for walkaround preparation. Use only verified OEM data in all briefings and never invent local sales figures or APRs. Export relevant subsets through the AgentOS APIs catalog for team reference or training.

AgentOS control room on this rooftop

Click the AgentOS rail in the sidebar to open the Monitor desk first and review live HITL counts, SLA cards, and next actions. Drill into the Agents tab to inspect contracts then use Chat exclusively for draft generation that queues to Approvals. Schedule recurring jobs on the Cron board knowing every execution produces reviewable drafts only. Register models at Models (credential key names only). Open Policies to see fail-closed worker-session rules. Check Tokens usage post-session and the APIs page before any external integration.

Journal

Playbooks written here. Drafts stay internal.