BossAgents Smart Enterprise Brain — Demo Video Plan

Supporting Document: HICOOL Developer Challenge · MTClaw Agent Track Proposal

Video Duration: ≤7 minutes

Demo Core: Four-scenario comparison → Proving MTClaw's high availability attribution → Continuous dialogue capability demonstration

I. Demo Overview

II. Equipment and Data Assurance

2.1 Environment Requirements

2.2 Recording Tools

3. Demo Script (5 Stages, 7 Minutes)

Stage 1: Opening Hook (≤30 Seconds)

| Time | Visual | Voiceover |

|------|------|------|

| 0:00-0:15 | Screen shows "Main Service Down" pop-up | "When traditional Agents encounter a main service crash, all capabilities are paralyzed." |

| 0:15-0:30 | Switch to BossAgents interface, responding normally | "But BossAgents, based on MTClaw, runs 100% locally and independently—even if the network is cut or the main service is down, it still works." |

Purpose: Create an impactful opening to grab the judges' attention and instantly establish the perception that 'MTClaw = High Availability'.

Phase 2: High Availability Proof (≤2 minutes)

| Time | Visual | Voiceover |

|------|------|------|

| 0:30-1:00 | Execute Scenario D (Bypass MTClaw, directly connect to port 3006), showing failure. | "Scenario D: We bypass MTClaw and connect directly to the main service—request fails." |

| 1:00-1:30 | Execute Scenario A (MTClaw + edge-side model), showing a successful response. | "Scenario A: Same hardware, same problem, processed through MTClaw—100% success." |

| 1:30-2:00 | Side-by-side comparison: Scenario D vs. Scenario A. | "The only variable is the use of MTClaw—100% vs. 0%. High availability belongs to MTClaw." |

Purpose: Reinforce the perception that 'High Availability = MTClaw's Unique Value' through visual contrast.

Phase 3: Continuous Dialogue Demo (≤3 minutes)

Four consecutive requests across different domains, demonstrating routing intelligence and perceived speed.

| Round | User Instruction | Expected Routing | Expected Response | Expected Duration |

|------|----------|----------|----------|----------|

| 1 | "Check System Health Status" | system_health_check → DS-SYS-001 | Returns database/SCSAI status |

| 2 | "Help me procure a servo motor" | procurement_assistant → DS-PROC-001 | Returns supplier price comparison results |

| 3 | "Analyze procurement cost trends for the past three months" | analytics_assistant → DS-BIZ-001 | Returns trend chart + conclusion |

| 4 | "Optimize part process" | process_optimization → DS-PROCESS-OPT-001 | Returns optimization plan + approval |

Screen Requirements:

• Overlay a real-time timer in the top-left corner of the screen
• Highlight the MTClaw routing log on each route switch
• Display the full chain: routing decision → tool invocation → result return

Purpose: Demonstrate scenario breadth across 4 different domains, real-time timer proves speed, routing log proves MTClaw intelligent scheduling.

Stage 4: Four-Scenario Comparison Report (≤1 minute)

| Time | Visual | Voiceover |

|------|------|------|

| 5:00-5:30 | Display ECharts comparison report (four-scenario bar chart) | "Full-scale testing across four scenarios: Scenario A achieved 100% success rate, while Scenario D showed 0% success rate after bypassing MTClaw." |

| 5:30-6:00 | Display comparison chart of on-device execution ratio (5.6%→75%) | "The on-device execution ratio increased from 5.6% to 75%, and response time dropped from 500ms+ to 80ms—this isn't about calling models faster, but about ensuring more tasks don't require calling a model at all." |

Objective: Use data to support the earlier experiential demonstration, turning the perception of 'fast, accurate, and decisive' into quantifiable facts.

Stage 5: Conclusion (≤30 seconds)

IV. Review Correspondence Table

V. Contingency Plan

VI. Pre-recording Checklist

• [ ] Ollama is running, deepseek-r1:8b is loaded
• [ ] MTClaw Function Router is running
• [ ] BossAgents service is running
• [ ] 43 digital employees configured, 7 new ones verified
• [ ] 4 rounds of continuous dialogue commands prepared
• [ ] OBS (screen recording) + timer overlay configured
• [ ] Narration script rehearsed ≥3 times
• [ ] Emergency pre-recorded materials prepared

VII. Video File Specifications

VIII. Strategy for Synergy Between Proposal and Demo Video

| Dimension | Proposal (PDF) | Demo Video (MP4) | Synergy Effect |

|------|----------------|----------------|----------|

| Core Proposition | Text details MTClaw high availability | On-screen comparison of Scenario A vs D | Closed evidence loop |

| Performance Data | Table shows 860 test data | Real-time timer as proof | Data made tangible |

| Scenario Coverage | List shows 43 employees | 4-domain continuous dialogue | Breadth + Depth |

| Innovation Points | Technical architecture diagram explanation | Routing log highlights | Technology made understandable |

| Product Readiness | Deployment plan description | Demo interface runs smoothly | Deliverable and credible |

Core Strategy: The proposal provides a complete evidence chain and in-depth analysis, while the demo video delivers intuitive experience and speed impact—the two complement each other, making judges "feel the solidity after reading the PDF, and feel the awe after watching the video."

Document Version: v1.0

Creation Date: July 18, 2026

Applicable Competition: HICOOL Developer Challenge · Agent Track